e full stack trace of the root cause is
> available in the Apache Tomcat/5.0.27 logs. noshade="noshade">Apache Tomcat/5.0.27
>
> *END OF RESPONSE
>
> Thanks in advance,
> Jayachandra
>
>
>
> On Thu, 16 Sep 2004 16:48:41 +0530, jayachandra <
Title: Message
done
http://nagoya.apache.org/jira/browse/AXIS-1683
done
with bea too (only for
IncompatibleClassChangeError with weblogic with
1.2-RC1)
stack produce witch changes in MessageElement.java
(line
1388)
got exception when calling Document.createTextNode(String)
with object of
> De : Olivier Lamy [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 19 novembre 2004 11:02
> À : Axis-User
> Objet : EntityResolver trouble in 1.2-RC2 and IncompatibleClassChangeError
> with weblogic 8.1 sp3 (sun jdk) with 1.2-RC1
>
>
>
>
> Hello,
> I have a t
Title: Message
Some
can help me ?
Or
it's bea bug ?
-Message d'origine-De : Olivier Lamy
[mailto:[EMAIL PROTECTED] Envoyé : vendredi 19 novembre
2004 11:02À : Axis-UserObjet : EntityResolver
trouble in 1.2-RC2 and IncompatibleClassChangeError with weblogic 8.
Hello,
I have a trouble on weblogic server (I'm using the axis client part).
The stack trace is :
java.lang.NullPointerException
at
weblogic.xml.jaxp.ChainingEntityResolver.popEntityResolver(ChainingEnti
tyResolver.java:61)
at
weblogic.xml.jaxp.RegistryDocumentBuilder.setEntityResol
Hi, I'm looking for a little help. I deployed Axis 1.2RC1 (Java) under
Jboss (w/embedded Tomcat). If you are familiar with Liferay, we are using
their Jboss-Tomcat-Liferay bundled distribution. Anyway, I deploy Axis as
axis.war and it loads happy (Axis happy page says so). Jws-style web
service
Yes, mine was in the client too - it wasn't able to connect to the
server - it threw an error 500 with this exception...
Arijit
>-Original Message-
>From: Jeff Greif [mailto:[EMAIL PROTECTED]
>Sent: 14 October 2004 09:39
>To: [EMAIL PROTECTED]
>Subject: Re: Incompat
I see. I hit the exception in a client, not within Tomcat.
Jeff
- Original Message -
From: "Arijit Mukherjee" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 14, 2004 1:07 AM
Subject: RE: IncompatibleClassChangeError in Axis-1.2-RC1
I did t
tched.
Cheers
Arijit
>-Original Message-
>From: Jeff Greif [mailto:[EMAIL PROTECTED]
>Sent: 14 October 2004 09:04
>To: [EMAIL PROTECTED]
>Subject: Re: IncompatibleClassChangeError in Axis-1.2-RC1
>
>I was getting exactly the same exception. The problem went
>a
Sent: Thursday, October 14, 2004 12:31 AM
Subject: RE: IncompatibleClassChangeError in Axis-1.2-RC1
Hi Jeff
So have you solved this? Did new versions of saaj and xerces get rid of
this problem? I already have the new version of saaj (I mean the one
that comes with RC1) - do I need to c
>Sent: 13 October 2004 20:33
>To: [EMAIL PROTECTED]
>Subject: Re: IncompatibleClassChangeError in Axis-1.2-RC1
>
>I just spent yesterday struggling with this. I believe it is
>caused by needing a new version of saaj.jar (the one that
>comes with Axis-1.2RC1) (and maybe the
IL PROTECTED]>
Sent: Wednesday, October 13, 2004 12:29 PM
Subject: IncompatibleClassChangeError in Axis-1.2-RC1
Hi
I am working on a document oriented Web Service which was originally
developed with Axis-1.2-beta2, and still works with that. Recently, I
tried to use the new Axis-1.2-RC1, and I am g
Hi
I am working on a document oriented Web Service which was originally
developed with Axis-1.2-beta2, and still works with that. Recently, I
tried to use the new Axis-1.2-RC1, and I am getting a problem while
trying to use the service. The service gets deployed under tomcat
5.0.28, and the wsdl c
+0530, jayachandra <[EMAIL PROTECTED]> wrote:
> Hi there!
> I'm trying to run some ws-addressing interop scenario using
> axis1.2beta and Tomcat5.0. In the response message I'm getting an
> AxisFault because of IncompatibleClassChangeError. Did any of u
> encounter similar p
Hi there!
I'm trying to run some ws-addressing interop scenario using
axis1.2beta and Tomcat5.0. In the response message I'm getting an
AxisFault because of IncompatibleClassChangeError. Did any of u
encounter similar problem? I've browsed to find out that such error
might come
ED]Subject:
IncompatibleClassChangeError
Hi all,
I'm trying to upgrade from 1.2beta
to the more current versions. But whenever I try to deploy using the
AdminClient, I keep getting a java.lang.IncompatibleClasChangeError.
I've tried using beta2, beta3, and cvs version fro
Hi all,
I'm trying to upgrade from 1.2beta to the more current
versions. But whenever I try to deploy using the AdminClient, I keep
getting a java.lang.IncompatibleClasChangeError. I've tried using
beta2, beta3, and cvs version from today - same error. I also tried
making sure that t
I finally found the reason of my problem.
I can use WSDL2Java included in the beta2 version to generate stub
compatible.
The bug of the alpha3 version with the return of byte[] doesn't exist
anymore in this new version of axis. So I'm happy.
I just regret that the use of attachment is'nt compat
Hi,
I've got this exception when trying to run a client with stub generated by
IBM toolkit wsdl2java. The toolkit was using axis alpha3 and I had a problem
with reception of byte[]. (i didn't receive everything, but just a part).
This problem doesn't appear with soap and .NET.
I though it was
19 matches
Mail list logo
