Jeffrey Damick wrote:
-----Original Message-----
From: Dan Diephouse [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 27, 2006 11:30 PM
To: [email protected]
Subject: Re: [xfire-user] Adding Headers and setting the wsdl name?
Jeffrey Damick wrote:
Is there a way to specify required soap headers (i.e. one of ws-*
standards) for an operation(s) of a service that dynamically
generates
the WSDL from a spring pojo service using XMLBeans?
I don't think JSR 181 offers that. I think your only option is to futz
with the headers on the messsage yourself. Take a look at the
MessageContext and Handler stuff in the manual for some pointers on
how
to do that.
It would appear that section 6.2 of the spec. allows for specifying
headers: "Parameters annotated with the @WebParam.header attribute map
to SOAP headers"
So my question now is can I use the jsr 181 annotations for a service
interface with XMLBeans as the binding?
Yes, @WebParam.header works just fine, but there is no way to pass a
header that way and tell the soap stack to output the MustUnderstand
attribute.
Also,
Is there a way to set the name attribute for a dynamically generated
WSDL using a spring pojo service and XMLBeans?
i.e. <wsdl:definitions name="MyService" ....>
(other than doing something like overriding
XmlBeansWSDLBuilderFactory
and setting it there?)
Try setting the name property of the ServiceBean or the XFireExporter.
The name property only seems to set the service element's name
attribute, not the definitions element's attribute and I don't see a way
to do it in jsr 181.. :(
Ah yes, it does appear there is no way to set the name attribute on the
definitions right now. I don't know that there is even a way to set it
via WSDL4J. It shouldn't be required. If you're using Eclipse WTP and it
is telling you that it is, I think it is lying :-)
- Dan
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
