I am running XFire 1.2 on WAS 6.0. I had to set following jars in JVM classpath 
to get it working.

jaxen.jar (1.1 B7)
jdom-1.0.jar
wsdl4j-1.5.2.jar (Need this to get WSDL).

Note: I haven't changed default classloader policies.


________________________________
From: Venkat G [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 11, 2007 11:15 AM
To: [email protected]
Subject: Re: [xfire-user] Error initializing Xfire servlet in websphere 6.0

Hi Tomek,

  Thanks for your prompt response.
   but the issue is still not resolved after following steps in 
http://xfire.codehaus.org
/WebSphere+6.x link


Regards
Venkat


On 9/11/07, Tomek Sztelak <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote:
http://xfire.codehaus.org/WebSphere+6.x

On 9/11/07, Venkat G <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
> I am getting error initializing xfire servlet in WAS 6.0
>
> Please let me know how to resolve the issue. How can I make WAS use JDOM1..0
>
> Regards
> Venkat
>


--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email




-----------------------------------------
Note:  The information contained in this email and in any
attachments is intended only for the person or entity to which it
is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use
of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.  The recipient should check this email and any
attachments for the presence of viruses.  Sender accepts no
liability for any damages caused by any virus transmitted by this
email. If you have received this email in error, please notify us
immediately by replying to the message and delete the email from
your computer.  This e-mail is and any response to it will be
unencrypted and, therefore, potentially unsecure.  Thank you.  NOVA
Information Systems, Inc.

Reply via email to