Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Clemens Utschig - Utschig wrote: simon - the testcase is quite large - especially the server side to it - as it contains oracle SDO / adfbc libs .. if you tell me where to go debugging, I am happy to help.. Sorry that my request was not clear. Please can you post the client side only, including the Java code, .wsdl file and .composite file that you are using. I would like to see the exact files you are using as this often gives the vital clue that doesn't come out when talking about things. I'm not expecting to run your code as is but I might adapt it so it can run with a mocked up server side that I would create. Simon /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Saturday, February 16, 2008 7:13 AM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: I got the dynamic wsdl import to work, thx guys - however, the wrong namespace is still sent out to the webservice and hence causes the error reported. Please can you open a JIRA and attach a complete test case including the Java code, .wsdl file and .composite file that you are using. This will allow me to recreate and debug the problem. Simon /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 12:58 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace [EMAIL PROTECTED] wrote: Jean-sebastien, Qualified = target namespace?or wsdl name? Say my wsdl is named aaa.wsdl do I reference it by http://aaa ? Sorry for the slow response. I have been out sick for the last few days. The following definitely works. Other things might work as well, but I haven't tried them. The filename can be anything.wsdl as Sebastien says. (The anything part isn't used by Tuscany.) When you reference the WSDL in your .composite using interface.wsdl interface=mynamespace#wsdl.interface(myporttype) / you need to replace mynamespace and myporttype in the above line to correspond with the actual QName of the portType as defined in your .wsdl file. Simon Thx clemens -Original Message- From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: 2/11/08 6:33 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. - 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: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
attache the testcase with interface.wsdl to my original jira (TUSCANY-2033) it contains all the src + a couple libs to be able to compile it, and fixed versions of my other jiras. thx -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 5:39 AM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: simon - the testcase is quite large - especially the server side to it - as it contains oracle SDO / adfbc libs .. if you tell me where to go debugging, I am happy to help.. Sorry that my request was not clear. Please can you post the client side only, including the Java code, .wsdl file and .composite file that you are using. I would like to see the exact files you are using as this often gives the vital clue that doesn't come out when talking about things. I'm not expecting to run your code as is but I might adapt it so it can run with a mocked up server side that I would create. Simon /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Saturday, February 16, 2008 7:13 AM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: I got the dynamic wsdl import to work, thx guys - however, the wrong namespace is still sent out to the webservice and hence causes the error reported. Please can you open a JIRA and attach a complete test case including the Java code, .wsdl file and .composite file that you are using. This will allow me to recreate and debug the problem. Simon /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 12:58 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace [EMAIL PROTECTED] wrote: Jean-sebastien, Qualified = target namespace?or wsdl name? Say my wsdl is named aaa.wsdl do I reference it by http://aaa ? Sorry for the slow response. I have been out sick for the last few days. The following definitely works. Other things might work as well, but I haven't tried them. The filename can be anything.wsdl as Sebastien says. (The anything part isn't used by Tuscany.) When you reference the WSDL in your .composite using interface.wsdl interface=mynamespace#wsdl.interface(myporttype) / you need to replace mynamespace and myporttype in the above line to correspond with the actual QName of the portType as defined in your .wsdl file. Simon Thx clemens -Original Message- From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: 2/11/08 6:33 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. - 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: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Clemens Utschig - Utschig wrote: I got the dynamic wsdl import to work, thx guys - however, the wrong namespace is still sent out to the webservice and hence causes the error reported. Please can you open a JIRA and attach a complete test case including the Java code, .wsdl file and .composite file that you are using. This will allow me to recreate and debug the problem. Simon /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 12:58 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace [EMAIL PROTECTED] wrote: Jean-sebastien, Qualified = target namespace?or wsdl name? Say my wsdl is named aaa.wsdl do I reference it by http://aaa ? Sorry for the slow response. I have been out sick for the last few days. The following definitely works. Other things might work as well, but I haven't tried them. The filename can be anything.wsdl as Sebastien says. (The anything part isn't used by Tuscany.) When you reference the WSDL in your .composite using interface.wsdl interface=mynamespace#wsdl.interface(myporttype) / you need to replace mynamespace and myporttype in the above line to correspond with the actual QName of the portType as defined in your .wsdl file. Simon Thx clemens -Original Message- From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: 2/11/08 6:33 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
simon - the testcase is quite large - especially the server side to it - as it contains oracle SDO / adfbc libs .. if you tell me where to go debugging, I am happy to help.. /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Saturday, February 16, 2008 7:13 AM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: I got the dynamic wsdl import to work, thx guys - however, the wrong namespace is still sent out to the webservice and hence causes the error reported. Please can you open a JIRA and attach a complete test case including the Java code, .wsdl file and .composite file that you are using. This will allow me to recreate and debug the problem. Simon /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 12:58 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace [EMAIL PROTECTED] wrote: Jean-sebastien, Qualified = target namespace?or wsdl name? Say my wsdl is named aaa.wsdl do I reference it by http://aaa ? Sorry for the slow response. I have been out sick for the last few days. The following definitely works. Other things might work as well, but I haven't tried them. The filename can be anything.wsdl as Sebastien says. (The anything part isn't used by Tuscany.) When you reference the WSDL in your .composite using interface.wsdl interface=mynamespace#wsdl.interface(myporttype) / you need to replace mynamespace and myporttype in the above line to correspond with the actual QName of the portType as defined in your .wsdl file. Simon Thx clemens -Original Message- From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: 2/11/08 6:33 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. - 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: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
[EMAIL PROTECTED] wrote: Jean-sebastien, Qualified = target namespace?or wsdl name? Say my wsdl is named aaa.wsdl do I reference it by http://aaa ? Sorry for the slow response. I have been out sick for the last few days. The following definitely works. Other things might work as well, but I haven't tried them. The filename can be anything.wsdl as Sebastien says. (The anything part isn't used by Tuscany.) When you reference the WSDL in your .composite using interface.wsdl interface=mynamespace#wsdl.interface(myporttype) / you need to replace mynamespace and myporttype in the above line to correspond with the actual QName of the portType as defined in your .wsdl file. Simon Thx clemens -Original Message- From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: 2/11/08 6:33 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
I got the dynamic wsdl import to work, thx guys - however, the wrong namespace is still sent out to the webservice and hence causes the error reported. /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 12:58 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace [EMAIL PROTECTED] wrote: Jean-sebastien, Qualified = target namespace?or wsdl name? Say my wsdl is named aaa.wsdl do I reference it by http://aaa ? Sorry for the slow response. I have been out sick for the last few days. The following definitely works. Other things might work as well, but I haven't tried them. The filename can be anything.wsdl as Sebastien says. (The anything part isn't used by Tuscany.) When you reference the WSDL in your .composite using interface.wsdl interface=mynamespace#wsdl.interface(myporttype) / you need to replace mynamespace and myporttype in the above line to correspond with the actual QName of the portType as defined in your .wsdl file. Simon Thx clemens -Original Message- From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: 2/11/08 6:33 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. - 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: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Clemens Utschig - Utschig wrote: would it help to have a interface.wsdl? that contains the whole thing - rather than generating it from the annonated java interface? -- if so, any example for that? Yes, it would help. It might not solve all the problems, but it should get you further. I couldn't find a sample that uses interface.wsdl on a reference (seems like an omission), though there are a few that use it on a service definition. You would need to replace the interface.java element with something like interface.wsdl interface=http://model/common/serviceinterface#wsdl.interface(EmpFlexFieldService) / The generated wsdl file needs to be somewhere on your classpath. In our samples and tests that use generated wsdl, we put the wsdl files in the src/main/resources/wsdl directory. Simon cherrs clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Sunday, February 10, 2008 12:42 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Jean-Sebastien Delfino wrote: Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. I don't think the code in the interface-java-jaxws module is enough to solve this problem. We also need the ability to generate a WSDL interface at runtime from a Java interface containing JAX-WS annotations. (Our current code for this uses Axis2, which doesn't understand JAX-WS annotations.) The code we need would do the same as the JAX-WS tool wsgen -wsdl, or the CXF tool java2wsdl, except that the processing would be done at runtime and would generate WSDL to a stream instead of a file. From a quick look at both these options, it looks like it would be possible for the Tuscany runtime to call into code from either CXF or the JAX-WS tools to do the generation. However, this wouldn't be using any official APIs but would require a bit of copying and adapting the code that is currently there. Of the two options, the CXF code seems rather easier to work with. Also, since CXF is an Apache project, Tuscany could contribute back to
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Also how is the mapping from ns to wsdl done w/o an include? /clemens (powered by ocs mobile) clemens utschig - utschig soa product management -Original Message- From: Clemens Utschig - Utschig [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org tuscany-dev@ws.apache.org Sent: 2/11/08 7:30 AM Subject: RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 5:54 AM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: would it help to have a interface.wsdl? that contains the whole thing - rather than generating it from the annonated java interface? -- if so, any example for that? Yes, it would help. It might not solve all the problems, but it should get you further. I couldn't find a sample that uses interface.wsdl on a reference (seems like an omission), though there are a few that use it on a service definition. You would need to replace the interface.java element with something like interface.wsdl interface=http://model/common/serviceinterface#wsdl.interface(EmpFlexFieldService) / The generated wsdl file needs to be somewhere on your classpath. In our samples and tests that use generated wsdl, we put the wsdl files in the src/main/resources/wsdl directory. Simon cherrs clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Sunday, February 10, 2008 12:42 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Jean-Sebastien Delfino wrote: Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. I don't think the code in the interface-java-jaxws module is enough to
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 5:54 AM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: would it help to have a interface.wsdl? that contains the whole thing - rather than generating it from the annonated java interface? -- if so, any example for that? Yes, it would help. It might not solve all the problems, but it should get you further. I couldn't find a sample that uses interface.wsdl on a reference (seems like an omission), though there are a few that use it on a service definition. You would need to replace the interface.java element with something like interface.wsdl interface=http://model/common/serviceinterface#wsdl.interface(EmpFlexFieldService) / The generated wsdl file needs to be somewhere on your classpath. In our samples and tests that use generated wsdl, we put the wsdl files in the src/main/resources/wsdl directory. Simon cherrs clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Sunday, February 10, 2008 12:42 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Jean-Sebastien Delfino wrote: Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. I don't think the code in the interface-java-jaxws module is enough to solve this problem. We also need the ability to generate a WSDL interface at runtime from a Java interface containing JAX-WS annotations. (Our current code for this uses Axis2, which doesn't understand JAX-WS annotations.) The code we need would do the same as the JAX-WS tool wsgen -wsdl, or the CXF tool java2wsdl, except that the processing would be done at runtime and would generate WSDL to a stream instead of a file. From a quick look at both
Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Jean-sebastien, Qualified = target namespace?or wsdl name? Say my wsdl is named aaa.wsdl do I reference it by http://aaa ? Thx clemens -Original Message- From: Jean-Sebastien Delfino [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: 2/11/08 6:33 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: shouldn't an include do it, so that I could potentially store the wsdl anywhere .. I'll try that later today - thx for the advise.. You don't even need an include, just place the WSDL file anywhere inside your SCA contribution (JAR or folder), reference its qualified name from your .composite and we should find it. -- Jean-Sebastien - 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: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Jean-Sebastien Delfino wrote: Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. I don't think the code in the interface-java-jaxws module is enough to solve this problem. We also need the ability to generate a WSDL interface at runtime from a Java interface containing JAX-WS annotations. (Our current code for this uses Axis2, which doesn't understand JAX-WS annotations.) The code we need would do the same as the JAX-WS tool wsgen -wsdl, or the CXF tool java2wsdl, except that the processing would be done at runtime and would generate WSDL to a stream instead of a file. From a quick look at both these options, it looks like it would be possible for the Tuscany runtime to call into code from either CXF or the JAX-WS tools to do the generation. However, this wouldn't be using any official APIs but would require a bit of copying and adapting the code that is currently there. Of the two options, the CXF code seems rather easier to work with. Also, since CXF is an Apache project, Tuscany could contribute back to CXF any modifications we make to enable this. Before I launch into actually trying to get this working, does anyone else have comments or suggestions on the general approach? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
would it help to have a interface.wsdl? that contains the whole thing - rather than generating it from the annonated java interface? -- if so, any example for that? cherrs clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Sunday, February 10, 2008 12:42 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Jean-Sebastien Delfino wrote: Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. I don't think the code in the interface-java-jaxws module is enough to solve this problem. We also need the ability to generate a WSDL interface at runtime from a Java interface containing JAX-WS annotations. (Our current code for this uses Axis2, which doesn't understand JAX-WS annotations.) The code we need would do the same as the JAX-WS tool wsgen -wsdl, or the CXF tool java2wsdl, except that the processing would be done at runtime and would generate WSDL to a stream instead of a file. From a quick look at both these options, it looks like it would be possible for the Tuscany runtime to call into code from either CXF or the JAX-WS tools to do the generation. However, this wouldn't be using any official APIs but would require a bit of copying and adapting the code that is currently there. Of the two options, the CXF code seems rather easier to work with. Also, since CXF is an Apache project, Tuscany could contribute back to CXF any modifications we make to enable this. Before I launch into actually trying to get this working, does anyone else have comments or suggestions on the general approach? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Hi, I think we have two issues here: 1) Generate the WSDL port type from a java interface following the JAX-WS mapping rules (JSR-181 annotations can be used to customize the WSDL). The SCA spec chooses JAX-WS to map between remotable java interfaces and WSDLs. I assume Simon's proposal is for this step. 2) Generate or map the XML Schema for the java parameter types, return type and exception types. The data can be represented by different databindings such as JAXB, SDO or XMLBeans. Some of them have metadata for the XML elements/types such as JAXB annotations and SDO Type/Property. We need to make sure the generated XSDs are consistent with these information. The Java2XSD should be pluggable based on the databindings. Thanks, Raymond - Original Message - From: Simon Nash [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Sunday, February 10, 2008 12:42 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Jean-Sebastien Delfino wrote: Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. I don't think the code in the interface-java-jaxws module is enough to solve this problem. We also need the ability to generate a WSDL interface at runtime from a Java interface containing JAX-WS annotations. (Our current code for this uses Axis2, which doesn't understand JAX-WS annotations.) The code we need would do the same as the JAX-WS tool wsgen -wsdl, or the CXF tool java2wsdl, except that the processing would be done at runtime and would generate WSDL to a stream instead of a file. From a quick look at both these options, it looks like it would be possible for the Tuscany runtime to call into code from either CXF or the JAX-WS tools to do the generation. However, this wouldn't be using any official APIs but would require a bit of copying and adapting the code that is currently there. Of the two options, the CXF code seems rather easier to work with. Also, since CXF is an Apache project, Tuscany could contribute back to CXF any modifications we make to enable this. Before I launch into actually trying to get this working, does anyone else have comments or suggestions on the general approach? Simon - To
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
given that I have a full testcase on my box with SDO generated through oracle adf bc, I guess I am happy to play guinea pig .. /clemens -Original Message- From: Raymond Feng [mailto:[EMAIL PROTECTED] Sent: Sunday, February 10, 2008 9:56 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Hi, I think we have two issues here: 1) Generate the WSDL port type from a java interface following the JAX-WS mapping rules (JSR-181 annotations can be used to customize the WSDL). The SCA spec chooses JAX-WS to map between remotable java interfaces and WSDLs. I assume Simon's proposal is for this step. 2) Generate or map the XML Schema for the java parameter types, return type and exception types. The data can be represented by different databindings such as JAXB, SDO or XMLBeans. Some of them have metadata for the XML elements/types such as JAXB annotations and SDO Type/Property. We need to make sure the generated XSDs are consistent with these information. The Java2XSD should be pluggable based on the databindings. Thanks, Raymond - Original Message - From: Simon Nash [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Sunday, February 10, 2008 12:42 PM Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Jean-Sebastien Delfino wrote: Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. I don't think the code in the interface-java-jaxws module is enough to solve this problem. We also need the ability to generate a WSDL interface at runtime from a Java interface containing JAX-WS annotations. (Our current code for this uses Axis2, which doesn't understand JAX-WS annotations.) The code we need would do the same as the JAX-WS tool wsgen -wsdl, or the CXF tool java2wsdl, except that the processing would be done at runtime and would generate WSDL to a stream instead of a file. From a quick look at both these options, it looks like it would be possible for the Tuscany runtime to call into code from either CXF or the JAX-WS tools to do the generation. However, this wouldn't be using any official APIs but would
Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens At the moment Tuscany is ignoring JAX-WS annotations in interface.java interfaces. It should process these annotations. Can you open a JIRA and attach your test case so that we can track the problem? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
thx jean - this is key for SDO via SOAP interop (the complex case) - hence I guess also pretty interesting .. -- have you seen the other email today, with the bug in the Java2WSDL resolver and the NPE? /clemens -Original Message- From: Jean-Sebastien Delfino [mailto:[EMAIL PROTECTED] Sent: Friday, February 08, 2008 4:10 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
simon, sure - do I have credentials / rights to open a jira?/ -- also what about the NPE I reported in the morning, one for that too? /clemens -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Friday, February 08, 2008 4:14 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens At the moment Tuscany is ignoring JAX-WS annotations in interface.java interfaces. It should process these annotations. Can you open a JIRA and attach your test case so that we can track the problem? Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace
https://issues.apache.org/jira/browse/TUSCANY-2033 and https://issues.apache.org/jira/browse/TUSCANY-2034 latter one contains the patch /clemens -Original Message- From: Clemens Utschig - Utschig [mailto:[EMAIL PROTECTED] Sent: Friday, February 08, 2008 4:14 PM To: tuscany-dev@ws.apache.org Subject: RE: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace thx jean - this is key for SDO via SOAP interop (the complex case) - hence I guess also pretty interesting .. -- have you seen the other email today, with the bug in the Java2WSDL resolver and the NPE? /clemens -Original Message- From: Jean-Sebastien Delfino [mailto:[EMAIL PROTECTED] Sent: Friday, February 08, 2008 4:10 PM To: tuscany-dev@ws.apache.org Subject: Re: Tuscany: Axis2 codegen bug? - java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is not honoring the namespace Clemens Utschig - Utschig wrote: Folks, I have a simple composite as below - which makes use of SDO through SOAP in the reference ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=/model/common/ xmlns:dbsdo=http://tuscany.apache.org/xmlns/sca/databinding/sdo/1.0; name=FlexEmployeeComposite xmlns:tns=/model/common/types/ xmlns:types=/model/common/types/ xmlns:errors=http://xmlns.oracle.com/adf/svc/errors/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; component name=FlexEmployeeServiceComponent implementation.java class=com.oracle.soa.test.tuscany.impl.EmployeeServiceComponent/ reference name=empFlexFieldService/ /component reference name=empFlexFieldService promote=FlexEmployeeServiceComponent/empFlexFieldService interface.java interface=model.common.serviceinterface.EmpFlexFieldService/ binding.ws uri=http://localhost:1234/Application4710-Model-context-root/EmpFlexFieldService/ /reference /composite that promotes the java interface from the reference as service .. the interface is annotated as webservice - as below .. @javax.jws.WebMethod(action=/model/common/createEmployees1, operationName=createEmployees1) @javax.xml.ws.RequestWrapper(targetNamespace=/model/common/types/, localName=createEmployees1) @javax.xml.ws.ResponseWrapper(targetNamespace=/model/common/types/, localName=createEmployees1Response) @javax.jws.WebResult(name=result) DataObject createEmployees1(@javax.jws.WebParam(mode=javax.jws.WebParam.Mode.IN, name=employees1) DataObject employees1) throws ServiceException; which implies that the namespace for this element is /model/common/types/ however - Axis2, takes the targetNamespace - and hence tries to send out ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body _ns_:getEmployees1 xmlns:_ns_=/model/common/ empno xmlns=/model/common/1/empno /_ns_:getEmployees1 /soapenv:Body /soapenv:Envelope instead of soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body xmlns:ns1=/model/common/types/ ns1:getEmployees1 ns1:empno/ns1:empno /ns1:getEmployees1 /soap:Body /soap:Envelope anybody seen this? - this sounds like a real bug to me.. thx clemens I'm not sure that the support for jaxws annotations is ready and integrated in the build yet, although it may be pretty close. Raymond, it looks like you've been working on the interface-java-jaxws module recently, can you give us its status? Thanks. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
