[innova]

I have a problem with Tomcat hot deployment and xfire.

In the past the situation was:
If I changed a jsp file, it was deployed to Tomcat 5.5 immediatelly WITHOUT reloading the context.

Now I’ve added a xfire webservice to my web project.
If i change a jsp file, it is deployed to Tomcat immediatelly, BUT Tomcat is reloading the context.

If I disable the xfire Builder in my project properties, everything works like before (except what the xfire builder is doing).

Any solution?
What is the xfire builder doing in detail?
Copying the services.xml to META-INF\xfire?

Matthias

[Riyad Kalla]

Matthias,
This is certainly strange… the only thing that would cause a Tomcat reload is a class file change *or* your web.xml file getting “touched”… can you try and change a JSP and see if your web.xml file is getting touched (check the timestamp)… this would be strange, but I’m not sure all of what the xfire builder does.

[innova]

Riyad,

I’ve checked the timestamps of all files in my Tomcat webapp directory. Only 2 files have a new timestamp. The changed jsp file itself and the WEB-INF\classes\META-INF\xfire\services.xml
If I change the services.xml by hand Tomcat is reloading the context, too.

Matthias

[Riyad Kalla]

Matthias, I see… looks like the builder may be touching that file on deploy. I’ll file a report to look into this.

[Riyad Kalla]

We confirmed this and are looking into it, thank you for bringing this to our attention.

Management just targetted it for our M2 release.

[Riyad Kalla]

This bug has been fixed on an internal build now. Should be part of our 5.5M2 release here in another week or so.

[Author]

Posts