• 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

URGENT - Classes

 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We are working on Websphere3.5 on Solaris2.7. On developement environment during integration of modules everytime theres a change in the class file (for eg a DAO or VO) that my jsp is calling, we have to restart the server. Cant this be avoided on WAS3.5, so as if theres a change in the class file, I dont have to start the Server again. (As is the case with jsp's).
Thanks in advance
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Actually, if you're just developing with Servlets, JSP's and JavaBeans (not EJB's) at most you only have to restart the webapp -- not the entire application server. What you need to do is read in the InfoCenter about the reloadable servlet classpath -- any new or updated classes or jar files placed on this classpath (set during configuration of the web app) will cause an automatic restart of the webapp.

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
 
Kavita Saluja
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The problem is that we have three application servers running under one node. Each App Server has a its own classpath set on the commandline and only one web application. We have just one servlet i.e the Front Controller catering to all the requests which is under the servlets directory (which also has the core components). Parallel to the servlet directory there is a classes directory in which we have all of our DAO's and VO's (i.e utility classes). Now everytime we make a change in any utility class we have to restart the server.
I wasnt able to find any information regarding this in the infocentre.
Can you please help?
Thanks in advance
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Kavita Saluja:
The problem is that we have three application servers running under one node. Each App Server has a its own classpath set on the commandline and only one web application. We have just one servlet i.e the Front Controller catering to all the requests which is under the servlets directory (which also has the core components). Parallel to the servlet directory there is a classes directory in which we have all of our DAO's and VO's (i.e utility classes). Now everytime we make a change in any utility class we have to restart the server.
I wasnt able to find any information regarding this in the infocentre.
Can you please help?
Thanks in advance


What it comes down to is you're not using the classpaths right. First of all, don't put your classes in the directories that descend down from the application server installation directory. Create your own directory structure separate from the WebSphere installation. In a simple servlet/JSP application you should never have a reason to use the classpath from the command line. You should be able to put everything on the web app classpath that is set in the Advanced Tab of the Web Application configuration page. That classpath is the one that is reloadable. If you put everything there, all you will have to do is restart the web app at the most, as I have mentioned earlier. Carefully read section 6.3.1 of the WebSphere AE 3.5 InfoCenter.

------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
 
reply
    Bookmark Topic Watch Topic
  • New Topic