Millies, Sebastian wrote:
From: scottk...@gmail.com [mailto:scottk...@gmail.com] On Behalf Of Scott Kurz
Sent: Sunday, November 20, 2011 5:30 AM
Sebastian,
And did you re-generate the Java via wsimport after making the change to the
WSDL?
The generated Java SEI interface should have an annotation like;
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
If I'm remembering this path correctly, it looks from the stack trace that you
may not have regenerated.
Scott
Hi Scott,
yes, I did. However, I deleted the JAX-WS annotations and added
@Remotable instead, because the second paragraph of this post by
Simon Nash said so:
http://www.mail-archive.com/user@tuscany.apache.org/msg03426.html
Actually the referenced post says that you can either use the
artifacts that are generated by JAX-WS, or you can delete the JAX-WS
annotations and create an SCA remotable interface instead. From this
discussion it appears that the latter approach works in most cases
but not in all cases.
I believe that it is also possible to use JAX-WS annotations in
addition to the @Remotable annotation, but I don't have detailed
knowledge of what combinations work when doing this.
Simon
I do need a service reference with an interface, so I thought
that was the way to go.
-- Sebastian
IDS Scheer Consulting GmbH
Geschäftsführer/Managing Directors: Kamyar Niroumand, Ivo Totev
Sitz/Registered office: Altenkesseler Straße 17, 66115 Saarbrücken, Germany -
Registergericht/Commercial register: Saarbrücken HRB 19681
http://www.softwareag.com
