Are Hermes webservice definitions planned to be WS-I compliant?

[Martijn Morriën]

I'm using Hermes now, and I like the simplicity and the documentation.

I'm about to write Java webservice clients and I prefer to import the hermes wsdl's using wsimport. But unfortunately they are not WS-I compliant.

Using wsimport to generate a JAXWS java client fails e.g. on the EbmsMessageSenderService.wsdl because it expects an element not a type.
For example WS-I assertion BP2012 fails because when using document/literal message format, the <soap:part> should be referencing an element. Types are only valid for RPC message format (either RPC/encoded or RPC/literal).

The wsdl should contain something like:

<message name="EbmsRequestMsg">
  <part element="types:EbmsRequestMsg" name="parameters" />
</message>
<message name="EbmsResponseMsg">
  <part element="types:EbmsResponseMsg" name="parameters" />
</message>

instead of the current:

<message name="EbmsRequestMsg">
  <part name="cpaId" type="s:string" />
  <part name="service" type="s:string" />
  <part name="action" type="s:string" />
  <part name="convId" type="s:string" />
  <part name="fromPartyId" type="s:string" />
  <part name="fromPartyType" type="s:string" />
  <part name="toPartyId" type="s:string" />
  <part name="toPartyType" type="s:string" />
  <part name="refToMessageId" type="s:string" />
  <part name="serviceType" type="s:string" />
</message>
<message name="EbmsResponseMsg">
  <part name="message_id" type="s:string" />
</message>

Are there any future plans to make the webservice WS-I compliant?

Martijn

[Martijn Morriën]

I see this is a rather old issue:
http://groups.google.com/group/cecid-hermes2/browse_thread/thread/ce24ff9a5c605b4c/6f1134fac214d9ea?hl=en&lnk=gst&q=wsdl#6f1134fac214d9ea

I can write a client like described here:
http://community.cecid.hku.hk/index.php/product/article/writing_hermes_2_ws_client_under_java

But I do not prefer to work 'untyped'. So I'm still curious, do you plan to make the webservices WS-I compliant to make client development easier?

Martijn

2009/12/22 Martijn Morriën <dj.e...@gmail.com>

[David RR Webber (XML)]

Martijn,

Can't you just do this yourself?  Seems trivial to define the WSDL the way you want and an XSD message construct for it to reference that match the inline s:string constructs so that your WS-I tooling is happy.

Since everything is simple strings - should work mapping from the XML.

Thanks, DW

--

You received this message because you are subscribed to the Google Groups "Hermes 2.0 Discussion List" group.
To post to this group, send email to cecid-...@googlegroups.com.
To unsubscribe from this group, send email to cecid-hermes...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cecid-hermes2?hl=en.