Dan's technically on vacation this week, so perhaps I can answer:
Yes[1], although hardcoding the wsdlLocation makes it less maintainable
(can't change the value without recompiling) so keeping that value in
the cxf-servlet.xml or other XML configuration file[2] would be
preferable IMO.
HTH,
Glen
[1]
http://www.mulesoft.org/documentation/display/CXF/Building+a+web+service#Buildingawebservice-WSDLfirst
[2] http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep6
On 12/27/2011 12:41 PM, Guy Pardon wrote:
Dan,
One more thing: is wsdlLocation allowed on an SEI?
Guy
On 27-dec-2011, at 05:13, Daniel Kulp wrote:
On Monday, December 26, 2011 11:09:40 PM Daniel Kulp wrote:
On Monday, December 26, 2011 9:55:06 PM Guy Pardon wrote:
Hi all,
Last time I tried to do both an SEI class and an impl class, I was
turned
off by the combination of @WebService attributes on both/either of them.
Is there a clear summary of what should/can be present on both? What if
a
same value is present on both (like: wsdlLocation)?
The only one that I STRONGLY recommend sticking on both is the
targetNamespace. Per spec, that really has different meaning depending on
which it is on so putting it on both (and setting them the same) seems to
work the best.
Per JSR181, serviceName and endpointInterface is not allowed on the SEI.
I believe the others are pulled from the implementation except for portName
which is from the SEI if there is an SEI.
One more thing I forgot to mention.... One of the nice things about CXF is a
bunch of the things on the WebService annotation are overridable from the
config. The wsdlLocation, endpoint name, and servicename can be set there.
--
Glen Mazza
Talend Community Coders
http://coders.talend.com
blog: http://www.jroller.com/gmazza
