On 10 Apr 2010, at 00:13, Stuart Douglas wrote:
I have rolled back the changes, however I am not sure if it is
possible to do this as a decorator. From the spec section on how decorators are bound to
beans:
8.3. A decorator is bound to a bean if: .... The decorator is enabled in the bean archive
containing the bean
I read this as meaning that I would need to add the Decorator to the beans.xml of
weld-extensions to bind the decorator to ResourceLoaderImpl, which would mean a dependency
on seam-servlet from weld-extensions, which is not ok.
No, it means you need to enable the decorator in *your* module. Not in the beans.xml of
weld-extensions.
If this is the case what about removing the private constructor of ResourceLoaderImpl
and specialising it in seam-servlet?
Specialization was removed from the spec, otherwise this would be ideal :-)
We haven't implemented specialization as a portable extension have we?!