• 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

Update class file w/out deploying ear

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am currently running WAS 4 Adv. Single Server and am wondering if there is a way to update a class file without deploying a new ear. The reason I ask this is because the ear takes forever to load and during this time the server has to be down. I would like to just deploy a class file directly to the installedApps directory, but when I do that it is not being recognized as new. Any tips/thoughts would be really appreciated.
Thanks.
 
Ranch Hand
Posts: 178
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I use WAS 4.0.3 Advanced Edition, not single server. When I need to deploy a new class file, I simply FTP it to the WEB-INF/classes/<package name> directory under the installedApps directory (IBM calls this hot deployment). Then you need to stop and start the app server to allow the new class file to be recognized. This should do this trick...
 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Well if u are copying the class file in WEB-INF\classes folder and u have checked the option of reloading enabled(u can mention this at the time of deployment) than u dont need to restart the app server again to reload this class.This is true for web modules.
For ejb module, if u are modiying the jar by replacing the new class file than u have to restart the app server for it to get loaded.
Hot deployment is when u have to only restart the ejb module(for making the changes to reflect) in which u have changed the class file and not the whole appserver.
Regards,
-R
 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If there are no interface changes you can simply make a jar with your new classes. Add it to the classpath (in the beginning) and restart.
Its a good way if you want to put in a framework for updates.
reply
    Bookmark Topic Watch Topic
  • New Topic