[bobcoss]

Can you provide me with any insight as to how to proceed past a problem with deployment.

Environment:

ME Beta 2
Eclilpse 3.2
Weblogic 8.1 SP3

I followed the web service example in the help documentation exactly except for selecting J2EE 1.3 (because weblogic 8.1 doesn’t support J2EE 1.4) and deployed to the weblogic server instead of to tomcat like done in the example.

I’m getting an error:

<BEA-101216> <Servlet: “XFireServlet” failed to preload on startup in Web application: “HelloWorld”.
javax.servlet.ServletException: Error initializing XFireServlet.

Can you provide me with any tips on getting started?

Thank you.

Bob Coss

[bobcoss]

I found the solution… Check out http://xfire.codehaus.org/XFire+on+Weblogic+8.1

It seems that weblogic.jar has an old avax.xml.namespace.QName and xfire needs a newer one. This url provides a link to a new one, and the changes needed to the weblogic.xml to cause the library file to override the jar file.

I hope this helps someone else

Bob Coss

[Riyad Kalla]

Bob,
Thank you for following up, I am going to mark this thread sticky for others.

[fratelic]

is it the same for weblogic 9.2?

[Darrin Tisdale]

I found that on both WAS 6 and WAS 5.X, the QName jar was required.

[fabriziotarara]

I have tried exactly what this solution states with no luck. Has anyone else ran into this and gotten the same problem? If there is another solution to this project please let me know.

Fabrizio

[tomeksz]

Sometimes helps to put qname.jar at beginning of WLS classpath ( in startweblogic script ).
Not sure if its the best and most elegant solution, but works for me.

[tomeksz]

Solution for WLS 9.2
http://forums.bea.com/bea/message.jspa?messageID=400003454&tstart=40

[ojojoj]

> Sometimes helps to put qname.jar at beginning of WLS classpath

Yep. That works for me, but I’m worried – Does anyone know the consequences of replacing qname this way?

OJ

[tomeksz]

There should be no consequences, API should be backward compatible

[ojojoj]

@tomeksz wrote:

There should be no consequences, API should be backward compatible

Just completed a BEA support case. According to BEA putting qname.jar in the beginning of the WLS classpath is safe, and may be the only way to get XFire running (with Spring) on WL8.1 + java 1.4.x. They mentioned they were working on a patch as well.

[Riyad Kalla]

Thank you for posting with that information ojojoj

[Author]

Posts