Hi all,
Upon Kyle's advice, I've read the Infocenter part about module visibility (6.4) and I would like to have you opinion about this.
The
J2EE pateform does not allow to communicate between WARs due to the classloaders structure (AC).
But I can "bypass" this if put the classes to be shared in the application extension zone (AEX).
The each AC can "see" classes loaded by AEX, 'cause AEX is the parent.
My question is :
Is this really something we can recomend ?
1) As far as I am concerned, I thinks it is in opposition to the J2EE specification. The application packaging rules are not followed anymore
2) I'm not sure to fully understand the AEX zone, but I guess classes here are started once at the App Server start.
It means if I want to change a release, I got to stop all my Enterprise Servers... Yerk !!
Did I miss something.
Could you share your experience. Did you ever use this WAS feature ?
3) One more question.
The relationship between EAR and WAR is one-to-many.
If I can include many WAR in my EAR but I can't make these WAR communicate with each other, what is it used for ??