Please create a JIRA as a blocker for 1.3 .. we gotta fix this!
Gertjan, thanks for persisting and letting us know the details to
reproduce the error!
Sanjiva.
Charitha Kankanamge wrote:
Hi Gertjan,
Seems there is a problem with hotupdate when service archive is
exploded. I was able to reproduce the issue by setting hotupdate=true.
regards
Charitha
Gertjan van Oosten wrote:
As quoted from Charitha Kankanamge <[EMAIL PROTECTED]>:
I unpacked version-1.3-RC2.aar which comes with Axis2 and restarted
tomcat (I was running tomcat 6.0.10). I did not get such an error.
As quoted from Deepal jayasinghe <[EMAIL PROTECTED]>:
I did the same thing and it worked for me as well.
I'm under Tomcat 5.5.17. One maybe important issue is that I have set
<parameter name="hotupdate">true</parameter>
in axis2.xml. Try that and see if it keeps undeploying and deploying
for you as well. Happens to me every 10 seconds, like I said.
You will definitely get the following exception if both unpacked aar
and version-*.aar are placed in the WEB-INF/services directory.
Probably you haven't removed one of them.
No, I have removed the .aar, of course.
Kind regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
