facebook

Help with hotcode replace using tomcat. [Closed]

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #200356 Reply

    hudsonc
    Member

    Hi,

    I’m using the latest eclipse + myeclipse. I have a J2EE project using servlets and jsp. I’m currently testing on tomcat 4.1.24 as 27 is broken and 29 does not work with my eclipse 🙂 . The problem I have is that I can debug servlets but not jsp, If I make any changes to the jsp this is not reflected in tomcat and if I make changes to servlets or java beans then the application is restarted. I have had eclipse with lomboz working so that I can change code in servlets and it is reflected straight away. even when debugging.. So my question is.

    How do I get this functionality in my eclipse?

    Apart from that I think myelipse is great!

    #200360 Reply

    support-michael
    Keymaster

    The issue is that MyEclipse JSP debugging facilities require a web container to support the JSR045 spec. Consider upgrading your development environment with a Tomcat5 instance for JSP debugging.

    Happy Thanksgiving!

    Michael
    MyEclipse Support

    #200374 Reply

    hudsonc
    Member

    @support wrote:

    The issue is that MyEclipse JSP debugging facilities require a web container to support the JSR045 spec. Consider upgrading your development environment with a Tomcat5 instance for JSP debugging.

    Happy Thanksgiving!

    Michael
    MyEclipse Support

    Thanks.. if I use tomcat 5 then the hot code will work correctly? or will it sill reload the entire application? I’m not that fussed about jsp debuging as I have al little scipting as possible in the jsp.

    #200377 Reply

    support-michael
    Keymaster

    If Tomcat is configured to reload classes (the default) and your project is deployed in exploded format then sync-on-demand will update your server’s deploy location with modified resources resulting in the class being reloaded by the server. This approach has the benefit of allowing classes with shape changes (e.g., add/remove method or field) to be reloadable while JPDA-based hot-swap class reloading is limited to class changes that do not modify the shape of a class.

    If you desire exclusive hot-swap class reloading and don’t care about keeping the server and project in sync then deploying in packaged format will provide the effect.

    Michael
    MyEclipse Support

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Help with hotcode replace using tomcat. [Closed]

You must be logged in to post in the forum log in