History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XFIRE-286
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dan Diephouse
Reporter: Shahid Ahmed
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
XFire

Error creating bean with name 'xfire.typeMappingRegistry'

Created: 28/Feb/06 11:09 AM   Updated: 16/Dec/06 06:42 PM
Component/s: Spring
Affects Version/s: 1.0
Fix Version/s: 1.0

Time Tracking:
Not Specified

File Attachments: 1. Text File xfire-bug-1.txt (14 kb)

Environment:
WebSphere Platform 6.0
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.4.2 IBM Windows 32 build cn142sr1w-20041028 (JIT enabled: jitc),
Java VM name = Classic VM

activation-1.0.2.jar
commons-codec-1.3.jar
commons-httpclient-3.0.jar
commons-logging-1.0.4.jar
jdom-1.0.jar
mail-1.3.3_01.jar
spring-1.2.6.jar
stax-api-1.0.jar
stax-utils-snapshot-20040917.jar
txt
wsdl4j-1.5.2.jar
wstx-asl-2.9.jar
xbean-spring-2.2.jar
xfire-all-1.0.jar




 Description  « Hide
Simple service that returns the input String fails. The log shows:
[2/28/06 11:12:49:748 EST] 00000032 XFireServlet E Error initializing XFireServlet.
[2/28/06 11:12:49:758 EST] 00000032 XFireServlet E TRAS0014I: The following exception was logged org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xfire.typeMappingRegistry' defined in class path resource [org/codehaus/xfire/spring/xfire.xml]: Initialization of bean failed; nested exception is java.lang.VerifyError: (class: org/codehaus/xfire/aegis/type/basic/ObjectType, method: writeSchema signature: (Lorg/jdom/Element;)V) Incompatible argument to method
java.lang.VerifyError: (class: org/codehaus/xfire/aegis/type/basic/ObjectType, method: writeSchema signature: (Lorg/jdom/Element;)V) Incompatible argument to method
at org.codehaus.xfire.aegis.type.DefaultTypeMappingRegistry.createDefaultMappings(DefaultTypeMappingRegistry.java:294)

A complete log is attached.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Per Hammer - 16/Mar/06 11:37 AM
Yep, seeing the same thing here.

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.


Dan Diephouse - 16/Mar/06 02:26 PM

Mike Youngstrom - 16/Mar/06 05:03 PM
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.

Dan Diephouse - 16/Mar/06 11:09 PM
The issue, from what I can tell, is that there is an old version of JDOM somewhere around. Does WebSphere use JDOM?

Per Hammer - 17/Mar/06 03:46 AM
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


Shahid Ahmed - 17/Mar/06 01:42 PM
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


Shahid Ahmed - 17/Mar/06 01:47 PM
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).


Vladimir Aguirre Piedragil - 16/Dec/06 06:42 PM
Is correct!!!
It's works!
Thanks!!