Re: WSDL Parser java
i'm using now wsdl4j.
also axis2 used wsdl4j, but:
how can i read the xsd inside the wsdl?
i'm able to read all the informations, but not the types of the
message, i will explain better:
a snippet of a wsdl:
wsdl:types
xsd:schema targetNamespace=http://www.example.org/NewWSDLFile/;
xsd:element name=NewOperation
xsd:complexType
xsd:sequence
xsd:element name=in type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=NewOperationResponse
xsd:complexType
xsd:sequence
xsd:element name=out type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:element
/xsd:schema
/wsdl:types
wsdl:message name=NewOperationRequest
wsdl:part element=tns:NewOperation name=parameters/
/wsdl:message
wsdl:message name=NewOperationResponse
wsdl:part element=tns:NewOperationResponse name=parameters/
/wsdl:message
i'm able to read the message :
SchemaExtensibilityElement ({http://www.w3.org/2001/XMLSchema}schema):
required=null
element=[xsd:schema: null]
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
PortType: name={http://www.example.org/NewWSDLFile/}NewWSDLFile
Operation: name=NewOperation
style=REQUEST_RESPONSE
Input: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
Output: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
but i'm not able to read the definition of the content of message like
the lines inside wsdl:types/wsdl:types
any hints about that?
thanks all
--
Stefano
Re: WSDL Parser java
WSDL parsers only support for WSDL content, to read Schema you have to
use a Schema parser try for Apache XmlSchema [1].
[1] - http://ws.apache.org/commons/XmlSchema/
Thanks,
On Wed, Nov 11, 2009 at 3:27 PM, Stefano Tranquillini
stefano.tranquill...@gmail.com wrote:
i'm using now wsdl4j.
also axis2 used wsdl4j, but:
how can i read the xsd inside the wsdl?
i'm able to read all the informations, but not the types of the
message, i will explain better:
a snippet of a wsdl:
wsdl:types
xsd:schema targetNamespace=http://www.example.org/NewWSDLFile/;
xsd:element name=NewOperation
xsd:complexType
xsd:sequence
xsd:element name=in type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=NewOperationResponse
xsd:complexType
xsd:sequence
xsd:element name=out type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:element
/xsd:schema
/wsdl:types
wsdl:message name=NewOperationRequest
wsdl:part element=tns:NewOperation name=parameters/
/wsdl:message
wsdl:message name=NewOperationResponse
wsdl:part element=tns:NewOperationResponse name=parameters/
/wsdl:message
i'm able to read the message :
SchemaExtensibilityElement ({http://www.w3.org/2001/XMLSchema}schema):
required=null
element=[xsd:schema: null]
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
PortType: name={http://www.example.org/NewWSDLFile/}NewWSDLFile
Operation: name=NewOperation
style=REQUEST_RESPONSE
Input: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
Output: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
but i'm not able to read the definition of the content of message like
the lines inside wsdl:types/wsdl:types
any hints about that?
thanks all
--
Stefano
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: WSDL Parser java
i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to know the operation name and type. there's no class that read the wsdl and has method that returns operations name operations parameters and so on? thanks On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini stefano.tranquill...@gmail.com wrote: thanks, i take a look. but, i can use this class and doing what i want or the license of apache blocks me for somethings i.e. use for business applications? On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe deep...@gmail.com wrote: Is this about Axis2 or Axis1? if it is in Axis2 look at WSDL2AxisService Builder class. Thanks, Deepal Hi all. in the code of the project there's a class that parse the wsdl? which one? i need to know all the things inside the wsdl, in particular i'm interested in the name of the operations and smt else. thanks in advance. -- Stefano -- Thank you! http://blogs.deepal.org http://deepal.org -- Stefano -- Stefano
Re: WSDL Parser java
If you plan to write a class from the scratch to read the WSDL and get those details you can use JWSDL API [1] with WSDL4J [2]. [1] - wsdl4j.sourceforge.net/downloads/JSR110_proposed_final_draft.pdf [2] - http://sourceforge.net/projects/wsdl4j/ Thanks, On Sat, Nov 7, 2009 at 10:10 AM, Stefano Tranquillini stefano.tranquill...@gmail.com wrote: i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to know the operation name and type. there's no class that read the wsdl and has method that returns operations name operations parameters and so on? thanks On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini stefano.tranquill...@gmail.com wrote: thanks, i take a look. but, i can use this class and doing what i want or the license of apache blocks me for somethings i.e. use for business applications? On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe deep...@gmail.com wrote: Is this about Axis2 or Axis1? if it is in Axis2 look at WSDL2AxisService Builder class. Thanks, Deepal Hi all. in the code of the project there's a class that parse the wsdl? which one? i need to know all the things inside the wsdl, in particular i'm interested in the name of the operations and smt else. thanks in advance. -- Stefano -- Thank you! http://blogs.deepal.org http://deepal.org -- Stefano -- Stefano -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
Re: WSDL Parser java
i found that there's already smt done in java library: javax.wsdl.xml.WSDLReader On Sat, Nov 7, 2009 at 16:31, Sagara Gunathunga sagara.gunathu...@gmail.com wrote: If you plan to write a class from the scratch to read the WSDL and get those details you can use JWSDL API [1] with WSDL4J [2]. [1] - wsdl4j.sourceforge.net/downloads/JSR110_proposed_final_draft.pdf [2] - http://sourceforge.net/projects/wsdl4j/ Thanks, On Sat, Nov 7, 2009 at 10:10 AM, Stefano Tranquillini stefano.tranquill...@gmail.com wrote: i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to know the operation name and type. there's no class that read the wsdl and has method that returns operations name operations parameters and so on? thanks On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini stefano.tranquill...@gmail.com wrote: thanks, i take a look. but, i can use this class and doing what i want or the license of apache blocks me for somethings i.e. use for business applications? On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe deep...@gmail.com wrote: Is this about Axis2 or Axis1? if it is in Axis2 look at WSDL2AxisService Builder class. Thanks, Deepal Hi all. in the code of the project there's a class that parse the wsdl? which one? i need to know all the things inside the wsdl, in particular i'm interested in the name of the operations and smt else. thanks in advance. -- Stefano -- Thank you! http://blogs.deepal.org http://deepal.org -- Stefano -- Stefano -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/http://people.apache.org/%7Esagara/ -- Stefano
Re: WSDL client generation. Problem with more than one part and binding style document
Le vendredi 25 septembre 2009 à 10:35 +0530, Amila Suriarachchi a écrit : How to develop the fastest way an operational client and set the whole soap envelop you want to send ? Please see here[1] thanks, Amila. [1] http://amilachinthaka.blogspot.com/2009/09/sending-arbitrary-soap-message-with.html Thank you very much Amila, it works perfectly !
Re: WSDL client generation. Problem with more than one part and binding style document
- Amila Suriarachchi amilasuriarach...@gmail.com a écrit : [...] soap:body MapNametheName/MapName MapValues/MapValues /soap:body [...] How can I modify the WSDL to make axis2 generating a client which can produce the above request I want ? Is it possible ? Do I need to change the style to rpc ? If it's not possible, do you know an opensource project which know how to deal with my wsdl ? I think this is not possible with Axis2 unless you write an operational client and set the whole soap envelop you want to send. Thanks Amila, But why doesn't Axis2 know how to generate such a message ? I saw nothing in w3.org/TR/wsdl saying that multi parts inside soap:body is prohibited... I've only see this limitation (for compatibility if I've correctly understood) on ws-i.org. Axis2 only how to generate WS-I ? Not wsdl in general ? How to develop the fastest way an operational client and set the whole soap envelop you want to send ? Thanx again for help and informations
Re: WSDL client generation. Problem with more than one part and binding style document
On Thu, Sep 24, 2009 at 3:58 PM, err...@free.fr wrote: - Amila Suriarachchi amilasuriarach...@gmail.com a écrit : [...] soap:body MapNametheName/MapName MapValues/MapValues /soap:body [...] How can I modify the WSDL to make axis2 generating a client which can produce the above request I want ? Is it possible ? Do I need to change the style to rpc ? If it's not possible, do you know an opensource project which know how to deal with my wsdl ? I think this is not possible with Axis2 unless you write an operational client and set the whole soap envelop you want to send. Thanks Amila, But why doesn't Axis2 know how to generate such a message ? I saw nothing in w3.org/TR/wsdl saying that multi parts inside soap:body is prohibited... I've only see this limitation (for compatibility if I've correctly understood) on ws-i.org. Axis2 only how to generate WS-I ? Not wsdl in general ? This is to solve the problem now you have faced :). If soap stacks do not follow WS-I it is very difficult to interoperate between them. How to develop the fastest way an operational client and set the whole soap envelop you want to send ? Please see here[1] thanks, Amila. [1] http://amilachinthaka.blogspot.com/2009/09/sending-arbitrary-soap-message-with.html Thanx again for help and informations -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL client generation. Problem with more than one part and binding style document
On Thu, Sep 24, 2009 at 5:46 AM, error3 err...@free.fr wrote: Hello, with the attached wsdl file (it's an simplified version of mine), I'm trying to generate WS client (in eclipse, and with Axis2). while trying to generate the client, I have an error saying that more than one part in the message... (I do not have the message nor my development environment at that time). Googlin' and found that document binding style shouldn't have multiple parts message in the body. Ok. So I know that, to querying the webservice (I can't modify it, it's an application one) I must send something like : [...] soap:body MapNametheName/MapName MapValues/MapValues /soap:body [...] How can I modify the WSDL to make axis2 generating a client which can produce the request I want ? Is it possible ? Do I need to change the style to rpc ? If it's not possible, do you know an opensource project which know how to deal with my wsdl ? I think this is not possible with Axis2 unless you write an operational client and set the whole soap envelop you want to send. thanks, Amila. thank you very much for any help, -- Martin -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
RE: WSDL URL is Changing
Axis 2 version is 1.4.1 What is the parameter to that we need to change? Thanks in advance. From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] Sent: Thursday, September 17, 2009 11:21 AM To: axis-user@ws.apache.org Subject: Re: WSDL URL is Changing what is the axis2 version you use? there is a commented parameter in axis2.xml. try changing that. thanks, Amila. On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera shan...@aeturnum.com wrote: My Application is deployed on JBOSS Application server (SSL enabled) and WSDL access URL is https://localhost:9002/web/services/WS?wsdl For some reason its going to redirect to https://localhost:9002/axis2/services/WS?wsdl https://localhost:9002/axis2/services/PayfoneWS?wsdl I haven't specify /axis2/ any were and also my filter in web.xml is as follows, servlet servlet-nameAxisServlet/servlet-name servlet-classorg.apache.axis2.transport.http.AxisServlet/servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/services/*/url-pattern /servlet-mapping Also, in the later time some home client end point change to https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this end point is not working Thanks in advance. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL URL is Changing
On Thu, Sep 17, 2009 at 3:27 PM, E Shanaka Jayasundera shan...@aeturnum.com wrote: Axis 2 version is 1.4.1 What is the parameter to that we need to change? !--parameter name=contextRootaxis2/parameter-- thanks, Amila. Thanks in advance. *From:* Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] *Sent:* Thursday, September 17, 2009 11:21 AM *To:* axis-user@ws.apache.org *Subject:* Re: WSDL URL is Changing what is the axis2 version you use? there is a commented parameter in axis2.xml. try changing that. thanks, Amila. On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera shan...@aeturnum.com wrote: My Application is deployed on JBOSS Application server (SSL enabled) and WSDL access URL is https://localhost:9002/web/services/WS?wsdl For some reason its going to redirect to https://localhost:9002/axis2/services/WS?wsdlhttps://localhost:9002/axis2/services/PayfoneWS?wsdl I haven’t specify /axis2/ any were and also my filter in web.xml is as follows, servlet servlet-nameAxisServlet/servlet-name servlet-classorg.apache.axis2.transport.http.AxisServlet/servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/services/*/url-pattern /servlet-mapping Also, in the later time some home client end point change to https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this end point is not working Thanks in advance. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/ -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL URL is Changing
what is the axis2 version you use? there is a commented parameter in axis2.xml. try changing that. thanks, Amila. On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera shan...@aeturnum.com wrote: My Application is deployed on JBOSS Application server (SSL enabled) and WSDL access URL is https://localhost:9002/web/services/PayfoneWS?wsdl For some reason its going to redirect to https://localhost:9002/axis2/services/PayfoneWS?wsdl I haven’t specify /axis2/ any were and also my filter in web.xml is as follows, servlet servlet-nameAxisServlet/servlet-name servlet-classorg.apache.axis2.transport.http.AxisServlet/servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameAxisServlet/servlet-name url-pattern/services/*/url-pattern /servlet-mapping Also, in the later time some home client end point change to https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this end point is not working Thanks in advance. -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL gen error
And one more pt - If most likely we need to have entities in the WSDL file namespace qualified, and the WSDL parsers on the client side complain if they are not (as in the case of wsdl:types vs. types) then is this an exceptional case that should not occur? Why would Axis generate WSDL tags that the corresponding WSDL parsers cannot handle?? Lars Ericsson wrote: HI Demtirs! I couldn't understand what is your problem, please describe more about your problem. The namespace can be anything, and it is nothing to do whit network, connection or anything else. Please read more about namespace. but if you get two different wsdl from two different environment, sound strange, alse i suppose you have the same axis-version same-java version and so on. Please check manually call any service on those two service, if you don't get the same respons, it is some thing you should be worried about it. otherwise the differences between those two wsdl-s is not importent. *From:* Demetris G demet...@ece.neu.edu *To:* axis-user@ws.apache.org *Sent:* Sunday, July 12, 2009 7:32:32 AM *Subject:* Re: WSDL gen error Hi again, I am beginning to worry that (a) I am either asking a really stupid question here and in the thread that is listed further down in my email that is not worth wasting any time on (b) a really complicated question (I doubt it) (c) I am in the wrong list ... should I move these two questions to the axis-dev you think? If axis is giving me a different WSDL file in two different Linux machines while the configuration and version is the same, is that a bug I need to worry about? And at least any information on how to manipulate the IP address in the WSDL would be greatly appreciated. Anyone?? Thanks once again Demetris Demetris G wrote: Hi all, Calling a service on the same machine as the axis server will set the namespace http://127.0.0.1:8080/axis/services/ However, calling it from another node in the same network behind a NAT still returns the same IP address in the name space - is that normal? Also, how can the IP address in the first case (calling it from the same machine) be set to the true IP address of the machine? Also if anyone has any more info on my email below it will be greatly appreciated. Thanks Demetris Demetris G wrote: And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL gen error
In case it helps the case here is the exception I get on the client side - [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseExtensibilityElement(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) [java] at Utils.myWSDLParser.parseWSDL(myWSDLParser.java:46) Any ideas greatly appreciated - thanks. Demetris G wrote: And one more pt - If most likely we need to have entities in the WSDL file namespace qualified, and the WSDL parsers on the client side complain if they are not (as in the case of wsdl:types vs. types) then is this an exceptional case that should not occur? Why would Axis generate WSDL tags that the corresponding WSDL parsers cannot handle?? Lars Ericsson wrote: HI Demtirs! I couldn't understand what is your problem, please describe more about your problem. The namespace can be anything, and it is nothing to do whit network, connection or anything else. Please read more about namespace. but if you get two different wsdl from two different environment, sound strange, alse i suppose you have the same axis-version same-java version and so on. Please check manually call any service on those two service, if you don't get the same respons, it is some thing you should be worried about it. otherwise the differences between those two wsdl-s is not importent. *From:* Demetris G demet...@ece.neu.edu *To:* axis-user@ws.apache.org *Sent:* Sunday, July 12, 2009 7:32:32 AM *Subject:* Re: WSDL gen error Hi again, I am beginning to worry that (a) I am either asking a really stupid question here and in the thread that is listed further down in my email that is not worth wasting any time on (b) a really complicated question (I doubt it) (c) I am in the wrong list ... should I move these two questions to the axis-dev you think? If axis is giving me a different WSDL file in two different Linux machines while the configuration and version is the same, is that a bug I need to worry about? And at least any information on how to manipulate the IP address in the WSDL would be greatly appreciated. Anyone?? Thanks once again Demetris Demetris G wrote: Hi all, Calling a service on the same machine as the axis server will set the namespace http://127.0.0.1:8080/axis/services/ However, calling it from another node in the same network behind a NAT still returns the same IP address in the name space - is that normal? Also, how can the IP address in the first case (calling it from the same machine) be set to the true IP address of the machine? Also if anyone has any more info on my email below it will be greatly appreciated. Thanks Demetris Demetris G wrote: And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context
Re: WSDL gen error
HI Demtirs! I couldn't understand what is your problem, please describe more about your problem. The namespace can be anything, and it is nothing to do whit network, connection or anything else. Please read more about namespace. but if you get two different wsdl from two different environment, sound strange, alse i suppose you have the same axis-version same-java version and so on. Please check manually call any service on those two service, if you don't get the same respons, it is some thing you should be worried about it. otherwise the differences between those two wsdl-s is not importent. From: Demetris G demet...@ece.neu.edu To: axis-user@ws.apache.org Sent: Sunday, July 12, 2009 7:32:32 AM Subject: Re: WSDL gen error Hi again, I am beginning to worry that (a) I am either asking a really stupid question here and in the thread that is listed further down in my email that is not worth wasting any time on (b) a really complicated question (I doubt it) (c) I am in the wrong list ... should I move these two questions to the axis-dev you think? If axis is giving me a different WSDL file in two different Linux machines while the configuration and version is the same, is that a bug I need to worry about? And at least any information on how to manipulate the IP address in the WSDL would be greatly appreciated. Anyone?? Thanks once again Demetris Demetris G wrote: Hi all, Calling a service on the same machine as the axis server will set the namespace http://127.0.0.1:8080/axis/services/ However, calling it from another node in the same network behind a NAT still returns the same IP address in the name space - is that normal? Also, how can the IP address in the first case (calling it from the same machine) be set to the true IP address of the machine? Also if anyone has any more info on my email below it will be greatly appreciated. Thanks Demetris Demetris G wrote: And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL gen error
Hi Lars, thanks for the response and the info regarding the namespace. My issue is the following - We have the Axis (1.4) bundles running in the OSGi container on a set of Linux machines with no issues. Web Services can be published and invoked upon - the WSDL files that are generated by these Axis bundles are correct and they can generate correct operational stubs. We needed to run a few of these on some powerful mobile devices that can actually run Jalimo, a full version (for fhe most part) of Java 1.5 based on the GNU libraries. So we simply installed the same OSGi container and Axis (1.4) bundles on them and ran them. The Axis servers work as they should, the generate WSDL files when invoked - however, the WSDL file they generate encaplsulate the scheme definitions in types tags instead of wsdl:types ! This is an issue because the XML parsers that process wsdl:types tags nicely have a problem with the types tags. After hours of searching I came upon this - http://issues.apache.org/jira/browse/AXIS-2336. Others a while back have encountered the same issue when running Axis on particular containers. However, (a) their resolution is specific to their container (b) my issue is not the type of container since the OSGi container works fine with Axis. My issue is that I moved more a Linux desktop to a Linux mobile device, even though the executables and runtime remained the same. I know that Axis 1.4 is ancient, however, there are still many of them in production and migration for us is in our future plans but for now we need to get this to work. Any ideas would be greatly appreciated. Regards Lars Ericsson wrote: HI Demtirs! I couldn't understand what is your problem, please describe more about your problem. The namespace can be anything, and it is nothing to do whit network, connection or anything else. Please read more about namespace. but if you get two different wsdl from two different environment, sound strange, alse i suppose you have the same axis-version same-java version and so on. Please check manually call any service on those two service, if you don't get the same respons, it is some thing you should be worried about it. otherwise the differences between those two wsdl-s is not importent. *From:* Demetris G demet...@ece.neu.edu *To:* axis-user@ws.apache.org *Sent:* Sunday, July 12, 2009 7:32:32 AM *Subject:* Re: WSDL gen error Hi again, I am beginning to worry that (a) I am either asking a really stupid question here and in the thread that is listed further down in my email that is not worth wasting any time on (b) a really complicated question (I doubt it) (c) I am in the wrong list ... should I move these two questions to the axis-dev you think? If axis is giving me a different WSDL file in two different Linux machines while the configuration and version is the same, is that a bug I need to worry about? And at least any information on how to manipulate the IP address in the WSDL would be greatly appreciated. Anyone?? Thanks once again Demetris Demetris G wrote: Hi all, Calling a service on the same machine as the axis server will set the namespace http://127.0.0.1:8080/axis/services/ However, calling it from another node in the same network behind a NAT still returns the same IP address in the name space - is that normal? Also, how can the IP address in the first case (calling it from the same machine) be set to the true IP address of the machine? Also if anyone has any more info on my email below it will be greatly appreciated. Thanks Demetris Demetris G wrote: And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very
Re: WSDL gen error
Hi again, I am beginning to worry that (a) I am either asking a really stupid question here and in the thread that is listed further down in my email that is not worth wasting any time on (b) a really complicated question (I doubt it) (c) I am in the wrong list ... should I move these two questions to the axis-dev you think? If axis is giving me a different WSDL file in two different Linux machines while the configuration and version is the same, is that a bug I need to worry about? And at least any information on how to manipulate the IP address in the WSDL would be greatly appreciated. Anyone?? Thanks once again Demetris Demetris G wrote: Hi all, Calling a service on the same machine as the axis server will set the namespace wsdl:definitions targetNamespace=http://127.0.0.1:8080/axis/services/ However, calling it from another node in the same network behind a NAT still returns the same IP address in the name space - is that normal? Also, how can the IP address in the first case (calling it from the same machine) be set to the true IP address of the machine? Also if anyone has any more info on my email below it will be greatly appreciated. Thanks Demetris Demetris G wrote: And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types schema targetNamespace=http://xml.apache.org/xml-soap; ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL gen error
Hi all, Calling a service on the same machine as the axis server will set the namespace wsdl:definitions targetNamespace=http://127.0.0.1:8080/axis/services/ However, calling it from another node in the same network behind a NAT still returns the same IP address in the name space - is that normal? Also, how can the IP address in the first case (calling it from the same machine) be set to the true IP address of the machine? Also if anyone has any more info on my email below it will be greatly appreciated. Thanks Demetris Demetris G wrote: And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types schema targetNamespace=http://xml.apache.org/xml-soap; ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL gen error
At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types schema targetNamespace=http://xml.apache.org/xml-soap; ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL gen error
And scanning through the two WSDL files I see also other diffs - wsdl:message name=mainRequest wsdl:part name=args type=impl:ArrayOf_soapenc_string/ /wsdl:message vs. wsdl:message name=mainRequest wsdl:part name=args type=intf:ArrayOf_soapenc_string/ /wsdl:message So it seems to me that it treats the same service a bit differently on a separate machine even though the setup/config etc of the server is identical. Demetris G wrote: At least someone may know this - what would cause the Axis engine to generate WSDLs with types instead of wsdl:types? If I know that then I can probably figure out why the same Axis engine distribution on two different Linux boxes would generate two different types of WSDLs - I am using the same browser to issue the request: http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl One engine gives this: types schema targetNamespace=http://xml.apache.org/xml-soap; ... /types and the other: wsdl:types schema targetNamespace=http://xml.apache.org/xml-soap; ... /wsdl:types Any ideas? Thanks Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL gen error
And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL gen error
I am still stuck on this one - any hints would be greatly appreciated. Thanks again Demetris G wrote: And a follow up - same Axis engine (running in exactly same OSGi containers, same services, on one Linux machine it generates the WSDL file with types and the other with wsdl:types ! Why is that the case? This is a bit puzzling. Thanks very much in advance Demetris G wrote: Hi all, this may have been asked a while back - what would cause the Axis engine to generate WSDLs that carry types instead of wsdl:types: This causes the WSDL parser I use to throw: [java] WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: Using Axis 1.4 over java 1.5. Any ideas? Thanks
Re: WSDL representation for methods with no input parameters
Hi, You can use an empty sequence to represent a function with no input parameters in (doc-lit style), probably you can try it with java2wsdl tool. Here is one that should work. ?xml version=1.0 encoding=UTF-8? wsdl:definitions xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:mime= http://schemas.xmlsoap.org/wsdl/mime/; xmlns:ns0= http://wso2.org/dyn/codegen/demo; xmlns:soap12= http://schemas.xmlsoap.org/wsdl/ wsdl:types xs:schema xmlns:tns=http://wso2.org/dyn/codegen/demo; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://wso2.org/dyn/codegen/demo; !-- demonstrating element-- xs:element name=myDemo xs:sequence/ /xs:element !-- kept just for the completeness -- xs:element name=myDemoResponse type=xs:int/ /xs:schema /wsdl:types wsdl:message name=myDemoRequest wsdl:part name=parameters element=ns0:myDemo/ /wsdl:message wsdl:message name=myDemoResponse wsdl:part name=parameters element=ns0:myDemoResponse/ /wsdl:message wsdl:portType name=MyServicePortType wsdl:operation name=myDemo wsdl:input message=ns0:myDemoRequest/ wsdl:output message=ns0:myDemoResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=MyServiceSOAP12Binding type=ns0:MyServicePortType soap12:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=myDemo soap12:operation soapAction=urn:myDemo style=document/ wsdl:input soap12:body use=literal/ /wsdl:input wsdl:output soap12:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=MyService wsdl:port name=MyServiceSOAP12port_http binding=ns0:MyServiceSOAP12Binding soap:address location= http://localhost/services/wsdl_mode/SimpleTypeService.php/ /wsdl:port /wsdl:service /wsdl:definitions On Thu, Apr 9, 2009 at 4:43 AM, Bruce Edge bruce.e...@gmail.com wrote: Hi, I'm trying to get up to speed with Axis2/c. Can anyone provide an example of a wsdl that defines functions that do not have input parameters? IOW output parameters only. Thanks -Bruce -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org
Re: wsdl services, binding, and ports
Is this a WSDL question or is this something that you want to do with Axis2/C? It looks to me as if this is a WSDL related problem, and if so, this is not the correct list for that :( Samisa... Sam Carleton wrote: Folks, I would like my one physical to contain all my ports, which there will be quite a few. How exactly is that done? Within the WSDL's service element, should each port be listed? Can I use the same soap:address location or does each port need a different address? What about the binding? I see there is a wsdl:operation element within the binding, do I need a different operation element for every operation? Also, within the binding, what exactly is the soapAction attribute within the soap:operation element? In my WSDL it's value is: urn:mmpp:nodemanager/NewOperation, but I don't have an operation called 'NewOperation', is that just a namespace? If so, what perpose does it serve since I don't see that string anywhere else in the WSDL? Sam No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.285 / Virus Database: 270.11.40/2039 - Release Date: 04/03/09 06:19:00 -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company
Re: wsdl services, binding, and ports
Sam Carleton wrote: On Fri, Apr 3, 2009 at 1:35 PM, Samisa Abeysinghe sam...@wso2.com mailto:sam...@wso2.com wrote: Is this a WSDL question or is this something that you want to do with Axis2/C? It looks to me as if this is a WSDL related problem, and if so, this is not the correct list for that :( You would be correct that this is very WSDL related, but the engine is Axis2/C, which is why I posted here. If there is a pure WSDL forum to post these types of questions, I would love to know where to find it!!! I learned a long time ago that you get quicker responses when you post to the correct forum! If it is Axis2/C specific, ask the question that way. Point to the code location, and explain what you tried to do. Just don't throw in random question on generic WS stuff in here. Samisa... Sam No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.285 / Virus Database: 270.11.40/2039 - Release Date: 04/03/09 06:19:00 -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company
Re: WSDL attachment example
Thanks to Amila, he responded to my previous same question, but I missed it. This example is just what I need. Thank you very much! http://amilachinthaka.blogspot.com/2009/01/using-mtom-with-axis2.html On Wed, Mar 11, 2009 at 12:49 AM, Nan Null null@gmail.com wrote: I am developing a WSDL for a web service. However, I don't know what is the standard way of having an attachment or two in web service calls (with other data). The problem is that I saw some example, but in the WSDL, there is no mention of the attachment. I also use the Axis2 example of attachment, and then view the WSDL, again, there is no mention of the attachment. In the client and server code, the attachment is there (manually added into the code). After the WSDL is created, it will be sent to another unit for development. Therefore, if I need 1 or more attachment in an operation, I need a way to specify it exactly (as input, output or both). Please point me to the right location or give me a snippet of code. It cannot be this hard. Please use standard code only. Thanks.
Re: WSDL Specs
Try Web Services Essentials by Ethan Cerami, published by O'Reilly 2002 - Original Message - From: Harshad Chavan To: axis-user@ws.apache.org Sent: Monday, February 09, 2009 4:55 PM Subject: WSDL Specs Hi all, Does anybody know about any book/article, which explains WSDL and SOAP in detail (Not necessarily in Axis context). I went to w3c site, but the information is too cryptic. What we want to do is consume web services by third party, by reading the WSDLs from third party servers. Any help will be great. Thanks Harshad LongJump - Platform as a Service -- No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.233 / Virus Database: 270.10.19/1942 - Release Date: 02/08/09 17:57:00
Re: WSDL Specs
Thanks Michael. LongJump - Platform as a Service --- On Mon, 2/9/09, Michael mtarullo...@optonline.net wrote: From: Michael mtarullo...@optonline.net Subject: Re: WSDL Specs To: axis-user@ws.apache.org Date: Monday, February 9, 2009, 2:52 PM Try Web Services Essentials by Ethan Cerami, published by O'Reilly 2002 - Original Message - From: Harshad Chavan To: axis-user@ws.apache.org Sent: Monday, February 09, 2009 4:55 PM Subject: WSDL Specs Hi all, Does anybody know about any book/article, which explains WSDL and SOAP in detail (Not necessarily in Axis context). I went to w3c site, but the information is too cryptic. What we want to do is consume web services by third party, by reading the WSDLs from third party servers. Any help will be great. Thanks Harshad LongJump - Platform as a Service No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.233 / Virus Database: 270.10.19/1942 - Release Date: 02/08/09 17:57:00
Re: WSDL Specs
the following article from W3C , still it explains all the aspects of WSDL2.0 using examples. i myself learned WSDL2.0 using this primer. hope this is useful :) http://www.w3.org/TR/wsdl20-primer/
Re: WSDL Specs
On Tue, Feb 10, 2009 at 3:25 AM, Harshad Chavan harshadcha...@yahoo.comwrote: Hi all, Does anybody know about any book/article, which explains WSDL and SOAP in detail (Not necessarily in Axis context). I went to w3c site, but the information is too cryptic. Following articles explains the wsdl and soap basics[1][2]. After following this you may read the corresponding specifications for more information. thanks, Amila. [1] http://wso2.org/library/2873 [2] http://wso2.org/node/2935/ What we want to do is consume web services by third party, by reading the WSDLs from third party servers. Any help will be great. Thanks Harshad LongJump - Platform as a Service http://www.longjump.com -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Re: WSDL version issue
The WSDL namespace URI indicates the WSDL version. Anne On 1/19/09, Shah Asrani shahasr...@gmail.com wrote: Hi, Is the any way in Axis2 to find out the version of WSDL file programmatically, I need to find ouf if a given WSDL file is version 1.1 or 2.0? Best Regards
RE: WSDL Generation has incorrect port
Hello Nandana, Thanks for the reply. Is there a nightly build I can download? Or do I need to get the latest code from the trunk and build it? And where do I get the trunk from? Thanks, Kevin Witten Software Engineer Nomadix, Inc. * 1100 Business Center Circle, Suite 100, Newbury Park, CA 91320 * USA direct +1 (818) 575-2421 * main +1-818-597-1500 * fax interTouch Group of Companies * a NTT DoCoMo Group company Enhancing Guest Experience www.inter-touch.comhttp://www.inter-touch.com/ * www.maginet.nethttp://www.maginet.net/ * www.percipia.comhttp://www.percipia.com/ * www.nomadix.com http://www.nomadix.com/ * www.azure.com.auhttp://www.azure.com.au/ From: Nandana Mihindukulasooriya [mailto:nandana@gmail.com] Sent: Tuesday, January 06, 2009 8:09 PM To: axis-user@ws.apache.org Subject: Re: WSDL Generation has incorrect port Hi Kevin, Did you try this with the trunk ? There were few changes with respect to this in the trunk. thanks, nandana On Wed, Jan 7, 2009 at 3:45 AM, Kevin Witten kevin.wit...@nomadix.commailto:kevin.wit...@nomadix.com wrote: Hello, I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd. I setup Apache httpd to only support SSL and to connect to Tomcat via a proxy (AJP), via port 8009. Apache httpd.conf has SSLProxyEngine On ProxyRequests Off ProxyPass / ajp://localhost:8009/ ProxyPassReverse / ajp://localhost:8009/ ProxyPreserveHost On Tomcat server.xml has the following connector Connector port=8009 protocol=AJP/1.3 proxyPort=443/ Now I deploy an Axis2 service (ACSService.aar) in the webapps\axis2\WEB-INF\services directory. Restart Tomcat and Apache. This service includes a WSDL file with the following port: !-- The ACS Service -- wsdl:service name=ACSService wsdl:port binding=tns:ACSServiceSOAP name=ACSServiceSOAP soap:address location=https://localhost/axis2/services/ACSService/ /wsdl:port /wsdl:service I have changed the services.xml file to include parameter name=useOriginalwsdltrue/parameter Now when I run get the WSDL from the service (i.e. https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port is not correct. Notice the port 80. This is not correct as the only way to access this service is through SSL (port 443) as Apache is configured. wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13:80/axis2/services/ACSService// /wsdl:port /wsdl:service Next I tried adding the following to services.xml parameter name=modifyUserWSDLPortAddressfalse/parameter But this did not do what I expected. I would have expected the hostname up get updated to 67.130.148.13. Instead the URL was not changed at all. So the output was as follows, which is the unmodified URL form the original WSDL. wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://localhost/axis2/services/ACSService// /wsdl:port /wsdl:service This seems like a bug, as the modifyUserWSDLPortAddress controls updating of the hostname and port. How do I get the WSDL to update to the hostname with no port, or as a second choice port 443? wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13/axis2/services/ACSService// /wsdl:port /wsdl:service Thanks in advanced for the help. Kevin Witten Software Engineer Nomadix, Inc. * 1100 Business Center Circle, Suite 100, Newbury Park, CA 91320 * USA direct +1 (818) 575-2421 * main +1-818-597-1500 * fax interTouch Group of Companies * a NTT DoCoMo Group company Enhancing Guest Experience www.inter-touch.comhttp://www.inter-touch.com/ * www.maginet.nethttp://www.maginet.net/ * www.percipia.comhttp://www.percipia.com/ * www.nomadix.com http://www.nomadix.com/ * www.azure.com.auhttp://www.azure.com.au/ Notice● The information and attachment(s) contained in this communication are intended for the addressee only, and may be confidential and/or legally privileged. If you have received this communication in error, please contact the sender immediately, and delete this communication from any computer or network system. Any interception, review, printing, copying, re-transmission, dissemination, or other use of, or taking of any action upon this information by persons or entities other than the intended recipient is strictly prohibited by law and may subject them to criminal or civil liability. None of the interTouch Group of Companies shall be liable for the improper and/or incomplete transmission of the information contained in this communication or for any delay in its receipt. Notice● The information and attachment(s) contained
RE: WSDL Generation has incorrect port
I downloaded and build the latest trunk and gave it a try. Still does not work. The useOriginalwsdl parameter in the services.xml has no affect at all. The modifyUserWSDLPortAddress parameter, if set to true, in the services.xml causes the wsdl writer to change both the hostname and the port. So I get wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13:80/axis2/services/ACSService.ACSServiceSOAP// /wsdl:port /wsdl:service Notice the port is 80. What I need is wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13/axis2/services/ACSService.ACSServiceSOAP// /wsdl:port /wsdl:service Because Apache is configured to only accept https connections on the default port. Alternatively, this would also work wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13:443/axis2/services/ACSService.ACSServiceSOAP// /wsdl:port /wsdl:service Any other ideas? Kevin Witten Software Engineer Nomadix, Inc. * 1100 Business Center Circle, Suite 100, Newbury Park, CA 91320 * USA direct +1 (818) 575-2421 * main +1-818-597-1500 * fax interTouch Group of Companies * a NTT DoCoMo Group company Enhancing Guest Experience www.inter-touch.comhttp://www.inter-touch.com/ * www.maginet.nethttp://www.maginet.net/ * www.percipia.comhttp://www.percipia.com/ * www.nomadix.com http://www.nomadix.com/ * www.azure.com.auhttp://www.azure.com.au/ From: Nandana Mihindukulasooriya [mailto:nandana@gmail.com] Sent: Tuesday, January 06, 2009 8:09 PM To: axis-user@ws.apache.org Subject: Re: WSDL Generation has incorrect port Hi Kevin, Did you try this with the trunk ? There were few changes with respect to this in the trunk. thanks, nandana On Wed, Jan 7, 2009 at 3:45 AM, Kevin Witten kevin.wit...@nomadix.commailto:kevin.wit...@nomadix.com wrote: Hello, I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd. I setup Apache httpd to only support SSL and to connect to Tomcat via a proxy (AJP), via port 8009. Apache httpd.conf has SSLProxyEngine On ProxyRequests Off ProxyPass / ajp://localhost:8009/ ProxyPassReverse / ajp://localhost:8009/ ProxyPreserveHost On Tomcat server.xml has the following connector Connector port=8009 protocol=AJP/1.3 proxyPort=443/ Now I deploy an Axis2 service (ACSService.aar) in the webapps\axis2\WEB-INF\services directory. Restart Tomcat and Apache. This service includes a WSDL file with the following port: !-- The ACS Service -- wsdl:service name=ACSService wsdl:port binding=tns:ACSServiceSOAP name=ACSServiceSOAP soap:address location=https://localhost/axis2/services/ACSService/ /wsdl:port /wsdl:service I have changed the services.xml file to include parameter name=useOriginalwsdltrue/parameter Now when I run get the WSDL from the service (i.e. https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port is not correct. Notice the port 80. This is not correct as the only way to access this service is through SSL (port 443) as Apache is configured. wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13:80/axis2/services/ACSService// /wsdl:port /wsdl:service Next I tried adding the following to services.xml parameter name=modifyUserWSDLPortAddressfalse/parameter But this did not do what I expected. I would have expected the hostname up get updated to 67.130.148.13. Instead the URL was not changed at all. So the output was as follows, which is the unmodified URL form the original WSDL. wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://localhost/axis2/services/ACSService// /wsdl:port /wsdl:service This seems like a bug, as the modifyUserWSDLPortAddress controls updating of the hostname and port. How do I get the WSDL to update to the hostname with no port, or as a second choice port 443? wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13/axis2/services/ACSService// /wsdl:port /wsdl:service Thanks in advanced for the help. Kevin Witten Software Engineer Nomadix, Inc. * 1100 Business Center Circle, Suite 100, Newbury Park, CA 91320 * USA direct +1 (818) 575-2421 * main +1-818-597-1500 * fax interTouch Group of Companies * a NTT DoCoMo Group company Enhancing Guest Experience www.inter-touch.comhttp://www.inter-touch.com/ * www.maginet.nethttp://www.maginet.net/ * www.percipia.comhttp://www.percipia.com/ * www.nomadix.com http://www.nomadix.com/ * www.azure.com.auhttp
Re: WSDL Generation has incorrect port
Hi Kevin, Did you try this with the trunk ? There were few changes with respect to this in the trunk. thanks, nandana On Wed, Jan 7, 2009 at 3:45 AM, Kevin Witten kevin.wit...@nomadix.comwrote: Hello, I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd. I setup Apache httpd to only support SSL and to connect to Tomcat via a proxy (AJP), via port 8009. Apache httpd.conf has SSLProxyEngine On ProxyRequests Off ProxyPass / ajp://localhost:8009/ ProxyPassReverse / ajp://localhost:8009/ ProxyPreserveHost On Tomcat server.xml has the following connector Connector port=8009 protocol=AJP/1.3 proxyPort=443/ Now I deploy an Axis2 service (ACSService.aar) in the webapps\axis2\WEB-INF\services directory. Restart Tomcat and Apache. This service includes a WSDL file with the following port: !-- The ACS Service -- wsdl:service name=ACSService wsdl:port binding=tns:ACSServiceSOAP name=ACSServiceSOAP soap:address location=https://localhost/axis2/services/ACSService / /wsdl:port /wsdl:service I have changed the services.xml file to include parameter name=useOriginalwsdltrue/parameter Now when I run get the WSDL from the service (i.e. https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port is not correct. Notice the port 80. This is not correct as the only way to access this service is through SSL (port 443) as Apache is configured. wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location= https://67.130.148.13:80/axis2/services/ACSService// /wsdl:port /wsdl:service Next I tried adding the following to services.xml parameter name=modifyUserWSDLPortAddressfalse/parameter But this did not do what I expected. I would have expected the hostname up get updated to 67.130.148.13. Instead the URL was not changed at all. So the output was as follows, which is the unmodified URL form the original WSDL. wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://localhost/axis2/services/ACSService// /wsdl:port /wsdl:service This seems like a bug, as the modifyUserWSDLPortAddress controls updating of the hostname and port. How do I get the WSDL to update to the hostname with no port, or as a second choice port 443? wsdl:service name=ACSService wsdl:port name=ACSServiceSOAP binding=nomadixacs:ACSServiceSOAP soap:address location=https://67.130.148.13/axis2/services/ACSService/ / /wsdl:port /wsdl:service Thanks in advanced for the help. *Kevin Witten* Software Engineer Nomadix, Inc. * 1100 Business Center Circle, Suite 100, Newbury Park, CA 91320 * USA direct +1 (818) 575-2421 * main +1-818-597-1500 * fax *interTouch Group of Companies * a NTT DoCoMo Group company *Enhancing Guest Experience www.inter-touch.com * www.maginet.net * www.percipia.com * www.nomadix.com * www.azure.com.au -- Notice● The information and attachment(s) contained in this communication are intended for the addressee only, and may be confidential and/or legally privileged. If you have received this communication in error, please contact the sender immediately, and delete this communication from any computer or network system. Any interception, review, printing, copying, re-transmission, dissemination, or other use of, or taking of any action upon this information by persons or entities other than the intended recipient is strictly prohibited by law and may subject them to criminal or civil liability. None of the interTouch Group of Companies shall be liable for the improper and/or incomplete transmission of the information contained in this communication or for any delay in its receipt.
Re: wsdl problem
Miguel, Did you try this also with a more recent version of Axis2? Andreas On Tue, Dec 9, 2008 at 05:11, [EMAIL PROTECTED] wrote: Hi I have the following wsdl error when i deploy my web service project in a soalris server i get this information via http://ipserver:8080/MileniaServices/services/wsMilenia?wsdl - wsdl:service name=wsMilenia - wsdl:port name=wsMileniaSOAP11port_http binding=axis2:wsMileniaSOAP11Binding soap:address location=http://ipserver:8080/MileniaServices/services/wsMilenia; / /wsdl:port - wsdl:port name=wsMileniaSOAP12port_http binding=axis2:wsMileniaSOAP12Binding soap12:address location=http://ipserver:8080/MileniaServices/services/wsMilenia; / /wsdl:port - wsdl:port name=wsMileniaHttpport1 binding=axis2:wsMileniaHttpBinding http:address location=http://ipserver:8080/MileniaServices/rest/wsMilenia; / /wsdl:port /wsdl:service but suddenly or when i restart the tomcat server y get the following information in the wsdl via http://ipserver:8080/MileniaServices/services/wsMilenia?wsdl - wsdl:service name=wsMilenia - wsdl:port name=wsMileniaSOAP11port_http binding=axis2:wsMileniaSOAP11Binding soap:address location=http://ipserver:8080/axis2/services/wsMilenia; / /wsdl:port - wsdl:port name=wsMileniaSOAP12port_http binding=axis2:wsMileniaSOAP12Binding soap12:address location=http://ipserver:8080/axis2/services/wsMilenia; / /wsdl:port - wsdl:port name=wsMileniaHttpport1 binding=axis2:wsMileniaHttpBinding http:address location=http://ipserver:8080/axis2/rest/wsMilenia; / /wsdl:port /wsdl:service it is, the context name changes from MileniaServices to axis2 in the address attribute of the soap,soap12 and http tag of the wsdl so, i have to restart tomcat sometimes several times to it changes to the context i want (MileniaServices), it affects to my .net web services clients, because this reference is changing i've tried with parameter name=useOrignalWSDL true /parameter in the services.xml file but it gets me confused if axis2 really take it or not i really will be appreciate you be able to help me axis version axis2-1.1.1 tomcat versiontomcat 5.0.28 thanks!!! Miguel
Re: WSDL issue in Axis-C
hmm that is very strange. What is the version of Axis2 taht you are using? SAmisa... Primal Wijesekera wrote: No, TCPMon did not show any response from the server end. I think server crashes before sending the response. When I checked a memory dump of the crashed process, it says something wrong about axis2_engine.dll. But I am not an expert in examining memory dumps so I might be wrong. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 10:46:56 AM Subject: Re: WSDL issue in Axis-C The error happens in parsing the response sent from the service. Did you not get a response on TCPMon? Samisa... Primal Wijesekera wrote: Hi, There is not response from the server. When a client send the request, it gets crashed so response from it. I am attaching the client requests received by the server. I captured this using tcpmon tool. When I uses .Net 2003 client it crashed without giving any errors, when I used the .Net 2008 client it crashed giving the error message Invalid XML As of I know this can not be happened, like different client should not have different SOAP request since they all work on a same WSDL. However unfortunately it is happening, thats why i am suspecting that there can be error in the WSDL mapping. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org mailto:axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 9:54:49 AM Subject: Re: WSDL issue in Axis-C What is the request/response pair? Samisa... Primal Wijesekera wrote: Hi, I am using Apache 2.2.6 and wso2-wsf-c 1.3.0 on windows. I have successfully configured the WSF to work with Apache. It now shows the services deploy in Axis-c using apache web server. All the example clients shipped with axis-c is alse working (echo.exe). But my problem is with integrating wsdl with those services. When i tried to access the WSDL given for the calulator service from the .net client, it successfully detects the WSDL and create client ctub but when a method is called from that client the axis-c server gets crashed. I even tried this with the simple http server that comes with the Axis-c, btu still it crashes when a client calls its services via WSDL. So my What i feel is, there is something wrong in the WSDL to service mapping. Would that happen ? What could be the reason for this ?? P.S : Attached is the WSDL and the service.xml for calculator service. Regards, Primal - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company
Re: WSDL issue in Axis-C
Hi, I am using WSF-C version 1.3 from WSO2, and i think the version of Axis2c is 1.4. Apache version is 2.2.6 . Axis2 C should work with WSDL, right ? Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 1:17:09 PM Subject: Re: WSDL issue in Axis-C hmm that is very strange. What is the version of Axis2 taht you are using? SAmisa... Primal Wijesekera wrote: No, TCPMon did not show any response from the server end. I think server crashes before sending the response. When I checked a memory dump of the crashed process, it says something wrong about axis2_engine.dll. But I am not an expert in examining memory dumps so I might be wrong. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 10:46:56 AM Subject: Re: WSDL issue in Axis-C The error happens in parsing the response sent from the service. Did you not get a response on TCPMon? Samisa... Primal Wijesekera wrote: Hi, There is not response from the server. When a client send the request, it gets crashed so response from it. I am attaching the client requests received by the server. I captured this using tcpmon tool. When I uses .Net 2003 client it crashed without giving any errors, when I used the .Net 2008 client it crashed giving the error message Invalid XML As of I know this can not be happened, like different client should not have different SOAP request since they all work on a same WSDL. However unfortunately it is happening, thats why i am suspecting that there can be error in the WSDL mapping. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org mailto:axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 9:54:49 AM Subject: Re: WSDL issue in Axis-C What is the request/response pair? Samisa... Primal Wijesekera wrote: Hi, I am using Apache 2.2.6 and wso2-wsf-c 1.3.0 on windows. I have successfully configured the WSF to work with Apache. It now shows the services deploy in Axis-c using apache web server. All the example clients shipped with axis-c is alse working (echo.exe). But my problem is with integrating wsdl with those services. When i tried to access the WSDL given for the calulator service from the .net client, it successfully detects the WSDL and create client ctub but when a method is called from that client the axis-c server gets crashed. I even tried this with the simple http server that comes with the Axis-c, btu still it crashes when a client calls its services via WSDL. So my What i feel is, there is something wrong in the WSDL to service mapping. Would that happen ? What could be the reason for this ?? P.S : Attached is the WSDL and the service.xml for calculator service. Regards, Primal - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company
Re: WSDL issue in Axis-C
Primal Wijesekera wrote: Hi, I am using WSF-C version 1.3 from WSO2, and i think the version of Axis2c is 1.4. Apache version is 2.2.6 . This might be a problem with WSO2 framework and not Axis2/C. Specially something related to configuration. Please raise the issue with the WSO2 forums. Thanks, Samisa... Axis2 C should work with WSDL, right ? Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 1:17:09 PM Subject: Re: WSDL issue in Axis-C hmm that is very strange. What is the version of Axis2 taht you are using? SAmisa... Primal Wijesekera wrote: No, TCPMon did not show any response from the server end. I think server crashes before sending the response. When I checked a memory dump of the crashed process, it says something wrong about axis2_engine.dll. But I am not an expert in examining memory dumps so I might be wrong. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org mailto:axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 10:46:56 AM Subject: Re: WSDL issue in Axis-C The error happens in parsing the response sent from the service. Did you not get a response on TCPMon? Samisa... Primal Wijesekera wrote: Hi, There is not response from the server. When a client send the request, it gets crashed so response from it. I am attaching the client requests received by the server. I captured this using tcpmon tool. When I uses .Net 2003 client it crashed without giving any errors, when I used the .Net 2008 client it crashed giving the error message Invalid XML As of I know this can not be happened, like different client should not have different SOAP request since they all work on a same WSDL. However unfortunately it is happening, thats why i am suspecting that there can be error in the WSDL mapping. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org mailto:axis-c-user@ws.apache.org mailto:axis-c-user@ws.apache.org mailto:axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 9:54:49 AM Subject: Re: WSDL issue in Axis-C What is the request/response pair? Samisa... Primal Wijesekera wrote: Hi, I am using Apache 2.2.6 and wso2-wsf-c 1.3.0 on windows. I have successfully configured the WSF to work with Apache. It now shows the services deploy in Axis-c using apache web server. All the example clients shipped with axis-c is alse working (echo.exe). But my problem is with integrating wsdl with those services. When i tried to access the WSDL given for the calulator service from the .net client, it successfully detects the WSDL and create client ctub but when a method is called from that client the axis-c server gets crashed. I even tried this with the simple http server that comes with the Axis-c, btu still it crashes when a client calls its services via WSDL. So my What i feel is, there is something wrong in the WSDL to service mapping. Would that happen ? What could be the reason for this ?? P.S : Attached is the WSDL and the service.xml for calculator service. Regards, Primal - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL
Re: WSDL issue in Axis-C
What is the request/response pair? Samisa... Primal Wijesekera wrote: Hi, I am using Apache 2.2.6 and wso2-wsf-c 1.3.0 on windows. I have successfully configured the WSF to work with Apache. It now shows the services deploy in Axis-c using apache web server. All the example clients shipped with axis-c is alse working (echo.exe). But my problem is with integrating wsdl with those services. When i tried to access the WSDL given for the calulator service from the .net client, it successfully detects the WSDL and create client ctub but when a method is called from that client the axis-c server gets crashed. I even tried this with the simple http server that comes with the Axis-c, btu still it crashes when a client calls its services via WSDL. So my What i feel is, there is something wrong in the WSDL to service mapping. Would that happen ? What could be the reason for this ?? P.S : Attached is the WSDL and the service.xml for calculator service. Regards, Primal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL issue in Axis-C
Hi, There is not response from the server. When a client send the request, it gets crashed so response from it. I am attaching the client requests received by the server. I captured this using tcpmon tool. When I uses .Net 2003 client it crashed without giving any errors, when I used the .Net 2008 client it crashed giving the error message Invalid XML As of I know this can not be happened, like different client should not have different SOAP request since they all work on a same WSDL. However unfortunately it is happening, thats why i am suspecting that there can be error in the WSDL mapping. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 9:54:49 AM Subject: Re: WSDL issue in Axis-C What is the request/response pair? Samisa... Primal Wijesekera wrote: Hi, I am using Apache 2.2.6 and wso2-wsf-c 1.3.0 on windows. I have successfully configured the WSF to work with Apache. It now shows the services deploy in Axis-c using apache web server. All the example clients shipped with axis-c is alse working (echo.exe). But my problem is with integrating wsdl with those services. When i tried to access the WSDL given for the calulator service from the .net client, it successfully detects the WSDL and create client ctub but when a method is called from that client the axis-c server gets crashed. I even tried this with the simple http server that comes with the Axis-c, btu still it crashes when a client calls its services via WSDL. So my What i feel is, there is something wrong in the WSDL to service mapping. Would that happen ? What could be the reason for this ?? P.S : Attached is the WSDL and the service.xml for calculator service. Regards, Primal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Request from a .Net 1.1 Client POST /axis2/services/Calculator HTTP/1.1 VsDebuggerCausalityData: AwW+WrZbqF5PgKjPUWhXyKs AAACAEwAAoBMAsPMSAAB2AGUAcgBzAGkAbwBuAD0ANwAuADAAOwBhAHUAdABvAGE AdAB0AGEAYwBoAGMAbABzAGkAZAA9AHsANwAwAEYANgA1ADQAMQAxAC0ARgBFADgAQwAtADQAMgA0ADg ALQBCAEMARgBGAC0ANwAwADEAQwA4AEIAMgBGADQANQAyADkAfQA7AHMAZQBzAHMAaQBvAG4APQB7ADY ANQA4ADcANAAxADkAMwAtAEMARAA3ADIALQA0ADMAMABCAC0AQgBDAEQAOAAtAEQARAAzADMAMgA1AEI ANwBCADcAQgBBAH0
Re: WSDL issue in Axis-C
The error happens in parsing the response sent from the service. Did you not get a response on TCPMon? Samisa... Primal Wijesekera wrote: Hi, There is not response from the server. When a client send the request, it gets crashed so response from it. I am attaching the client requests received by the server. I captured this using tcpmon tool. When I uses .Net 2003 client it crashed without giving any errors, when I used the .Net 2008 client it crashed giving the error message Invalid XML As of I know this can not be happened, like different client should not have different SOAP request since they all work on a same WSDL. However unfortunately it is happening, thats why i am suspecting that there can be error in the WSDL mapping. Regards, Primal - Original Message From: Samisa Abeysinghe [EMAIL PROTECTED] To: Apache AXIS C User List axis-c-user@ws.apache.org Sent: Friday, October 10, 2008 9:54:49 AM Subject: Re: WSDL issue in Axis-C What is the request/response pair? Samisa... Primal Wijesekera wrote: Hi, I am using Apache 2.2.6 and wso2-wsf-c 1.3.0 on windows. I have successfully configured the WSF to work with Apache. It now shows the services deploy in Axis-c using apache web server. All the example clients shipped with axis-c is alse working (echo.exe). But my problem is with integrating wsdl with those services. When i tried to access the WSDL given for the calulator service from the .net client, it successfully detects the WSDL and create client ctub but when a method is called from that client the axis-c server gets crashed. I even tried this with the simple http server that comes with the Axis-c, btu still it crashes when a client calls its services via WSDL. So my What i feel is, there is something wrong in the WSDL to service mapping. Would that happen ? What could be the reason for this ?? P.S : Attached is the WSDL and the service.xml for calculator service. Regards, Primal - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1715 - Release Date: 10/8/2008 7:19 PM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl-level client side compatibility between Axis 2 and Axis 1
Axis2 does not support soap-encoding (whereas Axis does), but soap-encoding is actually deprecated. Other then that you should be just fine. And its much better for you to go with Axis2 than Axis. Thanks, Keith. On Tue, Sep 30, 2008 at 2:55 AM, Steve Cohen [EMAIL PROTECTED] wrote: Will a WSDL written and recommended to be used with Axis 1 definitely be usable with Axis 2 on the client side? We have no investment in Axis 1 so if the switch is possible, we should probably make it now. My group is going to be incorporating several web service clients into an application that currently has none, so my question is geared toward selecting the best client side technology going forward. - 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: wsdl port address uses incorrect port number for https
Hi, Does Axis2 include a class for transport listener which supports https? Is it possible to configure Axis2 to not include any port number when generating the soap address? Thanks, JP From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2008 4:10 PM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number for https Hi, The proxyPort does not help us as we are not using Apache as a proxy server. If I configure the axis2.xml as below: transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter /transportReceiver transportReceiver name=https class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8443/parameter /transportReceiver then the soap address for http includes the port 8080 and the soap address for https includes the port 8443 but the soap address itself is http and not https. When should the class for transportReceiver be set to for https? If I do not specify the transportReceiver for https in axis2.xml, the the default value of the port is taken as 80 instead of 443 which is the default port for https. Thanks, JP From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 9:09 PM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis 2.xml for an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED] wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 10:02 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED] wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav Subject: RE: wsdl port address uses incorrect port number for https Date: Sun, 21 Sep 2008 09:51:13 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org; axis-user@ws.apache.org Hi, My Axis2 web service is deployed for secure access and the URL is of the form https:// https:/// hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https). I have verified that the port number in the request object is also 443. Is this a bug in Axis2? Regards, Jai -Original Message- From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] Sent: Fri 9/19/2008 8:52 AM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl
RE: wsdl port address uses incorrect port number for https
Yes, I agree doesn't make sense to use the SimpleHTTPServer class for http and https. Looks like Axis2 uses a HTTPSListener internally if https configuration is not available in the axis2.xml. However this class is private and not exposed to general use. I noticed the SSL configuration about configuring non-blocking https transport based on SSL-NIO extensions. But to use it I need to configure keystore and truststore. All I am looking for is that the soap address generated in the WSDL has either no port number or the correct port number for https. JP From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2008 6:53 PM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number for https doesnt make sense to use the same org.apache.axis2.transport.http.SimpleHTTPServer class for both http and https transport this is the SSL configuration I see for configuring HttpCoreNIOSSLListener in axis2.xml !-- the non blocking https transport based on HttpCore + SSL-NIO extensions transportReceiver name=https class=org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener parameter name=port locked=false9002/parameter parameter name=non-blocking locked=falsetrue/parameter parameter name=keystore locked=false KeyStore Locationidentity.jks/Location TypeJKS/Type Passwordpassword/Password KeyPasswordpassword/KeyPassword /KeyStore /parameter parameter name=truststore locked=false TrustStore Locationtrust.jks/Location TypeJKS/Type Passwordpassword/Password /TrustStore /parameter-- !--parameter name=SSLVerifyClientrequire/parameter supports optional|require or defaults to none -- !--/transportReceiver-- //the default behaviour is to have your service engage Rampart module as in this definition in services.xml service... module ref=rampart / parameter name=InflowSecurity action itemsTimestamp Signature/items signaturePropFileservice.properties/signaturePropFile /action /parameter parameter name=OutflowSecurity action itemsTimestamp Signature/items userservice/user passwordCallbackClassorg.apache.rampart.samples.sample04.PWCBHandler/ passwordCallbackClass signaturePropFileservice.properties/signaturePropFile signatureKeyIdentifierDirectReference/signatureKeyIdentifier /action /parameter .. /service HTH Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: RE: wsdl port address uses incorrect port number for https Date: Mon, 22 Sep 2008 17:10:22 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Hi, The proxyPort does not help us as we are not using Apache as a proxy server. If I configure the axis2.xml as below: transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter /transportReceiver transportReceiver name=https class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8443/parameter /transportReceiver then the soap address for http includes the port 8080 and the soap address for https includes the port 8443 but the soap address itself is http and not https. When should the class for transportReceiver be set to for https? If I do not specify the transportReceiver for https in axis2.xml, the the default value of the port is taken as 80 instead of 443 which is the default port for https. Thanks, JP From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 9:09 PM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis 2.xml for an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED] wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2
Re: wsdl port address uses incorrect port number for https
You could easily extend the Listener shipped with Axis2 and override its getEPRsForService method. This is the method that generates the endpoint address, so you could handle it the way you want it to be by simple extending it. Thanks, Keith. On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP) [EMAIL PROTECTED]wrote: Hi, Does Axis2 include a class for transport listener which supports https? Is it possible to configure Axis2 to not include any port number when generating the soap address? Thanks, JP -- *From:* Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] *Sent:* Monday, September 22, 2008 4:10 PM *To:* axis-user@ws.apache.org *Subject:* RE: wsdl port address uses incorrect port number for https Hi, The proxyPort does not help us as we are not using Apache as a proxy server. If I configure the axis2.xml as below: transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter /transportReceiver transportReceiver name=https class= org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8443/parameter /transportReceiver then the soap address for http includes the port 8080 and the soap address for https includes the port 8443 but the soap address itself is http and not https. When should the class for transportReceiver be set to for https? If I do not specify the transportReceiver for https in axis2.xml, the the default value of the port is taken as 80 instead of 443 which is the default port for https. Thanks, JP -- *From:* keith chapman [mailto:[EMAIL PROTECTED] *Sent:* Sunday, September 21, 2008 9:09 PM *To:* axis-user@ws.apache.org *Subject:* Re: wsdl port address uses incorrect port number for https It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED]wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai -- *From:* keith chapman [mailto:[EMAIL PROTECTED] *Sent:* Sunday, September 21, 2008 10:02 AM *To:* axis-user@ws.apache.org *Subject:* Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED]wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav -- Subject: RE: wsdl port address uses incorrect port number for https Date: Sun, 21 Sep 2008 09:51:13 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org; axis-user@ws.apache.org Hi, My Axis2 web service is deployed for secure access and the URL is of the form https:// https:///hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https). I have verified that the port number in the request object is also 443. Is this a bug in Axis2? Regards, Jai -Original Message- From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED][EMAIL PROTECTED] ] Sent: Fri 9/19/2008 8:52 AM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl causing other problems. (There is a separate email chain on this issue). I do want the hostname to be updated to the machine name or ip address of the installed machine. The issue is port number is being set to a wrong value. How does Axis2 determine what the port number should be set to? Is there some way
RE: wsdl port address uses incorrect port number for https
Hi Keith, For now, I had solved the problem by writing my own Listener by implementing the TransportListener class. I like your suggestion of extending the existing Listener so I am going to try it out. I also tried by adding the proxyPort to the Connector configuration in the server.xml of Tomcat, however looks like Axis2 does not use it and instead takes a value of 80. I hope this gets fixed in future versions of Axis2. Thanks, JP From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2008 6:53 PM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https You could easily extend the Listener shipped with Axis2 and override its getEPRsForService method. This is the method that generates the endpoint address, so you could handle it the way you want it to be by simple extending it. Thanks, Keith. On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP) [EMAIL PROTECTED] wrote: Hi, Does Axis2 include a class for transport listener which supports https? Is it possible to configure Axis2 to not include any port number when generating the soap address? Thanks, JP From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2008 4:10 PM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number for https Hi, The proxyPort does not help us as we are not using Apache as a proxy server. If I configure the axis2.xml as below: transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter /transportReceiver transportReceiver name=https class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8443/parameter /transportReceiver then the soap address for http includes the port 8080 and the soap address for https includes the port 8443 but the soap address itself is http and not https. When should the class for transportReceiver be set to for https? If I do not specify the transportReceiver for https in axis2.xml, the the default value of the port is taken as 80 instead of 443 which is the default port for https. Thanks, JP From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 9:09 PM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis 2.xml for an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED] wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 10:02 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED] wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our
Re: wsdl port address uses incorrect port number for https
Would you mind opening a JIRA issue please. That way it will be tracked. Thanks, Keith. On Thu, Sep 25, 2008 at 7:34 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED]wrote: Hi Keith, For now, I had solved the problem by writing my own Listener by implementing the TransportListener class. I like your suggestion of extending the existing Listener so I am going to try it out. I also tried by adding the proxyPort to the Connector configuration in the server.xml of Tomcat, however looks like Axis2 does not use it and instead takes a value of 80. I hope this gets fixed in future versions of Axis2. Thanks, JP -- *From:* keith chapman [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, September 24, 2008 6:53 PM *To:* axis-user@ws.apache.org *Subject:* Re: wsdl port address uses incorrect port number for https You could easily extend the Listener shipped with Axis2 and override its getEPRsForService method. This is the method that generates the endpoint address, so you could handle it the way you want it to be by simple extending it. Thanks, Keith. On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP) [EMAIL PROTECTED]wrote: Hi, Does Axis2 include a class for transport listener which supports https? Is it possible to configure Axis2 to not include any port number when generating the soap address? Thanks, JP -- *From:* Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] *Sent:* Monday, September 22, 2008 4:10 PM *To:* axis-user@ws.apache.org *Subject:* RE: wsdl port address uses incorrect port number for https Hi, The proxyPort does not help us as we are not using Apache as a proxy server. If I configure the axis2.xml as below: transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter /transportReceiver transportReceiver name=https class= org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8443/parameter /transportReceiver then the soap address for http includes the port 8080 and the soap address for https includes the port 8443 but the soap address itself is http and not https. When should the class for transportReceiver be set to for https? If I do not specify the transportReceiver for https in axis2.xml, the the default value of the port is taken as 80 instead of 443 which is the default port for https. Thanks, JP -- *From:* keith chapman [mailto:[EMAIL PROTECTED] *Sent:* Sunday, September 21, 2008 9:09 PM *To:* axis-user@ws.apache.org *Subject:* Re: wsdl port address uses incorrect port number for https It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED]wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai -- *From:* keith chapman [mailto:[EMAIL PROTECTED] *Sent:* Sunday, September 21, 2008 10:02 AM *To:* axis-user@ws.apache.org *Subject:* Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED]wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav -- Subject: RE: wsdl port address uses incorrect port number for https Date: Sun, 21 Sep 2008 09:51:13 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org; axis-user@ws.apache.org Hi, My Axis2 web service is deployed for secure access and the URL is of the form https:// https:///hostname/axis2/services/Version
RE: wsdl port address uses incorrect port number for https
Hi, The proxyPort does not help us as we are not using Apache as a proxy server. If I configure the axis2.xml as below: transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter /transportReceiver transportReceiver name=https class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8443/parameter /transportReceiver then the soap address for http includes the port 8080 and the soap address for https includes the port 8443 but the soap address itself is http and not https. When should the class for transportReceiver be set to for https? If I do not specify the transportReceiver for https in axis2.xml, the the default value of the port is taken as 80 instead of 443 which is the default port for https. Thanks, JP From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 9:09 PM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis 2.xml for an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED] wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 10:02 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED] wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav Subject: RE: wsdl port address uses incorrect port number for https Date: Sun, 21 Sep 2008 09:51:13 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org; axis-user@ws.apache.org Hi, My Axis2 web service is deployed for secure access and the URL is of the form https:// https:/// hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https). I have verified that the port number in the request object is also 443. Is this a bug in Axis2? Regards, Jai -Original Message- From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] Sent: Fri 9/19/2008 8:52 AM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl causing other problems. (There is a separate email chain on this issue). I do want the hostname to be updated to the machine name or ip address of the installed machine. The issue is port number is being set to a wrong value. How does Axis2 determine what the port number should be set to? Is there some way we can specify
RE: wsdl port address uses incorrect port number for https
doesnt make sense to use the same org.apache.axis2.transport.http.SimpleHTTPServer class for both http and https transport this is the SSL configuration I see for configuring HttpCoreNIOSSLListener in axis2.xml !-- the non blocking https transport based on HttpCore + SSL-NIO extensions transportReceiver name=https class=org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener parameter name=port locked=false9002/parameter parameter name=non-blocking locked=falsetrue/parameter parameter name=keystore locked=false KeyStore Locationidentity.jks/Location TypeJKS/Type Passwordpassword/Password KeyPasswordpassword/KeyPassword /KeyStore /parameter parameter name=truststore locked=false TrustStore Locationtrust.jks/Location TypeJKS/Type Passwordpassword/Password /TrustStore /parameter-- !--parameter name=SSLVerifyClientrequire/parameter supports optional|require or defaults to none -- !--/transportReceiver-- //the default behaviour is to have your service engage Rampart module as in this definition in services.xml service... module ref=rampart / parameter name=InflowSecurity action itemsTimestamp Signature/items signaturePropFileservice.properties/signaturePropFile /action /parameter parameter name=OutflowSecurity action itemsTimestamp Signature/items userservice/user passwordCallbackClassorg.apache.rampart.samples.sample04.PWCBHandler/passwordCallbackClass signaturePropFileservice.properties/signaturePropFile signatureKeyIdentifierDirectReference/signatureKeyIdentifier /action /parameter .. /service HTH Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: RE: wsdl port address uses incorrect port number for https Date: Mon, 22 Sep 2008 17:10:22 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Hi, The proxyPort does not help us as we are not using Apache as a proxy server. If I configure the axis2.xml as below: transportReceiver name=http class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8080/parameter /transportReceiver transportReceiver name=https class=org.apache.axis2.transport.http.SimpleHTTPServer parameter name=port8443/parameter /transportReceiver then the soap address for http includes the port 8080 and the soap address for https includes the port 8443 but the soap address itself is http and not https. When should the class for transportReceiver be set to for https? If I do not specify the transportReceiver for https in axis2.xml, the the default value of the port is taken as 80 instead of 443 which is the default port for https. Thanks, JP From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 9:09 PM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xml for an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED] wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 10:02 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED] wrote: JP, We have had similar challenges with our service where Axis2
RE: wsdl port address uses incorrect port number for https
Hi, My Axis2 web service is deployed for secure access and the URL is of the form https://hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https). I have verified that the port number in the request object is also 443. Is this a bug in Axis2? Regards, Jai -Original Message- From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] Sent: Fri 9/19/2008 8:52 AM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl causing other problems. (There is a separate email chain on this issue). I do want the hostname to be updated to the machine name or ip address of the installed machine. The issue is port number is being set to a wrong value. How does Axis2 determine what the port number should be set to? Is there some way we can specify what the port number should be? Regards, Jai -Original Message- From: charitha kankanamge [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2008 8:24 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number Hi, You may set modifyUserWsdlPortAddress parameter to false in your services.xml. parameter name=*modifyUserWSDLPortAddress*false/parameter If you set this parameter to false and useoriginalWsdl set to true, the port address specified in the original wsdl (wsdl included in META-INF directory of your service archive) will be unchanged. regards Charitha http://charithaka.blogspot.com http://www.wso2.org Pugalia, Jai P (JP) wrote: Hi, Looks like the wsdl port numbers being populated in the wsdl port address by Axis2 is incorrect. wsdl:service name=Version wsdl:port name=VersionSOAP11port_https binding=ns0:VersionSOAP11Binding soap:address location=https://1.2.3.4:80/axis2/services/Version https://1.2.3.4:80/axis2/services/Version / /wsdl:port wsdl:port name=VersionSOAP11port_http1 binding=ns0:VersionSOAP11Binding soap:address location=http://1.2.3.4:8080/axis2/services/Version http://1.2.3.4:8080/axis2/services/Version / /wsdl:port /wsdl:service In our situation, the port number for https should be 443 and port for http should be 80. Is there any configuration which needs to be modified such that the right port number is included in the wsdl when it is retrieved using ?wsdl option. Thanks, Jai --- - No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 9/18/2008 5:03 PM - 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: wsdl port address uses incorrect port number for https
JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav Subject: RE: wsdl port address uses incorrect port number for httpsDate: Sun, 21 Sep 2008 09:51:13 -0600From: [EMAIL PROTECTED]: axis-user@ws.apache.org; axis-user@ws.apache.org Hi,My Axis2 web service is deployed for secure access and the URL is of the form https://hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https).I have verified that the port number in the request object is also 443. Is this a bug in Axis2?Regards,Jai-Original Message-From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]: Fri 9/19/2008 8:52 AMTo: [EMAIL PROTECTED]: RE: wsdl port address uses incorrect port numberHi Charitha,I am not including the wsdl with the aar file. Including the wsdlcausing other problems. (There is a separate email chain on this issue).I do want the hostname to be updated to the machine name or ip addressof the installed machine. The issue is port number is being set to awrong value. How does Axis2 determine what the port number should be setto? Is there some way we can specify what the port number should be?Regards,Jai-Original Message-From: charitha kankanamge [mailto:[EMAIL PROTECTED]: Friday, September 19, 2008 8:24 AMTo: [EMAIL PROTECTED]: Re: wsdl port address uses incorrect port numberHi,You may set modifyUserWsdlPortAddress parameter to false in yourservices.xml.parameter name=*modifyUserWSDLPortAddress*false/parameterIf you set this parameter to false and useoriginalWsdl set to true, theport address specified in the original wsdl (wsdl included in META-INFdirectory of your service archive) will be unchanged.regardsCharithahttp://charithaka.blogspot.comhttp://www.wso2.orgPugalia, Jai P (JP) wrote: Hi, Looks like the wsdl port numbers being populated in the wsdl port address by Axis2 is incorrect. wsdl:service name=Version wsdl:port name=VersionSOAP11port_https binding=ns0:VersionSOAP11Binding soap:address location=https://1.2.3.4:80/axis2/services/Version https://1.2.3.4:80/axis2/services/Version / /wsdl:port wsdl:port name=VersionSOAP11port_http1 binding=ns0:VersionSOAP11Binding soap:address location=http://1.2.3.4:8080/axis2/services/Version http://1.2.3.4:8080/axis2/services/Version / /wsdl:port /wsdl:service In our situation, the port number for https should be 443 and port for http should be 80. Is there any configuration which needs to be modified such that the right port number is included in the wsdl when it is retrieved using ?wsdl option. Thanks, Jai No virus found in this incoming message.Checked by AVG.Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date:9/18/2008 5:03 PM -To unsubscribe, e-mail: [EMAIL PROTECTED] additional commands, e-mail: [EMAIL PROTECTED] unsubscribe, e-mail: [EMAIL PROTECTED] additional commands, e-mail: [EMAIL PROTECTED] _ Stay up to date on your PC, the Web, and your mobile phone with Windows Live. http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/
Re: wsdl port address uses incorrect port number for https
Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED]wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav -- Subject: RE: wsdl port address uses incorrect port number for https Date: Sun, 21 Sep 2008 09:51:13 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org; axis-user@ws.apache.org Hi, My Axis2 web service is deployed for secure access and the URL is of the form https:// https:///hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https). I have verified that the port number in the request object is also 443. Is this a bug in Axis2? Regards, Jai -Original Message- From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]] Sent: Fri 9/19/2008 8:52 AM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl causing other problems. (There is a separate email chain on this issue). I do want the hostname to be updated to the machine name or ip address of the installed machine. The issue is port number is being set to a wrong value. How does Axis2 determine what the port number should be set to? Is there some way we can specify what the port number should be? Regards, Jai -Original Message- From: charitha kankanamge [mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]] Sent: Friday, September 19, 2008 8:24 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number Hi, You may set modifyUserWsdlPortAddress parameter to false in your services.xml. parameter name=*modifyUserWSDLPortAddress*false/parameter If you set this parameter to false and useoriginalWsdl set to true, the port address specified in the original wsdl (wsdl included in META-INF directory of your service archive) will be unchanged. regards Charitha http://charithaka.blogspot.com http://www.wso2.org Pugalia, Jai P (JP) wrote: Hi, Looks like the wsdl port numbers being populated in the wsdl port address by Axis2 is incorrect. wsdl:service name=Version wsdl:port name=VersionSOAP11port_https binding=ns0:VersionSOAP11Binding soap:address location=https://1.2.3.4:80/axis2/services/Version https://1.2.3.4:80/axis2/services/Version / /wsdl:port wsdl:port name=VersionSOAP11port_http1 binding=ns0:VersionSOAP11Binding soap:address location=http://1.2.3.4:8080/axis2/services/Version http://1.2.3.4:8080/axis2/services/Version / /wsdl:port /wsdl:service In our situation, the port number for https should be 443 and port for http should be 80. Is there any configuration which needs to be modified such that the right port number is included in the wsdl when it is retrieved using ?wsdl option. Thanks, Jai --- - No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 9/18/2008 5:03 PM - 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] -- Stay up to date on your PC, the Web, and your mobile phone with Windows Live. See Nowhttp://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/ -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
RE: wsdl port address uses incorrect port number for https
Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai From: keith chapman [mailto:[EMAIL PROTECTED] Sent: Sunday, September 21, 2008 10:02 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED] wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav Subject: RE: wsdl port address uses incorrect port number for https Date: Sun, 21 Sep 2008 09:51:13 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org; axis-user@ws.apache.org Hi, My Axis2 web service is deployed for secure access and the URL is of the form https:// https:/// hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https). I have verified that the port number in the request object is also 443. Is this a bug in Axis2? Regards, Jai -Original Message- From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] Sent: Fri 9/19/2008 8:52 AM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl causing other problems. (There is a separate email chain on this issue). I do want the hostname to be updated to the machine name or ip address of the installed machine. The issue is port number is being set to a wrong value. How does Axis2 determine what the port number should be set to? Is there some way we can specify what the port number should be? Regards, Jai -Original Message- From: charitha kankanamge [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2008 8:24 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number Hi, You may set modifyUserWsdlPortAddress parameter to false in your services.xml. parameter name=*modifyUserWSDLPortAddress*false/parameter If you set this parameter to false and useoriginalWsdl set to true, the port address specified in the original wsdl (wsdl included in META-INF directory of your service archive) will be unchanged. regards Charitha http://charithaka.blogspot.com http://charithaka.blogspot.com/ http://www.wso2.org http://www.wso2.org/ Pugalia, Jai P (JP) wrote: Hi, Looks like the wsdl port numbers being populated in the wsdl port address by Axis2 is incorrect. wsdl:service name=Version wsdl:port name=VersionSOAP11port_https binding=ns0:VersionSOAP11Binding soap:address location=https://1.2.3.4:80/axis2/services/Version https://1.2.3.4:80/axis2/services/Version / /wsdl:port wsdl:port name=VersionSOAP11port_http1 binding=ns0:VersionSOAP11Binding soap:address location=http://1.2.3.4:8080/axis2/services/Version http://1.2.3.4:8080/axis2/services/Version / /wsdl:port /wsdl:service In our situation, the port number for https should be 443 and port for http should be 80. Is there any configuration which needs to be modified such that the right port number is included in the wsdl when it is retrieved using ?wsdl option. Thanks, Jai --- - No virus found
Re: wsdl port address uses incorrect port number for https
It should be specified in the http transport listener of the axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor an example usage. This is the axis2.xml used in the WSO2 Mashup Server [1] Look for the following. !-- Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80 in this case. -- !--parameter name=proxyPort80/parameter-- Thanks, Keith. [1] http://wso2.org/projects/mashup On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) [EMAIL PROTECTED]wrote: Hi Keith, Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml, the http transport receiver has a port parameter is set to 8080 and the https transport receiver is commented out in axis2.xml. Am I heading in the right direction? Thanks, Jai -- *From:* keith chapman [mailto:[EMAIL PROTECTED] *Sent:* Sunday, September 21, 2008 10:02 AM *To:* axis-user@ws.apache.org *Subject:* Re: wsdl port address uses incorrect port number for https Hi, When its going through Apache you can use the following parameter in the transport listener to set the port address, parameter name=proxyPort80/parameter For the https listener you can set it to 443. Thanks, Keith. On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu [EMAIL PROTECTED]wrote: JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav -- Subject: RE: wsdl port address uses incorrect port number for https Date: Sun, 21 Sep 2008 09:51:13 -0600 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org; axis-user@ws.apache.org Hi, My Axis2 web service is deployed for secure access and the URL is of the form https:// https:///hostname/axis2/services/Version?wsdl. However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https). I have verified that the port number in the request object is also 443. Is this a bug in Axis2? Regards, Jai -Original Message- From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] ] Sent: Fri 9/19/2008 8:52 AM To: axis-user@ws.apache.org Subject: RE: wsdl port address uses incorrect port number Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl causing other problems. (There is a separate email chain on this issue). I do want the hostname to be updated to the machine name or ip address of the installed machine. The issue is port number is being set to a wrong value. How does Axis2 determine what the port number should be set to? Is there some way we can specify what the port number should be? Regards, Jai -Original Message- From: charitha kankanamge [mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]] Sent: Friday, September 19, 2008 8:24 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number Hi, You may set modifyUserWsdlPortAddress parameter to false in your services.xml. parameter name=*modifyUserWSDLPortAddress*false/parameter If you set this parameter to false and useoriginalWsdl set to true, the port address specified in the original wsdl (wsdl included in META-INF directory of your service archive) will be unchanged. regards Charitha http://charithaka.blogspot.com http://www.wso2.org Pugalia, Jai P (JP) wrote: Hi, Looks like the wsdl port numbers being populated in the wsdl port address by Axis2 is incorrect. wsdl:service name=Version wsdl:port name=VersionSOAP11port_https binding=ns0:VersionSOAP11Binding soap:address location=https://1.2.3.4:80/axis2/services/Version https://1.2.3.4:80/axis2/services/Version / /wsdl:port wsdl:port name=VersionSOAP11port_http1 binding=ns0:VersionSOAP11Binding soap:address location=http://1.2.3.4:8080/axis2/services/Version http://1.2.3.4:8080/axis2/services/Version / /wsdl:port /wsdl:service In our situation, the port number for https should be 443 and port for http should be 80. Is there any configuration which needs to be modified such that the right port number is included in the wsdl when it is retrieved using ?wsdl option. Thanks, Jai --- - No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 9/18/2008 5:03 PM
Re: wsdl port address uses incorrect port number
Hi, You may set modifyUserWsdlPortAddress parameter to false in your services.xml. parameter name=*modifyUserWSDLPortAddress*false/parameter If you set this parameter to false and useoriginalWsdl set to true, the port address specified in the original wsdl (wsdl included in META-INF directory of your service archive) will be unchanged. regards Charitha http://charithaka.blogspot.com http://www.wso2.org Pugalia, Jai P (JP) wrote: Hi, Looks like the wsdl port numbers being populated in the wsdl port address by Axis2 is incorrect. wsdl:service name=Version wsdl:port name=VersionSOAP11port_https binding=ns0:VersionSOAP11Binding soap:address location=https://1.2.3.4:80/axis2/services/Version https://1.2.3.4:80/axis2/services/Version / /wsdl:port wsdl:port name=VersionSOAP11port_http1 binding=ns0:VersionSOAP11Binding soap:address location=http://1.2.3.4:8080/axis2/services/Version http://1.2.3.4:8080/axis2/services/Version / /wsdl:port /wsdl:service In our situation, the port number for https should be 443 and port for http should be 80. Is there any configuration which needs to be modified such that the right port number is included in the wsdl when it is retrieved using ?wsdl option. Thanks, Jai No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 9/18/2008 5:03 PM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: wsdl port address uses incorrect port number
Hi Charitha, I am not including the wsdl with the aar file. Including the wsdl causing other problems. (There is a separate email chain on this issue). I do want the hostname to be updated to the machine name or ip address of the installed machine. The issue is port number is being set to a wrong value. How does Axis2 determine what the port number should be set to? Is there some way we can specify what the port number should be? Regards, Jai -Original Message- From: charitha kankanamge [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2008 8:24 AM To: axis-user@ws.apache.org Subject: Re: wsdl port address uses incorrect port number Hi, You may set modifyUserWsdlPortAddress parameter to false in your services.xml. parameter name=*modifyUserWSDLPortAddress*false/parameter If you set this parameter to false and useoriginalWsdl set to true, the port address specified in the original wsdl (wsdl included in META-INF directory of your service archive) will be unchanged. regards Charitha http://charithaka.blogspot.com http://www.wso2.org Pugalia, Jai P (JP) wrote: Hi, Looks like the wsdl port numbers being populated in the wsdl port address by Axis2 is incorrect. wsdl:service name=Version wsdl:port name=VersionSOAP11port_https binding=ns0:VersionSOAP11Binding soap:address location=https://1.2.3.4:80/axis2/services/Version https://1.2.3.4:80/axis2/services/Version / /wsdl:port wsdl:port name=VersionSOAP11port_http1 binding=ns0:VersionSOAP11Binding soap:address location=http://1.2.3.4:8080/axis2/services/Version http://1.2.3.4:8080/axis2/services/Version / /wsdl:port /wsdl:service In our situation, the port number for https should be 443 and port for http should be 80. Is there any configuration which needs to be modified such that the right port number is included in the wsdl when it is retrieved using ?wsdl option. Thanks, Jai --- - No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 9/18/2008 5:03 PM - 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: wsdl exploder
Lawrence, Thanks for that. I tried a simplistic: WSDLFactory factory = WSDLFactory.newInstance(); WSDLReader reader = factory.newWSDLReader(); Definition def = reader.readWSDL(http://myserver/mywsdl.wsdl;); WSDLWriter writer = factory.newWSDLWriter(); writer.writeWSDL(def, System.out); but the definition isn't exploded. On serialization, the output file only contained the top-level file. Not the explosion which included all referenced files. Presumably I could iterate over the imports and types to create a merged definition that would do what I want, but I haven't tried to do that yet. Regards, jon seymour. On Sat, Sep 13, 2008 at 4:37 AM, Lawrence Mandel [EMAIL PROTECTED] wrote: I think WSDL4J [1] will do what you want. Simply read in the WSDL and then serialize it out. AFAIK, WSDL will serialize to a single file. John Kaputin should know for sure whether WSDL4J will suit your purpose. [1] http://sourceforge.net/projects/wsdl4j Lawrence From: Jon Seymour [EMAIL PROTECTED] To: axis-user@ws.apache.org Date: 09/12/2008 07:47 AM Subject: wsdl exploder Has anyone ever come across a WSDL-exploder that converts a logical WSDL entity that spans multiple files (via the WSDL and XML schema import mechanisms) into a single entity that contains all the referenced entities inline? I need such a beast to help support a client whose ability to properly keep track of schema locations in a multi-file entity is somewhat suspect. jon seymour. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl exploder
I think WSDL4J [1] will do what you want. Simply read in the WSDL and then serialize it out. AFAIK, WSDL will serialize to a single file. John Kaputin should know for sure whether WSDL4J will suit your purpose. [1] http://sourceforge.net/projects/wsdl4j Lawrence From: Jon Seymour [EMAIL PROTECTED] To: axis-user@ws.apache.org Date: 09/12/2008 07:47 AM Subject: wsdl exploder Has anyone ever come across a WSDL-exploder that converts a logical WSDL entity that spans multiple files (via the WSDL and XML schema import mechanisms) into a single entity that contains all the referenced entities inline? I need such a beast to help support a client whose ability to properly keep track of schema locations in a multi-file entity is somewhat suspect. jon seymour. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL for attachments and WSDL2Java
soap:binding transport=http://schemas.xmlsoap.org/soap/http/ wsdl:operation name=GetAsset soap:operation soapAction=~/WebServices/GetAsset style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output mime:multipartRelated mime:part soap:body use=literal/ /mime:part mime:part mime:content part=asset type=application/octet-stream/ /mime:part /mime:multipartRelated /wsdl:output /wsdl:operation wsdl:operation name=StoreAsset soap:operation soapAction=~/WebServices/StoreAsset style=document/ wsdl:input mime:multipartRelated mime:part soap:body use=literal/ /mime:part mime:part mime:content part=asset type=application/octet-stream/ /mime:part /mime:multipartRelated /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=VersionCueService wsdl:port name=VersionCueService binding=tns:VersionCueService soap:address location=http://localhost:8080/axis/services/VersionCueService/ /wsdl:port /wsdl:service /wsdl:definitions Thanks, Ian From: keith chapman [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Tue, 2 Sep 2008 18:15:56 +0530 To: [EMAIL PROTECTED] Subject: Re: WSDL for attachments and WSDL2Java Hi, I guess the problem is caused by the following messages in your WSDL, wsdl:message name=GetAssetSoapOut wsdl:part name=parameters element=tns:GetAssetResponse/ wsdl:part name=asset type=s:base64Binary/ /wsdl:message wsdl:message name=StoreAssetSoapIn wsdl:part name=parameters element=tns:StoreAsset/ wsdl:part name=asset type=s:base64Binary/ /wsdl:message Modifying it to something like wsdl:message name=GetAssetSoapOut wsdl:part name=parameters element=tns:GetAssetResponse/ /wsdl:message wsdl:message name=StoreAssetSoapIn wsdl:part name=parameters element=tns:StoreAsset/ /wsdl:message and making asset a element of GetAssetResponse and StoreAsset should fix the issue (At least from the point of Axis2. I'm not sure weather this would break Axis1, but I doubt it will). Thanks, Keith. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl string pattern
You should consult the various Internet RFCs for allowed MIME typenames to get the allowed syntax, but your pattern will need to include hyphens at least, for such MIME types as application/octet-stream or message/external-body or x-application/my-experimental-app. Jeff Shehan Simen wrote: Hi, I want to have a pattern for a string in wsdl. The pattern is like: string/string e.g. : image/jpeg Is the following pattern correct? xs:pattern value=([a-zA-Z])*/([a-zA-Z])*/ I want to introduce this pattern for MIME types. Is it correct? Please help me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl
You need to run bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o directory\where\you\want\the\code\generated This will create a stub which is a class you can embed in your application. You simply need to create a new instance of this class and then call methods on it, those methods will call the remote service. Paul On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma [EMAIL PROTECTED] wrote: Hi, I am new to the web services and so as to axis. Please help me. I have to show something this week. I have been working to sort this out since last 4 days. I am sorry to say this. I have an existing web application. To use axis in existing application, I have done : 1.copy all jars from axis.lib directory 2.copy axis's web.xml servlet params and mapping to to my web.xml I have got a wsdl url from an external application (to be integrated with my application) Now what should I do to use this wsdl to access the external application ? Please kind enough to me. Many Thanks, Sent from Yahoo! Mail. A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl
Thanks Paul for the quick reply. I have got axis-bin-1_4. In which directory I should run this ?nbsp; I have done an advnced installation http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp nbsp; Thank you very much, nbsp; --- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote: From: Paul Fremantle lt;[EMAIL PROTECTED]gt; Subject: Re: wsdl To: axis-user@ws.apache.org, [EMAIL PROTECTED] Date: Wednesday, 4 June, 2008, 4:23 PM You need to run bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o directory\where\you\want\the\code\generated This will create a stub which is a class you can embed in your application. You simply need to create a new instance of this class and then call methods on it, those methods will call the remote service. Paul On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma lt;[EMAIL PROTECTED]gt; wrote: gt; Hi, gt; gt; gt; gt; I am new to the web services and so as to axis. Please help me. gt; gt; I have to show something this week. I have been working to sort this out gt; since last 4 days. gt; gt; I am sorry to say this. gt; gt; gt; gt; I have an existing web application. To use axis in existing application, gt; gt; I have done : gt; gt; 1.copy all jars from axis.lib directory gt; gt; 2.copy axis's web.xml servlet params and mapping to to my web.xml gt; gt; gt; gt; I have got a wsdl url from an external application (to be integrated with my gt; application) gt; gt; Now what should I do to use this wsdl to access the external application ? gt; gt; Please kind enough to me. gt; gt; gt; gt; Many Thanks, gt; gt; gt; gt; gt; gt; gt; Sent from Yahoo! Mail. gt; A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
Re: wsdl
I am using netbeans with ant to build the web application. --- On Wed, 4/6/08, Jyotsna Varma lt;[EMAIL PROTECTED]gt; wrote: From: Jyotsna Varma lt;[EMAIL PROTECTED]gt; Subject: Re: wsdl To: axis-user@ws.apache.org Date: Wednesday, 4 June, 2008, 4:56 PM Thanks Paul for the quick reply. I have got axis-bin-1_4. In which directory I should run this ?nbsp; I have done an advnced installation http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp nbsp; Thank you very much, nbsp; --- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote: From: Paul Fremantle lt;[EMAIL PROTECTED]gt; Subject: Re: wsdl To: axis-user@ws.apache.org, [EMAIL PROTECTED] Date: Wednesday, 4 June, 2008, 4:23 PM You need to run bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o directory\where\you\want\the\code\generated This will create a stub which is a class you can embed in your application. You simply need to create a new instance of this class and then call methods on it, those methods will call the remote service. Paul On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma lt;[EMAIL PROTECTED]gt; wrote: gt; Hi, gt; gt; gt; gt; I am new to the web services and so as to axis. Please help me. gt; gt; I have to show something this week. I have been working to sort this out gt; since last 4 days. gt; gt; I am sorry to say this. gt; gt; gt; gt; I have an existing web application. To use axis in existing application, gt; gt; I have done : gt; gt; 1.copy all jars from axis.lib directory gt; gt; 2.copy axis's web.xml servlet params and mapping to to my web.xml gt; gt; gt; gt; I have got a wsdl url from an external application (to be integrated with my gt; application) gt; gt; Now what should I do to use this wsdl to access the external application ? gt; gt; Please kind enough to me. gt; gt; gt; gt; Many Thanks, gt; gt; gt; gt; gt; gt; gt; Sent from Yahoo! Mail. gt; A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sent from Yahoo! Mail. A Smarter Email. __ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
Re: wsdl
Sorry, I was assuming you had Axis2 (the latest version). I'm not up to speed on Axis1 so I can't help out with that. Basically if you get Axis2-bin zipfile, unzip it, and it should become clear. If you are calling a webservice from your webapp you just need to include the axis2 libs in the webapp\lib directory. Paul On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma [EMAIL PROTECTED] wrote: Thanks Paul for the quick reply. I have got axis-bin-1_4. In which directory I should run this ? I have done an advnced installation http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp Thank you very much, --- On Wed, 4/6/08, Paul Fremantle [EMAIL PROTECTED] wrote: From: Paul Fremantle [EMAIL PROTECTED] Subject: Re: wsdl To: axis-user@ws.apache.org, [EMAIL PROTECTED] Date: Wednesday, 4 June, 2008, 4:23 PM You need to run bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o directory\where\you\want\the\code\generated This will create a stub which is a class you can embed in your application. You simply need to create a new instance of this class and then call methods on it, those methods will call the remote service. Paul On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma [EMAIL PROTECTED] wrote: Hi, I am new to the web services and so as to axis. Please help me. I have to show something this week. I have been working to sort this out since last 4 days. I am sorry to say this. I have an existing web application. To use axis in existing application, I have done : 1.copy all jars from axis.lib directory 2.copy axis's web.xml servlet params and mapping to to my web.xml I have got a wsdl url from an external application (to be integrated with my application) Now what should I do to use this wsdl to access the external application ? Please kind enough to me. Many Thanks, Sent from Yahoo! Mail. A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sent from Yahoo! Mail. A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsdl
Thanks Paul. I am downloading it. But I am not sure whether the external system accepts axis2. I will try. External system's documentation tells that it works with Axis 1.3. But it is an old documant. They must have updated it. Let me come back. --- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote: From: Paul Fremantle lt;[EMAIL PROTECTED]gt; Subject: Re: wsdl To: axis-user@ws.apache.org, [EMAIL PROTECTED] Date: Wednesday, 4 June, 2008, 5:01 PM Sorry, I was assuming you had Axis2 (the latest version). I'm not up to speed on Axis1 so I can't help out with that. Basically if you get Axis2-bin zipfile, unzip it, and it should become clear. If you are calling a webservice from your webapp you just need to include the axis2 libs in the webapp\lib directory. Paul On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma lt;[EMAIL PROTECTED]gt; wrote: gt; gt; Thanks Paul for the quick reply. gt; gt; I have got axis-bin-1_4. In which directory I should run this ? I have done gt; an advnced installation gt; http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp gt; gt; gt; gt; Thank you very much, gt; gt; gt; gt; --- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote: gt; gt; From: Paul Fremantle lt;[EMAIL PROTECTED]gt; gt; Subject: Re: wsdl gt; To: axis-user@ws.apache.org, [EMAIL PROTECTED] gt; Date: Wednesday, 4 June, 2008, 4:23 PM gt; gt; You need to run gt; gt; bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o gt; directory\where\you\want\the\code\generated gt; gt; This will create a stub which is a class you can embed in your gt; application. You simply need to create a new instance of this class gt; and then call methods on it, those methods will call the remote gt; service. gt; gt; Paul gt; gt; On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma lt;[EMAIL PROTECTED]gt; gt; wrote: gt;gt; Hi, gt;gt; gt;gt; gt;gt; gt;gt; I am new to the web services and so as to axis. Please help me. gt;gt; gt;gt; I have to show something this week. I have been working to sort this out gt;gt; since last 4 days. gt;gt; gt;gt; I am sorry to say this. gt;gt; gt;gt; gt;gt; gt;gt; I have an existing web application. To use axis in existing application, gt;gt; gt;gt; I have done : gt;gt; gt;gt; 1.copy all jars from axis.lib directory gt;gt; gt;gt; 2.copy axis's web.xml servlet params and mapping to to my web.xml gt;gt; gt;gt; gt;gt; gt;gt; I have got a wsdl url from an external application (to be integrated with gt; my gt;gt; application) gt;gt; gt;gt; Now what should I do to use this wsdl to access the external application ? gt;gt; gt;gt; Please kind enough to me. gt;gt; gt;gt; gt;gt; gt;gt; Many Thanks, gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; Sent from Yahoo! Mail. gt;gt; A Smarter Email. gt; gt; gt; gt; -- gt; Paul Fremantle gt; Co-Founder and CTO, WSO2 gt; Apache Synapse PMC Chair gt; OASIS WS-RX TC Co-chair gt; gt; blog: http://pzf.fremantle.org gt; [EMAIL PROTECTED] gt; gt; Oxygenating the Web Service Platform, www.wso2.com gt; gt; - gt; To unsubscribe, e-mail: [EMAIL PROTECTED] gt; For additional commands, e-mail: [EMAIL PROTECTED] gt; gt; gt; Sent from Yahoo! Mail. gt; A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
RE: wsdl
There are many reasons to adopt Axis2 Ability to use Axis Object Model to represent all of your entities (Axiom) Ability to incorporate more databinding types ADB, XMLBEANS, JIBX, JAXBRI Ability to engage or disengage AOP modules security, addressing, logging Ability to upload services without disrupting other services Martin Gainty __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Date: Wed, 4 Jun 2008 11:37:09 + From: [EMAIL PROTECTED] Subject: Re: wsdl To: axis-user@ws.apache.org Thanks Paul. I am downloading it. But I am not sure whether the external system accepts axis2. I will try. External system's documentation tells that it works with Axis 1.3. But it is an old documant. They must have updated it. Let me come back. --- On Wed, 4/6/08, Paul Fremantle [EMAIL PROTECTED] wrote: From: Paul Fremantle [EMAIL PROTECTED] Subject: Re: wsdl To: axis-user@ws.apache.org, [EMAIL PROTECTED] Date: Wednesday, 4 June, 2008, 5:01 PM Sorry, I was assuming you had Axis2 (the latest version). I'm not up to speed on Axis1 so I can't help out with that. Basically if you get Axis2-bin zipfile, unzip it, and it should become clear. If you are calling a webservice from your webapp you just need to include the axis2 libs in the webapp\lib directory. Paul On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma [EMAIL PROTECTED] wrote: Thanks Paul for the quick reply. I have got axis-bin-1_4. In which directory I should run this ? I have done an advnced installation http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp Thank you very much, --- On Wed, 4/6/08, Paul Fremantle [EMAIL PROTECTED] wrote: From: Paul Fremantle [EMAIL PROTECTED] Subject: Re: wsdl To: axis-user@ws.apache.org, [EMAIL PROTECTED] Date: Wednesday, 4 June, 2008, 4:23 PM You need to run bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o directory\where\you\want\the\code\generated This will create a stub which is a class you can embed in your application. You simply need to create a new instance of this class and then call methods on it, those methods will call the remote service. Paul On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma [EMAIL PROTECTED] wrote: Hi, I am new to the web services and so as to axis. Please help me. I have to show something this week. I have been working to sort this out since last 4 days. I am sorry to say this. I have an existing web application. To use axis in existing application, I have done : 1.copy all jars from axis.lib directory 2.copy axis's web.xml servlet params and mapping to to my web.xml I have got a wsdl url from an external application (to be integrated with my application) Now what should I do to use this wsdl to access the external application ? Please kind enough to me. Many Thanks, Sent from Yahoo! Mail. A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sent from Yahoo! Mail. A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sent from Yahoo! Mail. A Smarter Email. _ Now you can invite friends from Facebook and other groups to join you on Windows Live™ Messenger. Add now. https://www.invite2messenger.net/im/?source=TXT_EML_WLH_AddNow_Now
RE: wsdl
Thank you. I run wsdl2java in Axis2 1.3 version. But I am getting error :-
nbsp;
Caused by: javax.wsdl.WSDLException: WSDLException (at /html):
faultCode=INVALID_WSDL: Expected element '{http://schemas
.xmlsoap.org/wsdl/}definitions'.
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; at
com.ibm.wsdl.xml.WSDLReaderImpl.checkElementName(Unknown Source)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; at
com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; at
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; at
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; at
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:286)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.lt;initgt;(CodeGenerationEngine.java:105)
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; ... 2 more
I don't understand whats the cause of this error ? Is something missing in wsdl
document?
--- On Wed, 4/6/08, Martin Gainty lt;[EMAIL PROTECTED]gt; wrote:
From: Martin Gainty lt;[EMAIL PROTECTED]gt;
Subject: RE: wsdl
To: [EMAIL PROTECTED], axis-user@ws.apache.org
Date: Wednesday, 4 June, 2008, 5:20 PM
#yiv112315369 .hmmessage P
{
margin:0px;padding:0px;}
#yiv112315369 .hmmessage
{
FONT-SIZE:10pt;FONT-FAMILY:Tahoma;}
There are many reasons to adopt Axis2
Ability to use Axis Object Model to represent all of your entities (Axiom)
Ability to incorporate more databinding types ADB, XMLBEANS, JIBX, JAXBRI
Ability to engage or disengage AOP modules security, addressing, logging
Ability to upload services without disrupting other services
Martin Gainty
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
Date: Wed, 4 Jun 2008 11:37:09 +
From: [EMAIL PROTECTED]
Subject: Re: wsdl
To: axis-user@ws.apache.org
Thanks Paul. I am downloading it. But I am not sure whether the external system
accepts axis2. I will try. External system's documentation tells that it works
with Axis 1.3. But it is an old documant. They must have updated it. Let me
come back.
--- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote:
From: Paul Fremantle lt;[EMAIL PROTECTED]gt;
Subject: Re: wsdl
To: axis-user@ws.apache.org, [EMAIL PROTECTED]
Date: Wednesday, 4 June, 2008, 5:01 PM
Sorry, I was assuming you had Axis2 (the latest version).
I'm not up to speed on Axis1 so I can't help out with that. Basically
if you get Axis2-bin zipfile, unzip it, and it should become clear. If
you are calling a webservice from your webapp you just need to include
the axis2 libs in the webapp\lib directory.
Paul
On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma lt;[EMAIL PROTECTED]gt;
wrote:
gt;
gt; Thanks Paul for the quick reply.
gt;
gt; I have got axis-bin-1_4. In which directory I should run this ? I have
done
gt; an advnced installation
gt;
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
gt;
gt;
gt;
gt; Thank you very much,
gt;
gt;
gt;
gt; --- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote:
gt;
gt; From: Paul Fremantle lt;[EMAIL PROTECTED]gt;
gt; Subject: Re: wsdl
gt; To: axis-user@ws.apache.org, [EMAIL PROTECTED]
gt; Date: Wednesday, 4 June, 2008, 4:23 PM
gt;
gt; You need to run
gt;
gt; bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
gt; directory\where\you\want\the\code\generated
gt;
gt; This will create a stub which is a class you can embed in your
gt; application. You simply need to create a new instance of this class
gt; and then call methods on it, those methods will call the remote
gt; service.
gt;
gt; Paul
gt;
gt; On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma
lt;[EMAIL PROTECTED]gt;
gt; wrote:
gt;gt; Hi,
gt;gt;
gt;gt;
gt;gt;
gt;gt; I am new to the web services and so as to axis. Please help me.
gt;gt;
gt;gt; I have to show something this week. I have been working to sort this
out
gt;gt; since last 4 days.
gt;gt;
gt;gt; I am sorry to say this.
gt;gt;
gt;gt;
gt;gt;
gt;gt; I have an existing web application. To use axis in existing
application,
gt;gt;
gt;gt; I have done :
gt;gt;
gt;gt; 1.copy all jars from axis.lib directory
gt;gt;
gt;gt; 2.copy axis's web.xml servlet params and mapping to to my web.xml
gt;gt;
gt;gt;
gt;gt;
gt;gt; I have got a wsdl url from an external application (to be integrated
with
gt; my
gt;gt; application)
gt;gt;
gt;gt; Now what should I do to use this wsdl to access the external
application ?
gt;gt;
gt;gt; Please kind enough to me.
gt;gt;
gt;gt;
gt;gt;
gt
Re: wsdl
Thanks Paul. Now I think I am able to build stub classes. Thank you very much for your help. --- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote: From: Paul Fremantle lt;[EMAIL PROTECTED]gt; Subject: Re: wsdl To: axis-user@ws.apache.org, [EMAIL PROTECTED] Date: Wednesday, 4 June, 2008, 5:01 PM Sorry, I was assuming you had Axis2 (the latest version). I'm not up to speed on Axis1 so I can't help out with that. Basically if you get Axis2-bin zipfile, unzip it, and it should become clear. If you are calling a webservice from your webapp you just need to include the axis2 libs in the webapp\lib directory. Paul On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma lt;[EMAIL PROTECTED]gt; wrote: gt; gt; Thanks Paul for the quick reply. gt; gt; I have got axis-bin-1_4. In which directory I should run this ? I have done gt; an advnced installation gt; http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp gt; gt; gt; gt; Thank you very much, gt; gt; gt; gt; --- On Wed, 4/6/08, Paul Fremantle lt;[EMAIL PROTECTED]gt; wrote: gt; gt; From: Paul Fremantle lt;[EMAIL PROTECTED]gt; gt; Subject: Re: wsdl gt; To: axis-user@ws.apache.org, [EMAIL PROTECTED] gt; Date: Wednesday, 4 June, 2008, 4:23 PM gt; gt; You need to run gt; gt; bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o gt; directory\where\you\want\the\code\generated gt; gt; This will create a stub which is a class you can embed in your gt; application. You simply need to create a new instance of this class gt; and then call methods on it, those methods will call the remote gt; service. gt; gt; Paul gt; gt; On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma lt;[EMAIL PROTECTED]gt; gt; wrote: gt;gt; Hi, gt;gt; gt;gt; gt;gt; gt;gt; I am new to the web services and so as to axis. Please help me. gt;gt; gt;gt; I have to show something this week. I have been working to sort this out gt;gt; since last 4 days. gt;gt; gt;gt; I am sorry to say this. gt;gt; gt;gt; gt;gt; gt;gt; I have an existing web application. To use axis in existing application, gt;gt; gt;gt; I have done : gt;gt; gt;gt; 1.copy all jars from axis.lib directory gt;gt; gt;gt; 2.copy axis's web.xml servlet params and mapping to to my web.xml gt;gt; gt;gt; gt;gt; gt;gt; I have got a wsdl url from an external application (to be integrated with gt; my gt;gt; application) gt;gt; gt;gt; Now what should I do to use this wsdl to access the external application ? gt;gt; gt;gt; Please kind enough to me. gt;gt; gt;gt; gt;gt; gt;gt; Many Thanks, gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; Sent from Yahoo! Mail. gt;gt; A Smarter Email. gt; gt; gt; gt; -- gt; Paul Fremantle gt; Co-Founder and CTO, WSO2 gt; Apache Synapse PMC Chair gt; OASIS WS-RX TC Co-chair gt; gt; blog: http://pzf.fremantle.org gt; [EMAIL PROTECTED] gt; gt; Oxygenating the Web Service Platform, www.wso2.com gt; gt; - gt; To unsubscribe, e-mail: [EMAIL PROTECTED] gt; For additional commands, e-mail: [EMAIL PROTECTED] gt; gt; gt; Sent from Yahoo! Mail. gt; A Smarter Email. -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
Re: WSDL security
Hi, It is more like transport level security.You need to set it up on your HTTP server, or servlet/appserver container. Use basic/digest auhentication. If you;re using tomcat, please check Apache Tomcat Realm Configuration. Regards, Sukma On Wed, May 21, 2008 at 2:13 AM, sultanat [EMAIL PROTECTED] wrote: How can I protect a user from accessing or viewing a WSDL without authorization. I would like to implement something which the link below does when we try to view the WSDL. https://webservices.oit.umn.edu/axis2/services/AdvisingService?wsdl Thanks. -- View this message in context: http://www.nabble.com/WSDL-security-tp17348404p17348404.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]
Re: .wsdl to soap template generator
Hi Micheal, SOAPUI can easily be used to generate a template for request soap envelope Have a look http://www.soapui.org/ regards Charitha Michael Potter wrote: Axi2 crew, Is there a script that will read .wsdl file and output a soap message template much like wsdl2java reads .wsdl and outputs a java template. The reason I am hoping to find this is: I have some slightly complex data structures in in my .wsdl that do not lend themselves to a generic routine. I will need to write a routine for each message. If I had a script that will output a soap message template, then I could run the script and cut and paste it into my code. By code, I mean some javascript that will be invoking the webservice. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL
Hi Anne, thanks for your reply, i managed to generate a document/literal WSDL file (with java2wsdl), to use in the J2ME Wireless Toolkit Stub generator, but it seems i am getting the error: error: found unknown simple type: byte[] . I read that this error could be overcome with using a document/literal WSDL file, but it hasnt. Any idea on how to overcome this error? Thanks! ps, SAMS Securing Web Services with WS-Security, great book! :D Date: Tue, 11 Mar 2008 08:35:04 -0400 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL Using the style parameter. See http://ws.apache.org/axis/java/ant/axis-java2wsdl.html and http://ws.apache.org/axis/java/reference.html#Java2WSDLReference. Anne On Sun, Mar 9, 2008 at 3:55 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi Anne, thanks for your reply. How exactly would i specify the wrapped (for j2me) style while using the java2wsdl tool? currently i type: java2wsdl -cn packagename.mainclassDate: Sun, 9 Mar 2008 15:39:38 -0400 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL The Axis2 java2wsdl tool generates doc/literal -- but my guess is that it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2, etc. I suggest you use the Axis java2wsdl tool and specify wrapped style. The resulting WSDL should be acceptable to J2ME. You can then use that WSDL as input to the Axis2 wsdl2java tool. Anne On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid [EMAIL PROTECTED] wrote: hi, thanks for your reply, but i've used the java2wsdl tool from axis2, but this does not create acompatible WSDL (document/literal) for J2ME stub generator, which i need to create it for. has anyone used the WSDP tools, specifically wsgen, to create adocument/literal WSDL? (from java/class files)i've searched google, but i cant manage to get wsgen to work. thanks Date: Sun, 2 Mar 2008 23:13:24 +0800 From: [EMAIL PROTECTED]To: axis-user@ws.apache.orgSubject: Re: WSDL dude http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html i used that link to help me out. or if you're not contented with that.. google.. ;) On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi, does anyone know how to generate a document/literal WSDL file from .class files (or .java files)?or if anyone knows how to use the 'wscompile' tool, please can you help meout and tell me what commands i need to follow it's urgent thanks Think you know your TV, music and film? Try Search Charades! --Website: http://chitgoks.freehostia.comJava Casino Games: http://chitgoks.tripod.comMy Blogs: http://chitgoks.blogspot.comhttp://wuhtevah.blogspot.com Everything in one place. All new Windows Live! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Think you know your TV, music and film? Try Search Charades! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Who's friends with who and co-starred in what? http://www.searchgamesbox.com/celebrityseparation.shtml
Re: WSDL
A byte array is not a simple type. Can you use a different type? On Wed, Mar 12, 2008 at 6:05 AM, shams jawaid [EMAIL PROTECTED] wrote: Hi Anne, thanks for your reply, i managed to generate a document/literal WSDL file (with java2wsdl), to use in the J2ME Wireless Toolkit Stub generator, but it seems i am getting the error: error: found unknown simple type: byte[] . I read that this error could be overcome with using a document/literal WSDL file, but it hasnt. Any idea on how to overcome this error? Thanks! ps, SAMS Securing Web Services with WS-Security, great book! :D Date: Tue, 11 Mar 2008 08:35:04 -0400 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL Using the style parameter. See http://ws.apache.org/axis/java/ant/axis-java2wsdl.html and http://ws.apache.org/axis/java/reference.html#Java2WSDLReference. Anne On Sun, Mar 9, 2008 at 3:55 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi Anne, thanks for your reply. How exactly would i specify the wrapped (for j2me) style while using the java2wsdl tool? currently i type: java2wsdl -cn packagename.mainclass Date: Sun, 9 Mar 2008 15:39:38 -0400 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL The Axis2 java2wsdl tool generates doc/literal -- but my guess is that it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2, etc. I suggest you use the Axis java2wsdl tool and specify wrapped style. The resulting WSDL should be acceptable to J2ME. You can then use that WSDL as input to the Axis2 wsdl2java tool. Anne On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid [EMAIL PROTECTED] wrote: hi, thanks for your reply, but i've used the java2wsdl tool from axis2, but this does not create a compatible WSDL (document/literal) for J2ME stub generator, which i need to create it for. has anyone used the WSDP tools, specifically wsgen, to create a document/literal WSDL? (from java/class files) i've searched google, but i cant manage to get wsgen to work. thanks Date: Sun, 2 Mar 2008 23:13:24 +0800 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL dude http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html i used that link to help me out. or if you're not contented with that.. google.. ;) On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi, does anyone know how to generate a document/literal WSDL file from .class files (or .java files)? or if anyone knows how to use the 'wscompile' tool, please can you help me out and tell me what commands i need to follow it's urgent thanks Think you know your TV, music and film? Try Search Charades! -- Website: http://chitgoks.freehostia.com Java Casino Games: http://chitgoks.tripod.com My Blogs: http://chitgoks.blogspot.com http://wuhtevah.blogspot.com Everything in one place. All new Windows Live! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Think you know your TV, music and film? Try Search Charades! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sounds like? How many syllables? Guess and win prizes with Search Charades! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL
Using the style parameter. See http://ws.apache.org/axis/java/ant/axis-java2wsdl.html and http://ws.apache.org/axis/java/reference.html#Java2WSDLReference. Anne On Sun, Mar 9, 2008 at 3:55 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi Anne, thanks for your reply. How exactly would i specify the wrapped (for j2me) style while using the java2wsdl tool? currently i type: java2wsdl -cn packagename.mainclass Date: Sun, 9 Mar 2008 15:39:38 -0400 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL The Axis2 java2wsdl tool generates doc/literal -- but my guess is that it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2, etc. I suggest you use the Axis java2wsdl tool and specify wrapped style. The resulting WSDL should be acceptable to J2ME. You can then use that WSDL as input to the Axis2 wsdl2java tool. Anne On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid [EMAIL PROTECTED] wrote: hi, thanks for your reply, but i've used the java2wsdl tool from axis2, but this does not create a compatible WSDL (document/literal) for J2ME stub generator, which i need to create it for. has anyone used the WSDP tools, specifically wsgen, to create a document/literal WSDL? (from java/class files) i've searched google, but i cant manage to get wsgen to work. thanks Date: Sun, 2 Mar 2008 23:13:24 +0800 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL dude http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html i used that link to help me out. or if you're not contented with that.. google.. ;) On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi, does anyone know how to generate a document/literal WSDL file from .class files (or .java files)? or if anyone knows how to use the 'wscompile' tool, please can you help me out and tell me what commands i need to follow it's urgent thanks Think you know your TV, music and film? Try Search Charades! -- Website: http://chitgoks.freehostia.com Java Casino Games: http://chitgoks.tripod.com My Blogs: http://chitgoks.blogspot.com http://wuhtevah.blogspot.com Everything in one place. All new Windows Live! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Think you know your TV, music and film? Try Search Charades! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL element restrictions
Please try with a nighly build. I build with the current code base.
And the generated EndUserIdenfier class has the following method
public void setEndUserIdentifier(java.lang.String param) {
if ((1 = java.lang.String.valueOf(param).length()) (
java.lang.String.valueOf(param).length() = 255)) {
this.localEndUserIdentifier = param;
} else {
throw new java.lang.RuntimeException();
}
}
so this is checked at the setter method.
thanks,
Amila.
On Thu, Mar 6, 2008 at 6:21 AM, David Bunzli [EMAIL PROTECTED]
wrote:
Hi all,
I haven't been able to get restrictions to consistently work -
enumerations work, but not length restrictions. I've tried both Axis2
v1.1.1 (my production version) and Axis2 v1.3 (just in case v1.3 fixed
this) with no success. Does anyone have any ideas why?
To help, here are the relevant types...
!-- This restriction works. The generated class checks for these
values --
xsd:simpleType name=CrlChecking
xsd:restriction base=xsd:string
xsd:enumeration value=Not required /
xsd:enumeration value=Desirable /
xsd:enumeration value=Mandatory /
/xsd:restriction
/xsd:simpleType
!-- This restriction doesn't work. The generated class doesn't contain
any length checks --
xsd:simpleType name=EndUserIdentifier
xsd:restriction base=xsd:string
xsd:minLength value=1 /
xsd:maxLength value=255 /
/xsd:restriction
/xsd:simpleType
Here is the complete WSDL...
?xml version=1.0 encoding=UTF-8 standalone=no?
wsdl:definitions
xmlns:eSig=urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xmime=http://www.w3.org/2005/05/xmlmime;
name=SigningServices_v1_0_0
targetNamespace=urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au
wsdl:types
xsd:schema
targetNamespace=urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au
xmlns:eSig=urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au
xsd:import namespace=http://www.w3.org/2005/05/xmlmime;
schemaLocation=xmlmime.xsd /
!-- This restriction works --
xsd:simpleType name=CrlChecking
xsd:restriction base=xsd:string
xsd:enumeration value=Not required /
xsd:enumeration value=Desirable /
xsd:enumeration value=Mandatory /
/xsd:restriction
/xsd:simpleType
!-- This restriction doesn't work --
xsd:simpleType name=EndUserIdentifier
xsd:restriction base=xsd:string
xsd:minLength value=1 /
xsd:maxLength value=255 /
/xsd:restriction
/xsd:simpleType
xsd:complexType name=Document
xsd:sequence
xsd:element name=ID type=xsd:string minOccurs=1 maxOccurs=1
/
xsd:element name=File type=xmime:base64Binary minOccurs=1
maxOccurs=1 xmime:expectedContentTypes=application/binary /
xsd:element name=Filename type=xsd:string minOccurs=1
maxOccurs=1 /
/xsd:sequence
/xsd:complexType
xsd:complexType name=Certificate
xsd:sequence
xsd:element name=Issuer type=xsd:string minOccurs=1
maxOccurs=1 /
xsd:element name=Subject type=xsd:string minOccurs=1
maxOccurs=1 /
xsd:element name=SerialNumber type=xsd:string minOccurs=0
maxOccurs=1 /
xsd:element name=ValidFrom type=xsd:dateTime minOccurs=0
maxOccurs=1 /
xsd:element name=ValidTo type=xsd:dateTime minOccurs=0
maxOccurs=1 /
/xsd:sequence
/xsd:complexType
xsd:element name=VerifyRequest
xsd:complexType
xsd:sequence
xsd:element name=SignID type=xsd:long minOccurs=1
maxOccurs=1 /
xsd:element name=EndUserIdentifier type=eSig:EndUserIdentifier
minOccurs=1 maxOccurs=1 /
xsd:element name=Document type=eSig:Document minOccurs=1
maxOccurs=2 /
xsd:element name=CrlChecking type=eSig:CrlChecking
minOccurs=0 maxOccurs=1 /
xsd:element name=SignatoryDetailsRequired type=xsd:boolean
minOccurs=0 maxOccurs=1 /
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:element name=VerifyResponse
xsd:complexType
xsd:sequence
xsd:element name=RequestID type=xsd:string minOccurs=0
maxOccurs=1 /
xsd:element name=isVerified type=xsd:boolean minOccurs=1
maxOccurs=1 /
xsd:element name=CrlStatus type=xsd:string minOccurs=0
maxOccurs=1 /
xsd:element name=Certificate type=eSig:Certificate
maxOccurs=1 minOccurs=0 /
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:complexType name=SigningServiceError
xsd:sequence
xsd:element minOccurs=0 maxOccurs=1 name=RequestID
type=xsd:string /
xsd:element minOccurs=1 maxOccurs=1 name=Fault
type=xsd:string /
xsd:element minOccurs=1 maxOccurs=1 name=Datetime
type=xsd:dateTime /
/xsd:sequence
/xsd:complexType
xsd:element name=ApplicationError type=eSig:SigningServiceError /
Re: WSDL
The Axis2 java2wsdl tool generates doc/literal -- but my guess is that it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2, etc. I suggest you use the Axis java2wsdl tool and specify wrapped style. The resulting WSDL should be acceptable to J2ME. You can then use that WSDL as input to the Axis2 wsdl2java tool. Anne On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid [EMAIL PROTECTED] wrote: hi, thanks for your reply, but i've used the java2wsdl tool from axis2, but this does not create a compatible WSDL (document/literal) for J2ME stub generator, which i need to create it for. has anyone used the WSDP tools, specifically wsgen, to create a document/literal WSDL? (from java/class files) i've searched google, but i cant manage to get wsgen to work. thanks Date: Sun, 2 Mar 2008 23:13:24 +0800 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL dude http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html i used that link to help me out. or if you're not contented with that.. google.. ;) On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi, does anyone know how to generate a document/literal WSDL file from .class files (or .java files)? or if anyone knows how to use the 'wscompile' tool, please can you help me out and tell me what commands i need to follow it's urgent thanks Think you know your TV, music and film? Try Search Charades! -- Website: http://chitgoks.freehostia.com Java Casino Games: http://chitgoks.tripod.com My Blogs: http://chitgoks.blogspot.com http://wuhtevah.blogspot.com Everything in one place. All new Windows Live! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL
Hi Anne,
thanks for your reply. How exactly would i specify the wrapped (for j2me)
style while using the java2wsdl tool? currently i type:
java2wsdl -cn packagename.mainclass Date: Sun, 9 Mar 2008 15:39:38 -0400
From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL The
Axis2 java2wsdl tool generates doc/literal -- but my guess is that it
generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2, etc. I
suggest you use the Axis java2wsdl tool and specify wrapped style. The
resulting WSDL should be acceptable to J2ME. You can then use that WSDL as
input to the Axis2 wsdl2java tool. Anne On Sun, Mar 2, 2008 at 3:50 PM,
shams jawaid [EMAIL PROTECTED] wrote: hi, thanks for your reply,
but i've used the java2wsdl tool from axis2, but this does not create a
compatible WSDL (document/literal) for J2ME stub generator, which i
need to create it for. has anyone used the WSDP tools, specifically
wsgen, to create a document/literal WSDL? (from java/class files) i've
searched google, but i cant manage to get wsgen to work.thanks
Date: Sun, 2 Mar 2008 23:13:24 +0800
From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL
dude http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html
i used that link to help me out. or if you're not contented with that..
google.. ;)On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL
PROTECTED] wrote:Hi, does anyone know how to generate a
document/literal WSDL file from .class files (or .java files)? or if
anyone knows how to use the 'wscompile' tool, please can you help me out and
tell me what commands i need to follow it's urgent thanks
Think you know your TV, music and film? Try
Search Charades!-- Website: http://chitgoks.freehostia.com Java
Casino Games: http://chitgoks.tripod.com My Blogs:
http://chitgoks.blogspot.com http://wuhtevah.blogspot.com
Everything in one place. All new Windows
Live! -
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
[EMAIL PROTECTED]
_
Get Hotmail on your mobile, text MSN to 63463!
http://mobile.uk.msn.com/pc/mail.aspx
Re: WSDL
dude http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html i used that link to help me out. or if you're not contented with that.. google.. ;) On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi, does anyone know how to generate a document/literal WSDL file from .class files (or .java files)? or if anyone knows how to use the 'wscompile' tool, please can you help me out and tell me what commands i need to follow it's urgent thanks -- Think you know your TV, music and film? Try Search Charades!https://www.searchcharades.com -- Website: http://chitgoks.freehostia.com Java Casino Games: http://chitgoks.tripod.com My Blogs: http://chitgoks.blogspot.com http://wuhtevah.blogspot.com
RE: WSDL
hi, thanks for your reply, but i've used the java2wsdl tool from axis2, but this does not create a compatible WSDL (document/literal) for J2ME stub generator, which i need to create it for. has anyone used the WSDP tools, specifically wsgen, to create a document/literal WSDL? (from java/class files) i've searched google, but i cant manage to get wsgen to work. thanks Date: Sun, 2 Mar 2008 23:13:24 +0800From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Re: WSDLdudehttp://www.onjava.com/pub/a/onjava/2002/06/05/axis.htmli used that link to help me out.or if you're not contented with that.. google.. ;) On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi, does anyone know how to generate a document/literal WSDL file from .class files (or .java files)?or if anyone knows how to use the 'wscompile' tool, please can you help me out and tell me what commands i need to follow it's urgent thanks Think you know your TV, music and film? Try Search Charades!-- Website: http://chitgoks.freehostia.comJava Casino Games: http://chitgoks.tripod.comMy Blogs: http://chitgoks.blogspot.comhttp://wuhtevah.blogspot.com _ Share what Santa brought you https://www.mycooluncool.com
Re: WSDL
ah sorry cant say with j2me since ive used it for webapp On Mon, Mar 3, 2008 at 3:50 AM, shams jawaid [EMAIL PROTECTED] wrote: hi, thanks for your reply, but i've used the java2wsdl tool from axis2, but this does not create a compatible WSDL (document/literal) for J2ME stub generator, which i need to create it for. has anyone used the WSDP tools, specifically wsgen, to create a document/literal WSDL? (from java/class files) i've searched google, but i cant manage to get wsgen to work. thanks -- Date: Sun, 2 Mar 2008 23:13:24 +0800 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: WSDL dude http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html i used that link to help me out. or if you're not contented with that.. google.. ;) On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid [EMAIL PROTECTED] wrote: Hi, does anyone know how to generate a document/literal WSDL file from .class files (or .java files)? or if anyone knows how to use the 'wscompile' tool, please can you help me out and tell me what commands i need to follow it's urgent thanks -- Think you know your TV, music and film? Try Search Charades!https://www.searchcharades.com/ -- Website: http://chitgoks.freehostia.com Java Casino Games: http://chitgoks.tripod.com My Blogs: http://chitgoks.blogspot.com http://wuhtevah.blogspot.com -- Everything in one place. All new Windows Live!http://www.windowslive.co.uk/get-live -- Website: http://chitgoks.freehostia.com Java Casino Games: http://chitgoks.tripod.com My Blogs: http://chitgoks.blogspot.com http://wuhtevah.blogspot.com
Re: WSDL element restrictions
if you generated classes with ADB these restrictions are forced within the classes. you can see these codes from the generated classes. thanks, Amila. On Mon, Feb 25, 2008 at 11:21 AM, David Bunzli [EMAIL PROTECTED] wrote: Hi, Where does Axis2 enforce WSDL element restrictions? For example, if you wish a string element to have a minLength of 1 and maxLength of 3, are requests rejected by Schema validation if they don't conform? Or are these restrictions in the generated classes from Wsdl2Java? Regards, David * This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. -- Amila Suriarachchi, WSO2 Inc.
Re: WSDL parser
Hi all,
does anyone know of a piece of code similar to the one below that
can read/parse a local WSDL file
serialized in a string rather than a remote WSDL given by a URI?
Thanks
Sukma Agung Verdianto wrote:
Hi Demetris,
You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to
get the operations of specified wsdl file. (AFAIK, Axis2 uses this in
their wsdl2java code)
public static void main(String[] args) throws Exception {
WSDLFactory fac = WSDLFactoryImpl.newInstance();
WSDLReader reader = fac.newWSDLReader();
Definition def =
reader.readWSDL(http://api.google.com/GoogleSearch.wsdl;);
Map services = def.getServices();
for(Object serviceKey : services.keySet()) {
QName serviceQName = (QName) serviceKey;
Service service = (Service) services.get(serviceQName);
System.out.println(Namespace: +
service.getQName().getNamespaceURI() + , Service Name: +
service.getQName().getLocalPart());
Map ports = service.getPorts();
for(Object portKey : ports.keySet()) {
String portName = (String) portKey;
Port port = (Port) ports.get(portName);
System.out.println( Namespace: +
port.getBinding().getQName().getNamespaceURI() + , Binding Name: +
port.getBinding().getQName().getLocalPart());
List operations = port.getBinding().getBindingOperations();
for(Object operation : operations) {
BindingOperation op = (BindingOperation) operation;
System.out.print(Operation Name: + op.getName());
List ll = op.getExtensibilityElements();
for(Object soap : ll) {
if(SOAPOperation.class.isInstance(soap)) {
System.out.print( ( + ((SOAPOperation)soap).getSoapActionURI() + ));
}
}
System.out.println();
}
}
}
}
Above code read remote wsdl, and extract its information.
Regards,
Sukma
On Feb 17, 2008 2:09 PM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL parser
Hi Demetris,
To read a local file you could simply use file:///path/to/wsdl/file.wsdl
as readWSDL argument - reader.readWSDL(file:///path/to/your/wsdl);,
Or if you have a WSDL serialized in String, you could use reader.readWSDL(
null, new InputSource(new StringReader(wsdlString)));
Regards,
Sukma
On Fri, Feb 22, 2008 at 1:22 PM, Demetris G [EMAIL PROTECTED] wrote:
Hi all,
does anyone know of a piece of code similar to the one below that
can read/parse a local WSDL file
serialized in a string rather than a remote WSDL given by a URI?
Thanks
Sukma Agung Verdianto wrote:
Hi Demetris,
You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to
get the operations of specified wsdl file. (AFAIK, Axis2 uses this in
their wsdl2java code)
public static void main(String[] args) throws Exception {
WSDLFactory fac = WSDLFactoryImpl.newInstance();
WSDLReader reader = fac.newWSDLReader();
Definition def =
reader.readWSDL(http://api.google.com/GoogleSearch.wsdl;);
Map services = def.getServices();
for(Object serviceKey : services.keySet()) {
QName serviceQName = (QName) serviceKey;
Service service = (Service) services.get(serviceQName);
System.out.println(Namespace: +
service.getQName().getNamespaceURI() + , Service Name: +
service.getQName().getLocalPart());
Map ports = service.getPorts();
for(Object portKey : ports.keySet()) {
String portName = (String) portKey;
Port port = (Port) ports.get(portName);
System.out.println( Namespace: +
port.getBinding().getQName().getNamespaceURI() + , Binding Name: +
port.getBinding().getQName().getLocalPart());
List operations = port.getBinding().getBindingOperations();
for(Object operation : operations) {
BindingOperation op = (BindingOperation) operation;
System.out.print(Operation Name: + op.getName());
List ll = op.getExtensibilityElements();
for(Object soap : ll) {
if(SOAPOperation.class.isInstance(soap)) {
System.out.print( ( + ((SOAPOperation)soap).getSoapActionURI() + ));
}
}
System.out.println();
}
}
}
}
Above code read remote wsdl, and extract its information.
Regards,
Sukma
On Feb 17, 2008 2:09 PM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL parser
Hey Sukma,
thanks for the response - I oringally went with the second option
but I was getting an exception
on the StringReader. I think I know what the problem is - at least you
verified for me that I am on
the right path. I appreciate it.
Many regards once again
Sukma Agung Verdianto wrote:
Hi Demetris,
To read a local file you could simply use
file:///path/to/wsdl/file.wsdl as readWSDL argument
- reader.readWSDL(file:///path/to/your/wsdl);,
Or if you have a WSDL serialized in String, you could
use reader.readWSDL(null, new InputSource(new StringReader(wsdlString)));
Regards,
Sukma
On Fri, Feb 22, 2008 at 1:22 PM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
does anyone know of a piece of code similar to the one below that
can read/parse a local WSDL file
serialized in a string rather than a remote WSDL given by a URI?
Thanks
Sukma Agung Verdianto wrote:
Hi Demetris,
You can try to use wsdl4j
(http://sourceforge.net/projects/wsdl4j) to
get the operations of specified wsdl file. (AFAIK, Axis2 uses
this in
their wsdl2java code)
public static void main(String[] args) throws Exception {
WSDLFactory fac = WSDLFactoryImpl.newInstance();
WSDLReader reader = fac.newWSDLReader();
Definition def =
reader.readWSDL(http://api.google.com/GoogleSearch.wsdl;);
Map services = def.getServices();
for(Object serviceKey : services.keySet()) {
QName serviceQName = (QName) serviceKey;
Service service = (Service) services.get(serviceQName);
System.out.println(Namespace: +
service.getQName().getNamespaceURI() + , Service Name: +
service.getQName().getLocalPart());
Map ports = service.getPorts();
for(Object portKey : ports.keySet()) {
String portName = (String) portKey;
Port port = (Port) ports.get(portName);
System.out.println( Namespace: +
port.getBinding().getQName().getNamespaceURI() + , Binding
Name: +
port.getBinding().getQName().getLocalPart());
List operations = port.getBinding().getBindingOperations();
for(Object operation : operations) {
BindingOperation op = (BindingOperation) operation;
System.out.print(Operation Name: + op.getName());
List ll = op.getExtensibilityElements();
for(Object soap : ll) {
if(SOAPOperation.class.isInstance(soap)) {
System.out.print( ( + ((SOAPOperation)soap).getSoapActionURI()
+ ));
}
}
System.out.println();
}
}
}
}
Above code read remote wsdl, and extract its information.
Regards,
Sukma
On Feb 17, 2008 2:09 PM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Hi all,
I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could
get the
operations
of the remote service out of the WSDL file? I would
appreciate it.
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL parser
Hey Sukma,
the code below worked fine - I can get the operations out of the
WSDL. Is there
a similar parser for identifying and extracting the methods out of
outgoing (from the
stubs) SOAP messages? I capture the SOAP message and I can parse it manually
but is there a standard way (like the code below) for identifying the
methods the
SOAP message is destined to?
Thanks much once again
Sukma Agung Verdianto wrote:
Hi Demetris,
You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to
get the operations of specified wsdl file. (AFAIK, Axis2 uses this in
their wsdl2java code)
public static void main(String[] args) throws Exception {
WSDLFactory fac = WSDLFactoryImpl.newInstance();
WSDLReader reader = fac.newWSDLReader();
Definition def =
reader.readWSDL(http://api.google.com/GoogleSearch.wsdl;);
Map services = def.getServices();
for(Object serviceKey : services.keySet()) {
QName serviceQName = (QName) serviceKey;
Service service = (Service) services.get(serviceQName);
System.out.println(Namespace: +
service.getQName().getNamespaceURI() + , Service Name: +
service.getQName().getLocalPart());
Map ports = service.getPorts();
for(Object portKey : ports.keySet()) {
String portName = (String) portKey;
Port port = (Port) ports.get(portName);
System.out.println( Namespace: +
port.getBinding().getQName().getNamespaceURI() + , Binding Name: +
port.getBinding().getQName().getLocalPart());
List operations = port.getBinding().getBindingOperations();
for(Object operation : operations) {
BindingOperation op = (BindingOperation) operation;
System.out.print(Operation Name: + op.getName());
List ll = op.getExtensibilityElements();
for(Object soap : ll) {
if(SOAPOperation.class.isInstance(soap)) {
System.out.print( ( + ((SOAPOperation)soap).getSoapActionURI() + ));
}
}
System.out.println();
}
}
}
}
Above code read remote wsdl, and extract its information.
Regards,
Sukma
On Feb 17, 2008 2:09 PM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL parser
Hi Demitris,
Sorry for this late response,
I'm not sure if there is a 'ready to use' parser to extract information out
of SOAP message. But I guess Axis2 have it.
Extracting information from soap message is quite complex.
There are several ways to get those information (eg: operations, to,
replyto):
1. If you use older SOAP version (1.1) and HTTP transport - operation name
is defined as HTTP attribute (Could not remember the name, Action or
Operation)
2. In SOAP (1.2) and HTTP transport there is also an extra HTTP attribute
(not sure where, you can check by capturing using tcpmon)
3. This is more difficult, if your soap use WS_Addressing standard, you may
read the SOAP header and look for wsa:Action element value.
Example of SOAP with WS-Addressing header. (see wsa:Action element)
wsa:To
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1
wsu:Id=Id-13283276http://localhost:/axis2/services/CalculatorService?wsdl/wsa:To
wsa:ReplyTo
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1 wsu:Id=Id-14395294
wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
/wsa:ReplyTo
wsa:MessageID
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1
wsu:Id=Id-14264518urn:uuid:0E4DF98317F35D31DE1179281210189/wsa:MessageID
wsa:Action
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1
wsu:Id=Id-14123379urn:Divide/wsa:Action /soapenv:Header
I hope this will help. :)
Regards,
Sukma
On Feb 19, 2008 11:46 AM, Demetris G [EMAIL PROTECTED] wrote:
Hey Sukma,
the code below worked fine - I can get the operations out of the
WSDL. Is there
a similar parser for identifying and extracting the methods out of
outgoing (from the
stubs) SOAP messages? I capture the SOAP message and I can parse it
manually
but is there a standard way (like the code below) for identifying the
methods the
SOAP message is destined to?
Thanks much once again
Sukma Agung Verdianto wrote:
Hi Demetris,
You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to
get the operations of specified wsdl file. (AFAIK, Axis2 uses this in
their wsdl2java code)
public static void main(String[] args) throws Exception {
WSDLFactory fac = WSDLFactoryImpl.newInstance();
WSDLReader reader = fac.newWSDLReader();
Definition def =
reader.readWSDL(http://api.google.com/GoogleSearch.wsdl;);
Map services = def.getServices();
for(Object serviceKey : services.keySet()) {
QName serviceQName = (QName) serviceKey;
Service service = (Service) services.get(serviceQName);
System.out.println(Namespace: +
service.getQName().getNamespaceURI() + , Service Name: +
service.getQName().getLocalPart());
Map ports = service.getPorts();
for(Object portKey : ports.keySet()) {
String portName = (String) portKey;
Port port = (Port) ports.get(portName);
System.out.println( Namespace: +
port.getBinding().getQName().getNamespaceURI() + , Binding Name: +
port.getBinding().getQName().getLocalPart());
List operations = port.getBinding().getBindingOperations();
for(Object operation : operations) {
BindingOperation op = (BindingOperation) operation;
System.out.print(Operation Name: + op.getName());
List ll = op.getExtensibilityElements();
for(Object soap : ll) {
if(SOAPOperation.class.isInstance(soap)) {
System.out.print( ( + ((SOAPOperation)soap).getSoapActionURI() + ));
}
}
System.out.println();
}
}
}
}
Above code read remote wsdl, and extract its information.
Regards,
Sukma
On Feb 17, 2008 2:09 PM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi all,
I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL parser
Hi Sukma -
once again thanks for the quick response - much appreciated -
I tried #1 but not #3. I am migrating to SOAP 1.2 so I will also
look into the second option you list. I will let the list know how that
one goes as well.
Regards
Sukma Agung Verdianto wrote:
Hi Demitris,
Sorry for this late response,
I'm not sure if there is a 'ready to use' parser to extract
information out of SOAP message. But I guess Axis2 have it.
Extracting information from soap message is quite complex.
There are several ways to get those information (eg: operations, to,
replyto):
1. If you use older SOAP version (1.1) and HTTP transport - operation
name is defined as HTTP attribute (Could not remember the name,
Action or Operation)
2. In SOAP (1.2) and HTTP transport there is also an extra HTTP
attribute (not sure where, you can check by capturing using tcpmon)
3. This is more difficult, if your soap use WS_Addressing standard,
you may read the SOAP header and look for wsa:Action element value.
Example of SOAP with WS-Addressing header. (see wsa:Action element)
wsa:To
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1
wsu:Id=Id-13283276http://localhost:/axis2/services/CalculatorService?wsdl/wsa:To
wsa:ReplyTo
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1 wsu:Id=Id-14395294
wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
/wsa:ReplyTo
wsa:MessageID
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1
wsu:Id=Id-14264518urn:uuid:0E4DF98317F35D31DE1179281210189/wsa:MessageID
wsa:Action
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
soapenv:mustUnderstand=1 wsu:Id=Id-14123379urn:Divide/wsa:Action
/soapenv:Header
I hope this will help. :)
Regards,
Sukma
On Feb 19, 2008 11:46 AM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hey Sukma,
the code below worked fine - I can get the operations out of the
WSDL. Is there
a similar parser for identifying and extracting the methods out of
outgoing (from the
stubs) SOAP messages? I capture the SOAP message and I can parse
it manually
but is there a standard way (like the code below) for identifying the
methods the
SOAP message is destined to?
Thanks much once again
Sukma Agung Verdianto wrote:
Hi Demetris,
You can try to use wsdl4j
(http://sourceforge.net/projects/wsdl4j) to
get the operations of specified wsdl file. (AFAIK, Axis2 uses
this in
their wsdl2java code)
public static void main(String[] args) throws Exception {
WSDLFactory fac = WSDLFactoryImpl.newInstance();
WSDLReader reader = fac.newWSDLReader();
Definition def =
reader.readWSDL(http://api.google.com/GoogleSearch.wsdl;);
Map services = def.getServices();
for(Object serviceKey : services.keySet()) {
QName serviceQName = (QName) serviceKey;
Service service = (Service) services.get(serviceQName);
System.out.println(Namespace: +
service.getQName().getNamespaceURI() + , Service Name: +
service.getQName().getLocalPart());
Map ports = service.getPorts();
for(Object portKey : ports.keySet()) {
String portName = (String) portKey;
Port port = (Port) ports.get(portName);
System.out.println( Namespace: +
port.getBinding().getQName().getNamespaceURI() + , Binding
Name: +
port.getBinding().getQName().getLocalPart());
List operations = port.getBinding().getBindingOperations();
for(Object operation : operations) {
BindingOperation op = (BindingOperation) operation;
System.out.print(Operation Name: + op.getName());
List ll = op.getExtensibilityElements();
for(Object soap : ll) {
if(SOAPOperation.class.isInstance(soap)) {
System.out.print( ( + ((SOAPOperation)soap).getSoapActionURI()
+ ));
}
}
System.out.println();
}
}
}
}
Above code read remote wsdl, and extract its information.
Regards,
Sukma
On Feb 17, 2008 2:09 PM, Demetris G [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Hi all,
I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could
get the
operations
of the remote service out of the WSDL file? I would
Re: WSDL parser
Hi Demetris,
You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to get
the operations of specified wsdl file. (AFAIK, Axis2 uses this in their
wsdl2java code)
public static void main(String[] args) throws Exception {
WSDLFactory fac = WSDLFactoryImpl.newInstance();
WSDLReader reader = fac.newWSDLReader();
Definition def = reader.readWSDL(http://api.google.com/GoogleSearch.wsdl;
);
Map services = def.getServices();
for(Object serviceKey : services.keySet()) {
QName serviceQName = (QName) serviceKey;
Service service = (Service) services.get(serviceQName);
System.out.println(Namespace: + service.getQName().getNamespaceURI() + ,
Service Name: + service.getQName().getLocalPart());
Map ports = service.getPorts();
for(Object portKey : ports.keySet()) {
String portName = (String) portKey;
Port port = (Port) ports.get(portName);
System.out.println( Namespace: +
port.getBinding().getQName().getNamespaceURI()
+ , Binding Name: + port.getBinding().getQName().getLocalPart());
List operations = port.getBinding().getBindingOperations();
for(Object operation : operations) {
BindingOperation op = (BindingOperation) operation;
System.out.print(Operation Name: + op.getName());
List ll = op.getExtensibilityElements();
for(Object soap : ll) {
if(SOAPOperation.class.isInstance(soap)) {
System.out.print( ( + ((SOAPOperation)soap).getSoapActionURI() + ));
}
}
System.out.println();
}
}
}
}
Above code read remote wsdl, and extract its information.
Regards,
Sukma
On Feb 17, 2008 2:09 PM, Demetris G [EMAIL PROTECTED] wrote:
Hi all,
I am trying to use the wsdlParser from the Axis API to parse the
methods
out of an incoming WSDL file - does anyone who has used this before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL parser
$AXIS2_HOME/bin/wsdl2java -uri NameOfWsdl.wsdl M- - Original Message - From: Demetris G [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Sunday, February 17, 2008 2:09 AM Subject: WSDL parser Hi all, I am trying to use the wsdlParser from the Axis API to parse the methods out of an incoming WSDL file - does anyone who has used this before have any info on how to use this tool? OR any other way I could get the operations of the remote service out of the WSDL file? I would appreciate it. 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]
Re: WSDL / SOAP reply namespaces problem.
Amila is correct. A valid response would look semantically equivalent to this:
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
getUserResponse xmlns=http://server.ws.te0.com;
xmlns:ns1=http://ws.apache.org/axis1/xsd;
getUserReturn
ns1:daysValid39 /ns1:daysValid
ns1:lastUserUpdate20080211084047 /ns1:lastUserUpdate
ns1:resumeDate1-01-01 /ns1:resumeDate
ns1:suspendFlagN /ns1:suspendFlag
ns1:userFirstNameMASTER /ns1:userFirstName
ns1:userInitials/
ns1:userLastNameSECURITY /ns1:userLastName
ns1:userNameMAS /ns1:userName
ns1:vaxID12027 /ns1:vaxID
/getUserReturn
/getUserResponse
/soapenv:Body
/soapenv:Envelope
Anne
On Feb 14, 2008 12:11 AM, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
According to your wsdl, the following elements under the complex type User
belongs to
http://ws.apache.org/axis1/xsd namespace.
element name=daysValid nillable=true type=xsd:string/
element name=lastUserUpdate nillable=true type=xsd:string/
element name=resumeDate nillable=true type=xsd:string/
element name=suspendFlag nillable=true type=xsd:string/
element name=userFirstName nillable=true type=xsd:string/
element name=userInitials nillable=true type=xsd:string/
element name=userLastName nillable=true type=xsd:string/
element name=userName nillable=true type=xsd:string/
element name=vaxID nillable=true type=xsd:string/
But According to the response they belongs to a different namesapce. So the
response is invalid.
thanks,
Amila.
On Feb 12, 2008 12:26 AM, [EMAIL PROTECTED] wrote:
Paul,
Thanks for the reply
I get this wsdl from the server i am suppused to connect to.
How does the http://ws.apache.org/axis1/xsd namespace come to play?
schema targetNamespace=http://ws.apache.org/axis1/xsd;
xmlns=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified
My generated client code is trying to locate the reply elements in this
namespace.
( ireformatted the generated code for better readability )
if (reader.isStartElement() new
javax.xml.namespace.QName(http://ws.apache.org/axis1/xsd,daysValid;).equals(reader.getName()))
{
nillableValue =
reader.getAttributeValue(http://www.w3.org/2001/XMLSchema-instance,nil;);
if (!true.equals(nillableValue) !1.equals(nillableValue))
{
java.lang.String content = reader.getElementText();
object.setDaysValid(org.apache.axis2.databinding.utils.ConverterUtil.convertToString(content));
}
else
{
reader.getElementText(); // throw away text nodes if any.
}
reader.next();
} // End of if for expected property start element
else
{
// A start element we are not expecting indicates an invalid parameter
was passed
throw new org.apache.axis2.databinding.ADBException(Unexpected
subelement + reader.getLocalName());
}
thanks
LF
Leonid Flom · The Bank of New York Mellon
Treasury Systems - CA$H-Register Plus · Tel 212.815.7023 · Fax
212.815.8200 · [EMAIL PROTECTED]
Paul Fremantle [EMAIL PROTECTED]
02/11/2008 01:46 PM
Please respond to
axis-user@ws.apache.org
To axis-user@ws.apache.org
cc
Subject Re: WSDL / SOAP reply namespaces problem.
Leonid
The response element is defined in the second schema which has the
schema targetNamespace=http://server.ws.te0.com;
So the response matches the WSDL as far as I can see.
To be honest its a really strange WSDL! Wouldn't it make sense to clean it
up?
Paul
On Feb 11, 2008 6:15 PM, [EMAIL PROTECTED] wrote:
hello, everybody
Can anybody tell me if this SOAP reply message is valid for the given
wsdl?
I am using Axis2 to generate the client stub and when running the
client I
get the
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement exception.
WSDL is generated by Axis1.
It seems that the problem is the namespace of the nested elements of
the
getUserReturn.
In wsdl they are defined to be in the http://ws.apache.org/axis1/xsd;
namespace, but the reply has them in the http://server.ws.te0.com;.
I traced the generated source code it is exactly where it is failing.
Thanks
LF
SOAP reply:
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
getUserResponse xmlns=http://server.ws.te0.com;
getUserReturn
daysValid39 /daysValid
lastUserUpdate20080211084047 /lastUserUpdate
Re: WSDL parser
Thanks Martin and Sukma - I will try the two methods you send me and see how they work. I will share on the list the results on anything I find Regards Martin Gainty wrote: $AXIS2_HOME/bin/wsdl2java -uri NameOfWsdl.wsdl M- - Original Message - From: Demetris G [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Sunday, February 17, 2008 2:09 AM Subject: WSDL parser Hi all, I am trying to use the wsdlParser from the Axis API to parse the methods out of an incoming WSDL file - does anyone who has used this before have any info on how to use this tool? OR any other way I could get the operations of the remote service out of the WSDL file? I would appreciate it. 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL / SOAP reply namespaces problem.
According to your wsdl, the following elements under the complex type User
belongs to
http://ws.apache.org/axis1/xsd namespace.
element name=daysValid nillable=true type=xsd:string/
element name=lastUserUpdate nillable=true type=xsd:string/
element name=resumeDate nillable=true type=xsd:string/
element name=suspendFlag nillable=true type=xsd:string/
element name=userFirstName nillable=true type=xsd:string/
element name=userInitials nillable=true type=xsd:string/
element name=userLastName nillable=true type=xsd:string/
element name=userName nillable=true type=xsd:string/
element name=vaxID nillable=true type=xsd:string/
But According to the response they belongs to a different namesapce. So the
response is invalid.
thanks,
Amila.
On Feb 12, 2008 12:26 AM, [EMAIL PROTECTED] wrote:
Paul,
Thanks for the reply
I get this wsdl from the server i am suppused to connect to.
How does the http://ws.apache.org/axis1/xsd namespace come to play?
schema targetNamespace=*http://ws.apache.org/axis1/xsd*;
xmlns=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified
My generated client code is trying to locate the reply elements in this
namespace.
( ireformatted the generated code for better readability )
if (reader.isStartElement() new javax.xml.namespace.QName(*
http://ws.apache.org/axis1/xsd,daysValid*).equals(reader.getName()))
{
nillableValue = reader.getAttributeValue(
http://www.w3.org/2001/XMLSchema-instance,nil;);
if (!true.equals(nillableValue) !1.equals(nillableValue))
{
java.lang.String content = reader.getElementText();
object.setDaysValid(
org.apache.axis2.databinding.utils.ConverterUtil.convertToString
(content));
}
else
{
reader.getElementText(); // throw away text nodes if any.
}
reader.next();
} // End of if for expected property start element
else
{
// A start element we are not expecting indicates an invalid parameter
was passed
throw new org.apache.axis2.databinding.ADBException(Unexpected
subelement + reader.getLocalName());
}
thanks
LF
--
*Leonid Flom · *The Bank of New York Mellon
Treasury Systems - CA$H-Register Plus* ·* Tel 212.815.7023* ·* Fax
212.815.8200* ·* [EMAIL PROTECTED] [EMAIL PROTECTED]* *
*Paul Fremantle [EMAIL PROTECTED]*
02/11/2008 01:46 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org cc
Subject
Re: WSDL / SOAP reply namespaces problem.
Leonid
The response element is defined in the second schema which has the
schema targetNamespace=http://server.ws.te0.com;
So the response matches the WSDL as far as I can see.
To be honest its a really strange WSDL! Wouldn't it make sense to clean it
up?
Paul
On Feb 11, 2008 6:15 PM, [EMAIL PROTECTED] wrote:
hello, everybody
Can anybody tell me if this SOAP reply message is valid for the given
wsdl?
I am using Axis2 to generate the client stub and when running the
client I
get the
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement exception.
WSDL is generated by Axis1.
It seems that the problem is the namespace of the nested elements of
the
getUserReturn.
In wsdl they are defined to be in the http://ws.apache.org/axis1/xsd;
namespace, but the reply has them in the http://server.ws.te0.com;.
I traced the generated source code it is exactly where it is failing.
Thanks
LF
SOAP reply:
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
getUserResponse xmlns=http://server.ws.te0.com;
getUserReturn
daysValid39 /daysValid
lastUserUpdate20080211084047 /lastUserUpdate
resumeDate1-01-01 /resumeDate
suspendFlagN /suspendFlag
userFirstNameMASTER /userFirstName
userInitials/
userLastNameSECURITY /userLastName
userNameMAS /userName
vaxID12027 /vaxID
/getUserReturn
/getUserResponse
/soapenv:Body
/soapenv:Envelope
WSDL:
?xml version=1.0 encoding=UTF-8?
wsdl:definitions
targetNamespace=
https://www-nr.qa.thebank.com/services/EntitlementWebServices;
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=
https://www-nr.qa.thebank.com/services/EntitlementWebServices;
xmlns:intf=
https://www-nr.qa.thebank.com/services/EntitlementWebServices;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns1=http://ws.apache.org/axis1/xsd;
xmlns:tns2=http://server.ws.te0.com;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema
Re: WSDL / SOAP reply namespaces problem.
Paul,
Thanks for the reply
I get this wsdl from the server i am suppused to connect to.
How does the http://ws.apache.org/axis1/xsd namespace come to play?
schema targetNamespace=http://ws.apache.org/axis1/xsd;
xmlns=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified
My generated client code is trying to locate the reply elements in this
namespace.
( ireformatted the generated code for better readability )
if (reader.isStartElement() new javax.xml.namespace.QName(
http://ws.apache.org/axis1/xsd,daysValid;).equals(reader.getName()))
{
nillableValue =
reader.getAttributeValue(http://www.w3.org/2001/XMLSchema-instance,nil;);
if (!true.equals(nillableValue) !1.equals(nillableValue))
{
java.lang.String content = reader.getElementText();
object.setDaysValid(org.apache.axis2.databinding.utils.ConverterUtil.convertToString(content));
}
else
{
reader.getElementText(); // throw away text nodes if any.
}
reader.next();
} // End of if for expected property start element
else
{
// A start element we are not expecting indicates an invalid parameter
was passed
throw new org.apache.axis2.databinding.ADBException(Unexpected
subelement + reader.getLocalName());
}
thanks
LF
Leonid Flom · The Bank of New York Mellon
Treasury Systems - CA$H-Register Plus · Tel 212.815.7023 · Fax
212.815.8200 · [EMAIL PROTECTED]
Paul Fremantle [EMAIL PROTECTED]
02/11/2008 01:46 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Re: WSDL / SOAP reply namespaces problem.
Leonid
The response element is defined in the second schema which has the
schema targetNamespace=http://server.ws.te0.com;
So the response matches the WSDL as far as I can see.
To be honest its a really strange WSDL! Wouldn't it make sense to clean it
up?
Paul
On Feb 11, 2008 6:15 PM, [EMAIL PROTECTED] wrote:
hello, everybody
Can anybody tell me if this SOAP reply message is valid for the given
wsdl?
I am using Axis2 to generate the client stub and when running the
client I
get the
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
Unexpected subelement exception.
WSDL is generated by Axis1.
It seems that the problem is the namespace of the nested elements of
the
getUserReturn.
In wsdl they are defined to be in the http://ws.apache.org/axis1/xsd;
namespace, but the reply has them in the http://server.ws.te0.com;.
I traced the generated source code it is exactly where it is failing.
Thanks
LF
SOAP reply:
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
getUserResponse xmlns=http://server.ws.te0.com;
getUserReturn
daysValid39 /daysValid
lastUserUpdate20080211084047 /lastUserUpdate
resumeDate1-01-01 /resumeDate
suspendFlagN /suspendFlag
userFirstNameMASTER /userFirstName
userInitials/
userLastNameSECURITY /userLastName
userNameMAS /userName
vaxID12027 /vaxID
/getUserReturn
/getUserResponse
/soapenv:Body
/soapenv:Envelope
WSDL:
?xml version=1.0 encoding=UTF-8?
wsdl:definitions
targetNamespace=
https://www-nr.qa.thebank.com/services/EntitlementWebServices;
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=
https://www-nr.qa.thebank.com/services/EntitlementWebServices;
xmlns:intf=
https://www-nr.qa.thebank.com/services/EntitlementWebServices;
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns1=http://ws.apache.org/axis1/xsd;
xmlns:tns2=http://server.ws.te0.com;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
wsdl:types
schema targetNamespace=http://ws.apache.org/axis1/xsd;
xmlns=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified
complexType name=User
sequence
element name=daysValid nillable=true type=xsd:string/
element name=lastUserUpdate nillable=true type=xsd:string/
element name=resumeDate nillable=true type=xsd:string/
element name=suspendFlag nillable=true type=xsd:string/
element name=userFirstName nillable=true type=xsd:string/
element name=userInitials nillable=true type=xsd:string/
element name=userLastName nillable=true type=xsd:string/
element name=userName nillable=true type=xsd:string/
element name=vaxID nillable=true type=xsd:string/
/sequence
/complexType
/schema
schema targetNamespace=http://server.ws.te0.com;
xmlns=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified
element name=getUser
complexType
sequence
element name=requestingKNumber type=xsd:string/
element name=requestingSubID type
Re: WSDL / SOAP reply namespaces problem.
Leonid The response element is defined in the second schema which has the schema targetNamespace=http://server.ws.te0.com; So the response matches the WSDL as far as I can see. To be honest its a really strange WSDL! Wouldn't it make sense to clean it up? Paul On Feb 11, 2008 6:15 PM, [EMAIL PROTECTED] wrote: hello, everybody Can anybody tell me if this SOAP reply message is valid for the given wsdl? I am using Axis2 to generate the client stub and when running the client I get the org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement exception. WSDL is generated by Axis1. It seems that the problem is the namespace of the nested elements of the getUserReturn. In wsdl they are defined to be in the http://ws.apache.org/axis1/xsd; namespace, but the reply has them in the http://server.ws.te0.com;. I traced the generated source code it is exactly where it is failing. Thanks LF SOAP reply: 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 getUserResponse xmlns=http://server.ws.te0.com; getUserReturn daysValid39 /daysValid lastUserUpdate20080211084047 /lastUserUpdate resumeDate1-01-01 /resumeDate suspendFlagN /suspendFlag userFirstNameMASTER /userFirstName userInitials/ userLastNameSECURITY /userLastName userNameMAS /userName vaxID12027 /vaxID /getUserReturn /getUserResponse /soapenv:Body /soapenv:Envelope WSDL: ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=https://www-nr.qa.thebank.com/services/EntitlementWebServices; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=https://www-nr.qa.thebank.com/services/EntitlementWebServices; xmlns:intf=https://www-nr.qa.thebank.com/services/EntitlementWebServices; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns1=http://ws.apache.org/axis1/xsd; xmlns:tns2=http://server.ws.te0.com; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; wsdl:types schema targetNamespace=http://ws.apache.org/axis1/xsd; xmlns=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified complexType name=User sequence element name=daysValid nillable=true type=xsd:string/ element name=lastUserUpdate nillable=true type=xsd:string/ element name=resumeDate nillable=true type=xsd:string/ element name=suspendFlag nillable=true type=xsd:string/ element name=userFirstName nillable=true type=xsd:string/ element name=userInitials nillable=true type=xsd:string/ element name=userLastName nillable=true type=xsd:string/ element name=userName nillable=true type=xsd:string/ element name=vaxID nillable=true type=xsd:string/ /sequence /complexType /schema schema targetNamespace=http://server.ws.te0.com; xmlns=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified element name=getUser complexType sequence element name=requestingKNumber type=xsd:string/ element name=requestingSubID type=xsd:string/ element name=requestingBankNumber type=xsd:string/ element name=transactionBankNumber type=xsd:string/ element name=transactionKNumber type=xsd:string/ element name=transactionSubID type=xsd:string/ /sequence /complexType /element element name=getUserResponse complexType sequence element name=getUserReturn type=tns1:User/ /sequence /complexType /element /schema /wsdl:types wsdl:message name=getUserResponse wsdl:part element=tns2:getUserResponse name=parameters/ /wsdl:message wsdl:message name=getUserRequest wsdl:part element=tns2:getUser name=parameters/ /wsdl:message wsdl:portType name=EntReadWebServices wsdl:operation name=getUser parameterOrder= wsdl:input message=impl:getUserRequest name=getUserRequest/ wsdl:output message=impl:getUserResponse name=getUserResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=EntitlementWebServicesSoapBinding type=impl:EntReadWebServices wsdlsoap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ wsdl:operation name=getUser wsdlsoap:operation soapAction=/ wsdl:input name=getUserRequest wsdlsoap:body use=literal/ /wsdl:input wsdl:output name=getUserResponse wsdlsoap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=EntReadWebServicesService wsdl:port binding=impl:EntitlementWebServicesSoapBinding name=EntitlementWebServices wsdlsoap:address
Re: WSDL import and schemaLocation
Yeah maybe I should try that. Want to know one more thing is there a specific reason why it is implemented that way. Coz in real life WSDL files and schema would be developed by some other parties which you would use it. If they implement schema location with the relative path there is a problem. One more thing if I set useOriginalWSDL parameter to false, the generated WSDL should have entire path to the schema file. I have not tried doing it. many thanks - Original Message - From: keith chapman [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, January 15, 2008 6:16 PM Subject: Re: WSDL import and schemaLocation If you need an absolute URI in there you can try saving the WSDL to your hard disk, Update it manually to have an absolute URI and then add it to the META-INF folder of your aar. Also add the parameter useOriginalWSDL=true to your services.xml. Thanks, Keith. On Jan 16, 2008 5:18 AM, prasad c iyer [EMAIL PROTECTED] wrote: I did used WSDL2Java tool. What I'm trying to do is consume the service using PHP. But when I query the WSDL file it returns me the following schema location. I don't think it takes care of this. regards - Original Message - From: Amila Suriarachchi To: axis-user@ws.apache.org Sent: Monday, January 14, 2008 8:04 PM Subject: Re: WSDL import and schemaLocation On Jan 15, 2008 9:08 AM, prasad c iyer [EMAIL PROTECTED] wrote: Hi, I am creating the client for an existing web service. My problem is the schemaLocation is points to the relative path. Is there a way to resolve this. So that my client can download the schema. Are you using wsdl2java with Axis2? it can handle the relative schemaLocations. I think any tool would do this. thanks, Amila. ?xml version=1.0 encoding=UTF-8? definitions name=BankServices targetNamespace=http://localhost:8080/my-app/services/BankServices xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:tns=http://localhost:8080/my-app/services/BankServices; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:bank=http://localhost:8080/my-app/services/BankServices/types; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; types xsd:schema xsd:import namespace=http://localhost:8080/my-app/services/BankServices/types; schemaLocation=BankServices?xsd=xsd0.xsd/ /xsd:schema /types regards -- Amila Suriarachchi, WSO2 Inc. -- Keith Chapman Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.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: WSDL import and schemaLocation
Hard coded values did the trick. But it is not good for me. I ran into other problem my xsd imports many other schema which uses the relative path. Even my WSDL file uses many schema. It is very error prone to edit the location. I might have to think something different. Any help would be highly appreciated. regards - Original Message - From: prasad c iyer [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, January 16, 2008 9:28 AM Subject: Re: WSDL import and schemaLocation Yeah maybe I should try that. Want to know one more thing is there a specific reason why it is implemented that way. Coz in real life WSDL files and schema would be developed by some other parties which you would use it. If they implement schema location with the relative path there is a problem. One more thing if I set useOriginalWSDL parameter to false, the generated WSDL should have entire path to the schema file. I have not tried doing it. many thanks - Original Message - From: keith chapman [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, January 15, 2008 6:16 PM Subject: Re: WSDL import and schemaLocation If you need an absolute URI in there you can try saving the WSDL to your hard disk, Update it manually to have an absolute URI and then add it to the META-INF folder of your aar. Also add the parameter useOriginalWSDL=true to your services.xml. Thanks, Keith. On Jan 16, 2008 5:18 AM, prasad c iyer [EMAIL PROTECTED] wrote: I did used WSDL2Java tool. What I'm trying to do is consume the service using PHP. But when I query the WSDL file it returns me the following schema location. I don't think it takes care of this. regards - Original Message - From: Amila Suriarachchi To: axis-user@ws.apache.org Sent: Monday, January 14, 2008 8:04 PM Subject: Re: WSDL import and schemaLocation On Jan 15, 2008 9:08 AM, prasad c iyer [EMAIL PROTECTED] wrote: Hi, I am creating the client for an existing web service. My problem is the schemaLocation is points to the relative path. Is there a way to resolve this. So that my client can download the schema. Are you using wsdl2java with Axis2? it can handle the relative schemaLocations. I think any tool would do this. thanks, Amila. ?xml version=1.0 encoding=UTF-8? definitions name=BankServices targetNamespace=http://localhost:8080/my-app/services/BankServices xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:tns=http://localhost:8080/my-app/services/BankServices; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:bank=http://localhost:8080/my-app/services/BankServices/types; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; types xsd:schema xsd:import namespace=http://localhost:8080/my-app/services/BankServices/types; schemaLocation=BankServices?xsd=xsd0.xsd/ /xsd:schema /types regards -- Amila Suriarachchi, WSO2 Inc. -- Keith Chapman Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL import and schemaLocation
I did used WSDL2Java tool. What I'm trying to do is consume the service using PHP. But when I query the WSDL file it returns me the following schema location. I don't think it takes care of this. regards - Original Message - From: Amila Suriarachchi To: axis-user@ws.apache.org Sent: Monday, January 14, 2008 8:04 PM Subject: Re: WSDL import and schemaLocation On Jan 15, 2008 9:08 AM, prasad c iyer [EMAIL PROTECTED] wrote: Hi, I am creating the client for an existing web service. My problem is the schemaLocation is points to the relative path. Is there a way to resolve this. So that my client can download the schema. Are you using wsdl2java with Axis2? it can handle the relative schemaLocations. I think any tool would do this. thanks, Amila. ?xml version=1.0 encoding=UTF-8? definitions name=BankServices targetNamespace=http://localhost:8080/my-app/services/BankServices xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:tns=http://localhost:8080/my-app/services/BankServices; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:bank=http://localhost:8080/my-app/services/BankServices/types; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; types xsd:schema xsd:import namespace=http://localhost:8080/my-app/services/BankServices/types; schemaLocation=BankServices?xsd=xsd0.xsd/ /xsd:schema /types regards -- Amila Suriarachchi, WSO2 Inc.
Re: WSDL import and schemaLocation
If you need an absolute URI in there you can try saving the WSDL to your hard disk, Update it manually to have an absolute URI and then add it to the META-INF folder of your aar. Also add the parameter useOriginalWSDL=true to your services.xml. Thanks, Keith. On Jan 16, 2008 5:18 AM, prasad c iyer [EMAIL PROTECTED] wrote: I did used WSDL2Java tool. What I'm trying to do is consume the service using PHP. But when I query the WSDL file it returns me the following schema location. I don't think it takes care of this. regards - Original Message - From: Amila Suriarachchi To: axis-user@ws.apache.org Sent: Monday, January 14, 2008 8:04 PM Subject: Re: WSDL import and schemaLocation On Jan 15, 2008 9:08 AM, prasad c iyer [EMAIL PROTECTED] wrote: Hi, I am creating the client for an existing web service. My problem is the schemaLocation is points to the relative path. Is there a way to resolve this. So that my client can download the schema. Are you using wsdl2java with Axis2? it can handle the relative schemaLocations. I think any tool would do this. thanks, Amila. ?xml version=1.0 encoding=UTF-8? definitions name=BankServices targetNamespace=http://localhost:8080/my-app/services/BankServices xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:tns=http://localhost:8080/my-app/services/BankServices; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:bank=http://localhost:8080/my-app/services/BankServices/types; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; types xsd:schema xsd:import namespace=http://localhost:8080/my-app/services/BankServices/types; schemaLocation=BankServices?xsd=xsd0.xsd/ /xsd:schema /types regards -- Amila Suriarachchi, WSO2 Inc. -- Keith Chapman Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL import and schemaLocation
On Jan 15, 2008 9:08 AM, prasad c iyer [EMAIL PROTECTED] wrote: Hi, I am creating the client for an existing web service. My problem is the schemaLocation is points to the relative path. Is there a way to resolve this. So that my client can download the schema. Are you using wsdl2java with Axis2? it can handle the relative schemaLocations. I think any tool would do this. thanks, Amila. ?xml version=1.0 encoding=UTF-8? definitions name=BankServices targetNamespace= http://localhost:8080/my-app/services/BankServices; xmlns= http://schemas.xmlsoap.org/wsdl/; xmlns:tns= http://localhost:8080/my-app/services/BankServices; xmlns:xsd= http://www.w3.org/2001/XMLSchema; xmlns:bank= http://localhost:8080/my-app/services/BankServices/types; xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; types xsd:schema xsd:import namespace= http://localhost:8080/my-app/services/BankServices/types; schemaLocation=BankServices?xsd=xsd0.xsd/ /xsd:schema /types regards -- Amila Suriarachchi, WSO2 Inc.
Re: WSDL XSD Schema Importing...
To answer your first question, yes it was a typo. I can also validate the wsdl and xsd's fine in eclipse, and when i set up the web service I can hit it and return a response using SOAPUI. Mauro Molinari wrote: silver17 ha scritto: http://localhost:8080/app/services'.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd xsd:import namespace=http://www.opengis.net/cat/csw/2.0.2; schemaLocation=RegistryPublish?xsd=csw-Publication.xsd/ http://www.nabble.com/file/p14722764/csw-Publication.xsd csw-Publication.xsd Is the first a copy 'n' paste problem or does Axis2 really says it can't find http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd? Because your file name seems to start with csw-, not cs-... Anyway, I can make Axis2 1.3 work with schema imports, except when trying to do some more complex things like sharing a schema between multiple services (please see https://issues.apache.org/jira/browse/AXIS2-3354). Does Eclipse give you any validation error on your WSDL and/or XSDs? (try right-click = Validate)? -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14734904.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]
Re: WSDL XSD Schema Importing...
As an addition to this discussion, if instead of trying to reference the http://localhost/app/services/RegistryPublish.wsdl i get the following error: http://www.nabble.com/file/p14736457/serviceError.jpg silver17 wrote: Hi Guys, I've searched a lot of these forum posts and haven't been able to find a resolution to my problem. Currently I am using Axis 2.1.3 and Eclipse Europa with the Apache Codegen wizard plugins. I created a WSDL that imports a couple of schemas and I'm having problems. When I attempt to use the wizards to generate the client stubs using a URL like: http://localhost:8080/app/services/RegistryPublish?wsdl I get the following error: An error occured while completing process - java.lang.InterruptedException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred while trying to resolve schema referenced at 'RegistryPublish?xsd=csw-Publication.xsd, relative to http://localhost:8080/app/services'.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd And I don't know why it's doing that. Here's a sample of that wsdl: wsdl:definitions name=RegistryPublish targetNamespace=http://services.registry.company.com/publish/; wsdl:documentation WSDL Description for the Registry Publishing Service. /wsdl:documentation wsdl:types xsd:schema xsd:import namespace=http://www.opengis.net/cat/csw/2.0.2; schemaLocation=RegistryPublish?xsd=csw-Publication.xsd/ xsd:import namespace=http://www.opengis.net/ows/1.1; schemaLocation=RegistryPublish?xsd=owsExceptionReport.xsd/ /xsd:schema /wsdl:types ... My web app directory structure is: app-web-inf-services-RegistryPublish-META-INF ... csw-Publication.xsd owsExceptionReport.xsd RegistryPublish.wsdl services.xml I tried using a program called SOAPUI to run a test request to that same url as above and it returned a successful result. Any thoughts? I've attached the files. http://www.nabble.com/file/p14722764/RegistryPublish.wsdl RegistryPublish.wsdl http://www.nabble.com/file/p14722764/services.xml services.xml http://www.nabble.com/file/p14722764/owsExceptionReport.xsd owsExceptionReport.xsd http://www.nabble.com/file/p14722764/csw-Publication.xsd csw-Publication.xsd -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14736457.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]
