Ah - interesting... I did try to find a JAX-WS @Notification
annotation but to no avail.
The wsdl2java tools blow up as well if there isn't an operation input.
I understand why now :-)
Ok...
It might be nice to support notification and solicit response. I guess
this is on the JAX-WS roadmap.
Thanks,
Andrew
On 23 Sep 2009, at 16:52, Daniel Kulp wrote:
Not a bug, this mapping is correct. JAX-WS doesn't support
notification
style stuff. All methods are either request/response or one-way.
If this is needed, we'd need to create new non-standard annotations
and such
to mark this. (doable pretty easily on 2.3/trunk, not as easy on 2.2)
Dan
On Wed September 23 2009 7:54:51 am Andrew Harrison wrote:
Hi,
If I have a SEI with a method that returns a value, but takes in no
parameters, i.e. a notification style message, the WSDL generated
still contains an input message.
I have something like:
@WebMethod(operationName = "Event")
@WebResult(name = "Text")
public String event();
Which produces:
<wsdl:message name="EventResponse">
<wsdl:part element="tns:Text" name="Text"></wsdl:part>
</wsdl:message>
<wsdl:message name="Event"></wsdl:message>
<wsdl:operation name="Event">
<wsdl:input message="tns:Event" name="Event"></wsdl:input>
<wsdl:output message="tns:EventResponse" name="EventResponse"></
wsdl:output>
</wsdl:operation>
If this is considered a bug, I can create a JIRA issue with a patch.
cheers,
Andrew
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
