• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Getting started - env issues

 
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hey Guys,

I'm starting to study for the SCBCD certification and I'm getting really bored when building my test cases with Eclipse+JBOSS.

The problem is that every time I make a change in the JSP (even a small one) Eclipse redeploys the entire WAR to JBOSS... And that takes a considerable time to reload...

Is there a way to avoid this WAR redeploy? I'm not hoping to avoid that with my EJBs, however, I thought there would be something faster for the JSP changes... How do you guys deal with this issue?

Thanks a lot,
Wagner
[ November 21, 2007: Message edited by: Wagner Danda ]
 
Ranch Hand
Posts: 226
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What about if you tell Eclipse to deploy in an exploded fashion.

If compressed into a single WAR, the container probably notices the timestamp change and simply reloaded the app.
If exploded into a directory, perhaps the container will just reload that file.

P.S. I'm new to EJB, so sorry if this sounds a little naive.
 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Danda,

\server\default\tmp\deploy\

I deal woth this by apcking my app to an ear file, and above is a place where Jboss put tmp application file, you could copy and paste your changed jsp directly to that folder. (your application name will be tmpxxxxYOUR_APLLICATION_NAME.ear)
 
Wagner Danda Da Silva Filho
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Mark Garland:
What about if you tell Eclipse to deploy in an exploded fashion.

If compressed into a single WAR, the container probably notices the timestamp change and simply reloaded the app.
If exploded into a directory, perhaps the container will just reload that file.

P.S. I'm new to EJB, so sorry if this sounds a little naive.



Thanks Mark. My question then would be: where should I place my JSPs and EJB classes?
 
Wagner Danda Da Silva Filho
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Nguyen Long:
Dear Danda,

\server\default\tmp\deploy\

I deal woth this by apcking my app to an ear file, and above is a place where Jboss put tmp application file, you could copy and paste your changed jsp directly to that folder. (your application name will be tmpxxxxYOUR_APLLICATION_NAME.ear)



Thanks Nguyen. I understand your suggestion but I was expecting something more automated from Eclipse... What I expect to see is once I clicked "Save" in either a JSP (or a Java class) they would get automatically uploaded to JBOSS (I think this is called hot-swap).

Currently when I change a jsp or a java class Eclipse notice that and redeploy the two projects: an WAR file for the web project and a JAR file for the EJB. I've already tried creating an Enteprise Project that wrap the two projects and creates a EAR file, but the behavior is the same: redeployment of the whole project for any simple change (ie. change a comment in a log)! That really slows my tests...
 
reply
    Bookmark Topic Watch Topic
  • New Topic