Difference between revisions of "Debug Core With Teee"
m |
|||
Line 1: | Line 1: | ||
+ | {{Admon/obsolete}} | ||
+ | |||
[[category:Debugging]][[category:NexJ Express JSON Adapter]][[category: NexJ Express Development]][[category: NexJ Express]] | [[category:Debugging]][[category:NexJ Express JSON Adapter]][[category: NexJ Express Development]][[category: NexJ Express]] | ||
Latest revision as of 19:33, 26 January 2014
Contents
Summary
In order to debug core with eclipse, the Teee server provided with NexJ Studio Express should be configured to run the core project and not its inbuilt NexJ Express Server.
Configuration Steps
Generate Scheme Server Console Debug Configuration
Enable Run Configuration Recording
- Install the NexJ Express Studio Plugin
- Close eclipse
- Enable run configuration recording
- Open the eclipse.ini for editing
- Add this line to the end:
- -DZeniBuddy=4
- Start eclipse
- Go into NexJ Studio Perspective
- window > Open Perspective > Other > NexJ Studio
- On the navigator panel, select Deployment (bottom far right)
- Create a development environment
- Select the current environment file
- Right click and select Create Copy
- Give the file a new name and click OK
- Edit Development environment file
- Open the development environment file that was created above
- For “Type”, select “Generic” from the drop down
- For “Deployment Location” enter “c:\java\container\deploy”
- Save
- Set Current Server to the Development Environment
- Add User “nexjsa”
- Click the User Management Button
- Click Add
- Type “nexjsa”
- Click OK
- Run Server Console
- Click the down arrow on the “Run Scheme console”
- Select “Server Console”
- Wait for the server to start and then Stop the Server
- Click the stop button (read button) on the console window
- Close eclipse
Disable run configuration recording
- Open eclipse.ini for debugging
- Set the ZeniBuddy flag to 1
- -DZeniBuddy=1
Configure Teee to use core project
Add Jars to Run Configuration class path
- Start eclipse
- Change to Java perspective
- Window > Open perspective > java
- Open Scheme run configuration
- Run > Debug Configurations
- Expand Java Application
- Select “Run Scheme …”
- Set logger to Debug mode
- Click the “Arguments” tab
- Under VM arguments, replace INFO with DEBUG
- Click apply
- Add jars to the classpath
- Select the “Classpath” tab
- Expand “User Entries”
- Select the entry “nexj-bootsrap.jab”
- Click the “Advanced” button
- Select “Add Classpath Variables” > OK
- Select “THIRD_PARTY” > Extend
- Expand to xerces-2_7_1/xercesImpl.jar > OK
- Repeat the above 4 steps and add the following jars in this order:
- xerces-2_7_1/xercesImpl.jar
- xalan-j_2_7_0/xalan.jar
- xalan-j_2_7_0/serializer.jar
- logging-log4j-1.2.14/dist/lib/log4j-1.2.14.jar
- junit3.8.1/junit.jar
- apache-ant-1.7.1/lib/ant-jai.jar
- **Select ECLIPSE_HOME > Extend
- plugins/com.jcraft.jsch_0.1.41.v200903070017.jar
- apache-tomcat-6.0.18/lib/catalina.jar
- apache-tomcat-6.0.18/lib/servlet-api.jar
- jca-1.5/connector-api.jar
- jta-1_1/jta-1_1-classes.zip
- ejb-2.1-api/ejb-2_1-api.jar
- jms1.1/lib/jms.jar
- javamail-1.2/mail.jar
- jaf-1.0.2/activation.jar
- apache-tomcat-6.0.18/lib/tomcat-coyote.jar
- apache-tomcat-6.0.18/lib/annotations-api.jar
- apache-tomcat-6.0.18/lib/el-api.jar
- apache-tomcat-6.0.18/lib/jasper-el.jar
- apache-tomcat-6.0.18/lib/jasper-jdt.jar
- apache-tomcat-6.0.18/lib/jasper.jar
- apache-tomcat-6.0.18/lib/jsp-api.jar
- apache-tomcat-6.0.18/lib/tomcat-dbcp.jar
- jboss-4.0.5.GA/server/all/lib/jbosssx.jar
- ** Select ECLIPSE_HOME > Extend
- plugins/com.nexj…/activemq-core-5.3.1.jar
- jboss-4.0.5.GA/lib/jboss-jmx-jar
- ** Select ECLIPSE_HOME > Extend
- plugins/com.nexj…/tomcat-juli.jar
- plugins/com.nexj…/nexj-teee.jar
- plugins/com.nexj…/commons-logging-1.0.2.jar
- plugins/com.nexj…/javax77.jar
- plugins/com.nexj…/kahadb-5.3.1.jar
- plugins/com.nexj…/nexj-express.jar
- '** Ensure that these jars are before nexj-bootstrap.jar
- Add Core project to classpath
- Select nexj-express.jar
- Click “Advanced” button
- Select “Add Folder” >
- OK
- Select “core” project folder > OK
- Click “Apply”
Add Run Scheme configuration to debug and run favorites
- Select “Common” tab
- Under “Display in favorites menu”
- Select Debug
- Select Run
- Click Apply
- Debug Core build in Studio
- Click “Debug” button