On Tue, 02 Dec 2008 15:07:31 +0100, Ales Justin <ales.justin(a)gmail.com>
wrote:
It depends if you need any other metadata file from that META-INF
directory.
If no, then simply exclude that META-INF as metadata path.
If yes, I currently cannot see how we can handle that,
unless you remove certain deployer.
How do others handle this?
As this is contradiction, since you expect for all other things to work
out-of-the-box,
but not this one + you're not willing to change core configuration.
Beats me. :-)
AS 4.x did not do this, so it was never an issue before - hence looking
for ways
to have those apps still be able to deploy without a lot of changes.
We are not saying the default is bad, just that we would like to control
it for
issues listed.
/max
Max Rydahl Andersen wrote:
> Could you give me an example on how to use jboss-structure.xml to have
> it not pick-up META-INF/persistence.xml even if it is there
> (i.e. to allow a thirdparty library pick it up) ?
> /max
>
>>> We should fix AS 5 to have something that can allow it to be disabled
>>> (preferably
>>> without having to change AS 5 structure deployers as Ales suggest)
>>
>> See my #4 --> jboss-structure.xml.
>> Changing structure deployers was more severe option. ;-)
>>
>> jboss-structure.xml is non invasive,
>> it will work on JBossAS, but won't interfere with other environments.
>>
>> Or what more do you want? :-)
>
--
/max