Debugging test generated by Sun ONE Connector Builder
Is it possible to make Sun ONE Studio 4 stop execution on breakpoints set in the test generated by the Sun ONE Connector Builder? These are the steps I have followed in an attempt to do so:
1. Configured the J2EESDK 1.4 RI Application Server to listen on port 1044 for debugging connections.
2. Restarted the Application Server for the changes to take effect.
3. Configured Sun ONE Studio 4 to attach to the Application Server. In the Debug menu, in the Attach option:
- Debugger Type: Default Debugger (JPDA)
- Transport: dt_socket
- Host: localhost
- Port: 1044
4. In the Output Window, made sure "Connection established" appeared.
5. Set breakpoints in my Connector test.
6. In the Debugger Window, made sure the breakpoints appeared in the correct frame.
7. Ran the following command:
# /usr/local/s1studio/connector/bin/ictstclnt -i \
/path/to/Connectorrun.properties
8. Checked the output log which indeed ran the test where I set breakpoints.
After all this, Sun ONE Studio 4 still doesn't stop execution where I set breakpoints. So is it even possible to debug the test generated by the Sun ONE Connector Builder?
[1232 byte] By [
MarcTardif] at [2007-11-25 10:39:57]
Hi,
Are you using the default connectores that are bundled with the Product i.e COTS and DBMS? and adding new test cases to the existing test cases?
Or are you generating new connectors for a new backend system?
When you say that you are generating new test cases have you build them using the connector builder product and pacakged in the directory structure,so that they get are a part of the rar archive. Please refer to the developers guide to get more details to add your new test cases.
The test cases get bundled with the resource adapter and you need to deploy it in the Application server just like any other j2ee component.
What i could make from your description was that you have added debug statements to the test cases and they are bundled with the resource adapter now.
The test vehicle which call these test case are in the form of a servlet packaged as a war archive , which needs to be deployed too on the ap server.
The client program will call this servlet and this client program is being called from the ictstclnt script. This is what you are invoking from the usr/local/s1studio/connector/bin/. The logs will appear since you are running the test client as a seperate entity using the command line tool. If you start the test client from the Studio itself just like a standalone java program then you can stop at the breakpoints. This would require setting of the classpath with the testclient runtime classes. We have not made those classes publicaly available and that is why we call them from the scripts. Hence you cannot do it calling it through the script.
If you can debug any j2ee component(deployed in app server) through Studio you should be able to debug the resource adapter test classes packaged with the resource adapter archive(subjected to the mentioned constraint).
Thx
