Re: WSDL2C is not generating soap 1.2 compliant client stubs for wsdl with soap 1.2 bindings
Hello group, Kindly let me know if my queries are relevant to this forum. I have not received any response for the query posted below. Do i need to post this axis2/java forum? Assistance needed. On Mon, May 26, 2008 at 4:47 AM, naveen bhat [EMAIL PROTECTED] wrote: Hello group, I am using a wsdl with soap 1.2 bindings.I generated client stub using three version of axis2/java (1.2/1.3/1.4). In all three I found that in the client stub the call for the operation,let say add(for eg) always sets the soap version to AXIS2_SOAP11,but actually it should be AXIS2_SOAP12 for a wsdl with soap 1.2 bindings. I am not finding any options in WSDL2C tool to generate client code for soap 1.2 . I also tried to set the soap version to 1.2 (in main function of client) before calling the operation defined in stub ,but this did not work as the soap version was reset back to soap 1.1 in the stub(let say axis2_stub_op_add() for eg). So my question is how do i use code generator to generate stub which can send soap 1.2 compliant message at the client side. PS: Following command was used to generate stub WSDL2C.sh -uri wsdlpath -d adb -u
Re: SOAP fault not working in axis2c 1.4
Hi Naveen, Could you please set your log level to debug and send your log file here ? thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAP fault not working in axis2c 1.4
Hi Naveen, naveen bhat [EMAIL PROTECTED] writes: Hi Dinesh , I have attached the mtom log file and the tcpmon log file. I executed the client thrice. I got the same result. Please check logs and let me know wat is wrong. I think your problem is in server side. Therefore if you could send server log (axis2.log) that would be useful. thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL2C is not generating soap 1.2 compliant client stubs for wsdl with soap 1.2 bindings
Hi, Please check the comment https://issues.apache.org/jira/browse/AXIS2C-1168?focusedCommentId=12601123#action_12601123 Thanks Dimuthu On Fri, May 30, 2008 at 4:02 PM, naveen bhat [EMAIL PROTECTED] wrote: Hello Dimuthu, I have raised a jira with key AXIS2C-1168 . Thanks , Naveen On Fri, May 30, 2008 at 1:49 AM, Dimuthu Gamage [EMAIL PROTECTED] wrote: Hi naveen, In fact looks like this is not possible with the current wsdl2c generated code. It just pick the first binding and generate code for that. Can you please raise a JIRA. I will look in to that asap. Thanks Dimuthu On Fri, May 30, 2008 at 3:06 PM, naveen bhat [EMAIL PROTECTED] wrote: Hello group, Kindly let me know if my queries are relevant to this forum. I have not received any response for the query posted below. Do i need to post this axis2/java forum? Assistance needed. On Mon, May 26, 2008 at 4:47 AM, naveen bhat [EMAIL PROTECTED] wrote: Hello group, I am using a wsdl with soap 1.2 bindings.I generated client stub using three version of axis2/java (1.2/1.3/1.4). In all three I found that in the client stub the call for the operation,let say add(for eg) always sets the soap version to AXIS2_SOAP11,but actually it should be AXIS2_SOAP12 for a wsdl with soap 1.2 bindings. I am not finding any options in WSDL2C tool to generate client code for soap 1.2 . I also tried to set the soap version to 1.2 (in main function of client) before calling the operation defined in stub ,but this did not work as the soap version was reset back to soap 1.1 in the stub(let say axis2_stub_op_add() for eg). So my question is how do i use code generator to generate stub which can send soap 1.2 compliant message at the client side. PS: Following command was used to generate stub WSDL2C.sh -uri wsdlpath -d adb -u - 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]
suggested patch: _array class should have exposed size()
I added a public 'int size();' to my *_Array classes. It is useful for
determining the size of the _Array.
In ArrayParamHeaderWriter.java-writeMethods() add
writer.write(\t\tint size();\n);
In ArrayParamWriter.java-writeMethods() add
this.writeSizeMethod();
Add this method:
/**
* @throws WrapperFault
*/
protected void writeSizeMethod() throws WrapperFault
{
try
{
writer.write(int + classname + :: + size()\n);
writer.write({\n);
writer.write(\treturn m_Size;\n);
writer.write(}\n\n);
}
catch (IOException e)
{
throw new WrapperFault(e);
}
}
Ryan McCullough | RightNow Technologies | Integration Tools Engineer
406-556-3162 office | Bozeman, MT | mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] | http://www.rightnow.com/
http://www.rightnow.com
smime.p7s
Description: S/MIME cryptographic signature
minor bug (spelling) in org\apache\axis\wsdl\wsdl2ws\ParamWriter.java
attribfeilds should be attribfields (4 occurences) elementfeilds should be elementfields (4 occurences) Ryan McCullough | RightNow Technologies | Integration Tools Engineer 406-556-3162 office | Bozeman, MT | mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] | http://www.rightnow.com/ http://www.rightnow.com smime.p7s Description: S/MIME cryptographic signature
Re: [Axis2] Axis2/C support for AIX?
Hi Brent, We are also working on this problem. Have you gotten any closer? We should collaborate. - Hal -- View this message in context: http://www.nabble.com/-Axis2--Axis2-C-support-for-AIX--tp17136222p17565012.html 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: minor bug (spelling) in org\apache\axis\wsdl\wsdl2ws\ParamWriter.java
Done! Nadir Amra McCullough, Ryan [EMAIL PROTECTED] wrote on 05/30/2008 12:15:58 PM: attribfeilds should be attribfields (4 occurences) elementfeilds should be elementfields (4 occurences) Ryan McCullough | RightNow Technologies | Integration Tools Engineer 406-556-3162 office | Bozeman, MT | [EMAIL PROTECTED] | http: //www.rightnow.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 with JMS Transport
Finally it's an error in Axis2. If so do you have any idea who will fix it when? publish via an actual Axis 2 client - means we should use Axis2 client to put message in to MQseries? Or else use it directly to contact Axis2? Can you please provide more info or any reference? Mean while I will try using INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory suggested by others at http://www.mqseries.net/phpBB2/viewtopic.php?p=216263#216263 _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2008 4:10 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport Your axis2.xml looks correct - as long as your MQ is setup as a JNDI provider. Note that you can setup all your JMS stuff in MQ explorer visually if you have the correct support packs installed - you don't need to use the JMS admin tool. I just tried your approach with publishing a message via MQ explorer and got the same error: Exception in thread JMSWorker-1 java.lang.NullPointerException at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMe ssageReceiver.java:190) at org.apache.axis2.transport.jms.JMSMessageReceiver.access$000(JMSMessageRecei ver.java:50) at org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageRecei ver.java:246) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) This looks like an error in Axis 2 - so it looks like you'll have to publish via an actual Axis 2 client. I had a look at the Axis 2 code and its something around the reply-to code - including a reply-to SOAP addressing header didn't resolve it. adisesha wrote: No, output can be sent to other queue also. For now the problem I have is w.r.to reading queue is guess. We can think of sending o/p to same/other queue later. 1. java.lang.NullPointerException at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMe ssageReceiver.java:190) May be the settings I used are wrong? Can you cross check the axis2.xml services.xml I have sent? _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2008 11:19 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport MQ 6.0.2.3 is good as the JNDI provider. It sounds like you want your web service to respond to the same queue? I've only done asynchronous web services over JMS, for synchronous I use HTTP, so can't help on responding to the same queue - i.e. all my JMS web services are one way traffic from MQ to Axis2/Tomcat. If you have addressing information in the SOAP header in your message envelope, then it should resolve your issue where it can't find the correct operation to invoke on your web service. Certainly, if you can configure axis2 to suit all your needs then go with that - I tend to keep environment specific JMS stuff out of my axis2.xml files because I have to deploy to the customer development, testing and production environments and don't like constantly changing axis2.xml files with every deployment. adisesha wrote: We want to work on existing settings, with out need of code. i.e create WS with one method, set connection details in axis2.xml then create JNDI either in tomcat or in websphereMQ. Now when user puts info in MQ automatically WS should be called then return xxx to o/p Queue. For this sequence I don't see the need of code if axis2 works correctly. What is your opinion on this? _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2008 3:43 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport 1. Add the ws-addressing support to your service and your client. (go to the axis 2 site to see how to do this). This may/should help in getting your web service to be able work out what method needs to be invoked. 2. When you are configuring the JMS sender - your connection details (provider factory class, URL etc) can be configured in the code instead of in the axis2.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Disclaimer The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by forwarding this email to [EMAIL PROTECTED] and then
Update on compiling source and a little feedback
Hi, I've previously had some problems with compiling Axis2 source code, mainly due to issues with tests failing during compilation. I've tried jdk 6 and 5, and many other tweak, but I could not manage to get maven compile sources without any errors. I've decided to try something different, and I've setup Ubuntu 8.04. Switching from XP sp2 to Ubuntu worked for me, and I've managed to compile both Axis2 1.4 source release and the latest code I've checked out from svn using both jdk 5 and 6 However, I could not compile 1.3, neither with jdk5 nor with 6. Actually jdk 6 appears to be a no go for 1.3 anyway. Tests still fail (2 failures actually) for 1.3 with maven 2.0.9 . The feedback is: there are still ant build files and instructions in readme files. However, some of the instructions related to ant are out of date. For example to create eclipse plugin projects, if you choose the ant way, you are expected to do a maven create-lib according to docs, but this is not possible, since maven is used in maven 1.x and mvn is used in maven 2. Axis2 uses maven 2 so this part of the doc is broken I guess. The doc does not mention that you can do mvn eclipse:eclipse in eclipse tools dirs to get plugin projects, and when you do that, the libs that the plugin project require are not copied to lib folder of the generated project. Overall, the process requires a little digging, considerably more if you are not used to maven, and I've still not managed to get 1.3 source to compile. Still, I'm very glad that I've reached a point where I can see the bigger picture much better, and I'd like to thank to all contributers for making such a great piece of work available. All the best Seref
RE: unexpected subelement exception
Can anybody help on the below issue? From: Rajendra Kumar Miryala [mailto:[EMAIL PROTECTED] Sent: Monday, May 26, 2008 7:58 PM To: axis-user@ws.apache.org Subject: unexpected subelement exception Hi, I am getting below exception while receiving response from web-service. This service works fine on JBOS and exception is raised in the Glassfish (v9.1). I am using Axis2 1.2. Also using ADB data binding and axis2 code generation tools to generate the WSDL and stub class. The Element msgID is nillable=true (even with minoccurs = 0). Still service is expecting the value for msgID. Please help me in resolving the issue. Exception: Caused by: java.lang.RuntimeException: Unexpected subelement msgID at com.test.client.MyWebServiceStub$SummaryResponse$Factory.parse(MyWebServ iceStub.java:8704) at com.test.client.MyWebServiceStub$GetSummaryResponse$Factory.parse(MyWebS erviceStub.java:5279) at com.test.client.MyWebServiceStub.fromOM(MyWebServiceStub.java:26442) XSD definition in WSDL: xs:complexType name=SummaryResponse xs:sequence xs:element name=msgID nillable=true type=xs:string / xs:element name=statusCode nillable=true type=xs:string / /xs:sequence /xs:complexType Thanks In advance Rajendra This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
RE: Axis2-1.3, xmlbeans error
Any update on this. Thanks Meena From: Karunanidhi, Meena Sent: 29 May 2008 16:14 To: '[EMAIL PROTECTED]' Subject: Axis2-1.3, xmlbeans error Hi I created a web service using Axis2-1.3, xmlbeans on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: I am NOT using any authentication for my web service, it is simple enough to send and receive an order. Any suggestions,pls Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
[axis-user] Axis Client with gSOAP server
Hi everybody,
I try to use Axis to build a Web service client for a gSOAP server.
I get a wsdl file from the server and use WSDL2Java to generate stub code.
And, when I run my Client it said me this error :
org.apache.axis.types.URI$MalformedURIException: Cannot initialize URI with
empty parameters .
I search on the Internet, but I cant fidn any solution or clues to resolve
this error.
To be more precise the gSOAP server is a magicservice from the samples on
there website.
Attach to this mail is the wsdl file and the Client Code file.
If someone have an idea of when it could come from.
Thanks in advance.
Maxime.
?xml version=1.0 encoding=UTF-8?
definitions name=Service
targetNamespace=http://localhost:80/Service.wsdl;
xmlns:tns=http://localhost:80/Service.wsdl;
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:ns1=http://tempuri.org/ns1.xsd;
xmlns:SOAP=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:MIME=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:DIME=http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/;
xmlns:WSDL=http://schemas.xmlsoap.org/wsdl/;
xmlns=http://schemas.xmlsoap.org/wsdl/;
types
schema targetNamespace=http://tempuri.org/ns1.xsd;
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:ns1=http://tempuri.org/ns1.xsd;
xmlns=http://www.w3.org/2001/XMLSchema;
elementFormDefault=unqualified
attributeFormDefault=unqualified
import namespace=http://schemas.xmlsoap.org/soap/encoding//
complexType name=ArrayOfint
complexContent
restriction base=SOAP-ENC:Array
sequence
element name=item type=xsd:int minOccurs=0 maxOccurs=unbounded/
/sequence
attribute ref=SOAP-ENC:arrayType WSDL:arrayType=xsd:int[]/
/restriction
/complexContent
/complexType
complexType name=ArrayOfArrayOfint
complexContent
restriction base=SOAP-ENC:Array
sequence
element name=item type=ns1:ArrayOfint minOccurs=0 maxOccurs=unbounded/
/sequence
attribute ref=SOAP-ENC:arrayType WSDL:arrayType=ns1:ArrayOfint[]/
/restriction
/complexContent
/complexType
!-- operation request element --
element name=magic
complexType
sequence
element name=rank type=xsd:int minOccurs=1 maxOccurs=1/
/sequence
/complexType
/element
!-- operation response element --
element name=magicResponse
complexType
sequence
element name=result type=ns1:ArrayOfArrayOfint minOccurs=0 maxOccurs=1 nillable=true/
/sequence
/complexType
/element
/schema
/types
message name=magicRequest
part name=parameters element=ns1:magic/
/message
message name=magicResponse
part name=parameters element=ns1:magicResponse/
/message
portType name=ServicePortType
operation name=magic
documentationService definition of function ns1__magic/documentation
input message=tns:magicRequest/
output message=tns:magicResponse/
/operation
/portType
binding name=Service type=tns:ServicePortType
SOAP:binding style=document transport=http://schemas.xmlsoap.org/soap/http/
operation name=magic
SOAP:operation soapAction=/
input
SOAP:body parts=parameters use=literal/
/input
output
SOAP:body parts=parameters use=literal/
/output
/operation
/binding
service name=Service
documentationgSOAP 2.7.10 generated service definition/documentation
port name=Service binding=tns:Service
SOAP:address location=http://ozzy-6.tml.hut.fi:15081/
/port
/service
/definitions
import localhost.Service_wsdl.*;
import java.net.URL;
import java.rmi.RemoteException;
import javax.xml.rpc.ServiceException;
public class ServiceClient{
public static void main(String[] args)throws Exception {
try{
String url = http://ozzy-6.tml.hut.fi:15082/;;
int rank = 5;
Service service = new ServiceLocator();
ServicePortType port = service.getService(new URL(url));
String addr = service.getServiceAddress();
System.out.println(Service address : +addr+\n);
try{
int[][] response = port.magic(rank);
}catch (RemoteException e1){
e1.printStackTrace();
}
}catch (ServiceException e) {
e.printStackTrace();
}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Axis, WS-I and .NET 2.0
HI! Until now we were using Axis 1.3 (embedded in our server), default style encoding (RPC) and .NET 2.0 client. This works OK with arrays, nulls and beans. But this is not WS-I conform and so JAX-WS clients complain. Now we tried changing the style to wrapped for WSDL creation and service creation, so we added: emitter.setStyle(wrapped); // WSDL creation and service.setStyle(org.apache.axis.constants.Style.WRAPPED); // service creation When we test that with the .NET 2.0 client (after recreating the proxies), arrays still work but NULL return values (for strings) are not null anymore. Axis sent before: parameterTest3Return xsi:type=xsd:string xsi:nil=true/ And with wrapped: parameterTest3Return xsi:nil=true/ The missing type seems to be a problem for .NET 2.0 So, then we tried document/literal as style/use but with this, Axis produces a messed up WSDL with wrong parameter types. We also tried Axis 1.4 with the same results. Any help would be greatly appreciated to get our web services WS-I conform and working with .NET 2.0 clients with NULLs, arrays and beans. Thanks! Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: unexpected subelement exception
Can you post relevant parts of WSDL? -Rushikesh On Fri, May 30, 2008 at 10:17 AM, Rajendra Kumar Miryala [EMAIL PROTECTED] wrote: Can anybody help on the below issue? -- *From:* Rajendra Kumar Miryala [mailto: [EMAIL PROTECTED] *Sent:* Monday, May 26, 2008 7:58 PM *To:* axis-user@ws.apache.org *Subject:* unexpected subelement exception Hi, I am getting below exception while receiving response from web-service. This service works fine on JBOS and exception is raised in the Glassfish (v9.1). I am using Axis2 1.2. Also using ADB data binding and axis2 code generation tools to generate the WSDL and stub class. The Element msgID is nillable=true (even with minoccurs = 0). Still service is expecting the value for msgID. Please help me in resolving the issue. Exception: Caused by: java.lang.RuntimeException: Unexpected subelement msgID at com.test.client.MyWebServiceStub$SummaryResponse$Factory.parse(MyWebServiceStub.java:8704) at com.test.client.MyWebServiceStub$GetSummaryResponse$Factory.parse(MyWebServiceStub.java:5279) at com.test.client.MyWebServiceStub.fromOM(MyWebServiceStub.java:26442) XSD definition in WSDL: xs:complexType name=SummaryResponse xs:sequence xs:element name=msgID nillable=true type=xs:string / xs:element name=statusCode nillable=true type=xs:string / /xs:sequence /xs:complexType Thanks In advance Rajendra This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Axis2 (ADB) : Problem with empty RequestBody
I can see thanks to dubugging that the soapEnvelope in request is constructed in Stub class correctly and it remains unchainged during axis2 engine which ended in the correct request calling messageContext is OK (afaik). Then why is it changed (empty - no body) when it comes to server. -- View this message in context: http://www.nabble.com/Axis2-%28ADB%29-%3A-Problem-with-empty-RequestBody-tp17532435p17557256.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN][Axis2] QuickStart Axis2 -- My first b ook on Axis2 is published
This is to inform you with great joy that I was able to complete my book on Axis2. The book is now published and available on most of the online book stores [1] . It took more than 18 months to complete the book. I tried my best to cover most of the commonly used features as well as basis of Axis2 . I believe the book will help you to overcome and clarify most of the unknown areas of Axis2 as well as to improve your knowledge on Axis2 . I have added a number of code samples to make the reader's job easier , I hope that will help you to understand the content very easy manner. You can find more information from [2] , [3]. [1] : http://www.packtpub.com/creating-web-services-with-apache-axis-2/book [2] : http://www.packtpub.com/article/create-quality-web-services-with-quicktstart-apache-axis2 [3] : http://blogs.deepal.org/2008/05/quickstart-axis2-my-first-book-on-axis2.html Thank you! Deepal http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN][Axis2] QuickStart Axis2 -- My first book on Axis2 is published
Congrats!!! On Fri, May 30, 2008 at 8:19 AM, Deepal jayasinghe [EMAIL PROTECTED] wrote: This is to inform you with great joy that I was able to complete my book on Axis2. The book is now published and available on most of the online book stores [1] . It took more than 18 months to complete the book. I tried my best to cover most of the commonly used features as well as basis of Axis2 . I believe the book will help you to overcome and clarify most of the unknown areas of Axis2 as well as to improve your knowledge on Axis2 . I have added a number of code samples to make the reader's job easier , I hope that will help you to understand the content very easy manner. You can find more information from [2] , [3]. [1] : http://www.packtpub.com/creating-web-services-with-apache-axis-2/book [2] : http://www.packtpub.com/article/create-quality-web-services-with-quicktstart-apache-axis2 [3] : http://blogs.deepal.org/2008/05/quickstart-axis2-my-first-book-on-axis2.html Thank you! Deepal http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN][Axis2] QuickStart Axis2 -- My first book on Axis2 is published
Looks very interesting. Do you have a sample chapter for the book? Cheers Sanjay -Original Message- From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Sent: 30 May 2008 13:19 To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: [ANN][Axis2] QuickStart Axis2 -- My first book on Axis2 is published This is to inform you with great joy that I was able to complete my book on Axis2. The book is now published and available on most of the online book stores [1] . It took more than 18 months to complete the book. I tried my best to cover most of the commonly used features as well as basis of Axis2 . I believe the book will help you to overcome and clarify most of the unknown areas of Axis2 as well as to improve your knowledge on Axis2 . I have added a number of code samples to make the reader's job easier , I hope that will help you to understand the content very easy manner. You can find more information from [2] , [3]. [1] : http://www.packtpub.com/creating-web-services-with-apache-axis-2/book [2] : http://www.packtpub.com/article/create-quality-web-services-wit h-quicktstart-apache-axis2 [3] : http://blogs.deepal.org/2008/05/quickstart-axis2-my-first-book- on-axis2.html Thank you! Deepal http://blogs.deepal.org - 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]
service_PortType and service
Hi, I have just noticed that sometimes the method serviceLocator.getService in the stubs I generate with wsdl2java returns a type of myService and at othertimes it returns a type of myService_PortType. I don't know what I have done during the generation to enforce this change. Can anybody tell me the reason for it? Paul Ockleford ** This message may contain confidential and privileged information. If you are not the intended recipient please accept our apologies. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Thank you for your co-operation. NHSmail is used daily by over 100,000 staff in the NHS. Over a million messages are sent every day by the system. To find out why more and more NHS personnel are switching to this NHS Connecting for Health system please visit www.connectingforhealth.nhs.uk/nhsmail ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: unexpected subelement exception
Hi, Thanks for your response. On further analysis on this problem I find that response xml's getting from two servers are different (JBOSS and glassfish). In Jboss we are getting namespace for all elements properly and in glassfish does not provide the namespace, because of which unexpected sub element exception is raised. Please help me in getting proper response from glassfish with namespaces. I had attached the SOAP response messages and wsdl along with this mail. Let me know if you need anymore information. _ M V Rajendra Kumar / Capgemini India / Hyderabad GE-UK Com1: +040-23125000-25072/ Mobile: 9959811162 www.capgemini.com http://www.capgemini.com/ #5,Software Units Layout,Madhapur,Hyderabad-82 Together. Free your energies _ Capgemini is a trading name used by the Capgemini Group of companies which includes Capgemini Country legal, a company registered in Country (number x) whose registered office is at insert head office address. From: Rushikesh Thakkar [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2008 4:44 PM To: axis-user@ws.apache.org Subject: Re: unexpected subelement exception Can you post relevant parts of WSDL? -Rushikesh On Fri, May 30, 2008 at 10:17 AM, Rajendra Kumar Miryala [EMAIL PROTECTED] wrote: Can anybody help on the below issue? From: Rajendra Kumar Miryala [mailto: [EMAIL PROTECTED] Sent: Monday, May 26, 2008 7:58 PM To: axis-user@ws.apache.org Subject: unexpected subelement exception Hi, I am getting below exception while receiving response from web-service. This service works fine on JBOS and exception is raised in the Glassfish (v9.1). I am using Axis2 1.2. Also using ADB data binding and axis2 code generation tools to generate the WSDL and stub class. The Element msgID is nillable=true (even with minoccurs = 0). Still service is expecting the value for msgID. Please help me in resolving the issue. Exception: Caused by: java.lang.RuntimeException: Unexpected subelement msgID at com.test.client.MyWebServiceStub$SummaryResponse$Factory.parse(MyWebServ iceStub.java:8704) at com.test.client.MyWebServiceStub$GetSummaryResponse$Factory.parse(MyWebS erviceStub.java:5279) at com.test.client.MyWebServiceStub.fromOM(MyWebServiceStub.java:26442) XSD definition in WSDL: xs:complexType name=SummaryResponse xs:sequence xs:element name=msgID nillable=true type=xs:string / xs:element name=statusCode nillable=true type=xs:string / /xs:sequence /xs:complexType Thanks In advance Rajendra This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. image001.gifimage002.gif?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns:SummaryResponse xmlns:ns=http://service.web.test.com/xsd; ns:return account xmlns=http://response.test.com/xsd; address xmlns=http://vo.test.com/xsd; faltNumber xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true / houseName8120475 Test Road/houseName houseNumber8120475/houseNumber postCode125/postCode /address blockCodes xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlbeans - Parser already accessed!
Hi I created a web service using Axis2-1.3, xmlbeans with MTOM attachments on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: Is this an error with AXIOM Serialization Any help would be appreciated. Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
Re: [axis-user] Axis Client with gSOAP server
Hi, It seems that the WSDL2Java doesn't not respect the wsdl ,because I successfully connect to the gsoap Webservice, after modifying the ServiceStub.java generated and when I look at the message sent by the client, it use magic/magic instead of ns1:magic/ns1:magic I I dont know why ^^. It will be really helpful if someone have an idea from where it can come from. Regards, Maxime. 2008/5/30 BRACHET Maxime [EMAIL PROTECTED]: Hi everybody, I try to use Axis to build a Web service client for a gSOAP server. I get a wsdl file from the server and use WSDL2Java to generate stub code. And, when I run my Client it said me this error : org.apache.axis.types.URI$MalformedURIException: Cannot initialize URI with empty parameters . I search on the Internet, but I cant fidn any solution or clues to resolve this error. To be more precise the gSOAP server is a magicservice from the samples on there website. Attach to this mail is the wsdl file and the Client Code file. If someone have an idea of when it could come from. Thanks in advance. Maxime.
AXIOM xmlbeans - Parser already accessed!
Found a similar bug in the following link https://issues.apache.org/jira/browse/AXIS2-3068?page=com.atlassian.jira .plugin \ I tried nightly build ... still the client throws the below exception. Any help or suggestion would be greatly appreciated. Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) Thanks Meena From: Karunanidhi, Meena Sent: 30 May 2008 14:28 To: 'axis-user@ws.apache.org'; '[EMAIL PROTECTED]' Subject: xmlbeans - Parser already accessed! Hi I created a web service using Axis2-1.3, xmlbeans with MTOM attachments on weblogic 8.1. The same code worked fine with ADB, but when I tried to do the same with xmlbeans throws the following exception: Is this an error with AXIOM Serialization Any help would be appreciated. Thanks - Meena Exception org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! org.apache.axis2.AxisFault: problem accessing the parser. Parser already accessed! at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessage Formatter.java:72) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisReque stEntity.java:84) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequest Body(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase .java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMe thodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho dDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 96) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 46) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac tHTTPSender.java:520) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 91) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:327) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:374) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA xisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 ) = -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately. Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. permanent tsb is a trading name of Irish Life Permanent plc which is regulated by the Financial Regulator and is a tied insurance agent for Irish Life Assurance plc. Irish Life Permanent plc is a limited liability company registered in Dublin under No. 222332. The company's registered office is: Irish Life Centre, Lower Abbey Street, Dublin 1. ==
Re: Axis2 1.4 not Thread safe (possible bug)
sultanat wrote: Is someone working to fix this bug? This is not a bug as I see this.. but a case where the http/s transport does not yet support pipelining. It would be easier to turn this off from your client side. asankha asankha wrote: Chuck Brinkman wrote: We are seeing responses of one type that have the body of another type. For example say we have serviceA that returns a serviceAresponse and serviceB that returns a serviceBresponse. We have captured the network packet and see things like serviceAresponse that has the data from a serviceBresponse. It appears to be related to a flash client we have. The flash client will open a connection and can send a second request using the original connection before it gets a response or a timeout from the first request. I'm still working on the issue but it is in some way good to know that I'm not the only one thinking Axis2 has a thread safety issue. Your flash client is using HTTP pipelining http://en.wikipedia.org/wiki/HTTP_pipelining and this seems like a limitation/bug on the http/s transport, and not necessarily an Axis2 thread safety issue. Can you post the tcpdump traces you have? asankha
Axis logging problem
Hi All, This question is about axis logging. I have declared my PropertyConfigurator.configure for webs service in web service constructor and deployed the web service. But when I request a web service the logging informations are not been created. The tomcat could not load the PropertyConfigurator also the logged information to be written into a file, rather here it was writing in to the console(catalina.out file) Please help me to fix this issue Regards, Thamizhannal P - Save all your chat conversations. Find them online.
Re: [Axis2] valid SOAP operations
AxisService service = messageContext.getAxisService()
Jack Sprat [EMAIL PROTECTED] wrote: Where/how do I get the AxisService object
in the code sample below?
The code will be in the invoke method of my handler class that is invoked in
the InFlow phase.
Thanks.
T
Eran Chinthaka [EMAIL PROTECTED] wrote:
AxisService service; // your axis service
String action = messageContext.getSoapAction();
AxisOperation op = service.getOperationBySOAPAction(action);
if (op == null) {
op = service.getOperationByAction(action);
}
Please see [1] for more details.
HTH,
Chinthaka
[1] :
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/dispatchers/ActionBasedOperationDispatcher.java?view=markup
On Tue, May 27, 2008 at 10:58 AM, Jack Sprat [EMAIL PROTECTED] wrote:
I think I've made the question more complicated than it needed to be.
All I really need to know is whether the valid SOAP operations for a service
are available in an Axis2 class somewhere?
Something like getValidSOAPOpeations() that returns a list would be ideal.
Otherwise I'll need to hard-code constants for each operation in the WSDL and
compare the results of getSOAPAction to each one.
Thanks,
T
keith chapman [EMAIL PROTECTED] wrote: Why not write a custom dispatcher
that does this. After all this is what your trying to do (Dispatch to an
operation using some custom information). You can have a look at the inbuilt
dispatchers tp get an idea. Its pretty simple to write a new one.
Thanks,
Keith.
On Tue, May 27, 2008 at 8:33 PM, Jack Sprat [EMAIL PROTECTED] wrote:
What I am trying to do is validate the SOAP operation invoked in the handler
class so I can take the appropriate action.
I've found that many clients trying to consume the service don't know much
about web services so they may send a request with no SOAPAction header or an
invalid one.
For example, my valid operations may be echo and calculate. Can these 2
operations be determined programatically somehow? I'd like to get the valid
operations this way and compare what I got from the getSOAPAction() method to
see if I got a valid operation. Basically, I'm trying to avoid hard-coding the
operations in my Java code.
Thanks,
T
keith chapman [EMAIL PROTECTED] wrote: Hi Jack,
Can you state your requirement more clearly, that should help us provide you
with a clear answer too. I couldn't understand what you are intending to do
Thanks,
Keith.
On Tue, May 27, 2008 at 7:50 PM, Jack Sprat [EMAIL PROTECTED] wrote:
I have a service that invokes a handler at the InFlow phase. Is there a way
to programatically determine the valid SOAP operations at this point? I'd like
to compare the value from getSOAPAction() to ensure a valid operation was
requested.
I'm open to a better way of doing this.
Thanks,
T.
Re: Axis2 (ADB) : Problem with empty RequestBody
The part that I can see as the problem is the last one where the request is written to the wire. I can't understand how the content type became application/x-www-form-urlencoded (should have been text/xml for soap1.1. Since I see the SOAPAction header I suppose its 1.1). Is there any other configuration regarding the httpclient ? (that may have changed its behavior) Ajith On Fri, May 30, 2008 at 8:01 AM, Aljen7 [EMAIL PROTECTED] wrote: I can see thanks to dubugging that the soapEnvelope in request is constructed in Stub class correctly and it remains unchainged during axis2 engine which ended in the correct request calling messageContext is OK (afaik). Then why is it changed (empty - no body) when it comes to server. -- View this message in context: http://www.nabble.com/Axis2-%28ADB%29-%3A-Problem-with-empty-RequestBody-tp17532435p17557256.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu Reading, after a certain age, diverts the mind too much from its creative pursuits. Any man who reads too much and uses his own brain too little falls into lazy habits of thinking - Albert Einstein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: unexpected subelement exception
Rajendra, I've seen this error while working with Axis 1.4. This error normally occurs when the SOAP message contains an element which is *not present in the WSDL*. I don't think it has anything to do with server. I would advise you to run wsdl2java once again and deploy the same war on both the servers. The other possibility could be *different set of jars on both servers*, esp. related to xml and SOAP. As I see the portion of WSDL you posted in the first msg, it doesn't even contain definition of 'account' element that's found in SOAP messages that you've posted. So, it looks like a WSDL problem in general. Correct me if I'm pointing to a wrong direction. regards, - Rushikesh On Fri, May 30, 2008 at 3:20 PM, Rajendra Kumar Miryala [EMAIL PROTECTED] wrote: Hi, Thanks for your response. On further analysis on this problem I find that response xml's getting from two servers are different (JBOSS and glassfish). In Jboss we are getting namespace for all elements properly and in glassfish does not provide the namespace, because of which unexpected sub element exception is raised. Please help me in getting proper response from glassfish with namespaces. I had attached the SOAP response messages and wsdl along with this mail. Let me know if you need anymore information. _ M V Rajendra Kumar / *Capgemini India **/* Hyderabad GE-UK Com1: +040-23125000-25072/ Mobile: 9959811162 www.capgemini.com #5,Software Units Layout,Madhapur,Hyderabad-82 *Together. Free your energies* _ *Capgemini is a trading name used by the Capgemini Group of companies which includes Capgemini Country legal, a company registered in Country (number x) whose registered office is at insert head office address. * -- *From:* Rushikesh Thakkar [mailto:[EMAIL PROTECTED] *Sent:* Friday, May 30, 2008 4:44 PM *To:* axis-user@ws.apache.org *Subject:* Re: unexpected subelement exception Can you post relevant parts of WSDL? -Rushikesh On Fri, May 30, 2008 at 10:17 AM, Rajendra Kumar Miryala [EMAIL PROTECTED] wrote: Can anybody help on the below issue? -- *From:* Rajendra Kumar Miryala [mailto: [EMAIL PROTECTED] *Sent:* Monday, May 26, 2008 7:58 PM *To:* axis-user@ws.apache.org *Subject:* unexpected subelement exception Hi, I am getting below exception while receiving response from web-service. This service works fine on JBOS and exception is raised in the Glassfish (v9.1). I am using Axis2 1.2. Also using ADB data binding and axis2 code generation tools to generate the WSDL and stub class. The Element msgID is nillable=true (even with minoccurs = 0). Still service is expecting the value for msgID. Please help me in resolving the issue. Exception: Caused by: java.lang.RuntimeException: Unexpected subelement msgID at com.test.client.MyWebServiceStub$SummaryResponse$Factory.parse(MyWebServiceStub.java:8704) at com.test.client.MyWebServiceStub$GetSummaryResponse$Factory.parse(MyWebServiceStub.java:5279) at com.test.client.MyWebServiceStub.fromOM(MyWebServiceStub.java:26442) XSD definition in WSDL: xs:complexType name=SummaryResponse xs:sequence xs:element name=msgID nillable=true type=xs:string / xs:element name=statusCode nillable=true type=xs:string / /xs:sequence /xs:complexType Thanks In advance Rajendra This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
WSDL 2.0 and REST article
I've just published an article entitled Describe REST Web services with WSDL 2.0 [1] on developerWorks. I think this will be useful to the Web services community so I thought I'd share the link. [1] http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/ Lawrence Mandel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
org.apache.axis2.databinding.ADBException: !!!Unexpected subelement item
I have a third party web service I'm trying to call, but I keep getting databinding exceptions from the response. I used ADB to generate a stub class from their wsdl and it looks like the problem is related to a problem with xml namespaces... If I hack the generated stub class like the following the exception goes away, but it feels like a less than optimal way to go: change occurances of this in the stub class: javax.xml.namespace.QName(http://xml.apache.org/xml-soap,item;) javax.xml.namespace.QName(http://xml.apache.org/xml-soap,key;) into this: javax.xml.namespace.QName(item) javax.xml.namespace.QName(key) 17:54:44,720 DEBUG [content] ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyns3:runCustomer xmlns:ns3=http://docstyle.webservices;ns3:dhd_usermyuser/ns3:dhd_userns3:dhd_passwordblahblah/ns3:dhd_passwordns3:dhd_roleWebServicesSub/ns3:dhd_rolens3:modeCustomer_Cancel/ns3:modens3:merch_id383/ns3:merch_idns3:cust_id123123/ns3:cust_idns3:cust_fnametrue/ns3:cust_fnamens3:cust_lnametrue/ns3:cust_lnamens3:cust_email[EMAIL PROTECTED]/ns3:cust_emailns3:sub_usernametrue/ns3:sub_usernamens3:sub_passwordtrue/ns3:sub_passwordns3:cust_mail_statustrue/ns3:cust_mail_statusns3:cust_id_exttrue/ns3:cust_id_extns3:sub_cancel_datetrue/ns3:sub_cancel_datens3:addr_addresstrue/ns3:addr_addressns3:addr_citytrue/ns3:addr_cityns3:addr_statetrue/ns3:addr_statens3:addr_countrytrue/ns3:addr_countryns3:addr_ziptrue/ns3:addr_zipns3:cust_phonetrue/ns3:cust_phone/ns3:runCustomer/soapenv:Body/soapenv:Envelope 17:54:44,743 DEBUG [EntityEnclosingMethod] Request body sent 17:54:45,242 DEBUG [header] HTTP/1.1 200 OK[\r][\n] 17:54:45,243 DEBUG [header] Date: Fri, 30 May 2008 00:54:44 GMT[\r][\n] 17:54:45,243 DEBUG [header] Server: Apache/1.3.39 (Unix) JRun/4.0 mod_ssl/2.8.30 OpenSSL/0.9.8g mod_perl/1.29[\r][\n] 17:54:45,243 DEBUG [header] Content-Language: en-US[\r][\n] 17:54:45,243 DEBUG [header] Transfer-Encoding: chunked[\r][\n] 17:54:45,243 DEBUG [header] Content-Type: text/xml; charset=utf-8[\r][\n] 17:54:45,267 DEBUG [content] 3 17:54:45,267 DEBUG [content] 8 17:54:45,267 DEBUG [content] 2 17:54:45,268 DEBUG [content] [\r] 17:54:45,268 DEBUG [content] [\n] 17:54:45,268 DEBUG [content] ?xm 17:54:45,270 DEBUG [content] l version=1.0 encoding=UTF-8?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;[\n] 17:54:45,270 DEBUG [content] soapenv:Body[\n] 17:54:45,271 DEBUG [content] runCustomerResponse xmlns=http://docstyle.webservices;[\n] 17:54:45,274 DEBUG [content] runCustomerReturn xsi:type=ns1:Map xmlns:ns1=http://xml.apache.org/xml-soap;[\n] 17:54:45,275 DEBUG [content] item xmlns=[\n] 17:54:45,275 DEBUG [content] key xsi:type=xsd:stringSTATUS/key[\n] 17:54:45,275 DEBUG [content] value xsi:type=xsd:stringTRUE/value[\n] 17:54:45,275 DEBUG [content] /item[\n] 17:54:45,275 DEBUG [content] item xmlns=[\n] 17:54:45,275 DEBUG [content] key xsi:type=xsd:stringMESSAGE/key[\n] 17:54:45,275 DEBUG [content] value xsi:type=xsd:stringCustomer has been successfully cancelled on 28-Jun-2008/value[\n] 17:54:45,275 DEBUG [content] /item[\n] 17:54:45,275 DEBUG [content] item xmlns=[\n] 17:54:45,276 DEBUG [content] key xsi:type=xsd:stringMETHOD/key[\n] 17:54:45,276 DEBUG [content] value xsi:type=xsd:stringdhd_cfcs.customers/value[\n] 17:54:45,276 DEBUG [content] /item[\n] 17:54:45,276 DEBUG [content] /runCustomerReturn[\n] 17:54:45,276 DEBUG [content] /runCustomerResponse[\n] 17:54:45,276 DEBUG [content] /soapenv:Body[\n] 17:54:45,276 DEBUG [content] /soapenv:Envelope 17:54:45,314 DEBUG [content] [\r] 17:54:45,314 DEBUG [content] [\n] 17:54:45,315 DEBUG [content] 0 17:54:45,315 DEBUG [content] [\r] 17:54:45,315 DEBUG [content] [\n] 17:54:45,315 DEBUG [content] [\r] 17:54:45,315 DEBUG [content] [\n] 17:54:45,315 DEBUG [HttpMethodBase] Resorting to protocol version default close connection policy 17:54:45,315 DEBUG [HttpMethodBase] Should NOT close connection, using HTTP/1.1 17:54:45,315 DEBUG [HttpConnection] Releasing connection back to connection manager. 17:54:45,315 DEBUG [MultiThreadedHttpConnectionManager] Freeing connection, hostConfig=HostConfiguration[host=https://secure.dhdmedia.com] 17:54:45,315 DEBUG [IdleConnectionHandler] Adding connection at: 1212108885315 17:54:45,315 DEBUG [MultiThreadedHttpConnectionManager] Notifying no-one, there are no waiting threads 17:54:45,315 ERROR [AccountMgrBean] Error cancelling dhd account: org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: !!!Unexpected subelement item at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at com.kink.heart.biz.billing.i.dhd.CustomersWebserviceStub.fromOM(CustomersWebserviceStub.java:4959) at
Re: [ANN][Axis2] QuickStart Axis2 -- My first book on Axis2 is published
Congrats Deepal, Remember all the discussions Srinath et al had about writing a book on axis2. I am very happy that it finnaly came to life. Regards, Rajith Attapattu http://rajith.2rlabs.com/ On Fri, May 30, 2008 at 8:19 AM, Deepal jayasinghe [EMAIL PROTECTED] wrote: This is to inform you with great joy that I was able to complete my book on Axis2. The book is now published and available on most of the online book stores [1] . It took more than 18 months to complete the book. I tried my best to cover most of the commonly used features as well as basis of Axis2 . I believe the book will help you to overcome and clarify most of the unknown areas of Axis2 as well as to improve your knowledge on Axis2 . I have added a number of code samples to make the reader's job easier , I hope that will help you to understand the content very easy manner. You can find more information from [2] , [3]. [1] : http://www.packtpub.com/creating-web-services-with-apache-axis-2/book [2] : http://www.packtpub.com/article/create-quality-web-services-with-quicktstart-apache-axis2 [3] : http://blogs.deepal.org/2008/05/quickstart-axis2-my-first-book-on-axis2.html Thank you! Deepal http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN][Axis2] QuickStart Axis2 -- My first book on Axis2 is published
Congrats Deepal !!!, glad to see it is get done at last :) --Srinath On Fri, May 30, 2008 at 3:13 PM, Rajith Attapattu [EMAIL PROTECTED] wrote: Congrats Deepal, Remember all the discussions Srinath et al had about writing a book on axis2. I am very happy that it finnaly came to life. Regards, Rajith Attapattu http://rajith.2rlabs.com/ On Fri, May 30, 2008 at 8:19 AM, Deepal jayasinghe [EMAIL PROTECTED] wrote: This is to inform you with great joy that I was able to complete my book on Axis2. The book is now published and available on most of the online book stores [1] . It took more than 18 months to complete the book. I tried my best to cover most of the commonly used features as well as basis of Axis2 . I believe the book will help you to overcome and clarify most of the unknown areas of Axis2 as well as to improve your knowledge on Axis2 . I have added a number of code samples to make the reader's job easier , I hope that will help you to understand the content very easy manner. You can find more information from [2] , [3]. [1] : http://www.packtpub.com/creating-web-services-with-apache-axis-2/book [2] : http://www.packtpub.com/article/create-quality-web-services-with-quicktstart-apache-axis2 [3] : http://blogs.deepal.org/2008/05/quickstart-axis2-my-first-book-on-axis2.html Thank you! Deepal http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Srinath Perera: Indiana University, Bloomington http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN][Axis2] QuickStart Axis2 -- My first book on Axis2 is published
Congratulations Deepal. Chathura On Fri, May 30, 2008 at 9:19 AM, Deepal jayasinghe [EMAIL PROTECTED] wrote: This is to inform you with great joy that I was able to complete my book on Axis2. The book is now published and available on most of the online book stores [1] . It took more than 18 months to complete the book. I tried my best to cover most of the commonly used features as well as basis of Axis2 . I believe the book will help you to overcome and clarify most of the unknown areas of Axis2 as well as to improve your knowledge on Axis2 . I have added a number of code samples to make the reader's job easier , I hope that will help you to understand the content very easy manner. You can find more information from [2] , [3]. [1] : http://www.packtpub.com/creating-web-services-with-apache-axis-2/book [2] : http://www.packtpub.com/article/create-quality-web-services-with-quicktstart-apache-axis2 [3] : http://blogs.deepal.org/2008/05/quickstart-axis2-my-first-book-on-axis2.html Thank you! Deepal http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Chathura Herath http://people.apache.org/~chathura/ http://chathurah.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN][Axis2] QuickStart Axis2 -- My first book on Axis2 is published
Congrats Deepal !! So when will the committers get the free copy? Don't worry about using some one like FedEx, just USPS is fine ;) On Fri, May 30, 2008 at 3:21 PM, Chathura Herath [EMAIL PROTECTED] wrote: Congratulations Deepal. Chathura On Fri, May 30, 2008 at 9:19 AM, Deepal jayasinghe [EMAIL PROTECTED] wrote: This is to inform you with great joy that I was able to complete my book on Axis2. The book is now published and available on most of the online book stores [1] . It took more than 18 months to complete the book. I tried my best to cover most of the commonly used features as well as basis of Axis2 . I believe the book will help you to overcome and clarify most of the unknown areas of Axis2 as well as to improve your knowledge on Axis2 . I have added a number of code samples to make the reader's job easier , I hope that will help you to understand the content very easy manner. You can find more information from [2] , [3]. [1] : http://www.packtpub.com/creating-web-services-with-apache-axis-2/book [2] : http://www.packtpub.com/article/create-quality-web-services-with-quicktstart-apache-axis2 [3] : http://blogs.deepal.org/2008/05/quickstart-axis2-my-first-book-on-axis2.html Thank you! Deepal http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Chathura Herath http://people.apache.org/~chathura/http://people.apache.org/%7Echathura/ http://chathurah.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- With Mettha, Eran Chinthaka Health is the greatest gift; contentment is the greatest wealth; trusting is the best relationship; nirvana is the highest joy. - Dhammapada
Re: [Axis2] valid SOAP operations
Ok now I am getting the picture here.
Are you trying to make sure the SOAP message that is just received has a
proper operation name in it. If that is the case, don't worry about that, we
are already doing that for you within dispatch phase. Dispatching is all
about finding the correct service and operation. If we can not find it, we
will send an error to the user, before the end of the dispatch phase. So
your handler will be redundant if you put it.
HTH
Chinthaka
On Fri, May 30, 2008 at 8:16 AM, Jack Sprat [EMAIL PROTECTED] wrote:
AxisService service = messageContext.getAxisService()
*Jack Sprat [EMAIL PROTECTED]* wrote:
Where/how do I get the AxisService object in the code sample below?
The code will be in the invoke method of my handler class that is invoked
in the InFlow phase.
Thanks.
T
*Eran Chinthaka [EMAIL PROTECTED]* wrote:
AxisService service; // your axis service
String action = messageContext.getSoapAction();
AxisOperation op = service.getOperationBySOAPAction(action);
*if* (op == *null*) {
op = service.getOperationByAction(action);
}
Please see [1] for more details.
HTH,
Chinthaka
[1] :
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/dispatchers/ActionBasedOperationDispatcher.java?view=markup
On Tue, May 27, 2008 at 10:58 AM, Jack Sprat [EMAIL PROTECTED]
wrote:
I think I've made the question more complicated than it needed to be.
All I really need to know is whether the valid SOAP operations for a
service are available in an Axis2 class somewhere?
Something like getValidSOAPOpeations() that returns a list would be
ideal. Otherwise I'll need to hard-code constants for each operation in the
WSDL and compare the results of getSOAPAction to each one.
Thanks,
T
*keith chapman [EMAIL PROTECTED]* wrote:
Why not write a custom dispatcher that does this. After all this is what
your trying to do (Dispatch to an operation using some custom information).
You can have a look at the inbuilt dispatchers tp get an idea. Its pretty
simple to write a new one.
Thanks,
Keith.
On Tue, May 27, 2008 at 8:33 PM, Jack Sprat [EMAIL PROTECTED]
wrote:
What I am trying to do is validate the SOAP operation invoked in the
handler class so I can take the appropriate action.
I've found that many clients trying to consume the service don't know
much about web services so they may send a request with no SOAPAction header
or an invalid one.
For example, my valid operations may be echo and calculate. Can these 2
operations be determined programatically somehow? I'd like to get the valid
operations this way and compare what I got from the getSOAPAction() method
to see if I got a valid operation. Basically, I'm trying to avoid
hard-coding the operations in my Java code.
Thanks,
T
*keith chapman [EMAIL PROTECTED]* wrote:
Hi Jack,
Can you state your requirement more clearly, that should help us provide
you with a clear answer too. I couldn't understand what you are intending to
do
Thanks,
Keith.
On Tue, May 27, 2008 at 7:50 PM, Jack Sprat [EMAIL PROTECTED]
wrote:
I have a service that invokes a handler at the InFlow phase. Is there a
way to programatically determine the valid SOAP operations at this point?
I'd like to compare the value from getSOAPAction() to ensure a valid
operation was requested.
I'm open to a better way of doing this.
Thanks,
T.
http://www.keith-chapman.org
--
With Mettha,
Eran Chinthaka
Health is the greatest gift; contentment is the greatest wealth; trusting is
the best relationship; nirvana is the highest joy. - Dhammapada
Re: Axis2 1.4 not Thread safe (possible bug)
Sounds like you are about to volunteer to fix this. Great, welcome to Axis2 ;) On Thu, May 29, 2008 at 4:58 PM, sultanat [EMAIL PROTECTED] wrote: Is someone working to fix this bug? asankha wrote: Chuck Brinkman wrote: We are seeing responses of one type that have the body of another type. For example say we have serviceA that returns a serviceAresponse and serviceB that returns a serviceBresponse. We have captured the network packet and see things like serviceAresponse that has the data from a serviceBresponse. It appears to be related to a flash client we have. The flash client will open a connection and can send a second request using the original connection before it gets a response or a timeout from the first request. I'm still working on the issue but it is in some way good to know that I'm not the only one thinking Axis2 has a thread safety issue. Your flash client is using HTTP pipelining http://en.wikipedia.org/wiki/HTTP_pipelining and this seems like a limitation/bug on the http/s transport, and not necessarily an Axis2 thread safety issue. Can you post the tcpdump traces you have? asankha -- View this message in context: http://www.nabble.com/Axis2-1.4-not-Thread-safe-%28possible-bug%29-tp17414803p17548699.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- With Mettha, Eran Chinthaka Health is the greatest gift; contentment is the greatest wealth; trusting is the best relationship; nirvana is the highest joy. - Dhammapada
Re: Update on compiling source and a little feedback
Hi Seref, you can make the life better of the other newcomers, if you have some time to help. Please checkout our source code, and improve the documentation. Then if you can send a patch, one of our existing committers can review that and apply it. So that in the next release everyone will get better docs. This is a community effort and your contribution and feedback is greatly appreciated. On Fri, May 30, 2008 at 12:46 AM, Seref Arikan [EMAIL PROTECTED] wrote: Hi, I've previously had some problems with compiling Axis2 source code, mainly due to issues with tests failing during compilation. I've tried jdk 6 and 5, and many other tweak, but I could not manage to get maven compile sources without any errors. I've decided to try something different, and I've setup Ubuntu 8.04. Switching from XP sp2 to Ubuntu worked for me, and I've managed to compile both Axis2 1.4 source release and the latest code I've checked out from svn using both jdk 5 and 6 However, I could not compile 1.3, neither with jdk5 nor with 6. Actually jdk 6 appears to be a no go for 1.3 anyway. Tests still fail (2 failures actually) for 1.3 with maven 2.0.9 . The feedback is: there are still ant build files and instructions in readme files. However, some of the instructions related to ant are out of date. For example to create eclipse plugin projects, if you choose the ant way, you are expected to do a maven create-lib according to docs, but this is not possible, since maven is used in maven 1.x and mvn is used in maven 2. Axis2 uses maven 2 so this part of the doc is broken I guess. The doc does not mention that you can do mvn eclipse:eclipse in eclipse tools dirs to get plugin projects, and when you do that, the libs that the plugin project require are not copied to lib folder of the generated project. Overall, the process requires a little digging, considerably more if you are not used to maven, and I've still not managed to get 1.3 source to compile. Still, I'm very glad that I've reached a point where I can see the bigger picture much better, and I'd like to thank to all contributers for making such a great piece of work available. All the best Seref -- With Mettha, Eran Chinthaka Health is the greatest gift; contentment is the greatest wealth; trusting is the best relationship; nirvana is the highest joy. - Dhammapada
Re: Webservice on SSL (HTTPS)
Keith, I think enabling https, will allow the client to access the service over https. But the question seems to be how to tell axis2 about the new https transport receiver. I also like to know the answer to this. (this is a question I got from my friend Ruwan also). basically once you configure Tomcat to use https, how can you tell Axis2 about this so that it will https as a transport binding in the WSDL? On Tue, May 27, 2008 at 7:35 AM, keith chapman [EMAIL PROTECTED] wrote: Hi Sandeep, All you need to do is enable https transport in Axis2 via the axis2.xml. It may be enabled already (check your axis2.xml). Now you should be able to access your service over https. Thanks, Keith. On Tue, May 27, 2008 at 7:26 PM, sandeep_khurana [EMAIL PROTECTED] wrote: I have made a simple webservice to work on HTTP. Now I want to make it run on HTTPS, I have configured my Tomcat for HTTPS. Can anybody give me steps of hosting my webservice on HTTPS (so that my wsdl is available on HTTPS)? Are there any configurational changes that I need to make? Thanks in advance. -- View this message in context: http://www.nabble.com/Webservice-on-SSL-%28HTTPS%29-tp17491012p17491012.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- With Mettha, Eran Chinthaka Health is the greatest gift; contentment is the greatest wealth; trusting is the best relationship; nirvana is the highest joy. - Dhammapada
Re: [Axis2] valid SOAP operations
It's not quite as simple as that. In this case, I was to bypass the
authentication if a simple echo request is received. So I need to ensure the
SOAPAction is valid and then check whether it is an echo request. If it is an
echo then continue. If not, then authenticate the user in the SOAP header.
Thanks,
T
Eran Chinthaka [EMAIL PROTECTED] wrote: Ok now I am getting the picture here.
Are you trying to make sure the SOAP message that is just received has a proper
operation name in it. If that is the case, don't worry about that, we are
already doing that for you within dispatch phase. Dispatching is all about
finding the correct service and operation. If we can not find it, we will send
an error to the user, before the end of the dispatch phase. So your handler
will be redundant if you put it.
HTH
Chinthaka
On Fri, May 30, 2008 at 8:16 AM, Jack Sprat [EMAIL PROTECTED] wrote:
AxisService service = messageContext.getAxisService()
Jack Sprat [EMAIL PROTECTED] wrote: Where/how do I get the AxisService
object in the code sample below?
The code will be in the invoke method of my handler class that is invoked in
the InFlow phase.
Thanks.
T
Eran Chinthaka [EMAIL PROTECTED] wrote:
AxisService service; // your axis service
String action = messageContext.getSoapAction();
AxisOperation op = service.getOperationBySOAPAction(action);
if (op ==
null) {
op = service.getOperationByAction(action);
}
Please see [1] for more details.
HTH,
Chinthaka
[1] :
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/dispatchers/ActionBasedOperationDispatcher.java?view=markup
On Tue, May 27, 2008 at 10:58 AM, Jack Sprat [EMAIL PROTECTED] wrote:
I think I've made the question more complicated than it needed to be.
All I really need to know is whether the valid SOAP operations for a service
are available in an Axis2 class somewhere?
Something like getValidSOAPOpeations() that returns a list would be ideal.
Otherwise I'll need to hard-code constants for each operation in the WSDL and
compare the results of getSOAPAction to each one.
Thanks,
T
keith chapman [EMAIL PROTECTED] wrote: Why not write a custom dispatcher
that does this. After all this is what your trying to do (Dispatch to an
operation using some custom information). You can have a look at the inbuilt
dispatchers tp get an idea. Its pretty simple to write a new one.
Thanks,
Keith.
On Tue, May 27, 2008 at 8:33 PM, Jack Sprat [EMAIL PROTECTED] wrote:
What I am trying to do is validate the SOAP operation invoked in the handler
class so I can take the appropriate action.
I've found that many clients trying to consume the service don't know much
about web services so they may send a request with no SOAPAction header or an
invalid one.
For example, my valid operations may be echo and calculate. Can these 2
operations be determined programatically somehow? I'd like to get the valid
operations this way and compare what I got from the getSOAPAction() method to
see if I got a valid operation. Basically, I'm trying to avoid hard-coding the
operations in my Java code.
Thanks,
T
keith chapman [EMAIL PROTECTED] wrote:Hi Jack,
Can you state your requirement more clearly, that should help us provide you
with a clear answer too. I couldn't understand what you are intending to do
Thanks,
Keith.
On Tue, May 27, 2008 at 7:50 PM, Jack Sprat [EMAIL PROTECTED] wrote:
I have a service that invokes a handler at the InFlow phase. Is there a way
to programatically determine the valid SOAP operations at this point? I'd like
to compare the value from getSOAPAction() to ensure a valid operation was
requested.
I'm open to a better way of doing this.
Thanks,
T.
