Multiple AM in CPX file - anyone got this to work ?

Question

Hi,
It seems impossible to use multiple application modules from the same CPX file.
For convenience reasons, I have many AM definitions in my CPX - (which the CPX wizard allows perfectly).
I can create a first app module and it works perfectly.
But when I create a second App Module (of a different class) using this :
pool = JUMetaObjectManager.getJUMom() .createPool("myCPX.secondModule", poolProps);
// ... create pool session cookie with a unique session ID
sessioncookie = pool .createSessionCookie(sessionId, sessionId, null);
// .. then use the AM
am = sessioncookie.useApplicationModule();
The AM I get is always of the same class (the first AM I created).
When decompiling the JUMom code, it appears that to create my pool, it only uses the first half of my definition (myCPX) instead of using the full definition (myCPX.secondModule).
Is this a bug ? or is there another method to use CPX files containing multiple App Modules ?
Thanks
Brice

Answer 1

This has in fact nothing to do with the CPX file (surely, it was easy to blame it).
We finally tracked this down.
In fact the JUMetaObjectManager uses the Application Module configuration name to identify the AM pool.
If you have two application modules that both have a "TEST" configuration for instance, you will only ever instantiate the first module class.
Clearly, this seems wrong, the pool should be identified both with the full package name and the configuration name.
If this is not filed as a bug already, it would be good to see this fixed.
If this is a feature, then please why but why would anyone benefit from such an implementation ???
Regards
Brice