[Axis2] Nightly build
Hi, Having had problems with the 1.0 release and XmlBeans, I left it alone and returned to 0.95. I'm really happy to find that the problems have been resolved in the current nightly build and I was able to upgrade my service without any difficulties. Thanks guys! Regards, Ken - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Maven plugin
Hi, Codehaus seems to be down today and I'm trying to build the Axis2 source with maven. Could some kind person please e-mail me maven-itest-plugin-1.0.jar? It does not appear to exist at Apache any more; all the links are dead. Thanks very much. Ken
[Axis2 1.0] MessageContext question
Hi Ajith and Davanum, I see.. ..and it seems that rolling XmlSchema forward to 1.03 doesn't help; neither can I roll back to XmlSchema-SNAPSHOT.jar as the axis2 code that invokes it seems to have changed to accommodate changes in 1.02. So it seems possible that there is a change to XmlSchema that might explain the sudden rash of data binding problems. I think I have to roll back to 0.95 as my difficulties with 1.0 do not seem to have a solution that I can code myself. (Glad I have an excuse to stop :-) , my head hurts ) I'll add to jira 710 regarding the 'gen361' prefix (as it's all related) when the system is back up. Thanks for looking at the problem. Regards, Ken -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: 14 May 2006 01:53 To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: [Axis2 1.0] MessageContext question Hmm... I see a possible bug of the XMLSchema library here. The schemas are kept as XMLschema objects inside the AxisService and what happens in the XMLBeans databinding is that the schema object is serialized and fed into the XMLBeans schema compiler. XMLSchema serilialization may have a problem and the mentioned namespace prefix may be generated by XMLSchema Ajith On 5/13/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Ken, > > Could u please log a JIRA bug and then upload your WSDL? > > thanks, > dims > > On 5/12/06, Ken Campbell <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Sorry to bang on about this but I tried removing the targetNamespace > > entirely from my wsdl and then re-ran WSDL2Java to see if the namespace > > declarations in the soap:body of the message could be removed. > > > > So now I am asking why WSDL2Java throws: > > Invalid QName value: Can't resolve prefix 'gen361' ? > > I don't have a 'gen361' prefix in my schema. > > > > Regards, > > Ken
RE: [Axis2 1.0] MessageContext question
Hi,
Sorry to bang on about this but I tried removing the targetNamespace
entirely from my wsdl and then re-ran WSDL2Java to see if the namespace
declarations in the soap:body of the message could be removed.
So now I am asking why WSDL2Java throws:
Invalid QName value: Can't resolve prefix 'gen361' ?
I don't have a 'gen361' prefix in my schema.
Regards,
Ken
>WSDL2Java -uri ..\DEVELOP\paf\PAF.wsdl -ss -sd -g -d xmlbeans -o
..\DEVELOP\paf -p edp.ws.paf.generated
Using AXIS2_HOME: C:\Apache\Tomcat5\webapps\axis2\WEB-INF
Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_04
org.apache.axis2.wsdl.codegen.CodeGenerationException
: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:185)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetExcepti
on
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB
eansExtension.java:93)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:140)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB
eansExtension.java:83)
... 3 more
Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException:
error:
Invalid QName value: Can't resolve prefix 'gen361'
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe
nerationUtility.java:192)
... 8 more
Caused by: org.apache.xmlbeans.XmlException: error: Invalid QName value:
Can't r
esolve prefix 'gen361'
at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(Sche
maTypeSystemCompiler.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:665)
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe
nerationUtility.java:161)
... 8 more
From: Ken Campbell [mailto:[EMAIL PROTECTED]
Sent: 12 May 2006 15:10
To: axis-user@ws.apache.org
Subject: RE: [Axis2 1.0] MessageContext question
Hi,
Further to my question, the data binding error is thrown by
org.apache.xmlbeans.SchemaTypeLoader.parse(XmlStreamReader, SchemaType,
XmlOptions) in one of my bound classes (LoginRequestDocument). However, with
the msgContext.getEnvelope() line placed in the code shown below it manages
to generate a LoginRequestDocument and a LoginResponseDocument (both of
which make sense) before the exception is thrown!? Surely there either is a
data binding error or there is not. How can it have it both ways? Here is
the SOAP envelope for the request:
http://schemas.xmlsoap.org/soap/envelope/";>
default
test
test
Regards,
Ken
From: Ken Campbell [mailto:[EMAIL PROTECTED]
Sent: 12 May 2006 11:07
To: axis-user@ws.apache.org
Subject: [Axis2 1.0] MessageContext question
Hi,
If someone understands the AxisEngine well Id appreciate them having a look
at this problem:
Im having a data binding error which I dont understand. In an attempt to
trace it Ive called:
System.out.println(msgContext.getEnvelope());
in MyMessageReceiverInOut.invokeBusinessLogic()
This seems to have a very weird effect. By placing it here :
if("login".equals(methodName)){
uk.co.edp.ws.paf.LoginResponseDocument param11 = null;
System.out.println(msgContext.getEnvelope());
//doc style
param11 =skel.login(
(uk.co.edp.ws.paf.LoginRequestDocument)fromOM(
msgContext.getEnvelope().getBody().getFirstElement(),
uk.co.edp.ws.paf.LoginRequestDocument.class,
getEnvelopeNamespaces(msgContext.getEnvelope(;
envelope = toEnvelope(getSOAPFactory(msgContext), param11,
false);
System.out.println("toEnvelope() returned.");
the service classes will return a valid param11,
RE: [Axis2 1.0] MessageContext question
Hi,
Further to my question, the data binding
error is thrown by org.apache.xmlbeans.SchemaTypeLoader.parse(XmlStreamReader,
SchemaType, XmlOptions) in one of my bound classes (LoginRequestDocument).
However, with the msgContext.getEnvelope() line placed in the code shown below it
manages to generate a LoginRequestDocument and a LoginResponseDocument (both of
which make sense) before the exception is thrown!? Surely there either is a
data binding error or there is not. How can it have it both ways? Here is the
SOAP envelope for the request:
default
test
test
Regards,
Ken
From: Ken Campbell
[mailto:[EMAIL PROTECTED]
Sent: 12 May 2006 11:07
To: axis-user@ws.apache.org
Subject: [Axis2 1.0]
MessageContext question
Hi,
If someone understands the AxisEngine well I’d
appreciate them having a look at this problem:
I’m having a data binding error which I
don’t understand. In an attempt to trace it I’ve called:
System.out.println(msgContext.getEnvelope());
in MyMessageReceiverInOut.invokeBusinessLogic()
This seems to have a very weird effect. By placing it
here :
…
if("login".equals(methodName)){
uk.co.edp.ws.paf.LoginResponseDocument param11 = null;
System.out.println(msgContext.getEnvelope());
//doc style
param11 =skel.login(
(uk.co.edp.ws.paf.LoginRequestDocument)fromOM(
msgContext.getEnvelope().getBody().getFirstElement(),
uk.co.edp.ws.paf.LoginRequestDocument.class,
getEnvelopeNamespaces(msgContext.getEnvelope(;
envelope = toEnvelope(getSOAPFactory(msgContext), param11, false);
System.out.println("toEnvelope() returned.");
…
the service classes will return a valid param11, but
axis throws an exception:
- Servlet.service() for servlet AxisServlet threw
exception
java.lang.NullPointerException
at com.ctc.wstx.util.BijectiveNsMap.findPrefixByUri(BijectiveNsMap.java:132)
at com.ctc.wstx.sw.SimpleOutputElement.getPrefix(SimpleOutputElement.java:453)
at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeAttributes(StreamingOMSerializer.java:214)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:147)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:73)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:56)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:315)
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:786)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:809)
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:780)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:171)
at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:809)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:381)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:256)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:210)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:43)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)…..
- Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: getOutputStream()
has already been called for this response….
So my question is, it seems as if
MessageContext.getEnvelope() in some way ‘consumes’ the data
stream. How is it possible
that I am getting a response from my service classes
when I do this and that no other class complains about my intercepting
msgContext until
BijectiveNsMap ? The data binding error is normally
thrown in MyMessageReceiverInOut.fromOM() at the request but when I call msgContext.getEnvelope()
it happily goes off and gets a proper response!
Regards,
Ken
[Axis2 1.0] MessageContext question
Hi,
If someone understands the AxisEngine well I’d
appreciate them having a look at this problem:
I’m having a data binding error which I don’t
understand. In an attempt to trace it I’ve called:
System.out.println(msgContext.getEnvelope());
in MyMessageReceiverInOut.invokeBusinessLogic()
This seems to have a very weird effect. By placing it
here :
…
if("login".equals(methodName)){
uk.co.edp.ws.paf.LoginResponseDocument param11 = null;
System.out.println(msgContext.getEnvelope());
//doc style
param11 =skel.login(
(uk.co.edp.ws.paf.LoginRequestDocument)fromOM(
msgContext.getEnvelope().getBody().getFirstElement(),
uk.co.edp.ws.paf.LoginRequestDocument.class,
getEnvelopeNamespaces(msgContext.getEnvelope(;
envelope = toEnvelope(getSOAPFactory(msgContext), param11, false);
System.out.println("toEnvelope() returned.");
…
the service classes will return a valid param11, but axis
throws an exception:
- Servlet.service() for servlet AxisServlet threw
exception
java.lang.NullPointerException
at
com.ctc.wstx.util.BijectiveNsMap.findPrefixByUri(BijectiveNsMap.java:132)
at
com.ctc.wstx.sw.SimpleOutputElement.getPrefix(SimpleOutputElement.java:453)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeAttributes(StreamingOMSerializer.java:214)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:147)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:73)
at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:56)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:315)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:786)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:809)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:780)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:171)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:809)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:381)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:256)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:210)
at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:43)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)…..
- Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: getOutputStream()
has already been called for this response….
So my question is, it seems as if
MessageContext.getEnvelope() in some way ‘consumes’ the data stream.
How is it possible
that I am getting a response from my service classes when
I do this and that no other class complains about my intercepting msgContext
until
BijectiveNsMap ? The data binding error is normally
thrown in MyMessageReceiverInOut.fromOM() at the request but when I call msgContext.getEnvelope()
it happily goes off and gets a proper response!
Regards,
Ken
RE: [Axis2 1.0] WSDL2Java producing garbage
Done. -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: 11 May 2006 11:18 To: axis-user@ws.apache.org Subject: Re: [Axis2 1.0] WSDL2Java producing garbage Hi Ken, Yes Seems a bug to me. could you report a jira and attach the WSDL there ? Ajith On 5/11/06, Ken Campbell <[EMAIL PROTECTED]> wrote: > Hi, > > I've upgraded my (working) web service from 0.95 to 1.0; I regenerated my > code using WSDl2Java taken from axis2-std-1.0-bin at the command line with: > WSDL2Java -uri -ss -sd -g -d xmlbeans -o -p > my.package.hierarchy.structure.generated > > However, the built code contains an uncompilable mass of errors caused by > my/package/hierarchy/structure.generated.GeneratedClasses littered > throughout the code. > > This seems to be related directly to the declared targetNamespace in the > wsdl definition which includes both '.' and '/' > > Might this constitute a bug? > > Regards, > Ken > > -- Ajith Ranabahu
[Axis2 1.0] WSDL2Java producing garbage
Hi, I've upgraded my (working) web service from 0.95 to 1.0; I regenerated my code using WSDl2Java taken from axis2-std-1.0-bin at the command line with: WSDL2Java -uri -ss -sd -g -d xmlbeans -o -p my.package.hierarchy.structure.generated However, the built code contains an uncompilable mass of errors caused by my/package/hierarchy/structure.generated.GeneratedClasses littered throughout the code. This seems to be related directly to the declared targetNamespace in the wsdl definition which includes both '.' and '/' Might this constitute a bug? Regards, Ken
RE: SOAP - literal x encoded
Hi Daniel, If you are using WSDL2Java then you could use the -d xmlbeans data binding option. This will generate XmlBeans objects for your types. Regards, Ken From: Daniel Destro [mailto:[EMAIL PROTECTED] Sent: 12 April 2006 17:38 To: axis-user@ws.apache.org Subject: SOAP - literal x encoded Someone told me here to use DOCUMENT/LITERAL instead of ENCODED SOAP, because I wanted a more simple SOAP response message. Well, it does work, BUT the problem is, it no longer uses Wrapper Types, instead it uses primitives. Is it possible to use wrappers using literal soap style? thanks Daniel
RE: Monitor progress of an AXIS SOAP request and response over http transport
Hi Martin, Excuse me butting in, but I was confused by your reply yesterday. If I understand you correctly you are saying that it is necessary that namespaces should be network accessible? However, I was under the impression that a namespace was required to be unique, not accessible. Is that not correct? Regards, Ken -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: 07 April 2006 14:44 To: axis-user@ws.apache.org Subject: Re: Monitor progress of an AXIS SOAP request and response over http transport Good Morning Daniel- I'll re-post the solution that I provided for Ken yesterday 1)First and foremost Go LOCAL! in other words place ALL of your files locally instead of xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; use "xmlns:soap=file://fu/bar/fubar/" instead of xmlns:tns="http://www.edp.co.uk/ws/PAF/"; use "xmlns:tns=file://fubar/fubar" instead of xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ use "xmlns:wsdl=file://fubar/ Now once all your local servers ARE proved to be operational you can migrate to different servers "xmlns:wsdl=file://FuBarServerIPAddress:/FuBarFolder ...
RE: [Axis2]0.95 MessageReceiver (plain text !!)
Hi, I found my solution. This is wrong: This is right: I spent the last two days on this, but now my question is: Where does the MessageContext come from on the service side? It isn't part of the SOAP message that is sent from the client, is it? Does the service derive it from the wsdl or something? Regards, Ken -Original Message- From: Ken Campbell [mailto:[EMAIL PROTECTED] Sent: 07 April 2006 09:43 To: axis-user@ws.apache.org Subject: [Axis2]0.95 MessageReceiver (plain text !!) Hi, I'm sure that when I send a LoginRequest to my service, the MessageContext which is sent contains a LoginRequest. At OutInAxisOperation line 267 : MessageContext response = send(mc); mc is the correct MessageContext where the operation name is "login". However, I'm also sure that in my MessageReceiver at invokeBusinessLogic : org.apache.axis2.description.AxisOperation op = msgContext.getOperationContext().getAxisOperation(); the operation name has turned into "formatAddress" even though the actual received message is still a LoginRequest. Hence the data binding error. Can anyone tell me what might cause this mismatch? I was wondering if there might be a problem here in the wsdl: http://schemas.xmlsoap.org/soap/http"/> or here in the services.xml http://www.w3.org/2004/08/wsdl/in-out"; class="edp.ws.paf.generated.PAFMessageReceiverInOut"/> edp.ws.paf.generated.PAFSkeleton http://www.w3.org/2004/08/wsdl/in-out";> http://www.w3.org/2004/08/wsdl/in-out"/> but I still don't understand why the problem does not occur when I send a LoginRequest from .NET. Regards, Ken
[Axis2]0.95 MessageReceiver (plain text !!)
Hi, I'm sure that when I send a LoginRequest to my service, the MessageContext which is sent contains a LoginRequest. At OutInAxisOperation line 267 : MessageContext response = send(mc); mc is the correct MessageContext where the operation name is "login". However, I'm also sure that in my MessageReceiver at invokeBusinessLogic : org.apache.axis2.description.AxisOperation op = msgContext.getOperationContext().getAxisOperation(); the operation name has turned into "formatAddress" even though the actual received message is still a LoginRequest. Hence the data binding error. Can anyone tell me what might cause this mismatch? I was wondering if there might be a problem here in the wsdl: http://schemas.xmlsoap.org/soap/http"/> or here in the services.xml http://www.w3.org/2004/08/wsdl/in-out"; class="edp.ws.paf.generated.PAFMessageReceiverInOut"/> edp.ws.paf.generated.PAFSkeleton http://www.w3.org/2004/08/wsdl/in-out";> http://www.w3.org/2004/08/wsdl/in-out"/> but I still don't understand why the problem does not occur when I send a LoginRequest from .NET. Regards, Ken
Profound Apologies re last message.
Hi All, Sincerest apologies for that last message. I installed outlook 2003 last week and neglected to switch message to plain text. I humbly beg everyone's pardon for the appalling waste of bandwidth. I'll go and stand in the corner for the rest of the afternoon. Regards, Ken
[Axis2 0.95]Stub problem.
Hi,
I’ve deployed a skeleton service with an
xmlbeans data binding which handles five types of operation: login,format,
search,metadata and page. I know the service is working because I’ve
accessed it from .NET and it returns correct responses. However, when I try to
use the generated Stub class in the following way:
PAFStub
stub = new PAFStub(null, "http://localhost:8080/axis2/services/PAF");
LoginRequestDocument ld = LoginRequestDocument.Factory.newInstance();
ld.addNewLoginRequest();
//
Populate the request
ld.getLoginRequest().setUserID("test");
ld.getLoginRequest().setPassword("test");
LoginResponseDocument loginResponse = stub.login(ld);
it throws an AxisFault telling me that there is a
data binding error;
The nested XmlException says: document is not a
[EMAIL PROTECTED]://www.edp.co.uk/ws/PAF/: document element local name
mismatch expected FormatRequest got LoginRequest
This has me very puzzled
bearing in mind that a login request works fine when using a .NET web reference
to the service. As far as I can work out problems arise in MessageReceiverInOut
fromOM(OMElement param, Class type) method.
Any ideas?
Regards,
Ken
RE: [Axis2] 0.95 Service and Client from WSDL - problems executing
Hi Sebastian, Looks like you are doing something similar to me. I've just deployed a skeleton service today built the same way with only minor problems (my own fault) along the way. It looks like your xmlbeans have been missed off the build path or are not where expected. Did you use the generated ant build.xml to build your archive? Regards, Ken -Original Message- From: Sebastian J. Schultheiss [mailto:[EMAIL PROTECTED] Sent: 05 April 2006 13:14 To: axis-user@ws.apache.org Subject: [Axis2] 0.95 Service and Client from WSDL - problems executing Hello, we have created a WSDL file (attached) to be used by an example web service that we would like to extend eventually. We used WSDL2Java to create the client and the service, with the xmlbeans Databinding. Maybe you can try to build it this way too and let us know if it should work in theory. After deploying the .aar in Axis2, we tried to connect to the server, but only got this exception report back. Please let us know if you need any additional information in order to tell us more. ... Thanks a lot for your time! -- Sebastian
RE: [Axis2] XmlBeans ClassNotFoundException
Hi, Sorry; please ignore previous enquiry. I found the solution. I wasn’t adding to my classpath at the correct level, so the package structure was wrong. I needed to add the %PROJECT_HOME%\resources folder so that it would put the generated TypeSystemHolder class in the correct package. Regards, Ken From: Ken Campbell [mailto:[EMAIL PROTECTED] Sent: 03 April 2006 14:46 To: axis-user@ws.apache.org Subject: [Axis2] XmlBeans ClassNotFoundException Hi, Sorry to be back with more problems so soon. After generating code using WSDL2Java with –d xmlbeans, I’ve been trying to run some experiments using the generated classes. However, I’m getting a ClassNotFoundException : Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4FEE54.TypeSystemHolder. Make sure the generated binary files are on the classpath. The following link suggests a solution: http://www.mail-archive.com/user@xmlbeans.apache.org/msg01232.html ..but I don’t understand… L I’ve made sure to put the schemaorg_apache_xmlbeans packages on my Eclipse build path, but I’m still getting the same error. Has anyone any experience of this? Regards, Ken
[Axis2] XmlBeans ClassNotFoundException
Hi, Sorry to be back with more problems so soon. After generating code using WSDL2Java with –d xmlbeans, I’ve been trying to run some experiments using the generated classes. However, I’m getting a ClassNotFoundException : Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4FEE54.TypeSystemHolder. Make sure the generated binary files are on the classpath. The following link suggests a solution: http://www.mail-archive.com/user@xmlbeans.apache.org/msg01232.html ..but I don’t understand… L I’ve made sure to put the schemaorg_apache_xmlbeans packages on my Eclipse build path, but I’m still getting the same error. Has anyone any experience of this? Regards, Ken
RE: [Axis2] 0.95 installation
Hi Chinthaka,
Now that I understand the problem I just need to refactor my services.
However, I am a bit confused when you say that you refactored om *after*
0.95. Does this mean the refactoring is now *in* 0.95, or does it mean it
will be in 0.96?
The Eclipse Axis code generator (which I downloaded from the 0.94 release)
produces a skeleton for me which has methods like:
public org.apache.axis2.om.OMElement getPage(
org.apache.axis2.om.OMElement param0) {
//Todo fill this with the necessary business logic
return null;
}
However, the 0.95 jars that I am using in my build path have
org.apache.ws.common.om.OMElement. I am pointing at
%TOMCAT_HOME%/webapps/axis2/WEB-INF/lib/axiom-api-0.95.jar which is the
directory that the 'magic' axis2.war created.
Yet the svn repository (which I would have thought would have the latest
source) is the same as the Eclipse generator signatures.
Which is the old package name and which is the new?
Regards,
Ken
-Original Message-
From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
Sent: 30 March 2006 12:38
To: axis-user@ws.apache.org
Subject: Re: [Axis2] 0.95 installation
Hi Ken,
Soon after Axis2 0.95 release I did a package name refactoring in OM. So
you will not able to use the latest om with Axis2 0.95.
But if you are only using the jars came with the release, you wouldn't
have got this issue.
Are you saying that you are getting errors even when using the jars came
in Axis2 0.95 ? If yes, let us reproduce the problem and we'll see what
we can do.
-- Chinthaka
RE: [Axis2] 0.95 installation
Hi Chinthaka, I found the solution today: the problems only came about when I dropped a service into axis2. I downloaded the axis2 source from http://svn.apache.org/repos/asf to try and track the problem and discovered that none of that source will build largely because it uses org.apache.axis2.om package structure instead of org.apache.ws.commons.om. Seemingly, all the service archives that I have dropped in have been using these package names. When I changed one of them to the new(?) ones and rebuilt the aar everything worked without problem. So now I am scratching my head and wondering is this a change from 0.94 or have I picked things up from even earlier versions? Looking back at every experiment I've done with axis2 it seems as if I have the wrong packages. I rebuilt my Eclipse axis2 library after I re-installed Tomcat at your suggestion, so you were right about the classpath problem. It never occurred to me that it was the Eclipse classpath and not the system or Tomcat classpath! Oh well, onwards...! Regards, Ken -Original Message- From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 17:01 To: axis-user@ws.apache.org Subject: Re: [Axis2] 0.95 installation >Anyway, it seems like you have a classpath problem. >-- Chinthaka
RE: [axis2] - 0.95 - WSDL2Java
Hi Ameet, Perhaps your problem is here : ... mailto:[EMAIL PROTECTED] Sent: 29 March 2006 16:57 To: axis-user@ws.apache.org Subject: RE: [axis2] - 0.95 - WSDL2Java Ok, here it is.
RE: [Axis2] 0.95 installation
O.K; I tried that. I've stripped out my classpath to .\;%JAVA_HOME%, taken axis and axis2 out, re-deployed the war; still not happy. Strangely, the administration page worked for a while; I was able to see the Version?wsdl from there, until I deployed some more services and restarted Tomcat at which point even the administration page started to complain that it couldn't find OMNode. Tomorrow, I'll take everything out of the Tomcat shared/lib (mail and activation) and common/lib (various) although there don't seem to be any conflicting jars. In the meantime if you have any other ideas I'd be grateful to hear them. Regards, Ken -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 16:17 To: axis-user@ws.apache.org Subject: Re: [Axis2] 0.95 installation Hmm.. Strange indeed. We've tested the war in both tomcat 5.0 and 5.5 (in JDK 1.5 for tomcat 5.5 and JDK 1.4 and 1.5 both for tomcat 5.0) and found no issue (before the release) I'm wondering that you may be having some older jars in your classpath. Please try removing any expanded directories named axis2 inside the webapp directory and redeploying the war ...
RE: [axis2] - 0.95 - WSDL2Java
Hi Ameet, I don’t think you can just change the type like that. How are you creating your wsdl? If you use Eclipse, for example, you can generate a new binding from the ‘graph’ tab of your wsdl. Depending on what transport type you choose, it will generate a number of elements for the binding. (rpc over http POST will generate a lot) Regards, Ken From: Ameet Hasmucrai Amarchande [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 15:30 To: axis-user@ws.apache.org Subject: RE: [axis2] - 0.95 - WSDL2Java But when I changed “document” to “rpc” it says: Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: org.apache.axis2.schema.SchemaCompilationException
RE: [Axis2] 0.95 installation
Hi Ajith, Yes; that's the one we are talking about. It comes down as a 'Compressed(zipped) folder'. Deploy that and we have no joy. Change its name to axis2.war and it will deploy the axis2 folder. The contents are as expected. However, browsing to http://localhost:8080/axis2 and clicking on the Services link throws: java.lang.NoSuchMethodError: org.apache.axis2.description.AxisService.getOperations()Ljava/util/HashMap; and the Validate link throws: java.lang.NoClassDefFoundError: org/apache/axis2/om/OMNode I'm running WindowsXP SP2 Tomcat 5.5.12 configured for Java 1.5.0_06 Axis 1 runs happily and Axis2 0.94 ran fairly happily except for the fact that I couldn't see the wsdl for the services that I deployed (although they seemed to work) Regards, Ken -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 15:16 To: axis-user@ws.apache.org Subject: Re: [Axis2] 0.95 installation Hi Ken, Just to get things straight, Are we talking about the download from http://ws.apache.org/axis2/download.cgi page which says war distrubution under 0.95? true that it says "zip" in the link but what you should be getting is a axis2.war file that is instantly deployable in tomcat! On 3/29/06, Ken Campbell <[EMAIL PROTECTED]> wrote: > Hi Eran, > > Thanks for your reply; I'm afraid no miracles, only a 404 error from Tomcat. > But then this was my point, I wasn't really expecting axis2.zip to provide > me with a web service. If I unzip it I get the axis2 folder. Put that in > webapps, restart Tomcat (5.5), I get a 500 error: >...
RE: [Axis2] 0.95 installation
Hi Eran, Thanks for your reply; I'm afraid no miracles, only a 404 error from Tomcat. But then this was my point, I wasn't really expecting axis2.zip to provide me with a web service. If I unzip it I get the axis2 folder. Put that in webapps, restart Tomcat (5.5), I get a 500 error: root cause: java.lang.NoSuchMethodError: org.apache.axis2.description.AxisService.getOperations()Ljava/util/HashMap; org.apache.jsp.listServices_jsp._jspService(org.apache.jsp.listServices_jsp: 90) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3 22) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) I'm running 0.94 at the minute, and to get that to run I needed the axis2 folder and the axis2.war in webapps. As I'm not seeing miracles, maybe there is something else I need to do; or do I just not have enough faith :-) Regards, Ken -Original Message- From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 14:32 To: axis-user@ws.apache.org Subject: Re: [Axis2] 0.95 installation Hi Ken, What you have downloaded is the war file itself. Just drop it (axis2.war) to $TOMCAT_HOME/webapps and start tomcat. Goto http://localhost:8080/axis2/ you will see the miracle :) (You may need to replace 8080 with the correct port tomcat is listening to). -- Chinthaka
RE: [axis2] - 0.95 - WSDL2Java
Hi, In your wsdl, perhaps your binding type = “document” rather than “rpc”. Regards, Ken From: Ameet Hasmucrai Amarchande [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 13:04 To: axis-user@ws.apache.org Subject: [axis2] - 0.95 - WSDL2Java Hi, After generating code with WSDL2Java, when I want to assign values for an operation I have just the option to assign OMElement type. Why does this happen? Is it a 0.95 specification? With 0.94 I had not this situation. Note: the WSDL have a complex type to represent a bean. Thanks, Ameet
[Axis2] 0.95 installation
Hi, A basic installation question: When I download the 0.95 war distribution I get a zip file of about 6Mb. When I unzip this there is no war. Was I just supposed to rename it or do something else? The installation instructions just say to drop the war file in the Tomcat webapps directory. Regards, Ken
