I'm afraid this illustrates why renaming "configuration" to "module"
is not such a wonderful idea, since it conflicts with the usage of
"module" as "sub-application inside an ear". ConfigurationData
only knows about what we used to call "configurations", not j2ee
modules.
thanks
david jencks
On Apr 29, 2006, at 8:40 PM, Dain Sundstrom wrote:
That is the way it works. I'm not sure if there is anything we can
do about this now, or if it is something we want to do something
about. I don't really care either way.
-dain
On Apr 29, 2006, at 8:33 PM, Aaron Mulder wrote:
So I deployed an EAR with an EJB JAR and a WAR, but the
ConfigurationData appears to include only the WAR in its list of
child
modules. Is that expected? I would still expect to see the EJB JAR
listed as a child module even though it doesn't have it's own class
loader, etc.
Thanks,
Aaron
