AXIS CPP 1.6b and Complex object
Hi ! I am new to AXIS CPP and I am having trouble executing the web services deployed in the server. Here is the situation . I am using AXIS CPP 1.6b and everything is setup as described and is working as expected. I have developed a webservice which consumes a complex object and returns similar object . In other word the request and response type are same. My client is a java application and I am using AXIS Java call object to invoke the web service. I can see in the SOAPMonitor that the message is getting across to the server . The problem is 1. I am not getting the values from the request in my web service method. 2. To diagnose tis problem I have added some trace messages in the deserialize method of the type class generated by the wsdl2ws tool . I never see this trace message . So that makes me suspicious if the deserialize method is executed on the server side. 3. Similarly I have trace messages in the web service method and the serialize methods. Both these trace messages are logged . My question is do I need to do any special coding for complex objects ? . I am attaching the wsdl , schema and the sample message. (See attached file: TestMessage.xsd)(See attached file: TestMessage.xml) (See attached file: TestService.wsdl) Appreciate any help in resolving this problem. Thanks Sunil Pandit RD , CSC FSG Austin (512)2755792 Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59 This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. TestMessage.xsd Description: Binary data TestMessage.xml Description: Binary data TestService.wsdl Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL2C create function conflicts with SOAP operation named create
Yes, Dimuthu, it occurred to me when I uncovered it that this is an issue without pretty solutions. Changing either the name of the axis support functions or the name of the generated operation functions would impact existing users who re-generated their stubs. On the other hand, there are real problems with selective name changing when conflicts are detected. In this particular case, imagine that the generated name is changed from create to op_create because create conflicts with the axis support function. Now the WSDL is changed to reflect a new function at the server, op_create. When the stubs are regenerated, the create operation would conflict with the support function, and the first alternative name would conflict as well. So the code would fall to a second alternate? That would mean that for this user, WSDL2C generated stubs with one name, op_create, and now started generated stubs with a different name. This now inflicts on the one user with the conflict the abrupt change in names that we would like to avoid inflicting on all the users one time. The general problem with selective name changes is that they seemingly occur at random and will be a surprise to anyone who is not already experienced with Axis and has not seen them before. My recommendation would be to change the interfaces to include a string, e.g., _op_, in front of all the operation names. The only way to avoid the possibility of conflicts with names from the WSDL is for the string to be added to the front, and not to the end. As there is an existing problem with the names asynchronous operations, e.g., _create_start, the asynchronous start of a create operation, has the same name as _create_start, the synchronous invocation of a create_start operation, I suggest that these be changed at the same time. So the old axis2_stub_servicename_opname becomes axis2_stub_op_servicename_opname, and the old axis2_stub_servicename_opname_start becomes axis2_stub_start_op_servicename_opname. As you imply this is a longstanding issue, you may already be aware of other name conflicts that I have not yet uncovered that should be solved at the same time. Maybe, to make it a general practice and example everywhere, you would want to change all the generated names to have all the axis assigned names precede the servicename or other username, e.g., axis2_stub_servicename_create itself becomes axis2_stub_create_servicename. This might avoid future problems and give you more freedom to add new stub functions without creating new conflicts. Obviously, it would be nice to avoid the abrupt change under the existing user base, so the old naming convention would still need to be available through a command-line option or an option in a properties file. I would suggest the improved naming convention be the default so that new adopters of Axis2C don't encounter problems, as the goal should be to increase the number of adopters by making it as easy and trouble free as possible. Clearly the longer one waits to introduce such a change, the more existing users there are and thus the more users are inconvenienced by the change. It might have been nice to associate such a change with the introduction of Axis2, so that people might be more accepting of a radical change from the Axis1 behavior. Dimuthu Gamage wrote: Hi Bill, Yea, that is a big issue. But since the tool has been there for sometime there would be codes that stick to the current api given by the generated code.. SO one thing we can do is, check whether the names for operations conflicts with the _create, _populate_services and _get_endpoint_uri_from_wsdl, and if so we can prefix the operation names with some thing like op So your create operation would be, 'axis2_stub_FService_op_create' but all the other non-conflicting functions stays the same. Any ideas? Thanks Dimuthu On Nov 16, 2007 6:01 AM, Bill Mitchell [EMAIL PROTECTED] wrote: In order to communicate with a service written with another tool, I have been given a WSDL that includes a SOAP operation with the name create: ... portType name=IFService operation name=create input message=fw:createRequest/ output message=fw:createResponse/ /operation /portType ... When I pass this WSDL through the WSDL2C utility, the generated header file constains two conflicting stubs with the same name. The first is for its internal procedure to create a stub for the service: axis2_stub_t* axis2_stub_FService_create (const axutil_env_t *env, axis2_char_t *client_home, axis2_char_t *endpoint_uri); The second is the procedure to invoke the create operation on the service: axiom_node_t* axis2_stub_FService_create( axis2_stub_t *stub, const axutil_env_t *env, axiom_node_t* create); Obviously, this doesn't work. It would be nice were
Re: WSDL2C create function conflicts with SOAP operation named create
In a similar vein, although I could raise it as a separate issue, I have come across another naming conflict in the output of the WSDL2C tool. In the same WSDL, I find another operation, this one named delete: ... operation name=delete input message=fw:deleteRequest/ output message=fw:deleteResponse/ /operation ... The template in the header for the stub for this operation is: axiom_node_t* axis2_stub_Fservice_delete( axis2_stub_t *stub, const axutil_env_t *env, axiom_node_t* delete); The problem with this is that, although delete is not a reserved word in C, it certainly is in C++. And my goal is to invoke the Axis2C code from within a C++ program. So I would suggest that WSDL2C should prefix all of the names generated as a result of the WSDL with something, and not leave them naked where they could conflict with reserved words in C or C++. Thanks, Bill Dimuthu Gamage wrote: Hi Bill, Yea, that is a big issue. But since the tool has been there for sometime there would be codes that stick to the current api given by the generated code.. SO one thing we can do is, check whether the names for operations conflicts with the _create, _populate_services and _get_endpoint_uri_from_wsdl, and if so we can prefix the operation names with some thing like op So your create operation would be, 'axis2_stub_FService_op_create' but all the other non-conflicting functions stays the same. Any ideas? Thanks Dimuthu On Nov 16, 2007 6:01 AM, Bill Mitchell [EMAIL PROTECTED] wrote: In order to communicate with a service written with another tool, I have been given a WSDL that includes a SOAP operation with the name create: ... portType name=IFService operation name=create input message=fw:createRequest/ output message=fw:createResponse/ /operation /portType ... When I pass this WSDL through the WSDL2C utility, the generated header file constains two conflicting stubs with the same name. The first is for its internal procedure to create a stub for the service: axis2_stub_t* axis2_stub_FService_create (const axutil_env_t *env, axis2_char_t *client_home, axis2_char_t *endpoint_uri); The second is the procedure to invoke the create operation on the service: axiom_node_t* axis2_stub_FService_create( axis2_stub_t *stub, const axutil_env_t *env, axiom_node_t* create); Obviously, this doesn't work. It would be nice were WSDL2C to add something more to the procedures that invoke the operations, such that the second were called axis2_stub_FService_invoke_create or ..._FService_create_operation. Is there some command line option I'm not seeing on WSDL2C that would force a more specific prefix on the operation stubs? Of course, in a C++ world, the two functions could both exist as they have different signatures. But I tried renaming and compiling the .c stub as a .cpp and that doesn't work. The generated .c stub uses delete as a parameter name. The brute force way is to edit the stubs everytime they are generated to solve the name conflict. Were I in control of both sides, I could avoid the issue by changing the name of the operation from create to something else. -- View this message in context: http://www.nabble.com/WSDL2C-create-function-conflicts-with-SOAP-operation-named-create-tf4818227.html#a13785056 Sent from the Axis - C++ - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/WSDL2C-create-function-conflicts-with-SOAP-operation-named-create-tf4818227.html#a13802853 Sent from the Axis - C++ - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL2C create function conflicts with SOAP operation named create
Bill Mitchell wrote: In a similar vein, although I could raise it as a separate issue, I have come across another naming conflict in the output of the WSDL2C tool. In the same WSDL, I find another operation, this one named delete: ... operation name=delete input message=fw:deleteRequest/ output message=fw:deleteResponse/ /operation ... The template in the header for the stub for this operation is: axiom_node_t* axis2_stub_Fservice_delete( axis2_stub_t *stub, const axutil_env_t *env, axiom_node_t* delete); The problem with this is that, although delete is not a reserved word in C, it certainly is in C++. And my goal is to invoke the Axis2C code from within a C++ program. So I would suggest that WSDL2C should prefix all of the names generated as a result of the WSDL with something, and not leave them naked where they could conflict with reserved words in C or C++. +1. I think we already track for C keywords. May be we can add C++ keywords to that table as well. Samisa... Thanks, Bill Dimuthu Gamage wrote: Hi Bill, Yea, that is a big issue. But since the tool has been there for sometime there would be codes that stick to the current api given by the generated code.. SO one thing we can do is, check whether the names for operations conflicts with the _create, _populate_services and _get_endpoint_uri_from_wsdl, and if so we can prefix the operation names with some thing like op So your create operation would be, 'axis2_stub_FService_op_create' but all the other non-conflicting functions stays the same. Any ideas? Thanks Dimuthu On Nov 16, 2007 6:01 AM, Bill Mitchell [EMAIL PROTECTED] wrote: In order to communicate with a service written with another tool, I have been given a WSDL that includes a SOAP operation with the name create: ... portType name=IFService operation name=create input message=fw:createRequest/ output message=fw:createResponse/ /operation /portType ... When I pass this WSDL through the WSDL2C utility, the generated header file constains two conflicting stubs with the same name. The first is for its internal procedure to create a stub for the service: axis2_stub_t* axis2_stub_FService_create (const axutil_env_t *env, axis2_char_t *client_home, axis2_char_t *endpoint_uri); The second is the procedure to invoke the create operation on the service: axiom_node_t* axis2_stub_FService_create( axis2_stub_t *stub, const axutil_env_t *env, axiom_node_t* create); Obviously, this doesn't work. It would be nice were WSDL2C to add something more to the procedures that invoke the operations, such that the second were called axis2_stub_FService_invoke_create or ..._FService_create_operation. Is there some command line option I'm not seeing on WSDL2C that would force a more specific prefix on the operation stubs? Of course, in a C++ world, the two functions could both exist as they have different signatures. But I tried renaming and compiling the .c stub as a .cpp and that doesn't work. The generated .c stub uses delete as a parameter name. The brute force way is to edit the stubs everytime they are generated to solve the name conflict. Were I in control of both sides, I could avoid the issue by changing the name of the operation from create to something else. -- View this message in context: http://www.nabble.com/WSDL2C-create-function-conflicts-with-SOAP-operation-named-create-tf4818227.html#a13785056 Sent from the Axis - C++ - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL2C create function conflicts with SOAP operation named create
Hi Bill, So briefly your suggestion is, For wsdl operations in the stub, axis2_stub_servicename_opname should be replaced with axis2_stub_op_servicename_opname. axis2_stub_servicename_opname_start should be replaced with axis2_stub_start_op_servicename_opname. and for consistency non wsdl-operations in the stub, axis2_stub_servicename_create should be replaced with axis2_stub_create_servicename. The only issue against this suggestion is, there the namespace part of the operation is not prefixed. But we can just forget that, if this solves all the problems. Anyway I doubt whether we can provide the old functions with a user option, since it need to add some code to the java tool (code portions not specific to c codegeneration), But we can give a try. I will let devs know this discussion and ask their suggestions. Thanks Dimuthu On Nov 17, 2007 2:32 AM, Bill Mitchell [EMAIL PROTECTED] wrote: Yes, Dimuthu, it occurred to me when I uncovered it that this is an issue without pretty solutions. Changing either the name of the axis support functions or the name of the generated operation functions would impact existing users who re-generated their stubs. On the other hand, there are real problems with selective name changing when conflicts are detected. In this particular case, imagine that the generated name is changed from create to op_create because create conflicts with the axis support function. Now the WSDL is changed to reflect a new function at the server, op_create. When the stubs are regenerated, the create operation would conflict with the support function, and the first alternative name would conflict as well. So the code would fall to a second alternate? That would mean that for this user, WSDL2C generated stubs with one name, op_create, and now started generated stubs with a different name. This now inflicts on the one user with the conflict the abrupt change in names that we would like to avoid inflicting on all the users one time. The general problem with selective name changes is that they seemingly occur at random and will be a surprise to anyone who is not already experienced with Axis and has not seen them before. My recommendation would be to change the interfaces to include a string, e.g., _op_, in front of all the operation names. The only way to avoid the possibility of conflicts with names from the WSDL is for the string to be added to the front, and not to the end. As there is an existing problem with the names asynchronous operations, e.g., _create_start, the asynchronous start of a create operation, has the same name as _create_start, the synchronous invocation of a create_start operation, I suggest that these be changed at the same time. So the old axis2_stub_servicename_opname becomes axis2_stub_op_servicename_opname, and the old axis2_stub_servicename_opname_start becomes axis2_stub_start_op_servicename_opname. As you imply this is a longstanding issue, you may already be aware of other name conflicts that I have not yet uncovered that should be solved at the same time. Maybe, to make it a general practice and example everywhere, you would want to change all the generated names to have all the axis assigned names precede the servicename or other username, e.g., axis2_stub_servicename_create itself becomes axis2_stub_create_servicename. This might avoid future problems and give you more freedom to add new stub functions without creating new conflicts. Obviously, it would be nice to avoid the abrupt change under the existing user base, so the old naming convention would still need to be available through a command-line option or an option in a properties file. I would suggest the improved naming convention be the default so that new adopters of Axis2C don't encounter problems, as the goal should be to increase the number of adopters by making it as easy and trouble free as possible. Clearly the longer one waits to introduce such a change, the more existing users there are and thus the more users are inconvenienced by the change. It might have been nice to associate such a change with the introduction of Axis2, so that people might be more accepting of a radical change from the Axis1 behavior. Dimuthu Gamage wrote: Hi Bill, Yea, that is a big issue. But since the tool has been there for sometime there would be codes that stick to the current api given by the generated code.. SO one thing we can do is, check whether the names for operations conflicts with the _create, _populate_services and _get_endpoint_uri_from_wsdl, and if so we can prefix the operation names with some thing like op So your create operation would be, 'axis2_stub_FService_op_create' but all the other non-conflicting functions stays the same. Any ideas? Thanks Dimuthu On Nov 16, 2007 6:01 AM, Bill Mitchell [EMAIL PROTECTED] wrote: In order to communicate with a service
axis2 java2wsdl ant task
Hello, Is there a way to generate a webservice from a java class using an ant task? I couldn't find nice documentation about that :( thanks, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with Axis2-1.3+ADB+MTOM in complex type
On Nov 16, 2007 12:25 PM, amit kumar [EMAIL PROTECTED] wrote: I am using same stax parser (wstx-asl-3.2.1.jar). I tried your code but still getting that exception. I think you are using the nightly build while I am using the standard Axis2-1.3 released version. Could this be the reason and it might get fixed in nightly build? please have a look amila. Amila Suriarachchi [EMAIL PROTECTED] wrote: I think the problem is with the stax parser. are you using a different one? On Nov 16, 2007 10:04 AM, amit kumar wrote: Here is the request message. - - - - - href=cid:1.urn:uuid:[EMAIL PROTECTED] xmlns:xop=http://www.w3.org/2004/08/xop/include; / test.txt Amila Suriarachchi wrote: ok i'll work on this wsdl. Can you please send the request message as well? amila On Nov 15, 2007 10:52 AM, amit kumar wrote: Hi Amila I am attaching the wsdl file. following is the soap response I got. - - - - soapenv:Receiver - org.apache.axis2.databinding.ADBException: Unexpected subelement fileName Amila Suriarachchi wrote: Can you send your request or response which gives this error and the full wsdl file? Can you try with a nighly build? Amila. On Nov 14, 2007 12:50 PM, amit kumar wrote: Hi I have a sample service for file upload. it takes complex type having fileName and fileData.I am using ADB. Environment is Eclipse, jre1.5, tomcat 5, axis 2-1.3 type=xs:base64Binary/ type=xs:string/ I have enabled mtom both on client and server side.when I run the client it gives me following exception. org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement fileName at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at com.test.client.MyServiceStub.uploadFile(MyServiceStub.java:178) at com.test.client.TestFileUpload.main(TestFileUpload.java:19) If I remove fileName from input it works fine. I think ADB is not able to handle any other parameter with binary data type in complex type. I tried to change the sequence of complex type in wsdl and regenerated the client side stuff then it started giving error for binaryData. Unlimited freedom, unlimited storage. Get it now -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Chat on a cool, new interface. No download required. Click here. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Share files, take polls, and discuss your passions - all under one roof. Click here. -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Forgot the famous last words? Access your message archive online. Click here. -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDL stub and skeleton generation few files missing
Hi all I ran the command for stub generation from wsdl, src is generated but few files which i expected in java are missing I m using axis2 v1.3 along with jdk1.5 wsdl2java tool is used Can any resolve my prob.. please help thanks, Amardeep -- View this message in context: http://www.nabble.com/WSDL-stub-and-skeleton-generation-few-files-missing-tf4820812.html#a13791913 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] maven plugin for wsdl2java
Hi everybody, I tried to find a suitable wsdl2java plugin for maven. The one linked in the tools section at the axis2 website is dead. Is there any new news about this plugin or a alternative? Or is an ant task the only option to automate the code generation in the build process? Thanks, Sietse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: faultString: org.apache.axis.deployment.wsdd.WSDDException: javax.xml.rpc.JAXRPCException: Null serializer factory specified
Hi Vaibhav,
I have never used wsdd for deployment so I can probably not solve your
problem. Although the URI of your typemapping looks invalid ( '}' is not
allowed I think). Maybe that brings you to the source of the problem.
And about xml and namespaces I would suggest to read the following
webpage http://www.w3schools.com/xml/xml_namespaces.asp . I think this
should be basic knowledge before you start working with webservices.
Sietse
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 16 November 2007 11:49
To: axis-user@ws.apache.org
Subject: RE: faultString: org.apache.axis.deployment.wsdd.WSDDException:
javax.xml.rpc.JAXRPCException: Null serializer factory specified
Thanks alot Sietse. The procseesing was succesful but with some
exceptions. I am new to web services and i dont know whats a namespace
and why its used.
Can you pls help me in solving the below exception .
- Unable to deploy typemapping: {http://ttdev.com/ss}concatRequest
java.lang.ClassNotFoundException: Found languageSpecificType namespace
'', expected 'http://xml.apache.org/axis/wsdd/providers/java'
at
org.apache.axis.deployment.wsdd.WSDDTypeMapping.getLanguageSpecificType(
WSDDTypeMapping.java:174)
at
org.apache.axis.deployment.wsdd.WSDDService.deployTypeMapping(WSDDServic
e.java:542)
at
org.apache.axis.deployment.wsdd.WSDDService.initTMR(WSDDService.java:253
)
at
org.apache.axis.deployment.wsdd.WSDDService.init(WSDDService.java:233)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.init(WSDDDeployment.jav
a:192)
at
org.apache.axis.deployment.wsdd.WSDDDocument.init(WSDDDocument.java:78
)
at org.apache.axis.utils.Admin.processWSDD(Admin.java:111)
at org.apache.axis.utils.Admin.process(Admin.java:158)
at org.apache.axis.utils.Admin.AdminService(Admin.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.axis.providers.java.MsgProvider.processMessage(MsgProvider.ja
va:126)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323
)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j
ava:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.j
ava:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvletStubImpl.java:1072)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:465)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:348)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:6981)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
etContext.java:3892)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
sietsenicolaas.tenhoeve wrote:
Hi Vaibhav,
It looks that your typemapping got some typos.
typeMapping
xmlns:ns=http://ttdev.com/ss;
qname=ns:concatRequest - (ns:concatRequest
without '' I guess)
type=java:com.myproject.simpleservice.ConcatRequest
-- (type=... Without java:com)
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=
/
Hope this helps you out.
Sietse
-Original Message-
From: Vaibhav Jungay [mailto:[EMAIL PROTECTED]
Sent: 16 November 2007 11:12
To: axis-user@ws.apache.org
Subject: faultString: org.apache.axis.deployment.wsdd.WSDDException:
javax.xml.rpc.JAXRPCException: Null serializer factory specified
Hi,
I get the above error when i try to deploy wsdd to my weblogic 8.1 app
server. I feel its because of typeMapping tag. Can somebody help me
pls...
RE: Stub ,skeleton generation from WSDL
thanks a lot sietse sietsenicolaas.tenhoeve wrote: Hi, I posted a similar message a few days ago. The -u option added to the wsdl2java command solved the problem. This is a bug and is probably solved in the next release (or the latest nightly release). Sietse -Original Message- From: amardeep [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 07:13 To: axis-user@ws.apache.org Subject: Stub ,skeleton generation from WSDL Hi all, I have a problem with generating stubs and skeleton from WSDL .I am using axis2 v1.3 along with jdk1.6. The problem is too many exceptions are thrown. I couldn't resolve the problem .If anyone could please help me out. The exception are: C:\Java\jdk1.5.0_05wsdl2Java -uri http://e1la41-320-10/IOGatewayWebService/Prod uctService.asmx?wsdl Using AXIS2_HOME: C:\axis2-1.3 Using JAVA_HOME:C:\Java\jdk1.5.0_05 [ERROR] PARSER_ERROR C:\Java\jdk1.5.0_05\.\src\uk\co\englandnet\gateway\iogatewaywebservice\P roductSe rviceStub.java:18464:16: unexpected token: staticabstract at de.hunsicker.jalopy.language.antlr.InternalJavaParser.classField(Inte rnalJavaParser.java:3119) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.classBlock(Inte rnalJavaParser.java:2457) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.classDefinition (InternalJavaParser.java:710) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinitionI nternal(InternalJavaParser.java:632) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinition( InternalJavaParser.java:465) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.parse(InternalJ avaParser.java:296) at de.hunsicker.jalopy.language.JavaRecognizer.parse(JavaRecognizer.java :588) at de.hunsicker.jalopy.Jalopy.parse(Jalopy.java:1212) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1044) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1017) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.util.PrettyPrinter.prettify(PrettyPrinter.java:89) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettifyFile(JavaPrettyPrinterExtension.java:66) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:46) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.AbstractPrettyPrinterExtensio n.engage(AbstractPrettyPrinterExtension.java:36) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:259) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) [ERROR] PARSER_ERROR C:\Java\jdk1.5.0_05\.\src\uk\co\englandnet\gateway\iogatewaywebservice\P roductSe rviceStub.java:21953:16: unexpected token: staticabstract at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinitionI nternal(InternalJavaParser.java:660) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinition( InternalJavaParser.java:465) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.parse(InternalJ avaParser.java:296) at de.hunsicker.jalopy.language.JavaRecognizer.parse(JavaRecognizer.java :588) at de.hunsicker.jalopy.Jalopy.parse(Jalopy.java:1212) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1044) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1017) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.util.PrettyPrinter.prettify(PrettyPrinter.java:89) at
RE: faultString: org.apache.axis.deployment.wsdd.WSDDException: javax.xml.rpc.JAXRPCException: Null serializer factory specified
Thanks alot Sietse. The procseesing was succesful but with some exceptions. I
am new to web services and i dont know whats a namespace and why its used.
Can you pls help me in solving the below exception .
- Unable to deploy typemapping: {http://ttdev.com/ss}concatRequest
java.lang.ClassNotFoundException: Found languageSpecificType namespace '',
expected 'http://xml.apache.org/axis/wsdd/providers/java'
at
org.apache.axis.deployment.wsdd.WSDDTypeMapping.getLanguageSpecificType(WSDDTypeMapping.java:174)
at
org.apache.axis.deployment.wsdd.WSDDService.deployTypeMapping(WSDDService.java:542)
at
org.apache.axis.deployment.wsdd.WSDDService.initTMR(WSDDService.java:253)
at
org.apache.axis.deployment.wsdd.WSDDService.init(WSDDService.java:233)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.init(WSDDDeployment.java:192)
at
org.apache.axis.deployment.wsdd.WSDDDocument.init(WSDDDocument.java:78)
at org.apache.axis.utils.Admin.processWSDD(Admin.java:111)
at org.apache.axis.utils.Admin.process(Admin.java:158)
at org.apache.axis.utils.Admin.AdminService(Admin.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.axis.providers.java.MsgProvider.processMessage(MsgProvider.java:126)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
sietsenicolaas.tenhoeve wrote:
Hi Vaibhav,
It looks that your typemapping got some typos.
typeMapping
xmlns:ns=http://ttdev.com/ss;
qname=ns:concatRequest - (ns:concatRequest
without '' I guess)
type=java:com.myproject.simpleservice.ConcatRequest
-- (type=... Without java:com)
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=
/
Hope this helps you out.
Sietse
-Original Message-
From: Vaibhav Jungay [mailto:[EMAIL PROTECTED]
Sent: 16 November 2007 11:12
To: axis-user@ws.apache.org
Subject: faultString: org.apache.axis.deployment.wsdd.WSDDException:
javax.xml.rpc.JAXRPCException: Null serializer factory specified
Hi,
I get the above error when i try to deploy wsdd to my weblogic 8.1 app
server. I feel its because of typeMapping tag. Can somebody help me
pls...
The wsdd is
!-- Use this file to deploy some handlers/chains and services --
!-- Two ways to do this: --
!-- java org.apache.axis.client.AdminClient deploy.wsdd --
!-- after the axis server is running --
!-- or --
!-- java org.apache.axis.utils.Admin client|server deploy.wsdd --
!-- from the same directory that the Axis engine runs --
deployment
xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
!-- Services from SimpleService WSDL service --
service name=SimpleServiceSOAP
Re: Optional elements of primitive type
Any hint for this? I just noticed that nil booleans are mapped to boolean false in Java, instead of a null Boolean reference :-( Thanks in advance! -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wsdl2java client threadsafe?
Hello, do you know if a client generated by the wsdl2java tool is said to be thread safe?I am using Axis2 1.3. /Pär Malmqvist _ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vistamkt=en-USform=QBRE
RE: Problem with Axis2-1.3+ADB+MTOM in complex type
Amit - Is it possible that you have sjsxp.jar in the classpath by any chance? I ran into the streaming parser conflicts while trying the default version service - it went away when I removed the sjsxp. Amila - can you possibly comment on a related question I asked - it is at http://www.nabble.com/-Axis2--Runtime-error-in-1.3-(version-service-fails)-due-to-streaming-parser-conflicts-t4807702.html -Original Message- From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Friday, November 16, 2007 2:17 AM To: axis-user@ws.apache.org Subject: Re: Problem with Axis2-1.3+ADB+MTOM in complex type On Nov 16, 2007 12:25 PM, amit kumar [EMAIL PROTECTED] wrote: I am using same stax parser (wstx-asl-3.2.1.jar). I tried your code but still getting that exception. I think you are using the nightly build while I am using the standard Axis2-1.3 released version. Could this be the reason and it might get fixed in nightly build? please have a look amila. Amila Suriarachchi [EMAIL PROTECTED] wrote: I think the problem is with the stax parser. are you using a different one? On Nov 16, 2007 10:04 AM, amit kumar wrote: Here is the request message. - - - - - href=cid:1.urn:uuid:[EMAIL PROTECTED] xmlns:xop=http://www.w3.org/2004/08/xop/include; / test.txt Amila Suriarachchi wrote: ok i'll work on this wsdl. Can you please send the request message as well? amila On Nov 15, 2007 10:52 AM, amit kumar wrote: Hi Amila I am attaching the wsdl file. following is the soap response I got. - - - - soapenv:Receiver - org.apache.axis2.databinding.ADBException: Unexpected subelement fileName Amila Suriarachchi wrote: Can you send your request or response which gives this error and the full wsdl file? Can you try with a nighly build? Amila. On Nov 14, 2007 12:50 PM, amit kumar wrote: Hi I have a sample service for file upload. it takes complex type having fileName and fileData.I am using ADB. Environment is Eclipse, jre1.5, tomcat 5, axis 2-1.3 type=xs:base64Binary/ type=xs:string/ I have enabled mtom both on client and server side.when I run the client it gives me following exception. org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement fileName at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:48 6) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInA xisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperati on.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxis Operation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at com.test.client.MyServiceStub.uploadFile(MyServiceStub.java:178) at com.test.client.TestFileUpload.main(TestFileUpload.java:19) If I remove fileName from input it works fine. I think ADB is not able to handle any other parameter with binary data type in complex type. I tried to change the sequence of complex type in wsdl and regenerated the client side stuff then it started giving error for binaryData. Unlimited freedom, unlimited storage. Get it now -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Chat on a cool, new interface. No download required. Click here. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Share files, take polls, and discuss your passions - all under one roof. Click here. -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Forgot the famous last words? Access your message archive online. Click here. -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl2java client threadsafe?
Thread parameters are configurable on Server-side via axis2.xml
!-- Here is the complete list of supported parameters (see example
settings further below):
port: the port to listen on (default 6060)
hostname: if non-null, url prefix used in reply-to endpoint
references (default null)
originServer: value of http Server header in outgoing messages
(default Simple-Server/1.1)
requestTimeout: value in millis of time that requests can wait for
data(default 2)
requestTcpNoDelay: true to maximize performance and minimize
latency (default true)
false to minimize bandwidth consumption by
combining segments
requestCoreThreadPoolSize: number of threads available for request
processing (unless queue fills up) (default 25)
requestMaxThreadPoolSize: number of threads available for request
processing if queue fills us (default 150)
note that default queue never fills up:
see HttpFactory
threadKeepAliveTime: time to keep threads in excess of core size
alive while inactive (default 180)
note that no such threads can exist with
default unbounded request queue
threadKeepAliveTimeUnit: TimeUnit of value in threadKeepAliveTime
(default SECONDS)(default SECONDS)
--
On the client side the closest to a asynchronous invocation is
/userguide/clients/EchoNonBlockingDualClient
//Callback to handle the response
Callback callback = new Callback() {
public void onComplete(AsyncResult result) {
System.out.println(result.getResponseEnvelope());
}
public void onError(Exception e) {
e.printStackTrace();
}
};
//Non-Blocking Invocation
sender = new ServiceClient();
sender.engageModule(Constants.MODULE_ADDRESSING);
sender.setOptions(options);
sender.sendReceiveNonBlocking(payload, callback);
//Wait till the callback receives the response.
while (!callback.isComplete()) {
Thread.sleep(1000);
}
As you can see the communications are asynchronous but are not truly Threadable
as there is no accomodation for
ThreadLocal attributes and
the methods are not synchronized
Does this help?
Martin--
- Original Message -
From: Pär Malmqvist
To: axis-user@ws.apache.org
Sent: Friday, November 16, 2007 10:22 AM
Subject: wsdl2java client threadsafe?
Hello,
do you know if a client generated by the wsdl2java tool is said to be thread
safe?
I am using Axis2 1.3.
/Pär Malmqvist
--
Discover the new Windows Vista Learn more!
RE: [axis2] maven plugin for wsdl2java
Thanks Upul and David! It works almost fine now! At least I get successful builds with maven (some configuration needs to be done). I tried to use this plugin already but somehow my groupId was incorrect. David, the extra repository wasn't needed in my case since it is in the default repo1. Sietse -Original Message- From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 11:16 To: axis-user@ws.apache.org Subject: Re: [axis2] maven plugin for wsdl2java Try this pom.xml. Plugin will be downloaded automatically when building. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.test/groupId artifactIdhello/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namehello/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.3/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.test.service/packageName /configuration /execution /executions /plugin /plugins /build /project Ant tasks are also available. http://ws.apache.org/axis2/tools/1_3/CodegenToolReference.html#ant Upul On Nov 16, 2007 4:31 PM, [EMAIL PROTECTED] wrote: Hi everybody, I tried to find a suitable wsdl2java plugin for maven. The one linked in the tools section at the axis2 website is dead. Is there any new news about this plugin or a alternative? Or is an ant task the only option to automate the code generation in the build process? Thanks, Sietse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 sample problem - Userguide sample still a problem
Hi Martin,
Thanks the suggestions.
I found the addressing problem, but the dual samples now give socket
errors and I had add the servlet.jar to the lib.
here are the steps
cd $AXIS2_HOME/samples/userguide
ant
OK
http://localhost:8080/axis2/axis2-admin/listService
UploadService
$AXIS2_HOME/repository/services/sample-MyService.aar
OK
Services/ActivateService MyService
dir F:\TOMCAT\APACHE~1.17\webapps\axis2\WEB-INF\sample-MyService.aar
vi F:\TOMCAT\APACHE~1.17\webapps\axis2\WEB-INF\services.list (make sure
sample-MyService.aar is listed)
OK
dir F:\TOMCAT\APACHE~1.17\webapps\axis2\WEB-INF\modules\addressing.mar
vi F:\TOMCAT\APACHE~1.17\webapps\axis2\WEB-INF\modules.list (make sure
addressing.mar is listed)
OK
EngageModule/For A ServiceModule:addressing
Select a Service:MyService
addressing module engaged to the service successfully
OK
Does this not work for you?
Still not working.
Summary
1.) The addressing module and, I guess all other modules, are found in
/modules/repository
which is due to the following setting in the build.xml
jvmarg value=-Daxis2.repo=${mainDir}/repository/
jvmarg value=-Daxis2.xml=conf/axis2.xml/
This is the reason for the addressing problem.
2.) For the following samples to run I had to add servlet-api.jar to Axis jars
in C:\apache-tomcat-5.5.25\webapps\axis2\WEB-INF\lib
See Tomcat startup problem.
3.) The following run OK
ant run.client.ping
ant run.client.blocking
ant run.client.nonblocking
ant run.client.servicewithmodule
4.) The following run - output to Tomcat window, then display many
connection errors and finally hang
ant run.client.blockingdual
ant run.client.nonblockingdual
ERROR: java.net.BindException: Address already in use: JVM_Bind see below.
5.) I have included files, logs and traces.
What do the tomcat logs say?
Tomcat startup log
The servlet-api.jar must be present in order for any of the sample to execute
INFO:
validateJarFile(C:\apache-tomcat-5.5.25\webapps\axis2\WEB-INF\lib\servlet-api.jar)
- jar not loaded.
See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
INFO] Deploying module: addressing-1.3
INFO] Deploying module: script-1.3
[INFO] Deploying module: addressing-1.3
[INFO] Deploying module: script-1.3
[INFO] Deploying module: metadataExchange-1.3
[INFO] Deploying module: ping-1.3
[INFO] Deploying module: sample-logging
[INFO] Deploying module: soapmonitor-1.3
[INFO] script module activated
[INFO] Deploying Web service: sample-MyService.aar
[INFO] Deploying Web service: sample-MyServiceWithModule.aar
[INFO] Deploying Web service: sample-WsaMappingService.aar
[INFO] Deploying Web service: SampleService.aar
[INFO] Deploying Web service: version-1.3.aar
6-Nov-2007 11:39:52 org.apache.coyote.http11.Htt
NFO: Starting Coyote HTTP/1.1 on http-8080
6-Nov-2007 11:39:52 org.apache.jk.common.Channel
...
INFO: Server startup in 9323 ms
original sample for usergruide build.xml
target name=run.client.ping depends=compile
java classname=userguide.clients.PingClient
classpathref=axis.classpath fork=true
jvmarg value=-Daxis2.repo=${mainDir}/repository/
looks in /respository
jvmarg value=-Daxis2.xml=conf/axis2.xml/ see below for logging
phase
/java
/target
My modules.list
addressing-1.3.mar
soapmonitor-1.3.mar
ping-1.3.mar
mex-1.3.mar
axis2-scripting-1.3.mar
logging.mar
My services.list
version-1.3.aar
sample-MyService.aar
sample-MyServiceWithModule.aar
sample-WsaMappingService.aar
AdminServlet
MyService
Service EPR : http://127.0.0.1:8080/axis2/services/MyService
Service Description : MyService
Service Status : Active
Engaged modules for the service
* addressing :: Disengage
* soapmonitor :: Disengage
Available operations
* ping
Engaged Modules for the Operation
o addressing :: Disengage
AdminServlet
Available Modules
* metadataExchange : module description not found
* addressing : This is the WS-Addressing implementation on Axis2,
supporting the WS-Addressing 1.0 Recommendation, as well as the
Submission version (2004/08).
* soapmonitor : module description not found
* sample-logging : module description not found
* ping : module description not found
* script : module description not found
Why is sample-logging not found?
ERROR with dual
In Tomcat window during run of blockingdual
Example1:echo
[INFO] ?xml version='1.0' encoding='utf-8'?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:wsa=http://www.w3.org/2005/08/addressing;
Re: [axis2] maven plugin for wsdl2java
Try this pom.xml. Plugin will be downloaded automatically when building. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.test/groupId artifactIdhello/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namehello/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.3/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.test.service/packageName /configuration /execution /executions /plugin /plugins /build /project Ant tasks are also available. http://ws.apache.org/axis2/tools/1_3/CodegenToolReference.html#ant Upul On Nov 16, 2007 4:31 PM, [EMAIL PROTECTED] wrote: Hi everybody, I tried to find a suitable wsdl2java plugin for maven. The one linked in the tools section at the axis2 website is dead. Is there any new news about this plugin or a alternative? Or is an ant task the only option to automate the code generation in the build process? Thanks, Sietse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: faultString: org.apache.axis.deployment.wsdd.WSDDException: javax.xml.rpc.JAXRPCException: Null serializer factory specified
Hi Vaibhav, It looks that your typemapping got some typos. typeMapping xmlns:ns=http://ttdev.com/ss; qname=ns:concatRequest - (ns:concatRequest without '' I guess) type=java:com.myproject.simpleservice.ConcatRequest -- (type=... Without java:com) serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle= / Hope this helps you out. Sietse -Original Message- From: Vaibhav Jungay [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 11:12 To: axis-user@ws.apache.org Subject: faultString: org.apache.axis.deployment.wsdd.WSDDException: javax.xml.rpc.JAXRPCException: Null serializer factory specified Hi, I get the above error when i try to deploy wsdd to my weblogic 8.1 app server. I feel its because of typeMapping tag. Can somebody help me pls... The wsdd is !-- Use this file to deploy some handlers/chains and services -- !-- Two ways to do this: -- !-- java org.apache.axis.client.AdminClient deploy.wsdd -- !-- after the axis server is running -- !-- or -- !-- java org.apache.axis.utils.Admin client|server deploy.wsdd -- !-- from the same directory that the Axis engine runs -- deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; !-- Services from SimpleService WSDL service -- service name=SimpleServiceSOAP provider=java:RPC style=document use=literal parameter name=wsdlTargetNamespace value=http://ttdev.com/ss/ parameter name=wsdlServiceElement value=SimpleService/ parameter name=schemaUnqualified value=http://ttdev.com/ss/ parameter name=wsdlServicePort value=SimpleServiceSOAP/ parameter name=className value=com.myproject.simpleservice.SimpleServiceSOAPImpl/ parameter name=wsdlPortType value=SimpleService/ parameter name=typeMappingVersion value=1.2/ operation name=concat qname=concat returnQName=concatResponse returnType=rtns:string xmlns:rtns=http://www.w3.org/2001/XMLSchema; soapAction=http://ttdev.com/ss/NewOperation; parameter qname=pns:concatRequest xmlns:pns=http://ttdev.com/ss; type=tns:concatRequest xmlns:tns=http://ttdev.com/ss/ /operation parameter name=allowedMethods value=concat/ typeMapping xmlns:ns=http://ttdev.com/ss; qname=ns:concatRequest type=java:com.myproject.simpleservice.ConcatRequest serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle= / /service /deployment - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: faultString: org.apache.axis.deployment.wsdd.WSDDException: javax.xml.rpc.JAXRPCException: Null serializer factory specified
Thank you Sietse !
sietsenicolaas.tenhoeve wrote:
Hi Vaibhav,
I have never used wsdd for deployment so I can probably not solve your
problem. Although the URI of your typemapping looks invalid ( '}' is not
allowed I think). Maybe that brings you to the source of the problem.
And about xml and namespaces I would suggest to read the following
webpage http://www.w3schools.com/xml/xml_namespaces.asp . I think this
should be basic knowledge before you start working with webservices.
Sietse
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 16 November 2007 11:49
To: axis-user@ws.apache.org
Subject: RE: faultString: org.apache.axis.deployment.wsdd.WSDDException:
javax.xml.rpc.JAXRPCException: Null serializer factory specified
Thanks alot Sietse. The procseesing was succesful but with some
exceptions. I am new to web services and i dont know whats a namespace
and why its used.
Can you pls help me in solving the below exception .
- Unable to deploy typemapping: {http://ttdev.com/ss}concatRequest
java.lang.ClassNotFoundException: Found languageSpecificType namespace
'', expected 'http://xml.apache.org/axis/wsdd/providers/java'
at
org.apache.axis.deployment.wsdd.WSDDTypeMapping.getLanguageSpecificType(
WSDDTypeMapping.java:174)
at
org.apache.axis.deployment.wsdd.WSDDService.deployTypeMapping(WSDDServic
e.java:542)
at
org.apache.axis.deployment.wsdd.WSDDService.initTMR(WSDDService.java:253
)
at
org.apache.axis.deployment.wsdd.WSDDService.init(WSDDService.java:233)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.init(WSDDDeployment.jav
a:192)
at
org.apache.axis.deployment.wsdd.WSDDDocument.init(WSDDDocument.java:78
)
at org.apache.axis.utils.Admin.processWSDD(Admin.java:111)
at org.apache.axis.utils.Admin.process(Admin.java:158)
at org.apache.axis.utils.Admin.AdminService(Admin.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.axis.providers.java.MsgProvider.processMessage(MsgProvider.ja
va:126)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323
)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j
ava:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.j
ava:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvletStubImpl.java:1072)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:465)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:348)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:6981)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
etContext.java:3892)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
sietsenicolaas.tenhoeve wrote:
Hi Vaibhav,
It looks that your typemapping got some typos.
typeMapping
xmlns:ns=http://ttdev.com/ss;
qname=ns:concatRequest - (ns:concatRequest
without '' I guess)
type=java:com.myproject.simpleservice.ConcatRequest
-- (type=... Without java:com)
serializer=org.apache.axis.encoding.ser.BeanSerializerFactory
deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory
encodingStyle=
/
Hope this helps you out.
Sietse
-Original Message-
From: Vaibhav Jungay [mailto:[EMAIL PROTECTED]
Sent: 16 November 2007 11:12
To: axis-user@ws.apache.org
Subject: faultString: org.apache.axis.deployment.wsdd.WSDDException:
javax.xml.rpc.JAXRPCException: Null serializer factory
Re: namespace issues with Apache Axis 1.4
Yes, you need to remove that and as well as java: in your typeMapping type inorder to deploy Dheepak Ramnathan wrote: Hi, I was trying to generated server deployment information from an existing wsdl thru WSDL2Java. I find that the generated namespaces in the server-config.wsdd contains a '' symbol as package name seperator. I want to know the significance of this . Can I just go ahead and remove this '' symbol . service name=FDPNotificationService provider=java:RPC style=document use=literal parameter name=wsdlTargetNamespace value=http://www.openuri.org//http://www.openuri.org/%22/ parameter name=wsdlServiceElement value=FDPActionsWS/ parameter name=schemaQualified value= http://www.openuri.org//http://www.openuri.org/%22/ parameter name=schemaUnqualified value=fdp-post-download-param,fdp-post-user-action-return,fdp-post-download-return,fdp-post-user-action-modify-param,fdp-post-content-action-return,fdp-post-content-action-delete-param,fdp-post-user-action-add-param,fdp-post-upload-return,fdp-post-upload-parameter,fdp-post-user-action-delete-param,fdp-post-content-action-add-param,fdp-post-content-action-modify-param/ parameter name=wsdlServicePort value=FDPNotificationService/ parameter name=className value= com.xyz.support.assets.fdp.service.FDPActionsWSSoapImpl/ parameter name=wsdlPortType value=FDPNotificationService/ parameter name=typeMappingVersion value=1.2/ operation name=postUploadEvent qname=postUploadEvent returnQName=retNS:postUploadEventResponse xmlns:retNS= http://www.openuri.org/; returnType=rtns:postUploadEventResponse xmlns:rtns= http://www.openuri.org/; soapAction= http://www.openuri.org/postUploadEvent; parameter qname=pns:fdp-message xmlns:pns=fdp-post-upload-parameter type=tns:post-upload-message xmlns:tns=fdp-post-upload-parameter/ /operation operation name=postDownloadEvent qname=postDownloadEvent returnQName=retNS:fdp-message xmlns:retNS=fdp-post-download-return returnType=rtns:post-download-message xmlns:rtns=fdp-post-download-return soapAction= http://www.openuri.org/postDownloadEvent; parameter qname=pns:fdp-message xmlns:pns=fdp-post-download-param type=tns:post-download-message xmlns:tns=fdp-post-download-param/ /operation operation name=postContentActionAddEvent qname=postContentActionAddEvent returnQName=retNS:fdp-message xmlns:retNS=fdp-post-content-action-return returnType=rtns:content-action-message xmlns:rtns=fdp-post-content-action-return soapAction= http://www.openuri.org/postContentActionAddEvent; parameter qname=pns:fdp-message xmlns:pns=fdp-post-content-action-add-param type=tns:content-action-message xmlns:tns=fdp-post-content-action-add-param/ /operation operation name=postContentActionDeleteEvent qname=postContentActionDeleteEvent returnQName=retNS:fdp-message xmlns:retNS=fdp-post-content-action-return returnType=rtns:content-action-message xmlns:rtns=fdp-post-content-action-return soapAction= http://www.openuri.org/postContentActionDeleteEvent; parameter qname=pns:fdp-message xmlns:pns=fdp-post-content-action-delete-param type=tns:content-action-message xmlns:tns=fdp-post-content-action-delete-param/ /operation operation name=postContentActionModifyEvent qname=postContentActionModifyEvent returnQName=retNS:fdp-message xmlns:retNS=fdp-post-content-action-return returnType=rtns:content-action-message xmlns:rtns=fdp-post-content-action-return soapAction= http://www.openuri.org/postContentActionModifyEvent; parameter qname=pns:fdp-message xmlns:pns=fdp-post-content-action-modify-param type=tns:content-action-message xmlns:tns=fdp-post-content-action-modify-param/ /operation operation name=postUserActionAddEvent qname=postUserActionAddEvent returnQName=retNS:fdp-message xmlns:retNS=fdp-post-user-action-return returnType=rtns:user-action-message xmlns:rtns=fdp-post-user-action-return soapAction= http://www.openuri.org/postUserActionAddEvent; parameter qname=pns:fdp-message xmlns:pns=fdp-post-user-action-add-param type=tns:user-action-message xmlns:tns=fdp-post-user-action-add-param/ /operation operation name=postUserActionDeleteEvent qname=postUserActionDeleteEvent returnQName=retNS:fdp-message xmlns:retNS=fdp-post-user-action-return returnType=rtns:user-action-message xmlns:rtns=fdp-post-user-action-return soapAction= http://www.openuri.org/postUserActionDeleteEvent; parameter qname=pns:fdp-message xmlns:pns=fdp-post-user-action-delete-param type=tns:user-action-message xmlns:tns=fdp-post-user-action-delete-param/ /operation operation name=postUserActionModifyEvent qname=postUserActionModifyEvent returnQName=retNS:fdp-message xmlns:retNS=fdp-post-user-action-return returnType=rtns:user-action-message xmlns:rtns=fdp-post-user-action-return soapAction=
RE: Dynamic web services (RequestUIRBasedDispatcher error)
Hi all, I enabled the debug log and found that the errors are coming from: (1) - [MessageContext: logID=urn:uuid:ED6C786C532D9A9EE51195200076405] Invoking Handler 'SOAPMessageBodyBasedDispatcher' in Phase 'Dispatch' - [MessageContext: logID=urn:uuid:ED6C786C532D9A9EE51195200076405] Checking for Service using SOAP message body's first child's namespace : urn:testWS - parseRequestURLForServiceAndOperation : [urn:testWS][/arsys/services] - Unable to parse request URL [urn:testWS][/arsys/services] (2) Then it continues and spits out the following message: - [MessageContext: logID=urn:uuid:ED6C786C532D9A9EE51195200076405] Invoking flowComplete() for Handler 'RequestURIBasedDispatcher' in Phase 'Transport' - org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) http://vedanta:8080/arsys/services/ARService And a fault is thrown. Does anyone know what is going on here? Is it trying to find 'ARService' class and cannot find it or is it because I have not specified any operation. I have a jar file ws.jar that contains ARService class and the jar is in the proper classpath. Thanks, --kumar -Original Message- From: Iyengar, Kumar [mailto:[EMAIL PROTECTED] Sent: Thursday, November 15, 2007 11:18 PM To: axis-user@ws.apache.org Subject: RE: Dynamic web services Hi Jeff, Thanks for the prompt reply. I tried this and it still gave me the same error. --kumar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Greif Sent: Thursday, November 15, 2007 10:21 PM To: axis-user@ws.apache.org Subject: Re: Dynamic web services I think you need service name=ARService rest of it /service Jeff On 11/15/07, Iyengar, Kumar [EMAIL PROTECTED] wrote: Hi all, The issue is getting a bit critical here and I would appreciate any help: I keep getting the error The service cannot be found for the endpoint reference (EPR) http://vedanta:8080/arsys/services/ARService; in my Soap Client (I am using SoapUI). But in Tomcat's log I see the error - Unable to parse request URL [urn:testWS][/arsys/services] . I am pretty sure this might be some dumb error on my part. I have set my axis2.xml as follows: parameter name=servicePathservices/parameter /* NOTE: contextRoot is not set */ I have set my service.xml as follows: service messageReceivers messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=org.apache.axis2.receivers.RawXMLINOUTMessageReceiver/ /messageReceivers parameter name=ServiceClass locked=falsecom.remedy.arsys.ws.services.ARService/parameter /service I have set my web.xml as follows: servlet servlet-nameAxisServlet/servlet-name display-nameApache-Axis Servlet/display-name servlet-classorg.apache.axis2.transport.http.AxisServlet/servlet-class /servlet servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/servlet/AxisServlet/url-pattern /servlet-mapping servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/services/*/url-pattern /servlet-mapping I have looked at Axis2 source code and it looks like the error is coming from Utils.java parseRequestURLForServiceAndOperation() routine. This routine is called by all the dispatchers. I am not sure why the 'path' parameter in 'parseRequestURLForServiceAndOperation()' is set to 'urn:testWS'. 'path' should point to EPR. The error message does mention the correct EPR. Also, when I set my 'servicePath' to 'arsys/services' then the error that is see in Tomcat's log is : - Unable to parse request URL [http://vedanta:8080/arsys/services/ARService][/arsys/arsys/services] - Unable to parse request URL [http://vedanta:8080/arsys/services/ARService][/arsys/arsys/services] - Unable to parse request URL [http://vedanta:8080/arsys/services/ARService][/arsys/arsys/services] - Unable to parse request URL [urn:testWS][/arsys/arsys/services] The 'path' parameter in 'parseRequestURLForServiceAndOperation()' routine now seems to contain the correct EPR but the 'servicePath' has '/arsys' prepended to it. Is 'contextRoot' supposed to be set? What is the definition of 'contextRoot'? Why does '/arsys' get prepended to 'servicePath'? Or in other words what is 'servicePath' supposed to be? How do I get axis2 log to be enabled? I did put log4j.properties and common-logging.properties in the classpath. I hope I can get some answers soon, Thanks, --kumar From: Iyengar, Kumar [mailto:[EMAIL PROTECTED] Sent: Thursday, November 15, 2007 1:22 AM To: axis-user@ws.apache.org Subject: RE: Dynamic web services Hi, I am afraid I am not making much headway here. I have my web.xml that specifies the servlet and servlet-mapping. However, I am not sure what values the axis2.xml parameters should have especially
RE: Stub ,skeleton generation from WSDL
Hi, I posted a similar message a few days ago. The -u option added to the wsdl2java command solved the problem. This is a bug and is probably solved in the next release (or the latest nightly release). Sietse -Original Message- From: amardeep [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 07:13 To: axis-user@ws.apache.org Subject: Stub ,skeleton generation from WSDL Hi all, I have a problem with generating stubs and skeleton from WSDL .I am using axis2 v1.3 along with jdk1.6. The problem is too many exceptions are thrown. I couldn't resolve the problem .If anyone could please help me out. The exception are: C:\Java\jdk1.5.0_05wsdl2Java -uri http://e1la41-320-10/IOGatewayWebService/Prod uctService.asmx?wsdl Using AXIS2_HOME: C:\axis2-1.3 Using JAVA_HOME:C:\Java\jdk1.5.0_05 [ERROR] PARSER_ERROR C:\Java\jdk1.5.0_05\.\src\uk\co\englandnet\gateway\iogatewaywebservice\P roductSe rviceStub.java:18464:16: unexpected token: staticabstract at de.hunsicker.jalopy.language.antlr.InternalJavaParser.classField(Inte rnalJavaParser.java:3119) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.classBlock(Inte rnalJavaParser.java:2457) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.classDefinition (InternalJavaParser.java:710) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinitionI nternal(InternalJavaParser.java:632) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinition( InternalJavaParser.java:465) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.parse(InternalJ avaParser.java:296) at de.hunsicker.jalopy.language.JavaRecognizer.parse(JavaRecognizer.java :588) at de.hunsicker.jalopy.Jalopy.parse(Jalopy.java:1212) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1044) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1017) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.util.PrettyPrinter.prettify(PrettyPrinter.java:89) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettifyFile(JavaPrettyPrinterExtension.java:66) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:46) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettify(JavaPrettyPrinterExtension.java:50) at org.apache.axis2.wsdl.codegen.extension.AbstractPrettyPrinterExtensio n.engage(AbstractPrettyPrinterExtension.java:36) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:259) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) [ERROR] PARSER_ERROR C:\Java\jdk1.5.0_05\.\src\uk\co\englandnet\gateway\iogatewaywebservice\P roductSe rviceStub.java:21953:16: unexpected token: staticabstract at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinitionI nternal(InternalJavaParser.java:660) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.typeDefinition( InternalJavaParser.java:465) at de.hunsicker.jalopy.language.antlr.InternalJavaParser.parse(InternalJ avaParser.java:296) at de.hunsicker.jalopy.language.JavaRecognizer.parse(JavaRecognizer.java :588) at de.hunsicker.jalopy.Jalopy.parse(Jalopy.java:1212) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1044) at de.hunsicker.jalopy.Jalopy.format(Jalopy.java:1017) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.util.PrettyPrinter.prettify(PrettyPrinter.java:89) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr ettifyFile(JavaPrettyPrinterExtension.java:66) at org.apache.axis2.wsdl.codegen.extension.JavaPrettyPrinterExtension.pr
RE: [axis2] maven plugin for wsdl2java
I also discovered where my wrong groupId came from. It is stated wrong on the axis2 website: http://ws.apache.org/axis2/tools/1_3/maven-plugins/maven-wsdl2code-plugi n.html In the xml snippet you see the groupId: 'org.apache.axis2.maven2' which should be 'org.apache.axis2' Is this message enough to let the maintainers change this, or is there somewhere a reporting instrument? Sietse -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 11:39 To: axis-user@ws.apache.org Subject: RE: [axis2] maven plugin for wsdl2java Thanks Upul and David! It works almost fine now! At least I get successful builds with maven (some configuration needs to be done). I tried to use this plugin already but somehow my groupId was incorrect. David, the extra repository wasn't needed in my case since it is in the default repo1. Sietse -Original Message- From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 11:16 To: axis-user@ws.apache.org Subject: Re: [axis2] maven plugin for wsdl2java Try this pom.xml. Plugin will be downloaded automatically when building. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.test/groupId artifactIdhello/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namehello/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.3/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.test.service/packageName /configuration /execution /executions /plugin /plugins /build /project Ant tasks are also available. http://ws.apache.org/axis2/tools/1_3/CodegenToolReference.html#ant Upul On Nov 16, 2007 4:31 PM, [EMAIL PROTECTED] wrote: Hi everybody, I tried to find a suitable wsdl2java plugin for maven. The one linked in the tools section at the axis2 website is dead. Is there any new news about this plugin or a alternative? Or is an ant task the only option to automate the code generation in the build process? Thanks, Sietse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with class generation using ADB from WSDL (with a complex type having attributeGroup and extension)
Hello, I am generating classes using axis2 and ADB binding. I have a type defined as below in the attached wsdl file. element name=TwoWayOneParameterEchoRequest complexType simpleContent extension base=xsd:string attributeGroup ref=impl:echoAttributeGroup/attributeGroup /extension /simpleContent /complexType /element But for some reason when server side classes are generated from wsdl the generated TwoWayOneParameterEchoRequest class has only the string attribute corresponding to extension base=xsd:string/ but there are no members in the class which correspond to the attributeGroup in the type. Command used: %AXIS2_HOME%\bin\WSDL2Java -uri ug.wsdl -d adb -ss (I even tried adding other options like -g and -uw but they did not solve the problem) Axis2 version: 1.3 If I use XmlBeans databinding, then generated class has members corresponding to both attributeGroup as well as the extension tag. Help appreciated. Thanks, Vivek DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. ug.wsdl Description: XML document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
faultString: org.apache.axis.deployment.wsdd.WSDDException: javax.xml.rpc.JAXRPCException: Null serializer factory specified
Hi, I get the above error when i try to deploy wsdd to my weblogic 8.1 app server. I feel its because of typeMapping tag. Can somebody help me pls... The wsdd is !-- Use this file to deploy some handlers/chains and services -- !-- Two ways to do this: -- !-- java org.apache.axis.client.AdminClient deploy.wsdd -- !-- after the axis server is running -- !-- or -- !-- java org.apache.axis.utils.Admin client|server deploy.wsdd -- !-- from the same directory that the Axis engine runs -- deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; !-- Services from SimpleService WSDL service -- service name=SimpleServiceSOAP provider=java:RPC style=document use=literal parameter name=wsdlTargetNamespace value=http://ttdev.com/ss/ parameter name=wsdlServiceElement value=SimpleService/ parameter name=schemaUnqualified value=http://ttdev.com/ss/ parameter name=wsdlServicePort value=SimpleServiceSOAP/ parameter name=className value=com.myproject.simpleservice.SimpleServiceSOAPImpl/ parameter name=wsdlPortType value=SimpleService/ parameter name=typeMappingVersion value=1.2/ operation name=concat qname=concat returnQName=concatResponse returnType=rtns:string xmlns:rtns=http://www.w3.org/2001/XMLSchema; soapAction=http://ttdev.com/ss/NewOperation; parameter qname=pns:concatRequest xmlns:pns=http://ttdev.com/ss; type=tns:concatRequest xmlns:tns=http://ttdev.com/ss/ /operation parameter name=allowedMethods value=concat/ typeMapping xmlns:ns=http://ttdev.com/ss; qname=ns:concatRequest type=java:com.myproject.simpleservice.ConcatRequest serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle= / /service /deployment - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Does non-blocking / Async in AXIS2 really work ?
Hi there,
I have AXIS2 release 1.3 installed (on PC, Windows XP)
I compile and deploy the ECHO service from
\axis2\samples\userguide\src\userguide\example1 (MyService.java)
I start the server from \axis2\bin\axis2server.bat
I compile and run different clients from
\axis2\samples\userguide\src\userguide\clients
Everything works fine and I can run different clients and request is sent to
server and response comes back.
Now I want to test the Async (non-blocking) aspect of Axis2:
In server code in echo() function I put a thread sleep so that it keeps it busy
before returning to client and I am expecting that Axis2 engine will take care
of non-blocking aspect and will return back to Client in another channel
(non-blocking async dual channel client) :
I put below Thread sleep in server code in Echo() function:
public class MyService {
public OMElement echo(OMElement element) throws XMLStreamException
{
element.build();
element.detach();
//This is put with Try/Catch but is removed here to see it better
Thread.sleep(6);
return element;
}
So when I run the client the server will simulate doing a job of 60 seconds (1
minute) which is more than the default Axis2 timeout of 30 seconds. What I
would expect to see on client side is :
OK - 1) If Sync client is run it should timeout as axis2 timeout is 30s and the
server is not done with its job. So I run the EchoBlockingClient.java that's
what I see it means it times out and the FAULT() function in client is called.
So far so good.
Not OK - 2) If Async(non-blocking dual or regular) is run I would expect that
finaly I will receive the complete method of Client called (onComplete()) but
it doesn't happen. I only get onError() or Axis.Fault() called.
It means I assume that when I run the example EchoNonBlockingDualClient.java it
is going to use 2 HTTP transport channels. The first one should timeout during
request but the second one should be used when responese is sent back after
60seconds.
But what happens is after 30 seconds the onError() function :
public void onError(Exception e)
inside Callback class is called. Then it just hangs and when the sleep on
server side wakes up after 60 seconds I don't receive any callback anymore on
Client side.
In case of EchoNonBlockingDualClient.java the thread (eclipse IDE) or Dos
Prompt is still active and waiting but in case of EchoNonBlockingClient.java
the thread dies and you get the Dos Prompt released.
I checked this article :
http://www.ibm.com/developerworks/webservices/library/ws-axis2/
And tried to play with services.xml with below:
Listing 4. Associating message receivers with the IN-OUT MEP variable
messageReceivers
// other message receivers
messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-out; class=
org.apache.axis2.async.AsyncMessageReceiver/
/messageReceivers
But I get class not found error for
org.apache.axis2.async.AsyncMessageReceiver. So probably this article is old
and this class doesn't exist anymore in new Axis release ?
I tried the code in this article:
http://www.onjava.com/lpt/a/6076
But most probably this article is old too as I get error in eclipse that it
can't resolve this clas CALL :
Call call = new Call();
And nothing to import.
In eclipse I also get depreciated warning for the included client code for
Callback:
Callback callback = new Callback()
I even change it to AxisCallback class in stead and its methods and run it but
still same problem I only get one callback which is during axis2 timeout.
So Question:
Has anybody got this non-blocking working?
[I mean make it working when your server job is longer than the Axis2 timeout,
as we have a lot of tasks which will take half a day or day etc and we want to
return to client longer than Axis2 timeout. I know you can change the Axis2
timeout to maximum 6 days or so (maximum of int) but that's not a good solution
as we want to have network timeout in place don't want to wait 6 days if it's
network problem but our job might take longer than 6 days or so]
Best Regards,
Jan
Be a better pen pal.
Text or chat with friends inside Yahoo! Mail. See how.
http://overview.mail.yahoo.com/
HTTP 502 Proxy Error in Axis 1.3
Hi,
We have a webservice which is using Axis 1.3.
There are some clients using our webservices. One of the clients
reported that he is getting a HTTP 502 Proxy Error intermittently when
accessing our webservices.
Does anyone face this problem before or know why this is occurring? Is
there any solution for this issue?
Here is the stack trace of the error.
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (502)Proxy Error
faultActor:
faultNode:
faultDetail:
{}string: return code: 502
lt;!DOCTYPE HTML PUBLIC quot;-//IETF//DTD HTML 2.0//ENquot;gt;
lt;htmlgt;lt;headgt;
lt;titlegt;502 Proxy Errorlt;/titlegt;
lt;/headgt;lt;bodygt;
lt;h1gt;Proxy Errorlt;/h1gt;
lt;pgt;The proxy server received an invalid^M
response from an upstream server.lt;br /gt;^M
The proxy server could not handle the request lt;emgt;lt;a
href=quot;/webservices/ResponsysWSquot;gt;POSTamp;nbsp;/webservices/
ResponsysWSlt;/agt;lt;/emgt;.lt;pgt;
Reason: lt;stronggt;Error reading from remote
serverlt;/stronggt;lt;/pgt;lt;/pgt;
lt;hrgt;
lt;addressgt;Apache/2.2.4 (Unix) mod_ssl/2.2.4 OpenSSL/0.9.7a Server
at ws1.responsys.net Port 80lt;/addressgt;
lt;/bodygt;lt;/htmlgt;
(502)Proxy Error
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java
:630)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:128)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j
ava:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
...
...
Thanks in advance
Raghu
Re: [axis2] maven plugin for wsdl2java
Sietse the doc is possibly incorrect...more importantly the pom.xml or at least the copy I have from axis2-1.3 distro is correct Martin-- - Original Message - From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, November 16, 2007 7:14 AM Subject: RE: [axis2] maven plugin for wsdl2java I also discovered where my wrong groupId came from. It is stated wrong on the axis2 website: http://ws.apache.org/axis2/tools/1_3/maven-plugins/maven-wsdl2code-plugi n.html In the xml snippet you see the groupId: 'org.apache.axis2.maven2' which should be 'org.apache.axis2' Is this message enough to let the maintainers change this, or is there somewhere a reporting instrument? Sietse -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 11:39 To: axis-user@ws.apache.org Subject: RE: [axis2] maven plugin for wsdl2java Thanks Upul and David! It works almost fine now! At least I get successful builds with maven (some configuration needs to be done). I tried to use this plugin already but somehow my groupId was incorrect. David, the extra repository wasn't needed in my case since it is in the default repo1. Sietse -Original Message- From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 11:16 To: axis-user@ws.apache.org Subject: Re: [axis2] maven plugin for wsdl2java Try this pom.xml. Plugin will be downloaded automatically when building. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.test/groupId artifactIdhello/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namehello/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.3/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.test.service/packageName /configuration /execution /executions /plugin /plugins /build /project Ant tasks are also available. http://ws.apache.org/axis2/tools/1_3/CodegenToolReference.html#ant Upul On Nov 16, 2007 4:31 PM, [EMAIL PROTECTED] wrote: Hi everybody, I tried to find a suitable wsdl2java plugin for maven. The one linked in the tools section at the axis2 website is dead. Is there any new news about this plugin or a alternative? Or is an ant task the only option to automate the code generation in the build process? Thanks, Sietse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 java2wsdl ant task
There's a maven plugin though. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.test/groupId artifactIdhello/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namehello/name urlhttp://maven.apache.org/url dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-java2wsdl-maven-plugin/artifactId configuration classNamecom.foo.myservice.MyHandler/className /configuration executions execution goals goaljava2wsdl/goal /goals /execution /executions /plugin /plugins /build /project Or you can call the AXIS2_HOME/bin/java2wsdl.sh command line program using an Ant java / task You can also deploy a Java class as a web service directly. Check this link http://ws.apache.org/axis2/1_3/pojoguide.html Upul On Nov 16, 2007 1:26 PM, Simon Steinacker [EMAIL PROTECTED] wrote: Hello, Is there a way to generate a webservice from a java class using an ant task? I couldn't find nice documentation about that :( thanks, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis2] maven plugin for wsdl2java
Hi Sietse I had the same problem about a week ago and found that if you add the repository repository idapache-repo/id nameapache repo/name urlhttp://people.apache.org/repo/m2-ibiblio-rsync-repository/url layoutdefault/layout releases enabledtrue/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled updatePolicynever/updatePolicy checksumPolicyfail/checksumPolicy /snapshots /repository Then you will be able to use the wsdl2code plugin as follows plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.3/version /plugin Hope this helps Regads David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 16 November 2007 11:02 To: axis-user@ws.apache.org Subject: [axis2] maven plugin for wsdl2java Hi everybody, I tried to find a suitable wsdl2java plugin for maven. The one linked in the tools section at the axis2 website is dead. Is there any new news about this plugin or a alternative? Or is an ant task the only option to automate the code generation in the build process? Thanks, Sietse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: HTTP 502 Proxy Error in Axis 1.3
I would hazard a guess that it is an infrastructure problem
(request/response routing, IP address changing), since your web services
do work some of the time.
You might want to get your production support (network engineers) onto
it.
-jeff
_
From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED]
Sent: Friday, November 16, 2007 2:04 PM
To: axis-user@ws.apache.org
Subject: HTTP 502 Proxy Error in Axis 1.3
Hi,
We have a webservice which is using Axis 1.3.
There are some clients using our webservices. One of the
clients reported that he is getting a HTTP 502 Proxy Error
intermittently when accessing our webservices.
Does anyone face this problem before or know why this is
occurring? Is there any solution for this issue?
Here is the stack trace of the error.
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (502)Proxy Error
faultActor:
faultNode:
faultDetail:
{}string: return code: 502
lt;!DOCTYPE HTML PUBLIC quot;-//IETF//DTD HTML
2.0//ENquot;gt;
lt;htmlgt;lt;headgt;
lt;titlegt;502 Proxy Errorlt;/titlegt;
lt;/headgt;lt;bodygt;
lt;h1gt;Proxy Errorlt;/h1gt;
lt;pgt;The proxy server received an invalid^M
response from an upstream server.lt;br /gt;^M
The proxy server could not handle the request lt;emgt;lt;a
href=quot;/webservices/ResponsysWSquot;gt;POSTamp;nbsp;/webservices/
ResponsysWSlt;/agt;lt;/emgt;.lt;pgt;
Reason: lt;stronggt;Error reading from remote
serverlt;/stronggt;lt;/pgt;lt;/pgt;
lt;hrgt;
lt;addressgt;Apache/2.2.4 (Unix) mod_ssl/2.2.4 OpenSSL/0.9.7a
Server at ws1.responsys.net Port 80lt;/addressgt;
lt;/bodygt;lt;/htmlgt;
(502)Proxy Error
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java
:630)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:128)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j
ava:71)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
at
org.apache.axis.client.Call.invokeEngine(Call.java:2564)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
...
...
Thanks in advance
Raghu
How to get child elements from a SOAP XML response?
Hi everybody!!! I would like to know how can I get child elements from a response message using AXIOM? For example: I make two invocations in a client program to a service provider, so I want to get all children elements from XML response. One by one. Thanks! Julio -- View this message in context: http://www.nabble.com/How-to-get--child-elements-from-a-SOAP-XML-response--tf4824179.html#a13802491 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Released Axis2 jars
Why is axis2-adb-1.3.jarmissing fromhttp://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.axis2/jars/?Alan M. FeldsteinCosmic Horizonhttp://www.alanfeldstein.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to get child elements from a SOAP XML response?
You may send only one invocation (expressed as the child element in a SOAP body) in a single SOAP message. Axis2 will ignore any additional child elements. Anne On Nov 16, 2007 4:59 PM, juliocest [EMAIL PROTECTED] wrote: Hi everybody!!! I would like to know how can I get child elements from a response message using AXIOM? For example: I make two invocations in a client program to a service provider, so I want to get all children elements from XML response. One by one. Thanks! Julio -- View this message in context: http://www.nabble.com/How-to-get--child-elements-from-a-SOAP-XML-response--tf4824179.html#a13802491 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
