On 02/15/2011 04:39 PM, Jason T. Greene wrote:
On 2/15/11 9:36 AM, Alessio Soldano wrote:
> On 02/15/2011 04:22 PM, David M. Lloyd wrote:
>>> Objections / comments ?
>> I object. This is incorrect.
>>
>> These modules are NOT intended to be a magic repository for appending
>> things on to user deployments! These modules are internal
>> implementation modules, which nobody should expect to ever appear on a
>> user class path.
>>
>> If you want to add these additional dependencies to EJB and Servlet
>> deployments then modify the EJB and Servlet deployers to add these
>> dependencies individually.
> Right, just to clarify, I think this is basically what's been said with
> Carlo and Emanuel later on; is that fine?
> IOW the real question here is, are we all OK with having the WS libs in
> the runtime classpath of every ejb/servlet deployments? (as a
> consequence of the need for supporting the usecases mentioned in
> Richard's email)
> Cheers
Isn't this just a matter of looking to see if there is a @WebServiceRef
in the annotaiton index?
No, people can also do a simple lookup. So I think the idea from Emanuel
of having a webservice deployer attach the proper dependencies would be
best.
The same EJB would have to do to web deployments then.
Carlo