MyEclipse Forums
This thread has been locked & this forum has been archived.
Please post new topics to Java EE Development (EJB, JSP, Struts, XDoclet, etc.)
View previous topic Printable version Log in to check your private messages View next topic
Author Message
bobcoss
Post subject: Web Service Error initializing XFireServlet on WebLogic  PostPosted: Jul 11, 2006 - 01:55 PM
Registered Member
Registered Member


Joined: Aug 04, 2005
Posts: 35

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
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
bobcoss
Post subject:   PostPosted: Jul 11, 2006 - 05:26 PM
Registered Member
Registered Member


Joined: Aug 04, 2005
Posts: 35

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
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
support-rkalla
Post subject:   PostPosted: Jul 11, 2006 - 06:41 PM
Registered Member
Registered Member


Joined: Jan 06, 2004
Posts: 23818

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

_________________
Riyad
MyEclipse Support
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
fratelic
Post subject:   PostPosted: Oct 10, 2006 - 07:21 AM



Joined: Oct 09, 2006
Posts: 11

is it the same for weblogic 9.2?
 
 View user's profile Send private message  
Reply with quote Back to top
tizzyd
Post subject: Same goes for WebSphere  PostPosted: Oct 25, 2006 - 08:15 PM
Registered Member
Registered Member


Joined: Jun 25, 2006
Posts: 1

I found that on both WAS 6 and WAS 5.X, the QName jar was required.
 
 View user's profile Send private message  
Reply with quote Back to top
fabriziotarara
Post subject: Does this really work???  PostPosted: Nov 17, 2006 - 10:31 PM



Joined: Aug 18, 2006
Posts: 2

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
 
 View user's profile Send private message  
Reply with quote Back to top
tomeksz
Post subject:   PostPosted: Mar 05, 2007 - 10:40 AM
Registered Member
Registered Member


Joined: Feb 27, 2007
Posts: 88

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.
 
 View user's profile Send private message  
Reply with quote Back to top
tomeksz
Post subject:   PostPosted: Mar 05, 2007 - 10:44 AM
Registered Member
Registered Member


Joined: Feb 27, 2007
Posts: 88

 
 View user's profile Send private message  
Reply with quote Back to top
ojojoj
Post subject:   PostPosted: Mar 19, 2007 - 09:25 AM



Joined: Mar 19, 2007
Posts: 2

> 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
 
 View user's profile Send private message  
Reply with quote Back to top
tomeksz
Post subject:   PostPosted: Mar 19, 2007 - 12:49 PM
Registered Member
Registered Member


Joined: Feb 27, 2007
Posts: 88

There should be no consequences, API should be backward compatible
 
 View user's profile Send private message  
Reply with quote Back to top
ojojoj
Post subject:   PostPosted: Mar 21, 2007 - 01:35 PM



Joined: Mar 19, 2007
Posts: 2

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.
 
 View user's profile Send private message  
Reply with quote Back to top
support-rkalla
Post subject:   PostPosted: Mar 26, 2007 - 04:12 PM
Registered Member
Registered Member


Joined: Jan 06, 2004
Posts: 23818

Thank you for posting with that information ojojoj

_________________
Riyad
MyEclipse Support
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 6 Hours
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.
View previous topic Printable version Log in to check your private messages View next topic
Powered by PNphpBB2 © 2003-2004 The PNphpBB Group
Credits