Thanks Glen,
That helps, too.
Guy
PS I am a big fan of your blog, BTW
On 27-dec-2011, at 19:14, Glen Mazza wrote:
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 recompi
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,
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 imp
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.
> >
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
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)?
Thanks
Guy
