-
1. Re: Soap namespaces not able to resolve with Blueprint.xml
ranajitjana Sep 11, 2012 10:41 AM (in response to ranajitjana)I was extremely lucky to find the answer after whole day of struggle.
I looked into the console and found the following
osgi.service.blueprint.namespace http://cxf.apache.org/blueprint/bindings/soap
Using Bundles org.apache.aries.blueprint (10)
org.apache.cxf.bundle (177)
thus using namespace "http://cxf.apache.org/blueprint/bindings/soap" is able to close the issue.
-
2. Re: Soap namespaces not able to resolve with Blueprint.xml
njiang Sep 11, 2012 9:54 PM (in response to ranajitjana)Yeah, there are bunch of schemas for blueprint, you need to pick up right one if you want to use them with blueprint.
Willem
-
3. Re: Soap namespaces not able to resolve with Blueprint.xml
ranajitjana Sep 12, 2012 4:50 AM (in response to njiang)Thanks Willam ,
One more question. Is it possible to deploy both version(1.1 , 1.2) of soap service by annotation. or blueprint xml. I can do the same if i generate two wsdl using two jaxws:server tag. I want to publish only one wsdl. Manual wsdl is one way but is there a autogenerated wsdl to support both Soap version
-
4. Re: Soap namespaces not able to resolve with Blueprint.xml
ffang Sep 12, 2012 5:14 AM (in response to ranajitjana)Hi,
You needn't do it.
If you specify a cxf endpoint to support soap 1.2, then it can support soap 1.1 message out-of-the-box.
Freeman
-
5. Re: Soap namespaces not able to resolve with Blueprint.xml
ranajitjana Sep 12, 2012 8:33 AM (in response to ffang)Thank you. It worked very well for both version of SOAP. only that the tools look at the wsdl to create the mock request. but if manually built soap request for 1.1 works very well.
Regards,
Ranajit