Peter Williams wrote:
>
>>
>> An alternative way to achieve this is to package such resources in a
>> separate jar and make the jar available in glassfish lib directory.
> True, but it breaks backwards compatibility and the customer would
> have to know they need to do this. These systems are supposed to
> "just work". Some failures may be hard to diagnose, especially since
> they will be unexpected (due to compatibility expectations). In other
> situations, it may not be clear there even is a failure -- just some
> weird and rare seemingly random problem.
I am not asking customers to create those library jars. Why can't we
install those jars in lib dir for things to work smoothly in v3?
Thanks,
Sahoo