Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
  - Korean
  - Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
  - Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in
UserPreferences


Referenced by
AppFuseDebug
AppFuseSupport
Articles
Articles_cn
Articles_de
Articles_ko
Articles_pt
Articles_zh
DevelopmentEnvironme...
DevelopmentEnvironme...
...and 1 more




JSPWiki v2.2.33

[RSS]


Hide Menu

AppFuseEclipse


Difference between version 28 and version 27:

At line 15 changed 1 line.
Open Eclipse (either with an existing or a new workspace) and to go File → Import... and select
Open Eclipse (either with an existing or a new workspace) and to go File → Import..., select ''Existing Project into Workspace'' and click ''Next >''. Enter the pathname to the directory of your project or click the Browse... button and select the directory. Click the Finish button. Eclipse will load and build the project. At this point you'll probably have 2 Problems complaining that it can't build your project due to an ''Unbound classpath variable''. You'll correct this in the next step.
At line 19 changed 1 line.
''Stay tuned while I finish putting this section back in. I had it all ready to go but the Wiki's Save button at the bottom of the Preview page seems to have lost much of the info.''
Go to Window → Preferences. Navigate to Java → Classpath Variables. Click the New... button and enter J2EE_HOME for the name field. In the path field enter the pathname to the directory of your J2EE JDK or click the Folder.. button and select the directory. Click on OK one or more times to return to the main Eclipse window. Eclipse will now rebuild your project and the Unbound class variable problem should be gone.
At line 22 changed 1 line.
Adding junit.jar to Ant's classpath is pretty easy. Open Eclipse and go to Window ? Preferences. Navigate to Ant ? Runtime and you should a window similar to the one below.
Adding junit.jar to Ant's classpath is pretty easy. Open Eclipse and go to Window → Preferences. Navigate to Ant → Runtime and you should a window similar to the one below.
At line 31 changed 1 line.
Now we need to add the build.xml to Eclipse's Ant View. To do this, go to Window ? Show View ? Ant. Then click on the first icon in this view (screenshot below) to add AppFuse's build file.
Now we need to add the build.xml to Eclipse's Ant View. To do this, go to Window → Show View → Ant. Then click on the first icon in this view (screenshot below) to add AppFuse's build file.
At line 41 changed 1 line.
It's also possible to run your JUnit tests in Eclipse. I should note that if you're running an ActionTest, you'll need to execute "ant deploy-test-war" and then start Tomcat before running them. To configure Eclipse to run AppFuse's JUnit Tests, all you need to do is define a J2EE_HOME variable. To do this, go to Window ? Preferences ? Java ? Classpath Variables. Add a new variable called J2EE_HOME and point it to the location where you have the [J2EE SDK|http://java.sun.com/j2ee/download.html#sdk] installed. AppFuse already has its classpath configured (in the .classpath file) to include J2EE_HOME/lib/j2ee.jar.
It's also possible to run your JUnit tests in Eclipse. I should note that if you're running an ActionTest, you'll need to execute "ant deploy-test-war" and then start Tomcat before running them. To configure Eclipse to run AppFuse's JUnit Tests, all you need to do is define a J2EE_HOME variable. To do this, go to Window → Preferences → Java → Classpath Variables. Add a new variable called J2EE_HOME and point it to the location where you have the [J2EE SDK|http://java.sun.com/j2ee/download.html#sdk] installed. AppFuse already has its classpath configured (in the .classpath file) to include J2EE_HOME/lib/j2ee.jar.
At line 43 changed 1 line.
Open a test you'd like to run (i.e. UserDaoTest) and go to Run ? Debug As ? JUnit Test. If this doesn't work, make sure you have AppFuse 1.0.1+
Open a test you'd like to run (i.e. UserDaoTest) and go to Run → Debug As → JUnit Test. If this doesn't work, make sure you have AppFuse 1.0.1+
At line 46 changed 2 lines.
For debugging, I use the Tomcat Plugin in Eclipse and set breakpoints. For little changes, I use "ant deploy-web" which only takes a couple of seconds. For truly minor tweaks, it's sometimes easier to edit the file in Tomcat's webapps folder. For major design changes, I usually run the app, view source on a page and save it to a "sandbox" folder in the same directory as my project. Then I do a find/replace and change all "/appfuse/" references to "../web/". This allows me to change CSS and
JS files and just refresh the file in the sandbox.
For debugging, I use the Tomcat Plugin in Eclipse and set breakpoints. For little changes, I use "ant deploy-web" which only takes a couple of seconds. For truly minor tweaks, it's sometimes easier to edit the file in Tomcat's webapps folder. For major design changes, I usually run the app, view source on a page and save it to a "sandbox" folder in the same directory as my project. Then I do a find/replace and change all "/appfuse/" references to "../web/". This allows me to change CSS and JS files and just refresh the file in the sandbox.

Back to AppFuseEclipse, or to the Page History.