Prerequisites
You will have to successfully obtain the dcm4jboss-all collection of dcm4chee modules from CVS:
cvs -d:pserver:anonymous@dcm4che.cvs.sourceforge.net:/cvsroot/dcm4che login cvs -z3 -d:pserver:anonymous@dcm4che.cvs.sourceforge.net:/cvsroot/dcm4che co -P dcm4jboss-all
Once you have done that, you need to build the software. At this point you're ready to start setting things up Eclipse.
Importing dcm4chee projects into Eclipse
1: Prep the workspace
It is recommended that you have an Eclipse workspace dedicated to dcm4che, since dcm4che may have different JVM and code formatting settings, as well as different classpath variables than your other projects.
Assuming you are starting with a clean workspace, import the code formatting settings from this wiki. Download the Eclipse settings (java-conventions-without-tabs.xml) which are attached to the Coding Standards page. In Eclipse, click on Windows, Preferences, and then navigate to the Java/Code Style/Formatter section. Click on Import, and select the java-conventions-without-tabs.xml file. Click on OK to make these your active formatting settings.
2: Set up classpath variables
Set up the following classpath variables within Eclipse. Click on Windows, Preferences, and then navigate to the Java/Build Path/Classpath Variables section.
Variable Name |
Path |
|---|---|
JBOSS_HOME |
The path to the root directory of your JBoss 4.0.5 GA installation. For example; |
FOP_HOME |
The path to the root directory of your FOP installation. For example; |
CACTUS_HOME |
The path to the root directory of your Cactus (J2EE testing framework) installation. For example; |
3: Import the dcm4chee projects
Click on File, Import, select Existing Projects into Workspace, and then click Next. With the "Select root directory" radio button selected, click on Browse, and then navigate to your dcm4jboss-all directory. Select this directory, and click OK. You should see the list box populated with the nine core dcm4chee projects. Click on the Finish button.
Running dcm4chee from within Eclipse
Option 1: Remote debugging of a local installation
To enable remote debugging you have to edit your run.conf file an JBOSS_HOME/bin/ and uncomment/add following line:
# Sample JPDA settings for remote socket debuging
JAVA_OPTS="$JAVA_OPTS -Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y"
This will enable java remote debugging on port 8787. Now you have to setup a new remote debugging session in Eclipse. This can be done via: Run -> Debug: Select Remote Java Application and press the "New launch configuration" button.
Choose dcm4jboss-sar as Project, set the connection properties port to 8787 and add on the Source tab all dcm4jboss projects. After hitting the Debug button the JBoss server will startup and you can start debugging.
Option 2: Launch dcm4chee from within Eclipse
This page has been viewed
zero
times.