|
|
|
Please see:
http://archive.xfire.codehaus.org/user/msg01534.html Does that help? That fix worked for us. However I'm curious what the root cause of the issue is. We had 2 installations of websphere on 2 different machines. On the one we could deploy it with no problems and on the other we couldn't without the above fix. We haven't been able to determine what the difference was between the two.
The issue, from what I can tell, is that there is an old version of JDOM somewhere around. Does WebSphere use JDOM?
Yep, that's it.
WebSphere/AppServer/lib contains a copy of JDOM Beta 7. Replaced it with JDOM 1.0 and everything started up just fine. Thanks for your help and quick response! =P Correct. It works fine when the JDOM package in WebSphere/AppServer/lib was replaced by JDOM 1.0.
Your promptness in resolving the issue is impressive. Shahid The documentation could be updated with this platform specific issue:
In WebSphere environment, check if the AppServer/lib contains the latest version of JDOM (at least 1.0). If not, replace the current JDOM package with JDOM 1.0 (or higher). Is correct!!!
It's works! Thanks!! |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WebSphere Application Server 6.0.2.7
Spring 1.2.6
Xfire 1.0
Works fine in JBoss 4.0.1, though, so it looks to be WAS6 related.