Hi Scott
> This is not going to work as many users already have stated they
> create deployment units that contain all app server DDs and even
> proprietary descriptors for their own use.
I don't think it would cause problems because I don't check if there
are "foe" DDs but if the archives misses necessary JBoss specific
DDs. That is how I think the test would work:
JAR archvies:
- check if "jboss.xml" is there if not then it is treated as "foe"
WAR archives:
- check if "jboss-web.xml" is there
- if not then check if another "foe" deployment descriptor is available
(I know this is weak and we have to go over it if this and check if
for the supported "foe"s this is true or if they can contain data
which
would not required a "jboss-web.xml" file). If FOUND then treat is
as "foe"
EAR archives: I don't know if there are vendor specific DDs but I guess
we don't need currently to make a mapping because we don't have a
JBoss specific DD for EARs.
Andy
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
