glassfish_at_javadesktop.org wrote:
> Yeah, I've assumed that much... I really find it pants, that I would have to rename all my beans just because they use the same global name...
>
> To me it seems logical that if you have an EAR, the name should be bound to that:
>
> java:comp/env/ear/bean
>
> Or even better, wouldn't it be more logical to name it thus:
>
> java:comp/env/ear/ejb/bean
>
> Failing that it would have been nice to have some sort of context isolation in Glassfish, by host, port, etc...
>
> I've now had to rethink the use of an EJB module for the backend because it's now not portable enough for me...
> [Message sent by forum member 'the_thunderbird' (the_thunderbird)]
>
Hi,
Perhaps you may consider installing the different application instances
under
separate Glassfish instances. That way you avoid the naming conflicts and
not have to recode.
--
Regards
Gabe Wong
NGASI AppServer Manager
JAVA AUTOMATION and SaaS Enablement
http://www.ngasi.com
NEW! 8.0 - Centrally manage multiple physical servers