axis2/c using openSSL with no-idea no-mdc2 no-rc5
Hi There, I am using axis2/c to develop a web service client application. I use openSSL to web service https/SSL communication. In order to avoid the patent issue for the portion of openSSL, I build the openSSL libraries myself using ./config no-idea no-mdc2 no-rc5. All is working fine as far as I am concerned, my client application can talk to web service server through https. Now my question is: What cypto algorith is actually used in the https/SSL communication? What is really turned off by using no-idea no-mdc2 no-rc5? If these things are not needed, then why they are there? Thanks much! Raymond
Exception deserialization problem
We have a server application running in WebSphere 6.1 and a client using Axis 1.4. Both the server and client are Java applications running in Java 1.4.2. The server and client side Java is generated from WSDL using axis and websphere ant target's wsdl2java. The server throws custom checked exceptions and we try to catch these on the client side. The problem is that they appear only as AxisFault with the textual part as the fully qualified name of the server exception that was thrown. We are expecting the client exception that corresponds to the server exception. The exception I'm currently investigating is an exception containing no extra data. I have used a network analyzer and found the web service data sent by WebSphere to the client, which shows how the exception is serialized for sending to the client. See data content for the message sent here: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header/ soapenv:Body soapenv:Fault faultcode xmlns:p799=http://backend.product.company.com; p799:PassengerNotExistException /faultcode faultstring ![CDATA[com.company.product.webservice.backend.server.PassengerNotExistException]] /faultstring detail encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; fault href=#id0/ /detail /soapenv:Fault multiRef id=id0 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=p799:PassengerNotExistException xmlns:p799=http://backend.product.company.com/ /soapenv:Body /soapenv:Envelope It can be seen that the exception is serialized in some way but I do not know if the problem is that Axis cannot deserialize this format to the correct exception and therefore gives the AxisFault instead ? Do anyone have the knowledge if the given message above should be possible for Axis to deserialize? or if the problem is interoperability between WebSphere and Axis ? I reckon the information on the exception issues in webservices are sparsely documented at best. Here follows an excerpt of the WSDL specifications. wsdl:types xsd:schema targetNamespace=http://backend.product.company.com; xsd:complexType name=PassengerNotExistException sequence / /xsd:complexType /wsdl:types wsdl:message name=PassengerNotExistException wsdl:part name=fault type=backend:PassengerNotExistException / /wsdl:message wsdl:portType name=BackendInterface wsdl:operation name=getClients wsdl:input message=... / wsdl:output message=... / wsdl:fault name=PassengerNotExistException message=backend:PassengerNotExistException / /wsdl:operation /wsdl:portType wsdl:binding name=BackendInterfaceSOAP type=backend:BackendInterface soap:binding style=rpc transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=getClients soap:operation soapAction=http://backend.product.company.com/getClients; / wsdl:input soap:body use=encoded encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://backend.product.company.com; / /wsdl:input wsdl:output soap:body use=encoded encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://backend.product.company.com; / /wsdl:output wsdl:fault name=PassengerNotExistException soap:fault name=PassengerNotExistException use=encoded encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://backend.product.company.com; / /wsdl:fault /wsdl:operation /wsdl:binding Thankful for any help or insight on the problem! Regards Henrik
Re: namespaces error
Could you post the schema section in the WSDL that describes GetOrderDetails. That would give us a clue to whats wrong. Thanks, Keith. On Tue, Oct 14, 2008 at 5:02 PM, Harm de Laat [EMAIL PROTECTED] wrote: Hi all, I'm having great difficulties calling a BizTalk webservice using axis2 (1.4.1) with ADB. I have generated my client using the following command: wsdl2java.sh -uri http://x.x.x.x/WebServices/AdvPortal/MDC/WebService_Sanoma_BizTalk_AdvertentiePortal_MDC.asmx?WSDL-p nl.kabisa.sanoma.webservices -d adb -s This generates all classes and using my (test)client I get to call the service. This generates the following SOAP message: soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Body ns3:GetOrderDetails xmlns:ns3= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; OrderInfo xmlns= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb Referentienummer123456.123/Referentienummer /OrderInfo /ns3:GetOrderDetails /soapenv:Body /soapenv:Envelope However, this call gets discarded by the BizTalk server. When I manually modify the soap message to the message below everything is fine. (Notice the ns2 namespace): soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Body ns3:GetOrderDetails xmlns:ns3= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; n2:OrderInfo xmlns:n2= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb Referentienummer123456.123/Referentienummer /n2:OrderInfo /ns3:GetOrderDetails /soapenv:Body /soapenv:Envelope What is going on here? Why is the NS2 namespace missing in the Axis2 generated Soap message? Also, what can I do to make this relatively simple client work? Kind regards, -- Harm de Laat Kabisa ICT -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
Re: [Axis2]Help! How to create a SOAP service using Axis2 in my own webapp?
Thishttp://www.keith-chapman.org/2008/10/how-to-embed-axis2-into-existing-web.htmlshould give you a clue. I think thats what your looking for. Thanks, Keith. [1] http://www.keith-chapman.org/2008/10/how-to-embed-axis2-into-existing-web.html On Tue, Oct 14, 2008 at 6:21 AM, Tian Chi [EMAIL PROTECTED] wrote: Hi all, Sorry previous message is still in wrong text format, this is it again. I'm a newbie on using Axis2. After reading through most of the documents on this site, I still couldn't find the answer I need. I'd really apreciate it if someone can help me on this. All Axis2 documents I read on this site are to build new web services/client using Axis2. Currently I have already a big web app in use and I need to add a SOAP service to my web app using Axis2. Is that doable? If yes, what are the steps to make that happen? Is it possible to copy axis2.war into my servlet container (Resin) (both 'axis2' and 'myWebapp' directories under webapps directory) , create a SOAP service in the axis2 app and then forward the request (by deinfing the 'ServiceClass' parameter in services.xml?) to my own web app to handle some complicated database processes? It seems to me it's not doable. Please don't laugh at me if this question is too sily. If the previous approach is not possible. The only other apprach I can think of is to embed Axis2 in my own webapp. In that case, do I need to copy all the needed Axis2 jar files to my own web app in WEB-INF/lib directory? If so, what are the needed jar files for a SOAP service? Basically the SOAP service is receive data from my client, save it to database and respond to client with the results. There are many jar files in Axis2. I just hope to skip some unnecessary Axis2 jar files to avoid overhead since my own web app is already very big. Besides the Axis2 jar files, what else needs to be done to embed a SOAP service in my own web app? I'd really really appreciate it if someone gives me some guidance or shed some lights on this. Hope to hear from you soon. thank you very much, -tian - 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
Re: How to make non-webmethod in axis2 webservices?
ERaj wrote: Hi, I have a webservice which have few service methods (webmethods) and other methods to inject object into the service (through spring) but when I generate wsdl file or deploy with default wsdl, my non-webmethods are also visible to client. Actually I can't make the non-webmethods as private/protected because spring needs them as public. How to overcome this? Please let me know your suggestion. Cheers, Raja Have a look at the following article that will help you, just read how to exclude operation section. http://wso2.org/library/2060 Deepal -- Thank you! http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: namespaces error
Here is the complete WSDL file (I just commented out the IP address for the service). What may be worth of mentioning is that I tried using SOAPUI, which worked instantly with this specific WSDL. ?xml version=1.0 encoding=utf-8? wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/; xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:mime= http://schemas.xmlsoap.org/wsdl/mime/; xmlns:tns= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; xmlns:s1= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; xmlns:s=http://www.w3.org/2001/XMLSchema; xmlns:s2= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http= http://schemas.xmlsoap.org/wsdl/http/; targetNamespace= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; wsdl:documentation xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;BizTalk assembly Sanoma.BizTalk.AdvertentiePortal.MDC, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8c063b3a22630ca9 published web service./wsdl:documentation wsdl:types s:schema elementFormDefault=qualified targetNamespace= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; s:import namespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; / s:import namespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb; / s:element name=GetOrderDetails s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 ref=s1:OrderInfo / /s:sequence /s:complexType /s:element s:element name=GetOrderDetailsResponse s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 ref=s2:OrderInfoResult / /s:sequence /s:complexType /s:element /s:schema s:schema elementFormDefault=qualified targetNamespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; s:element name=OrderInfo s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 form=unqualified name=Referentienummer type=s:string / /s:sequence /s:complexType /s:element /s:schema s:schema elementFormDefault=qualified targetNamespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb; s:element name=OrderInfoResult s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 form=unqualified name=Referentienr type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=NameAdvertiser type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=TypeOfAd type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=titleId type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=editionId type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=orderStatus type=s:integer / s:element minOccurs=0 maxOccurs=1 form=unqualified name=returnCode type=s:integer / s:element minOccurs=0 maxOccurs=1 form=unqualified name=returnMessage type=s:string / /s:sequence /s:complexType /s:element /s:schema /wsdl:types wsdl:message name=GetOrderDetailsSoapIn wsdl:part name=parameters element=tns:GetOrderDetails / /wsdl:message wsdl:message name=GetOrderDetailsSoapOut wsdl:part name=parameters element=tns:GetOrderDetailsResponse / /wsdl:message wsdl:portType name=WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap wsdl:operation name=GetOrderDetails wsdl:input message=tns:GetOrderDetailsSoapIn / wsdl:output message=tns:GetOrderDetailsSoapOut / /wsdl:operation /wsdl:portType wsdl:binding name=WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap type=tns:WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap soap:binding transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=GetOrderDetails soap:operation soapAction= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/WebService_Sanoma_BizTalk_AdvertentiePortal_MDC/GetOrderDetails; style=document / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:binding name=WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap12 type=tns:WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap soap12:binding transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=GetOrderDetails soap12:operation soapAction= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/WebService_Sanoma_BizTalk_AdvertentiePortal_MDC/GetOrderDetails; style=document / wsdl:input soap12:body use=literal / /wsdl:input
Re: namespaces error
Looking at the WSDL it looks like a correct message should be of the form. soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Body ns3:GetOrderDetails xmlns:ns3= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; n2:OrderInfo xmlns:n2= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; ns3:Referentienummer123456.123/ns3:Referentienummer /n2:OrderInfo /ns3:GetOrderDetails /soapenv:Body /soapenv:Envelope Could you a sample message generated using SOAPUI. Thanks, Keith. On Tue, Oct 14, 2008 at 6:52 PM, Harm de Laat [EMAIL PROTECTED] wrote: Here is the complete WSDL file (I just commented out the IP address for the service). What may be worth of mentioning is that I tried using SOAPUI, which worked instantly with this specific WSDL. ?xml version=1.0 encoding=utf-8? wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/; xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:mime= http://schemas.xmlsoap.org/wsdl/mime/; xmlns:tns= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; xmlns:s1= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; xmlns:s=http://www.w3.org/2001/XMLSchema; xmlns:s2= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http= http://schemas.xmlsoap.org/wsdl/http/; targetNamespace= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; wsdl:documentation xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;BizTalk assembly Sanoma.BizTalk.AdvertentiePortal.MDC, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8c063b3a22630ca9 published web service./wsdl:documentation wsdl:types s:schema elementFormDefault=qualified targetNamespace= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; s:import namespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; / s:import namespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb; / s:element name=GetOrderDetails s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 ref=s1:OrderInfo / /s:sequence /s:complexType /s:element s:element name=GetOrderDetailsResponse s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 ref=s2:OrderInfoResult / /s:sequence /s:complexType /s:element /s:schema s:schema elementFormDefault=qualified targetNamespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb s:element name=OrderInfo s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 form=unqualified name=Referentienummer type=s:string / /s:sequence /s:complexType /s:element /s:schema s:schema elementFormDefault=qualified targetNamespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb s:element name=OrderInfoResult s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 form=unqualified name=Referentienr type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=NameAdvertiser type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=TypeOfAd type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=titleId type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=editionId type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=orderStatus type=s:integer / s:element minOccurs=0 maxOccurs=1 form=unqualified name=returnCode type=s:integer / s:element minOccurs=0 maxOccurs=1 form=unqualified name=returnMessage type=s:string / /s:sequence /s:complexType /s:element /s:schema /wsdl:types wsdl:message name=GetOrderDetailsSoapIn wsdl:part name=parameters element=tns:GetOrderDetails / /wsdl:message wsdl:message name=GetOrderDetailsSoapOut wsdl:part name=parameters element=tns:GetOrderDetailsResponse / /wsdl:message wsdl:portType name=WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap wsdl:operation name=GetOrderDetails wsdl:input message=tns:GetOrderDetailsSoapIn / wsdl:output message=tns:GetOrderDetailsSoapOut / /wsdl:operation /wsdl:portType wsdl:binding name=WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap type=tns:WebService_Sanoma_BizTalk_AdvertentiePortal_MDCSoap soap:binding transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=GetOrderDetails soap:operation soapAction=
ADBException: Unexpected subelement return
I've got a Java Client and Server using the Calculator.wsdl supplies with the original Axis (not Axis2). I've generated Axis2 bindings using WSDL2Java. I also have a client and server written in C++ using gSoap. I have no issue with both the Java and C++ clients communicating with the C++ Server. I am however having an issue with the Java Client and the Java Server (using SimpleHTTPServer). I'm getting the following exception from the Client. The C++ client works fine with the Java Server. org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement return at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at localhost.axis.calculator.CalculatorStub.fromOM(Unknown Source) at localhost.axis.calculator.CalculatorStub.add(Unknown Source) at localhost.axis.calculator.CalculatorClient.main(Unknown Source) Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: Unexpected subelement return at localhost.axis.calculator.AddResponse$Factory.parse(Unknown Source) ... 3 more Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement return ... 4 more I've attached the WSDL and Java Source Any help would be great. Best Regards, Jeremy Jeremy F. Audino Senior Software Development Engineer Philips Healthcare -- Nuclear Medicine Tel: 440-483-7444 E-mail: [EMAIL PROTECTED] The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. calculator.wsdl Description: calculator.wsdl CalculatorServer_SimpleAxisServer.java Description: CalculatorServer_SimpleAxisServer.java CalculatorClient.java Description: CalculatorClient.java CalculatorServer.java Description: CalculatorServer.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ADBException: Unexpected subelement return
Hi Jeremy, It looks like your WSDL is RPC encoded (Which is not supported by axis2). How about simply deploying the calculator service as a POJO and then using the generated WSDL to write your client. That should work for you just fine (The WSDL generated by Axis2 by default is doc/lit). Thanks, Keith. On Tue, Oct 14, 2008 at 7:30 PM, Audino, Jeremy [EMAIL PROTECTED]wrote: I've got a Java Client and Server using the Calculator.wsdl supplies with the original Axis (not Axis2). I've generated Axis2 bindings using WSDL2Java. I also have a client and server written in C++ using gSoap. I have no issue with both the Java and C++ clients communicating with the C++ Server. I am however having an issue with the Java Client and the Java Server (using SimpleHTTPServer). I'm getting the following exception from the Client. The C++ client works fine with the Java Server. org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement return at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at localhost.axis.calculator.CalculatorStub.fromOM(Unknown Source) at localhost.axis.calculator.CalculatorStub.add(Unknown Source) at localhost.axis.calculator.CalculatorClient.main(Unknown Source) Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: Unexpected subelement return at localhost.axis.calculator.AddResponse$Factory.parse(Unknown Source) ... 3 more Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement return ... 4 more I've attached the WSDL and Java Source…. Any help would be great. Best Regards, Jeremy Jeremy F. Audino Senior Software Development Engineer Philips Healthcare -- Nuclear Medicine Tel: 440-483-7444 E-mail: [EMAIL PROTECTED] -- The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. - 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
FW: Axis2.war in weblogic
Hi, Is there any solution to deploy the axis2.war file instead of the exploded format? We receive below error in Weblogic Servlet: AxisServlet failed to preload on startup in Web application: axis2. javax.servlet.ServletException: Servlet class: 'org.apache.axis2.transport.http.AxisServlet' doesn't have a default constructor Thanks Regards, Peter Rajesh CI Production Support Office - 860-547-3881 Mobile - 201-6580195 * This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. *
Re: problem with String [] in axis 1.3 and .net client
This is the C# request which is not working,
?xml version=1.0 encoding=utf-8?
soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns=
http://external.soap.service.cps.moota.com; xmlns:types=
http://external.soap.service.cps.moota.com/encodedTypes; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
http://www.w3.org/2001/XMLSchema;
soap:Body soap:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
tns:sendSmsMessagein0 href=#id1 /
/tns:sendSmsMessage
q1:SmsRequestDto id=id1 xsi:type=q1:SmsRequestDto xmlns:q1=
http://dto.service.cps.moota.com;
projectId xsi:nil=true /user xsi:nil=true /
message xsi:nil=true /
msisdn href=#id2 /
applicationId xsi:nil=true /
accountExternalId xsi:nil=true /
accountId xsi:nil=true /
originatingAddress xsi:nil=true /
originatingAddressType xsi:nil=true /
/q1:SmsRequestDto
soapenc:Array id=id2 soapenc:arrayType=xsd:string[1]
Item123456/Item
/soapenc:Array
/soap:Body
/soap:Envelope
but for following Axis 1.3 client request it works fine
?xml 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;soapenv:Body
ns1:sendSmsMessage soapenv:encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=
http://soap.service.cps.moota.com;
in0 href=#id0/
/ns1:sendSmsMessage
multiRef id=id0 soapenc:root=0 soapenv:encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns2:SmsRequestDto
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns2=
http://dto.service.cps.moota.com;
projectId href=#id1/
user xsi:type=xsd:string xsi:nil=true/
message xsi:type=xsd:string xsi:nil=true/
msisdn soapenc:arrayType=xsd:string[1] xsi:type=soapenc:Array
ns3:item xsi:type=xsd:string xmlns:ns3=
http://webservice.clientprovisioning.moota.com;123456789/ns3:item
/msisdn
applicationId xsi:type=xsd:int xsi:nil=true/
accountExternalId xsi:type=xsd:int xsi:nil=true/
accountId xsi:type=xsd:int xsi:nil=true/
originatingAddress xsi:type=xsd:string xsi:nil=true/
originatingAddressType xsi:type=xsd:int xsi:nil=true/
/multiRef
multiRef id=id1 soapenc:root=0 soapenv:encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/; xsi:type=xsd:long
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
10/multiRef
/soapenv:Body/soapenv:Envelope
?xml version=1.0 encoding=utf-8?
soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns=
http://external.soap.service.cps.moota.com; xmlns:types=
http://external.soap.service.cps.moota.com/encodedTypes; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
http://www.w3.org/2001/XMLSchema;soap:Body soap:encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/;
tns:sendSmsMessagein0 href=#id1
//tns:sendSmsMessageq1:SmsRequestDto id=id1
xsi:type=q1:SmsRequestDto
xmlns:q1=http://dto.service.cps.moota.com;projectId
xsi:nil=true /user xsi:nil=true /message xsi:nil=true /msisdn
href=#id2 /applicationId xsi:nil=true /accountExternalId
xsi:nil=true /accountId xsi:nil=true /originatingAddress
xsi:nil=true /originatingAddressType xsi:nil=true
//q1:SmsRequestDtosoapenc:Array id=id2
soapenc:arrayType=xsd:string[1]Item123456/Item/soapenc:Array/soap:Body/soap:Envelope
?xml 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;
soapenv:Body
soapenv:Faultfaultcodesoapenv:Server.userException/faultcode
faultstringjava.lang.IllegalArgumentException: array element type
mismatch/faultstringdetail
ns1:hostname xmlns:ns1=http://xml.apache.org/axis/
jayalal-PC/ns1:hostname/detail/soapenv:Fault
/soapenv:Body/soapenv:Envelope
2008/10/13 Deepal Jayasinghe [EMAIL PROTECTED]
Did you check whether it sends the correct request , I mean is it valid
according to the WSDL ?
You can see the message if you send that via TCP Monitor.
-Deepal
jayalal jayarathna wrote:
Hi,
I have a web service developed on Axis 1.3, and it has following method.
SendTaskResponseDto sendSmsMessage(SmsRequestDto in0)
SmsRequestDto has an string array
public class SmsRequestDto implements java.io.Serializable {
private java.lang.Long projectId;
private java.lang.String user;
private java.lang.String message;
private java.lang.String[] msisdn;
private java.lang.Integer applicationId;
.
when I try to call SendTaskResponseDto sendSmsMessage(SmsRequestDto
in0) through C#.net client it gives following exception at server
13 Oct 2008 11:03:00,015 ERROR BeanPropertyTarget - Could not convert
[Ljava.lang.String; to bean
Re: namespaces error
The message generated by SOAPUI looks like: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:mdc=http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; xmlns:sch= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; soapenv:Header/ soapenv:Body mdc:GetOrderDetails sch:OrderInfo Referentienummer135756.010/Referentienummer /sch:OrderInfo /mdc:GetOrderDetails /soapenv:Body /soapenv:Envelope This works out of the box. The difference seems to be that SOAPUI declares all namespaces in the Envelope tag, and Axis does not. Also the Axis generated message does not include a namespace(prefix) on the OrderInfo tag. No matter what I try the Axis generated client does not work. Any idea? Thanks for your help, Harm! On Tue, Oct 14, 2008 at 3:57 PM, keith chapman [EMAIL PROTECTED]wrote: Looking at the WSDL it looks like a correct message should be of the form. soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Body ns3:GetOrderDetails xmlns:ns3= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; n2:OrderInfo xmlns:n2= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb ns3:Referentienummer123456.123/ns3:Referentienummer /n2:OrderInfo /ns3:GetOrderDetails /soapenv:Body /soapenv:Envelope Could you a sample message generated using SOAPUI. Thanks, Keith. On Tue, Oct 14, 2008 at 6:52 PM, Harm de Laat [EMAIL PROTECTED] wrote: Here is the complete WSDL file (I just commented out the IP address for the service). What may be worth of mentioning is that I tried using SOAPUI, which worked instantly with this specific WSDL. ?xml version=1.0 encoding=utf-8? wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/; xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:mime= http://schemas.xmlsoap.org/wsdl/mime/; xmlns:tns= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; xmlns:s1= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; xmlns:s=http://www.w3.org/2001/XMLSchema; xmlns:s2= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http= http://schemas.xmlsoap.org/wsdl/http/; targetNamespace= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; wsdl:documentation xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;BizTalk assembly Sanoma.BizTalk.AdvertentiePortal.MDC, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8c063b3a22630ca9 published web service./wsdl:documentation wsdl:types s:schema elementFormDefault=qualified targetNamespace= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; s:import namespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; / s:import namespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb; / s:element name=GetOrderDetails s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 ref=s1:OrderInfo / /s:sequence /s:complexType /s:element s:element name=GetOrderDetailsResponse s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 ref=s2:OrderInfoResult / /s:sequence /s:complexType /s:element /s:schema s:schema elementFormDefault=qualified targetNamespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb s:element name=OrderInfo s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 form=unqualified name=Referentienummer type=s:string / /s:sequence /s:complexType /s:element /s:schema s:schema elementFormDefault=qualified targetNamespace= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoResultWeb s:element name=OrderInfoResult s:complexType s:sequence s:element minOccurs=0 maxOccurs=1 form=unqualified name=Referentienr type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=NameAdvertiser type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=TypeOfAd type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=titleId type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=editionId type=s:string / s:element minOccurs=0 maxOccurs=1 form=unqualified name=orderStatus type=s:integer / s:element minOccurs=0 maxOccurs=1 form=unqualified name=returnCode type=s:integer / s:element minOccurs=0 maxOccurs=1 form=unqualified name=returnMessage type=s:string /
Threshold for File size in MTOM
Hello Axis Users, I am new to MTOM processing using Axis2. In MTOM, is there a way to specify the maximum attachment size on the server so that anything exceeding that size is rejected. Can this achieved by configuration or should I need to use a custom handler to enforce this limit. Any insight on this would be appreciated. Thanks Sriram
Re: [AXIS2] v1.4.1 WODEN using network URL for XMLSchema.xsd instead of WodenWjar file
Hi All, I've looked at the Woden code and it looks like this is purely a Woden issue. I'll switch this to the Woden user list. Thanks to anyone that was looking at this. leon On Mon, 13 Oct 2008 16:10:09 -0500, searl [EMAIL PROTECTED] wrote: Hi, Unless I am misunderstanding something, when a service starts up and the service is using user WSDL, it looks like WODEN is looking for the XMLSchema.xsd file over the network instead of looking in the Woden jar file (unless there is no network connection in which case it eventually uses the woden jar file after failing to obtain the network connection). Is there a mechanism that I can use (system property?) to force Woden to only use its jar file to find the XMLSchema.xsd. The reason that I want this is that I have a very slow network connection (1200baud) and I don't want to be using it to load the XMLSchema.xsd every time a service starts up. It makes for very slow service startup. Thanks leon -- Leon S. Searl, Software Research Engineer Information and Telecommunication Technology Center, University of Kansas Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612 Ph: 785-864-7820 Fax: 785-864-0387 http://www.ittc.ku.edu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
xmlbeans in Axis (not Axis2) using Eclipse IDE
Hello everyone, I'd like to know if someone of you knows how to modify the wizard used in Ecipse to create Web Services Skeleton to use a xmlbeans data binding. Alternatively, it could help to know what an how needs to be changed in a project generated by that wizard in order to use xmlbeans in the web service. -- View this message in context: http://www.nabble.com/xmlbeans-in-Axis-%28not-Axis2%29-using-Eclipse-IDE-tp19978820p19978820.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]
[Axis2] How to (using Axis2) get the XML file posted from a SOAP client?
Hi all, This is my first time to try to use Axis2 to create a SOAP service. Basically my SOAP service needs to recieve an XML file posted from an SOAP client. The SOAP client program is from a third party who is not using Axis2. Can anyone tell me how to do that or tell me where I can find documents/exmaples to accomplish that? Assume my service is something like http://myUrl/axis2/postXmlData I guess there should be some special Axis2 API codes in the function 'postXmlData', right? Can anyone tell me more about what kinds of codes there should be to receive the XML document sent from the SOAP client? I'd really appreciate it if someone can give me some guidance or shed some lights on this. thanks in advance, -tian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: In-flow request insertion
Actually I want to develop a passive replication schema, so I have the
handlers together in a group. If the Active member fails, I'll have to
re-invoke the message, but in another handler in another server. I'm
serializing the Messagecontext and moving it through the replicas, so when a
fault is detected I'll invoke the message again, but in another service . Is
there a way to do that?I tryed to use LocalTranportSender, but it returns me
a nullexception error...I've opened another thread on the list about it...if
you have time, could you take a lokk at it too? ;-)
Thanks again!!!,
Igor Nogueira
Amila Suriarachchi wrote:
On Mon, Oct 13, 2008 at 4:29 PM, Igor Nogueira
[EMAIL PROTECTED]
wrote:
Amila, thank you! I've tested what you said, but I've got this exception:
A message was added that is not valid. However, the operation context
was
complete.
this means it try to add an Axis2 Message to an operation context which
already has required number of Axis2 messages. This may happen when it
goes
through the dispatches again.
Here's the code I'm using:
contextomensagem.setCurrentHandlerIndex(0);
contextomensagem.setCurrentPhaseIndex(0);
AxisEngine engine = new
AxisEngine(contextomensagem.getConfigurationContext());
try {
engine.receive(contextomensagem);
you can simply called . AxisEngine.receive() since this is a static
method.
} catch (AxisFault e1) {
e1.printStackTrace();
return (e1.getReason());
}
contextomensagem is a static variable that keeps a copy of the
MessageContext received at the invoke method. As I'm testing I didin't
change the SOAPEnvelope, I'm just trying to re-send the same message. Is
there something else to do?
Are you experimenting with Axis2 Engine or what do you try to archive? why
you want to send the same message twice?
thanks,
Amila.
Thanks!
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
--
View this message in context:
http://www.nabble.com/In-flow-request-insertion-tp19946886p19977558.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]
Out Only MEP questions
1) I have built and successfully deployed the two mentioned services ActiveService and ClientService, when attempting to register with http://localhost:8080/axis2/rest/ActiveService?register?notifyEpr=http://localhost:8080/axis2/services/ClientServiceI get Requested resource not found! 2) I modified the axis2.xml as follows: !--Our HTTP endpoints can handle both REST and SOAP. Following parameters can be used to distinguiush those endpoints-- !--In case of a servlet, if you change this you have to manually change the settings of your servlet container to map this -- !--context path to proper Axis2 servlets-- !--parameter name=servicePathservices/parameter-- parameter name=restPathrest/parameter !-- Following parameter will completely disable REST handling in Axis2-- parameter name=disableREST locked=falsefalse/parameter This seemed to have no effect. How do I enable the 'rest' url to register my client service? Environment details: Axis2 Happiness Page Examining webapp configuration Essential Components Found Apache-Axis (org.apache.axis2.transport.http.AxisServlet) at C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\axis2\WEB-INF\lib\axis2-kernel-1.4.1.jar Found Jakarta-Commons Logging (org.apache.commons.logging.Log) at C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\axis2\WEB-INF\lib\commons-logging-1.1.1.jar Found Streaming API for XML (javax.xml.stream.XMLStreamReader) at an unknown location Found Streaming API for XML implementation (org.codehaus.stax2.XMLStreamWriter2) at C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\axis2\WEB-INF\lib\wstx-asl-3.2.4.jar The core axis2 libraries are present. Note: Even if everything this page probes for is present, there is no guarantee your Axis Service will work, because there are many configuration options that we do not check for. These tests are necessary but not sufficient Examining Version Service Found Axis2 default Version service and Axis2 is working properly. Now you can drop a service archive in axis2/WEB-INF/services. Following output was produced while invoking Axis2 version service Hello I am Axis2 version service , My version is 1.4.1 Examining Application Server Servlet version 2.5 Platform Apache Tomcat/6.0.16 Examining System Properties java.runtime.name Java(TM) SE Runtime Environment sun.boot.library.path C: \Program Files\Java\jre1.6.0_05\bin java.vm.version 10.0-b19 shared.loader java.vm.vendor Sun Microsystems Inc. java.vendor.url http: //java.sun.com/ path.separator ; java.vm.name Java HotSpot(TM) Client VM tomcat.util.buf.StringCache.byte.enabled true file.encoding.pkg sun.io java.util.logging.config.file C: \Program Files\Apache Software Foundation\Tomcat 6.0\conf\logging.properties user.country US sun.os.patch.level Service Pack 2 java.vm.specification.name Java Virtual Machine Specification user.dir C: \Program Files\Apache Software Foundation\Tomcat 6.0 java.runtime.version 1.6.0_05-b13 java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.endorsed.dirs C: \Program Files\Apache Software Foundation\Tomcat 6.0\common\endorsed os.arch x86 java.io.tmpdir C: \Program Files\Apache Software Foundation\Tomcat 6.0\temp line.separator java.vm.specification.vendor Sun Microsystems Inc. user.variant java.util.logging.manager org.apache.juli.ClassLoaderLogManager java.naming.factory.url.pkgs org.apache.naming os.name Windows XP sun.jnu.encoding Cp1252 java.library.path C: \Program Files\Apache Software Foundation\Tomcat 6.0\bin;.;C: \WINDOWS1\Sun\Java\bin;C: \WINDOWS1\system32;C: \WINDOWS1;D: \Program Files\Java\jdk1.5.0_15\bin;D: \axis\axis2-1.4.1\bin;c: \ruby\bin;C: \Program Files\IBM\WebSphere MQ\Java\lib;C: \OraHome_2\jre\1.4.2\bin\client;C: \OraHome_2\jre\1.4.2\bin;C: \oracle\ora92\bin;C: \WINDOWS1\system32;C: \WINDOWS1;C: \WINDOWS1\System32\Wbem;C: \Program Files\UltraEdit;C: \Program Files\IBM\WebSphere MQ\bin;C: \Program Files\IBM\WebSphere MQ\tools\c\samples\bin;C: \Program Files\Hummingbird\Connectivity\7.00\Accessories\;C: \Program Files\Subversion\bin;C: \Program Files\Support Tools\;c: \Program Files\Microsoft SQL Server\90\Tools\binn\;C: \Program Files\svnmerge;D: \apache-ant-1.7.0\bin;D: \Sun\SDK\bin;C: \Program Files\QuickTime\QTSystem\;D: \groovy\groovy-1.5.6\bin java.specification.name Java Platform API Specification java.class.version 50.0 sun.management.compiler HotSpot Client Compiler os.version 5.1 user.home C: \ user.timezone America/Los_Angeles catalina.useNaming true java.awt.printerjob sun.awt.windows.WPrinterJob java.specification.version 1.6 file.encoding Cp1252 catalina.home C: \Program Files\Apache Software Foundation\Tomcat 6.0 user.name SYSTEM java.class.path C: \Program Files\Apache Software Foundation\Tomcat 6.0\bin\bootstrap.jar java.naming.factory.initial org.apache.naming.java.javaURLContextFactory package.definition
Re: In-flow request insertion
On Mon, Oct 13, 2008 at 4:29 PM, Igor Nogueira [EMAIL PROTECTED]
wrote:
Amila, thank you! I've tested what you said, but I've got this exception:
A message was added that is not valid. However, the operation context was
complete.
this means it try to add an Axis2 Message to an operation context which
already has required number of Axis2 messages. This may happen when it goes
through the dispatches again.
Here's the code I'm using:
contextomensagem.setCurrentHandlerIndex(0);
contextomensagem.setCurrentPhaseIndex(0);
AxisEngine engine = new
AxisEngine(contextomensagem.getConfigurationContext());
try {
engine.receive(contextomensagem);
you can simply called . AxisEngine.receive() since this is a static method.
} catch (AxisFault e1) {
e1.printStackTrace();
return (e1.getReason());
}
contextomensagem is a static variable that keeps a copy of the
MessageContext received at the invoke method. As I'm testing I didin't
change the SOAPEnvelope, I'm just trying to re-send the same message. Is
there something else to do?
Are you experimenting with Axis2 Engine or what do you try to archive? why
you want to send the same message twice?
thanks,
Amila.
Thanks!
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
namespaces error
Hi all, I'm having great difficulties calling a BizTalk webservice using axis2 (1.4.1) with ADB. I have generated my client using the following command: wsdl2java.sh -uri http://x.x.x.x/WebServices/AdvPortal/MDC/WebService_Sanoma_BizTalk_AdvertentiePortal_MDC.asmx?WSDL-p nl.kabisa.sanoma.webservices -d adb -s This generates all classes and using my (test)client I get to call the service. This generates the following SOAP message: soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Body ns3:GetOrderDetails xmlns:ns3= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; OrderInfo xmlns= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; Referentienummer123456.123/Referentienummer /OrderInfo /ns3:GetOrderDetails /soapenv:Body /soapenv:Envelope However, this call gets discarded by the BizTalk server. When I manually modify the soap message to the message below everything is fine. (Notice the ns2 namespace): soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Body ns3:GetOrderDetails xmlns:ns3= http://webservices.sanoma-uitgevers.nl/AdvPortal/MDC/; n2:OrderInfo xmlns:n2= http://schemas.sanoma-uitgevers.nl/AdvPortal/MDC/SchemaOrderInfoRequestWeb; Referentienummer123456.123/Referentienummer /n2:OrderInfo /ns3:GetOrderDetails /soapenv:Body /soapenv:Envelope What is going on here? Why is the NS2 namespace missing in the Axis2 generated Soap message? Also, what can I do to make this relatively simple client work? Kind regards, -- Harm de Laat Kabisa ICT
regarding https://issues.apache.org/jira/browse/AXIS2-3732
Subject: regarding https://issues.apache.org/jira/browse/AXIS2-3732 Hello, I've ran into the same issue described in https://issues.apache.org/jira/browse/AXIS2-3732, but when I check the sources code distribution for 1.3, 1.4, and 1.4.1 I don't see the changes listed in the attachment in Jira. Could anyone suggest how to get this patch or any workaround? Currently it's causing huge memory leaks in my server after repeated re-deployments of the application. Thank you, Eugene
RE: Rampart 1.4 mustUnderstand
I switched back to axis 1.3 with rampart 1.3. Still getting mustUnderstand=1. I see others with the issue when using their own axis2.xml, but I'm using the default axis2.xml that comes with axis. I simply load the client policy (attached). Is it something in my policy that causes mustUnderstand=1? I wouldn't think so. Taariq Levack wrote: Had the same issue recently, the security header coming back from the service was empty in my case. For now I'm using 1.3 until the issue I raised is resolved. Try the same code with Axis 1.3 and Rampart 1.3 and see if that works for you. Taariq -Original Message- From: RonnieMJ [mailto:[EMAIL PROTECTED] Sent: 10 October 2008 23:32 To: axis-user@ws.apache.org Subject: Rampart 1.4 mustUnderstand Does rampart version 1.4 default mustUnderstand to 1? I'm getting the famous error, and am using a policy to set my configurations in code (client side ONLY). My wsse:security tag ends up as mustunderstand=1. wsse:Security xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse curity-secext-1.0.xsd soapenv:mustUnderstand=1 The security isn't set in the WSDL. I am using axis2 1.4.1. I've seen the WSDL2Constants flag, but I'm not using WSDL2Constants. Just the plain old: options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, loadPolicy(confDir + /clientSecurityPolicy.xml)); stub._getServiceClient().setOptions(options); stub._getServiceClient().engageModule(rampart); I also don't have access to or control over what is used on the service side (external). -- View this message in context: http://www.nabble.com/Rampart-1.4-mustUnderstand-tp19926442p19926442.htm l 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] http://www.nabble.com/file/p19984135/clientSecurityPolicyExternal.xml clientSecurityPolicyExternal.xml -- View this message in context: http://www.nabble.com/Rampart-1.4-mustUnderstand-tp19926442p19984135.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]
Help! How to set the value of SOAPAction for a SOAP service using Axis2?
Hi all, I'm new to Axis2 and SOAP. I need to create a SOAP service using Axis2. I wonder how to set the SOAPAction value so my service will verify the value when a client program call the service? I assume Axis2 will do the SOAPAction validation automatically as long as I set the value somewhere in my service, right? But how to do that? thanks in advance, -tian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help! How to set the value of SOAPAction for a SOAP service using Axis2?
Hi Tian, Have a look at the action mapping section of the following article. http://wso2.org/library/2060 Deepal Tian Chi wrote: Hi all, I'm new to Axis2 and SOAP. I need to create a SOAP service using Axis2. I wonder how to set the SOAPAction value so my service will verify the value when a client program call the service? I assume Axis2 will do the SOAPAction validation automatically as long as I set the value somewhere in my service, right? But how to do that? thanks in advance, -tian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thank you! http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axis2 datahandler to blob and viceversa
Hi, I want to create a datahandler out of a blob. Can we do that without saving the blob to a file? Also I want to save the file (coming through the datahandler) to a blob. Can it be done without saving it to a file (directly convert datahandler to blob)? Please help me. thanks
Rampart and WSS 1.0 DRAFT
Is there any way to use the WSS 1.0 Draft specification with rampart (pre Oasis - http://schemas.xmlsoap.org/ws/2002/07/secext)? I realize that one wouldn't WANT to do this, but I'm wondering if it's possible. -- View this message in context: http://www.nabble.com/Rampart-and-WSS-1.0-DRAFT-tp19985451p19985451.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]
Client address on messagecontext??
Guys, I have a doubt. I have handler engaged on the inflow and outflow. I'd like to know what's the client's address . I tested the MessageContext's From and To parameters and I have the following situation: At Inflow: From value is 127.0.0.1 (I invoke the webservice from localhost); To value is http://127.0.0.1:8080/axis2/services/ShoppingCart1;. At outflow: From is null; To is :http://www.w3.org/2005/08/addressing/anonymous; Is it possible to retrieve the real client's address on the messagecontext received as parameter of the handler's invoke method? Or is it built on a later phase of OutFlow and I can' access it? Thanks in advance, Igor
Re: [AXIS2] v1.4.1 WODEN using network URL for XMLSchema.xsd instead of WodenWjar file
Hi leon, There was a Woden issue locating W3C schema without network access [1] but it is already fixed from M7 release , I'm not sure what is your Woden version . Any way it's good place to post in Woden user list with a error trace you got . [1] - http://issues.apache.org/jira/browse/WODEN-83 thanks , On Tue, Oct 14, 2008 at 11:09 PM, searl [EMAIL PROTECTED] wrote: Hi All, I've looked at the Woden code and it looks like this is purely a Woden issue. I'll switch this to the Woden user list. Thanks to anyone that was looking at this. leon On Mon, 13 Oct 2008 16:10:09 -0500, searl [EMAIL PROTECTED] wrote: Hi, Unless I am misunderstanding something, when a service starts up and the service is using user WSDL, it looks like WODEN is looking for the XMLSchema.xsd file over the network instead of looking in the Woden jar file (unless there is no network connection in which case it eventually uses the woden jar file after failing to obtain the network connection). Is there a mechanism that I can use (system property?) to force Woden to only use its jar file to find the XMLSchema.xsd. The reason that I want this is that I have a very slow network connection (1200baud) and I don't want to be using it to load the XMLSchema.xsd every time a service starts up. It makes for very slow service startup. Thanks leon -- Leon S. Searl, Software Research Engineer Information and Telecommunication Technology Center, University of Kansas Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612 Ph: 785-864-7820 Fax: 785-864-0387 http://www.ittc.ku.edu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sagara Gunathunga Blog - ssagara.blogspot.com Web - http://sagaras.awardspace.com/
Re: Threshold for File size in MTOM
Hi,Currently it's not possible to specify this from Axis2.. IIRC somebody in this list earlier mentioned that it is possible to configure your servlet container to limit the incoming message size..May be that'll help as a work around. thanks, Thilina On Tue, Oct 14, 2008 at 1:41 PM, Sriram Vaidyanathan [EMAIL PROTECTED] wrote: Hello Axis Users, I am new to MTOM processing using Axis2. In MTOM, is there a way to specify the maximum attachment size on the server so that anything exceeding that size is rejected. Can this achieved by configuration or should I need to use a custom handler to enforce this limit. Any insight on this would be appreciated. Thanks Sriram -- Thilina Gunarathne - http://thilinag.blogspot.com
