Error while using the axis client
Hi, I am trying to call a web service that was written using some Oracle Framework. I am using axis 1.4.1 with ADB binding and Java 1.4 When I call the service from my client I am getting below exception message from the other side ?xml version = '1.0' encoding = 'UTF-8'? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; SOAP-ENV:Body SOAP-ENV:Fault faultcodeSOAP-ENV:Client/faultcode faultstringNo Deserializer found to deserialize a 'CcVaultPort:VaultId' using encoding style 'null'. [java.lang.IllegalArgumentException]/faultstring faultactor/Operajserv/CcVault/MHotelVaultApp/faultactor /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope And the request message is as below ?xml version = '1.0' encoding = 'UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns1:processCcMsg xmlns:ns1=CcVaultPort VaultId1/VaultId VendorUrl/ ActionGetCC/Action Originatoroo/Originator Requestrr/Request /ns1:processCcMsg /soapenv:Body /soapenv:Envelope When we call the same service with a C# client that sends a request as below and it works. How can we achieve the same with axis? ?xml version = '1.0' encoding = 'UTF-8'? env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:ns0=CcVault xmlns:ns1=http://ccVault/CcVault.xsd; env:Body ns0:processCcMsg env:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; VaultId xsi:type=xsd:string1/VaultId VendorUrl xsi:type=xsd:string/ Action xsi:type=xsd:stringGetID/Action Originator xsi:type=xsd:stringoo/Originator Request xsi:type=xsd:stringrr/Request /ns0:processCcMsg /env:Body /env:Envelope
Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI
Hi, I am getting an error[1] when I do a call to a .Net service by using and axis2 1.4.1 client. I did some research and I found that axis throws this error when it can't be sure about the soap version of the message.[2] I want to be sure that I am understanding correctly. According to the link below my message must have the Content type of http header as application/soap+xml not as text/xml. Is this a correct statement? Is there any quick workaround? Thanks 1-org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI 2-http://wso2.org/library/559 HTTP/1.1 200 OK Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428 Date: Thu, 02 Oct 2008 13:31:47 GMT Content-Type: text/xml; charset=utf-8 Content-Length: 1256 env:Envelope xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:env=http://www.w3.org/2003/05/soap-envelope; env:Header wsa:MessageIDuuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05/wsa:MessageID wsa:RelatesTourn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d/wsa:RelatesTo wsa:Tosoap.tcp://abcd:3456//wsa:To wsa:Actionhttp://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse/wsa:Action wsu:Timestamp wsu:Id=Timestamp-ea6490c2-d8a6-49ce-a09b-d02cd8f6b03f wsu:Created2008-10-02T13:31:47Z/wsu:Created wsu:Expires2008-10-02T13:41:47Z/wsu:Expires /wsu:Timestamp wsse:Security xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd/ /env:Header env:Body BeginCreateResponse xmlns:tns=http://www.zzz.com/BPEL/OpenActivity/CentralReservation/; xmlns=http://www.zzz.com/BPEL/OpenActivity/CentralReservation/; tns:ProcessIDf12fce7e-155e-4c02-871c-16254637fac7/tns:ProcessID /BeginCreateResponse /env:Body /env:Envelope
RE: Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI
Thanks for your reply, I already tried what you suggested and that is working. -ms From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2008 11:00 AM To: axis-user@ws.apache.org Subject: Re: Help-Error : org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI On Thu, Oct 2, 2008 at 7:36 PM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I am getting an error[1] when I do a call to a .Net service by using and axis2 1.4.1 client. I did some research and I found that axis throws this error when it can't be sure about the soap version of the message.[2] I want to be sure that I am understanding correctly. According to the link below my message must have the Content type of http header as application/soap+xml not as text/xml. Is this a correct statement? Yes. Your soap envelop is SOAP 1.2 ( cause its namespace is http://www.w3.org/2003/05/soap-envelope) hence its content-type should be application/soap+xml. The content-type of SOAP 1.1 is text/xml. So there is a problem in your response. I presume that Axis2 sent a SOAP 1.2 request (cause this is the default in Axis2). As a workaround try sending a SOAP 1.1 request. You could do this by setting the following on the options object, options.setSoapVersionURI(org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI); But the Server is definitely in fault here and not Axis2. You may wanna raise an issue against it. Thanks, Keith. Is there any quick workaround? Thanks 1-org.apache.axis2.AxisFault: Transport level information does not match with SOAP Message namespace URI 2-http://wso2.org/library/559 HTTP/1.1 200 OK Server: NGX.Transport.Protocol.Soap.Http/2.0.3167.26428 Date: Thu, 02 Oct 2008 13:31:47 GMT Content-Type: text/xml; charset=utf-8 Content-Length: 1256 env:Envelope xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:env=http://www.w3.org/2003/05/soap-envelope; env:Header wsa:MessageIDuuid:6c84daa4-36ed-4ec0-8771-bd91a5f1af05/wsa:MessageID wsa:RelatesTourn:uuid:66f38c0f-74cb-427d-91c4-f4cabdeb921d/wsa:RelatesTo wsa:Tosoap.tcp://abcd:3456//wsa:To wsa:Actionhttp://www.zzz.com/BPEL/OpenActivity/CentralReservation/CentralReservationPortType/BeginCreateResponse/wsa:Action wsu:Timestamp wsu:Id=Timestamp-ea6490c2-d8a6-49ce-a09b-d02cd8f6b03f wsu:Created2008-10-02T13:31:47Z/wsu:Created wsu:Expires2008-10-02T13:41:47Z/wsu:Expires /wsu:Timestamp wsse:Security xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd/ /env:Header env:Body BeginCreateResponse xmlns:tns=http://www.zzz.com/BPEL/OpenActivity/CentralReservation/; xmlns=http://www.zzz.com/BPEL/OpenActivity/CentralReservation/; tns:ProcessIDf12fce7e-155e-4c02-871c-16254637fac7/tns:ProcessID /BeginCreateResponse /env:Body /env:Envelope -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
RE: Error when generating the proxies using xmlbeans
In able to continue my work I tried -Ewdc (for xmlbeans) options of wsdl2java, and I could generate the files using xmlbens scomp. Now which files should I replace ? Thanks -- -Ewdc (for xmlbeans) Generate code with a dummy schema. if someone use this option they have to generate the xmlbeans code seperately with the scomp command comes with the xmlbeans distribution and replace the Axis2 generated classes with correct classes From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:01 PM To: axis-user@ws.apache.org Subject: Error when generating the proxies using xmlbeans Hi, I have a WSDL file which imports other WSDL files and they import XSD files. Looks like one of the XSD is being referred multiple times. I guess normally this shouldn't be an issue but when I use the xmlbeans binding I am getting an error saying that I have Duplicate global type . When I use the default binding ADB I don't get an error message but I can't use ADB because of its limitations for inherited complex types. I am using axis2 1.4.1 . Do you have any suggestions to work around the issue? Thanks Using JAVA_HOME:d:\jdev\10g10134\jdk Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. [INFO] A SOAP port was not found - picking a random port! [INFO] Resolving schema with publicId [http://schemas.zzz.com/OpenActivity/1/0/Reservation/] and systemId [XReservationService.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException
RE: Error when generating the proxies using xmlbeans
Hi David,
Thanks for your reply. It says that it will generate a dummy schema but when
I look at the generated files they look legitimate, which files should be dummy?
Thanks
-Original Message-
From: David Ojeda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 10:08 AM
To: axis-user@ws.apache.org
Subject: Re: Error when generating the proxies using xmlbeans
In my experience, I have to delete everything except the skeleton, message
receiver, and fault classes if any.
I do this with an ant task, so maybe this will help:
java classname=org.apache.axis2.wsdl.WSDL2Java
failonerror=true
fork=true
classpath refid=axis2.classpath/
classpath location=etc/axis2log4j/
arg value=-d/
arg value=xmlbeans/
arg value=-g/
arg value=-ss/
arg value=-Ewdc/
arg value=-xsdconfig/
arg file=xsd/NStoPkg.xsdconfig/
arg value=-sd/
arg value=-o/
arg file=output/${ws.name}/
arg value=--noBuildXML/
arg value=-uri/
arg file=wsdl/${ws.name}.wsdl/
/java
delete includeemptydirs=true
fileset dir=output/${ws.name}/src
include name=**/*/
exclude name=**/.svn/**/
exclude name=**/*Skeleton.java/
exclude name=**/*MessageReceiverInOut.java/
exclude name=**/*Fault.java/
/fileset
/delete
Note that all my fault classes are named *Fault, so their classes are not
deleted.
On Wednesday 01 October 2008 08:32:29 Soyer, Muhammed A. wrote:
In able to continue my work I tried -Ewdc (for xmlbeans) options of
wsdl2java, and I could generate the files using xmlbens scomp. Now which
files should I replace ?
Thanks
--
-Ewdc (for xmlbeans) Generate code with a dummy schema. if someone use
this option they have to generate the xmlbeans code seperately with the
scomp command comes with the xmlbeans distribution and replace the Axis2
generated classes with correct classes
From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:01 PM
To: axis-user@ws.apache.org
Subject: Error when generating the proxies using xmlbeans
Hi,
I have a WSDL file which imports other WSDL files and they import XSD
files. Looks like one of the XSD is being referred multiple times. I guess
normally this shouldn't be an issue but when I use the xmlbeans binding I
am getting an error saying that I have Duplicate global type . When I
use the default binding ADB I don't get an error message but I can't use
ADB because of its limitations for inherited complex types.
I am using axis2 1.4.1 . Do you have any suggestions to work around the
issue?
Thanks
Using JAVA_HOME:d:\jdev\10g10134\jdk
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document
at 'XClassService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XClassService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at
'XSpaService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XSpaService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at
'XCustomer.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at
'XLocation.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XLocationObjects.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at
'XTee.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at
'XDiningService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XDiningService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. Retrieving document at
'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema
wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2
RE: Error when generating the proxies using xmlbeans
Thanks for your help, I found another workaround for my case, I commented the
repeating imports and I could generate proxy classes then..
Thanks
-Original Message-
From: David Ojeda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 11:02 AM
To: axis-user@ws.apache.org
Subject: Re: Error when generating the proxies using xmlbeans
Hello Muhammed,
I am not sure about this. When I faced this problem I wasn't sure which files
should be deleted. I didn't find any docs about this but this -Ewdc was crucial
for my project (generation time was 5min without it and 10seconds with it).
The main problem was that there were duplicate classes in the jar generated by
scomp and the classes generated by wsdl2java.
What I did was erase everything but the ones I wrote in my last message[*]
Then I encountered more problems since I now needed the soap, wsdl and xml xsd
classes (Apparently the dummy classes of these xsd were generated by
wsdl2java... but I did not have the implementation classes). So my solution was
generating these classes with scomp as well. I am enclosing these xsd in case
you need them.
Hope it helps, but sorry I do not know the answer to your question
[*] I forgot that I must delete also schemaorg_apache_xmlbeans/**
On Wednesday 01 October 2008 10:16:31 Soyer, Muhammed A. wrote:
Hi David,
Thanks for your reply. It says that it will generate a dummy schema
but when I look at the generated files they look legitimate, which
files should be dummy?
Thanks
-Original Message-
From: David Ojeda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 10:08 AM
To: axis-user@ws.apache.org
Subject: Re: Error when generating the proxies using xmlbeans
In my experience, I have to delete everything except the skeleton,
message receiver, and fault classes if any.
I do this with an ant task, so maybe this will help:
java classname=org.apache.axis2.wsdl.WSDL2Java
failonerror=true
fork=true
classpath refid=axis2.classpath/
classpath location=etc/axis2log4j/
arg value=-d/
arg value=xmlbeans/
arg value=-g/
arg value=-ss/
arg value=-Ewdc/
arg value=-xsdconfig/
arg file=xsd/NStoPkg.xsdconfig/
arg value=-sd/
arg value=-o/
arg file=output/${ws.name}/
arg value=--noBuildXML/
arg value=-uri/
arg file=wsdl/${ws.name}.wsdl/
/java
delete includeemptydirs=true
fileset dir=output/${ws.name}/src
include name=**/*/
exclude name=**/.svn/**/
exclude name=**/*Skeleton.java/
exclude name=**/*MessageReceiverInOut.java/
exclude name=**/*Fault.java/
/fileset
/delete
Note that all my fault classes are named *Fault, so their classes are
not deleted.
On Wednesday 01 October 2008 08:32:29 Soyer, Muhammed A. wrote:
In able to continue my work I tried -Ewdc (for xmlbeans) options
of wsdl2java, and I could generate the files using xmlbens scomp.
Now which files should I replace ?
Thanks
--
-Ewdc (for xmlbeans) Generate code with a dummy schema. if someone
use this option they have to generate the xmlbeans code seperately
with the scomp command comes with the xmlbeans distribution and
replace the Axis2 generated classes with correct classes
From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:01 PM
To: axis-user@ws.apache.org
Subject: Error when generating the proxies using xmlbeans
Hi,
I have a WSDL file which imports other WSDL files and they import
XSD files. Looks like one of the XSD is being referred multiple
times. I guess normally this shouldn't be an issue but when I use
the xmlbeans binding I am getting an error saying that I have
Duplicate global type . When I use the default binding ADB I
don't get an error message but I can't use ADB because of its
limitations for inherited complex types.
I am using axis2 1.4.1 . Do you have any suggestions to work
around the issue?
Thanks
Using JAVA_HOME:d:\jdev\10g10134\jdk
Retrieving document at 'CentralReservation.wsdl'.
Retrieving document at 'XReservationService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving
schema wsdl:imported from 'XReservationService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving
document at 'XClassService.wsdl', relative to
'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving
schema wsdl:imported from 'XClassService.xsd', relative to
'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at
'XReservationService.xsd', relative to
'file:/D
Error when generating the proxies using xmlbeans
Hi, I have a WSDL file which imports other WSDL files and they import XSD files. Looks like one of the XSD is being referred multiple times. I guess normally this shouldn't be an issue but when I use the xmlbeans binding I am getting an error saying that I have Duplicate global type . When I use the default binding ADB I don't get an error message but I can't use ADB because of its limitations for inherited complex types. I am using axis2 1.4.1 . Do you have any suggestions to work around the issue? Thanks Using JAVA_HOME:d:\jdev\10g10134\jdk Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. Retrieving document at 'CentralReservation.wsdl'. Retrieving document at 'XReservationService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XReservationService.wsdl'. Retrieving document at 'XClassService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XClassService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XClassService.xsd'. Retrieving document at 'XSpaService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XSpaService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XSpaService.xsd'. Retrieving document at 'XCustomer.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XLocation.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XLocationObjects.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XLocation.wsdl'. Retrieving document at 'XTee.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving document at 'XDiningService.wsdl', relative to 'file:/D:/oa/Zzz2/Wsdl_New/CentralReservation.wsdl'. Retrieving schema wsdl:imported from 'XDiningService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.wsdl'. Retrieving schema at 'XReservationService.xsd', relative to 'file:/D:/oa/Zzz2/Wsdl_New/XDiningService.xsd'. [INFO] A SOAP port was not found - picking a random port! [INFO] Resolving schema with publicId [http://schemas.zzz.com/OpenActivity/1/0/Reservation/] and systemId [XReservationService.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused by:
Problem with generating the proxy classes using xmlbeans
Hi, I can generate the proxy classes by using the default binding but I need to use xmlbeans because of the limitations of ADB. When I try xmlbeans it is erroring out in some enumeration definitions. Is my WSDL file incorrect or do we have a problem with xmlbeans? I am sending a simplified WSDL file having the same issue. Here is the error I am getting D:\oad:\jdev\axis2-1.4.1\\bin\wsdl2java --noBuildXML -or -p com.zz -uri msoyer.wsdl -d xmlbeans d:\jdev\10g10134\jdk java version 1.4.2_08 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode) Using AXIS2_HOME: D:\jdev\axis2-1.4.1 Using JAVA_HOME:d:\jdev\10g10134\jdk Retrieving document at 'msoyer.wsdl'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:115) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: cvc-datatype-valid.1.1: string value '119' does not match pattern for xs:ID at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:325) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: cvc-datatype-valid.1.1: string value '119' does not match pattern for xs:ID at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:189) ... 8 more msoyer.wsdl Description: msoyer.wsdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Newbie wsdl2java question...
Can't you just download the WSDL using a browser and use it locally as a workaround ? From: james a. cubeta [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2008 8:28 PM To: axis-user@ws.apache.org Subject: Re: Newbie wsdl2java question... Thanks Ryan - some stupid follow-up question: First, setup a java keystore. A simple google search should get you going. Just set up an empty keystore? Next, put this code in the WSDL2Java main function: // set the keystore stuff System.setProperty(javax.net.ssl.trustStore, keystore_filename); System.setProperty(javax.net.ssl.keyStorePassword, keystore_password); How am I to modify the WSDL2Java utility? I only have a bunch of Axis-related JARs. Thanks, James -Ryan From: james a. cubeta [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Thursday, September 18, 2008 3:10 PM To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org Subject: Newbie wsdl2java question... Hello everyone, I am both new to Axis and new to this mailing list, so I apologize in advance if my questions are simple or have been covered... I am trying to use Axis 1.4 to develop a simple application that will test a web service that is deployed on a private network. As a first step, I am trying to generate stub code using the WSDL2Java tool. Because the server is https uses an IP only, my command line resembles this: java org.apache.axis.wsdl.WSDL2Java --username user --password pass https://192.168.1.150:8443/example-ws/services/SimpleExample?wsdl When I run this, I get the following exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target exception stack truncated Questions: 1. I assume that the reason this is happening is because the server is using a self-signed certificate, and the JVM cannot validate it. Is this assumption correct? 2. How can I get around this problem? (Note that I do not have administrative access to the server, so making changes on that end is probably not possible). Thanks in advance for any help or references, James -- james a. cubeta -- james a. cubeta
RE: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03
I don't have an aar file because I am not hosting the web services I am consuming them from a web application.. From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 3:05 AM To: axis-user@ws.apache.org Subject: Re: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03 try to put all the jar files under the lib folder of the service archive (.aar file) to WEB-INF/lib folder. thanks, Amila. On Wed, Sep 17, 2008 at 9:58 AM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I spent almost all my day trying to solve this issue. I am consuming web services using axis2 1.4.1 with XmlBeans binding. Everything works fine if I consume the web services with my test clients . But when I deploy my application to an app server (Oc4j or Oracle AS) I am getting some errors. When I try with jdk 1.5 it works fine.. I debugged the application and this line is the cause of the exception. It is in request document class. return (org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument)org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance(type, null); I did some further testing and found that it is happening when I call org.apache.xmlbeans.XmlBeans.getContextTypeLoader() The error messages that I am getting are 1. JBO-29000: Unexpected exception caught: java.lang.IllegalAccessError, msg=tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument 2. tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument As I understand somehow the application server is not allowing the XMLBeans APIs to dynamically load the classes ..But I couldn't find a way to convince it.. Does anybody have any idea by any chance? Thanks a lot -ms -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
RE: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03
Some more details .. I could make it work if I change the below getClassLoader with Thread.currentThread().getContextClassLoader() org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(FetchProfileResponseDocument.class.getClassLoader() This is a generated code and normally works fine with jdk 1.5 .. I guess there should be some setting to make it work in 1.4 as well.. Any Idea ? From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 7:10 AM To: axis-user@ws.apache.org Subject: RE: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03 I don't have an aar file because I am not hosting the web services I am consuming them from a web application.. From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 3:05 AM To: axis-user@ws.apache.org Subject: Re: XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03 try to put all the jar files under the lib folder of the service archive (.aar file) to WEB-INF/lib folder. thanks, Amila. On Wed, Sep 17, 2008 at 9:58 AM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I spent almost all my day trying to solve this issue. I am consuming web services using axis2 1.4.1 with XmlBeans binding. Everything works fine if I consume the web services with my test clients . But when I deploy my application to an app server (Oc4j or Oracle AS) I am getting some errors. When I try with jdk 1.5 it works fine.. I debugged the application and this line is the cause of the exception. It is in request document class. return (org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument)org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance(type, null); I did some further testing and found that it is happening when I call org.apache.xmlbeans.XmlBeans.getContextTypeLoader() The error messages that I am getting are 1. JBO-29000: Unexpected exception caught: java.lang.IllegalAccessError, msg=tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument 2. tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument As I understand somehow the application server is not allowing the XMLBeans APIs to dynamically load the classes ..But I couldn't find a way to convince it.. Does anybody have any idea by any chance? Thanks a lot -ms -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
axis2 1.4.1 wsdl2java fails with jdk 1.4.2_08-b03
Hi, I need to deploy my client code to an Oracle AS that is running on jdk 1.4.2_08-b03. So I am trying to generate the stub files with this jdk but I am getting error .. I did some googling and I found that this is because I am trying to run a java code compiled with an upper version of jdk. But in axis2 docs it is saying that it requires jdk 1.4 or up. And Most of the stub was being generated .. Any suggestions ? Thanks a lot d:\jdev\axis2-1.4.1\bin\wsdl2java.bat -u -uri GCWebAPI-Modified.wsdl -o xm4 -s -d xmlbeans -sp -p com.zzz.gc . . . [INFO] Resolving schema with publicId [http://htng.org/PWS/2008A/GuestSelfService/Booking/Types] and systemId [Booking.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:115) ... 3 more Caused by: java.lang.UnsupportedClassVersionError: org/apache/axis2/namespace/Constants (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at org.apache.axis2.xmlbeans.CodeGenerationUtility.findBase64Types(CodeGenerationUtility.java:349) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:202) ... 8 more
RE: axis2 1.4.1 wsdl2java fails with jdk 1.4.2_08-b03
Please ignore this mail .. I realized that I recompiled one of the axis2 classes with jdk 1.5 Sorry for the bothering From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2008 1:25 PM To: axis-user@ws.apache.org Subject: axis2 1.4.1 wsdl2java fails with jdk 1.4.2_08-b03 Hi, I need to deploy my client code to an Oracle AS that is running on jdk 1.4.2_08-b03. So I am trying to generate the stub files with this jdk but I am getting error .. I did some googling and I found that this is because I am trying to run a java code compiled with an upper version of jdk. But in axis2 docs it is saying that it requires jdk 1.4 or up. And Most of the stub was being generated .. Any suggestions ? Thanks a lot d:\jdev\axis2-1.4.1\bin\wsdl2java.bat -u -uri GCWebAPI-Modified.wsdl -o xm4 -s -d xmlbeans -sp -p com.zzz.gc . . . [INFO] Resolving schema with publicId [http://htng.org/PWS/2008A/GuestSelfService/Booking/Types] and systemId [Booking.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:126) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:115) ... 3 more Caused by: java.lang.UnsupportedClassVersionError: org/apache/axis2/namespace/Constants (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at org.apache.axis2.xmlbeans.CodeGenerationUtility.findBase64Types(CodeGenerationUtility.java:349) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:202) ... 8 more
XMLBeans issue when deployed to ORacle appserver with jdk 1.4.2_08-b03
Hi, I spent almost all my day trying to solve this issue. I am consuming web services using axis2 1.4.1 with XmlBeans binding. Everything works fine if I consume the web services with my test clients . But when I deploy my application to an app server (Oc4j or Oracle AS) I am getting some errors. When I try with jdk 1.5 it works fine.. I debugged the application and this line is the cause of the exception. It is in request document class. return (org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument)org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance(type, null); I did some further testing and found that it is happening when I call org.apache.xmlbeans.XmlBeans.getContextTypeLoader() The error messages that I am getting are 1. JBO-29000: Unexpected exception caught: java.lang.IllegalAccessError, msg=tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument 2. tried to access field org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument$1.class$org$htng$pws$_2008a$guestselfservice$name$types$FetchProfileRequestDocument from class org.htng.pws._2008a.guestselfservice.name.types.FetchProfileRequestDocument As I understand somehow the application server is not allowing the XMLBeans APIs to dynamically load the classes ..But I couldn't find a way to convince it.. Does anybody have any idea by any chance? Thanks a lot -ms
RE: axis2 rampart and ws-trust
Hi Ruchith, Thanks for your answer. In that sample they are using some policy files [1] , I don't have a policy file, I am not sure whether I need one. I need to pass the application user name and password to the Authentication service in able to get back the token. I couldn't understand how the STS service is implemented at the server side in this example, is this something provided by the framework? I have Web Service that I need to call to obtain the token. Can this be something custom and require some custom handling? I have .Net at the server side.. I am new to the area so I am sorry if I am asking some dumb questions. 1-stsClient.setRstTemplate(getRSTTemplate()); String action = TrustUtil.getActionValue(RahasConstants.VERSION_05_02, RahasConstants.RST_ACTION_ISSUE); stsClient.setAction(action); Token responseToken = stsClient.requestSecurityToken(loadPolicy(sample05/policy.xml), http://localhost:8080/axis2/services/STS;, loadPolicy(sample05/sts_policy.xml), null); System.out.println(\n# Requested Token ###\n); System.out.println(responseToken.getToken().toString()); TokenStorage store = TrustUtil.getTokenStore(ctx); store.add(responseToken); -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Sunday, September 14, 2008 11:00 AM To: axis-user@ws.apache.org Subject: Re: axis2 rampart and ws-trust Please have a look at samples/policy/sample05 in the rampart standard binary distribution. You can subscribe and post Rampart/WS-Trust related issues to [EMAIL PROTECTED] Thanks, Ruchith On Fri, Sep 12, 2008 at 11:43 AM, Soyer, Muhammed A. [EMAIL PROTECTED] wrote: Hi, Does anybody know any links for some documentation and sample about the usage of ws-trust with axis2? I did some googling and couldn't find anything that may help me.. Thanks a lot -- http://blog.ruchith.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]
RE: WS-Security with WSDL file that doesn't contain the policies
Hi Nandana, Thanks for your answers. By STS do you mean the web service that I will call to authenticate? If so ,that part is clear for me . I need to pass the the username and password to that service and it returns me the security token and user id back .. Then I need to build the binarySecurityToken using these values. Is there any document that you can suggest for WS-Trust? The other thing , instead of dealing with all these details I tried to building the soap headers manually and it worked fine. I mean I am creating the OMElements and adding them to the client using addHeader method of it. Is this something suggestible? Should I avoid building the WS-Security and WS-Addressing headers manually? Thanks From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 5:10 PM To: axis-user@ws.apache.org Subject: Re: WS-Security with WSDL file that doesn't contain the policies Hi Soyer, Yes, you can do this. You can use WS - Trust support in Apache Rampart to do this. But your binary token NGX-SecurityToken-Value seems to be a custom one. So need to know what are the exact parameters you need to send to the STS ( the web service that issue security tokens). thanks, nandana On Thu, Sep 11, 2008 at 1:39 PM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: I learnt some extra things, I first call a different web service to obtain some ticket (BinarySecurityToken) then I use this token in the following web calls. How can I do this? Thanks From: Soyer, Muhammed A. Sent: Thursday, September 11, 2008 1:47 PM To: 'axis-user@ws.apache.orgmailto:axis-user@ws.apache.org' Subject: RE: WS-Security with WSDL file that doesn't contain the policies IS it possible to figure out something from a sample header? What is binarySecurityToken ? Is it something custom or a generic thing? Thanks wsu:Timestamp wsu:Id=Timestamp-172be5bd-07e8-42e3-b4a8-07c13b9f7013 wsu:Created2008-09-03T12:30:09Z/wsu:Created wsu:Expires2008-09-03T12:30:39Z/wsu:Expires /wsu:Timestamp wsse:Security xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; wsse:BinarySecurityToken ValueType=NGX-SecurityToken-Value EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; wsu:Id=SecurityToken-5aec1e4b-e2ad-43e9-903e-40519d328f9aVILLfdssM027/jJb+iaYGg+M82bLdH1CkcT0yr3rkh0RAG4XXx6W1LJNglfYnWWkuck=/wsse:BinarySecurityToken /wsse:Security From: keith chapman [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Thursday, September 11, 2008 1:24 PM To: axis-user@ws.apache.orgmailto:axis-user@ws.apache.org Subject: Re: WS-Security with WSDL file that doesn't contain the policies If the WSDL does not advertise the policy then you will have speak to the guys who host the service and get the required security configurations. ;). There is no other way that you will know what to send to the other end. Its better if they can give you the security configuration as a policy file. Thanks, Keith. On Thu, Sep 11, 2008 at 10:40 PM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I have a WSDL file which doesn't have the security policies in it. But the server requires me to include the WSSE headers. They are using WSE3 on .Net at the server side. I am trying with rampart and confused about the possibility of achieving this with the WSDL file without the policies. Is it possible? I am using axis 1.4.1 and rampart 1.4 Thanks -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
axis2 rampart and ws-trust
Hi, Does anybody know any links for some documentation and sample about the usage of ws-trust with axis2? I did some googling and couldn't find anything that may help me.. Thanks a lot
WS-Security with WSDL file that doesn't contain the policies
Hi, I have a WSDL file which doesn't have the security policies in it. But the server requires me to include the WSSE headers. They are using WSE3 on .Net at the server side. I am trying with rampart and confused about the possibility of achieving this with the WSDL file without the policies. Is it possible? I am using axis 1.4.1 and rampart 1.4 Thanks
RE: WS-Security with WSDL file that doesn't contain the policies
IS it possible to figure out something from a sample header? What is binarySecurityToken ? Is it something custom or a generic thing? Thanks wsu:Timestamp wsu:Id=Timestamp-172be5bd-07e8-42e3-b4a8-07c13b9f7013 wsu:Created2008-09-03T12:30:09Z/wsu:Created wsu:Expires2008-09-03T12:30:39Z/wsu:Expires /wsu:Timestamp wsse:Security xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; wsse:BinarySecurityToken ValueType=NGX-SecurityToken-Value EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; wsu:Id=SecurityToken-5aec1e4b-e2ad-43e9-903e-40519d328f9aVILLfdssM027/jJb+iaYGg+M82bLdH1CkcT0yr3rkh0RAG4XXx6W1LJNglfYnWWkuck=/wsse:BinarySecurityToken /wsse:Security From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 1:24 PM To: axis-user@ws.apache.org Subject: Re: WS-Security with WSDL file that doesn't contain the policies If the WSDL does not advertise the policy then you will have speak to the guys who host the service and get the required security configurations. ;). There is no other way that you will know what to send to the other end. Its better if they can give you the security configuration as a policy file. Thanks, Keith. On Thu, Sep 11, 2008 at 10:40 PM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I have a WSDL file which doesn't have the security policies in it. But the server requires me to include the WSSE headers. They are using WSE3 on .Net at the server side. I am trying with rampart and confused about the possibility of achieving this with the WSDL file without the policies. Is it possible? I am using axis 1.4.1 and rampart 1.4 Thanks -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
RE: WS-Security with WSDL file that doesn't contain the policies
I learnt some extra things, I first call a different web service to obtain some ticket (BinarySecurityToken) then I use this token in the following web calls. How can I do this? Thanks From: Soyer, Muhammed A. Sent: Thursday, September 11, 2008 1:47 PM To: 'axis-user@ws.apache.org' Subject: RE: WS-Security with WSDL file that doesn't contain the policies IS it possible to figure out something from a sample header? What is binarySecurityToken ? Is it something custom or a generic thing? Thanks wsu:Timestamp wsu:Id=Timestamp-172be5bd-07e8-42e3-b4a8-07c13b9f7013 wsu:Created2008-09-03T12:30:09Z/wsu:Created wsu:Expires2008-09-03T12:30:39Z/wsu:Expires /wsu:Timestamp wsse:Security xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; wsse:BinarySecurityToken ValueType=NGX-SecurityToken-Value EncodingType=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; wsu:Id=SecurityToken-5aec1e4b-e2ad-43e9-903e-40519d328f9aVILLfdssM027/jJb+iaYGg+M82bLdH1CkcT0yr3rkh0RAG4XXx6W1LJNglfYnWWkuck=/wsse:BinarySecurityToken /wsse:Security From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 1:24 PM To: axis-user@ws.apache.org Subject: Re: WS-Security with WSDL file that doesn't contain the policies If the WSDL does not advertise the policy then you will have speak to the guys who host the service and get the required security configurations. ;). There is no other way that you will know what to send to the other end. Its better if they can give you the security configuration as a policy file. Thanks, Keith. On Thu, Sep 11, 2008 at 10:40 PM, Soyer, Muhammed A. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi, I have a WSDL file which doesn't have the security policies in it. But the server requires me to include the WSSE headers. They are using WSE3 on .Net at the server side. I am trying with rampart and confused about the possibility of achieving this with the WSDL file without the policies. Is it possible? I am using axis 1.4.1 and rampart 1.4 Thanks -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
How to add ws-addressing and ws-security headers to call a .Net Service
Hi I am new to axis and I am a little lost ... I want to add ws-addressing and ws-security headers to my soap calls in able to conform to my service requirements. I tried a lot of things and I couldn't progress much. I need to build a soap request as below. soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; soap:Header wsa:Actionhttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/AuthenticationPortType/AuthenticateUserRequest/wsa:Action wsa:MessageIDurn:uuid:1978176b-3ce0-4876-bc19-ba172ce40a7e/wsa:MessageID wsa:ReplyTo wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address /wsa:ReplyTo wsa:Tohttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0//wsa:To wsse:Security wsu:Timestamp wsu:Id=Timestamp-3ac1dee5-fd8b-4f98-97ec-92374a714cd2 wsu:Created2008-09-05T16:05:44Z/wsu:Created wsu:Expires2008-09-05T16:10:44Z/wsu:Expires /wsu:Timestamp /wsse:Security /soap:Header soap:Body AuthenticateUserRequest xmlns=http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/; domainNamelocal/domainName userLoginAdministrator/userLogin password type=PasswordTextABCD/password workstationMSOYERXP999/workstation /AuthenticateUserRequest /soap:Body /soap:Envelope But the message that I can create is as below ?xml version = '1.0' encoding = 'UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing; wsa:Tohttp://172.28.69.39:3457/NGX/Router/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:8CCEB06E38921578361221043202900/wsa:MessageID wsa:Actionhttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/AuthenticationPortType/AuthenticateUserRequest/wsa:Action /soapenv:Header soapenv:Body ns1:AuthenticateUserRequest xmlns:ns1=http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/; ns1:domainNameYYY/ns1:domainName ns1:userLoginmsoyer/ns1:userLogin ns1:password type=PasswordTextsecret/ns1:password ns1:workstationmsoyerxp/ns1:workstation /ns1:AuthenticateUserRequest /soapenv:Body /soapenv:Envelope I realized that the wsa namespace declarations are different. How can I make them same ? And I couldn't set the WSA:TO element correctly either. It is always taking my endpoint address which is not the case with the .Net client. Any help would be great... Thanks
RE: How to add ws-addressing and ws-security headers to call a .Net Service
Hi again, I could figure out the namespace issue by setting the WSA version as below gc._getServiceClient().getOptions().setProperty(AddressingConstants.WS_ADDRESSING_VERSION,http://schemas.xmlsoap.org/ws/2004/08/addressing;); But I still have trouble in setting the WSA:TO element correctly. My messages are being posted to a router and that router is distributing the messages depending on the WSA:TO value. So the values for WSA:TO and the endpoint should be different. WSA:TO is taking the endpoint's value and ignores my statements as below gc._getServiceClient().getOptions().setProperty(AddressingConstants.WSA_TO,http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/;); Could some shed a light to this? Is there any good API documentation for axis2 ? I am using the latest version 1.4.1..Is this OK? Thanks From: Soyer, Muhammed A. Sent: Wednesday, September 10, 2008 6:55 AM To: 'axis-user@ws.apache.org' Subject: How to add ws-addressing and ws-security headers to call a .Net Service Hi I am new to axis and I am a little lost ... I want to add ws-addressing and ws-security headers to my soap calls in able to conform to my service requirements. I tried a lot of things and I couldn't progress much. I need to build a soap request as below. soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; soap:Header wsa:Actionhttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/AuthenticationPortType/AuthenticateUserRequest/wsa:Action wsa:MessageIDurn:uuid:1978176b-3ce0-4876-bc19-ba172ce40a7e/wsa:MessageID wsa:ReplyTo wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address /wsa:ReplyTo wsa:Tohttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0//wsa:To wsse:Security wsu:Timestamp wsu:Id=Timestamp-3ac1dee5-fd8b-4f98-97ec-92374a714cd2 wsu:Created2008-09-05T16:05:44Z/wsu:Created wsu:Expires2008-09-05T16:10:44Z/wsu:Expires /wsu:Timestamp /wsse:Security /soap:Header soap:Body AuthenticateUserRequest xmlns=http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/; domainNamelocal/domainName userLoginAdministrator/userLogin password type=PasswordTextABCD/password workstationMSOYERXP999/workstation /AuthenticateUserRequest /soap:Body /soap:Envelope But the message that I can create is as below ?xml version = '1.0' encoding = 'UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing; wsa:Tohttp://172.28.69.39:3457/NGX/Router/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:8CCEB06E38921578361221043202900/wsa:MessageID wsa:Actionhttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/AuthenticationPortType/AuthenticateUserRequest/wsa:Action /soapenv:Header soapenv:Body ns1:AuthenticateUserRequest xmlns:ns1=http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/; ns1:domainNameYYY/ns1:domainName ns1:userLoginmsoyer/ns1:userLogin ns1:password type=PasswordTextsecret/ns1:password ns1:workstationmsoyerxp/ns1:workstation /ns1:AuthenticateUserRequest /soapenv:Body /soapenv:Envelope I realized that the wsa namespace declarations are different. How can I make them same ? And I couldn't set the WSA:TO element correctly either. It is always taking my endpoint address which is not the case with the .Net client. Any help would be great... Thanks
RE: How to add ws-addressing and ws-security headers to call a .Net Service
I found the solution for the other one also.. When set the addresses as below it worked fine gc._getServiceClient().getOptions().setTo(epTo); //Sets the WSA:TO value gc._getServiceClient().getOptions().setProperty(org.apache.axis2.Constants.Configuration.TRANSPORT_URL,http://172.28.69.39:3457/NGX/Router;); //Sets the actual URL Thanks From: Soyer, Muhammed A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 10, 2008 9:43 AM To: axis-user@ws.apache.org Subject: RE: How to add ws-addressing and ws-security headers to call a .Net Service Importance: Low Hi again, I could figure out the namespace issue by setting the WSA version as below gc._getServiceClient().getOptions().setProperty(AddressingConstants.WS_ADDRESSING_VERSION,http://schemas.xmlsoap.org/ws/2004/08/addressing;); But I still have trouble in setting the WSA:TO element correctly. My messages are being posted to a router and that router is distributing the messages depending on the WSA:TO value. So the values for WSA:TO and the endpoint should be different. WSA:TO is taking the endpoint's value and ignores my statements as below gc._getServiceClient().getOptions().setProperty(AddressingConstants.WSA_TO,http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/;); Could some shed a light to this? Is there any good API documentation for axis2 ? I am using the latest version 1.4.1..Is this OK? Thanks From: Soyer, Muhammed A. Sent: Wednesday, September 10, 2008 6:55 AM To: 'axis-user@ws.apache.org' Subject: How to add ws-addressing and ws-security headers to call a .Net Service Hi I am new to axis and I am a little lost ... I want to add ws-addressing and ws-security headers to my soap calls in able to conform to my service requirements. I tried a lot of things and I couldn't progress much. I need to build a soap request as below. soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; soap:Header wsa:Actionhttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/AuthenticationPortType/AuthenticateUserRequest/wsa:Action wsa:MessageIDurn:uuid:1978176b-3ce0-4876-bc19-ba172ce40a7e/wsa:MessageID wsa:ReplyTo wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address /wsa:ReplyTo wsa:Tohttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0//wsa:To wsse:Security wsu:Timestamp wsu:Id=Timestamp-3ac1dee5-fd8b-4f98-97ec-92374a714cd2 wsu:Created2008-09-05T16:05:44Z/wsu:Created wsu:Expires2008-09-05T16:10:44Z/wsu:Expires /wsu:Timestamp /wsse:Security /soap:Header soap:Body AuthenticateUserRequest xmlns=http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/; domainNamelocal/domainName userLoginAdministrator/userLogin password type=PasswordTextABCD/password workstationMSOYERXP999/workstation /AuthenticateUserRequest /soap:Body /soap:Envelope But the message that I can create is as below ?xml version = '1.0' encoding = 'UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing; wsa:Tohttp://172.28.69.39:3457/NGX/Router/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:8CCEB06E38921578361221043202900/wsa:MessageID wsa:Actionhttp://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/AuthenticationPortType/AuthenticateUserRequest/wsa:Action /soapenv:Header soapenv:Body ns1:AuthenticateUserRequest xmlns:ns1=http://schemas.ZZZ.com/NGX/1/0/XAuthentication/1/0/; ns1:domainNameYYY/ns1:domainName ns1:userLoginmsoyer/ns1:userLogin ns1:password type=PasswordTextsecret/ns1:password ns1:workstationmsoyerxp/ns1:workstation /ns1:AuthenticateUserRequest /soapenv:Body /soapenv:Envelope I realized that the wsa namespace declarations are different. How can I make them same ? And I couldn't set the WSA:TO element correctly either. It is always taking my endpoint address which is not the case with the .Net client. Any help would be great... Thanks
Controlling the serialization
Hi, Is it possible to control the serialization of the request messages. I am using axis2 1.4.1 to call .Net web services and looks like the other part is not using the standard de-serialization APIs and I am getting issues. Axis is serializing the request as below soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns2:FetchProfileRequest xmlns:ns2=http://htng.org/PWS/2008A/ZZZ/Name/Types; ns2:ProfileID1/ns2:ProfileID /ns2:FetchProfileRequest /soapenv:Body /soapenv:Envelope But the other part is expecting as below soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Body FetchProfileRequest xmlns=http://htng.org/PWS/2008A/ZZZ/Name/Types; ProfileID1/ProfileID /FetchProfileRequest /soap:Body /soap:Envelope Is there an easy way to avoid axis using the namespace alias for each element and use it as the above message? Thanks
RE: Controlling the serialization
Hi again I found a solution for the ns namespace prefixes by passing -sp to wsdl2java.bat during the generation but I still don't know how to use soap instead of soapenv . How can I use soap instead of soapenv? I know this sounds weird but the other side has a custom parser and they don't understand my messages otherwise.. Thanks From: Soyer, Muhammed A. Sent: Wednesday, September 10, 2008 4:00 PM To: axis-user@ws.apache.org Subject: Controlling the serialization Hi, Is it possible to control the serialization of the request messages. I am using axis2 1.4.1 to call .Net web services and looks like the other part is not using the standard de-serialization APIs and I am getting issues. Axis is serializing the request as below soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns2:FetchProfileRequest xmlns:ns2=http://htng.org/PWS/2008A/ZZZ/Name/Types; ns2:ProfileID1/ns2:ProfileID /ns2:FetchProfileRequest /soapenv:Body /soapenv:Envelope But the other part is expecting as below soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Body FetchProfileRequest xmlns=http://htng.org/PWS/2008A/ZZZ/Name/Types; ProfileID1/ProfileID /FetchProfileRequest /soap:Body /soap:Envelope Is there an easy way to avoid axis using the namespace alias for each element and use it as the above message? Thanks
RE: Controlling the serialization
I am getting the below error at the client org.apache.axis2.AxisFault: InputStream cannot be NULL. at org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:214) at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:265) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at com.micros.www.gcwebapi._3_1.GCWebAPIServiceStub.FetchProfile(GCWebAPIServiceStub.java:592) at gcaxis.GCAxisTest.main(GCAxisTest.java:38) When look at the logs of the other side I am seeing errors indicating un-expected end of file .. And when I use a general purpose test tool it works fine with message using soap and creates the same error with the soapenv alias. I agree with you that these messages are semantically same. Thanks -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 10, 2008 5:36 PM To: axis-user@ws.apache.org Subject: Re: Controlling the serialization The two messages are semantically the same. The .NET service should have no trouble deserializing it. What is the message you are receiving? Anne On Wed, Sep 10, 2008 at 3:59 PM, Soyer, Muhammed A. [EMAIL PROTECTED] wrote: Hi, Is it possible to control the serialization of the request messages. I am using axis2 1.4.1 to call .Net web services and looks like the other part is not using the standard de-serialization APIs and I am getting issues. Axis is serializing the request as below soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body ns2:FetchProfileRequest xmlns:ns2=http://htng.org/PWS/2008A/ZZZ/Name/Types; ns2:ProfileID1/ns2:ProfileID /ns2:FetchProfileRequest /soapenv:Body /soapenv:Envelope But the other part is expecting as below soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Body FetchProfileRequest xmlns=http://htng.org/PWS/2008A/ZZZ/Name/Types; ProfileID1/ProfileID /FetchProfileRequest /soap:Body /soap:Envelope Is there an easy way to avoid axis using the namespace alias for each element and use it as the above message? Thanks - 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]
