Thanks, I'll give that a try!
On 8/3/07, keith chapman <[EMAIL PROTECTED]> wrote:
>
> Yes, xml beans creates some classes in the resources directory which need
> to be in the class path. You can create a jar out of them and add it to your
> clasapath. Its how xmlBeans work.
>
> BTW did you try AD
Yes, xml beans creates some classes in the resources directory which need to
be in the class path. You can create a jar out of them and add it to your
clasapath. Its how xmlBeans work.
BTW did you try ADB? its much simpler than xml beans, although xmlbeans have
full schema support.
Thanks,
Keith.
Hi,
Try adding the "resources" directory which contains some generated artifacts
to the classpath. It is at the same level as the "src" directory.
Upul
On 8/4/07, New AxisU <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I am using axis2 1.3 RC2 (maybe I'll try RC3 while waiting for an answer)
> ...
something alternative.
Thanks,
Swavek
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 26, 2007 8:03 PM
To: axis-user@ws.apache.org
Subject: Re: Classpath Problem with Weblogic 8.1 JMS Server
Good Evening Swavek-
com/sun/corba/se/connection/ORBSocketFactory is in
From: Chad DeBauch [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 26, 2007 7:23 AM
To: axis-user@ws.apache.org
Subject: Re: Classpath Problem
I am not familiar with Weblogic. From reading the discussions I believe
there have been some issues in the past with Axis2 and Weblogic
@ws.apache.org
Subject: Re: Classpath Problem
I am not familiar with Weblogic. From reading the discussions I believe
there have been some issues in the past with Axis2 and Weblogic. Perhaps
there is someone else in the group that has had this issue and can respond.
Sorry,
Chad
On 6/26/07
had DeBauch [mailto:[EMAIL PROTECTED]
*Sent:* Monday, June 25, 2007 7:42 PM
*To:* axis-user@ws.apache.org
*Subject:* Re: Classpath Problem
You should keep the third party jars with the aar file and tackle the
problem from that angle. The jars in the WEB-INF/lib directory will be
loaded first so y
Chad DeBauch [mailto:[EMAIL PROTECTED]
Sent: Monday, June 25, 2007 7:42 PM
To: axis-user@ws.apache.org
Subject: Re: Classpath Problem
You should keep the third party jars with the aar file and tackle the
problem from that angle. The jars in the WEB-INF/lib directory will be
loaded first so you may
You should keep the third party jars with the aar file and tackle the
problem from that angle. The jars in the WEB-INF/lib directory will be
loaded first so you may have conflicts with the jars that you have in your
aar or in the jars that Tomcat loads. That is why you may be getting the
class n
