It may be possible to use a different ORB if you are just developing
CORBA applications in GlassFish, but if you want GlassFish EJB container
to use a different ORB, then I doubt that's possible. I will let the ORB
developers have a final word here.
Thanks,
Sahoo
n.b.: BTW, your question is more related to ORB than class loader and I
guess you did not get a response to your earlier email because your
subject did not draw attention of ORB developers. Please try to be more
precise in your subject to get faster response.
Donal Duane wrote:
>
> Hi all,
>
> I am looking for some help with the following query:
>
> Firstly, Glassfish V2 seems to have an internal omg/orb which is ancient.
> Can anyone tell me why this is, without having to go into the source
> code? What version is it?
>
> Aside from this, can anyone advise how to configure the glassfish
> application classloader to avoid this ORB and reference a newer
> external ORB, such as Visibroker 8?
>
> The classloader seems to have a major issue with nested dependencies.
>
> Any help appreciated.
>
>
> Regards,
> Dónal.
>
> << OLE Object: Picture (Metafile) >>
> /:* E-mail:* :_* donal.duane_at_ericsson.com *_/
> /CIF 3PP Integration Team Leader /
> ///*_http://atrclin2.athtem.eei.ericsson.se/wiki/index.php/CIF_3PP_*///
> /(* ECN* :* (830) 21767*/
> /(* Office* :* +353906431767*/
> /(* FAX* :* +353906431304*/
>
> LM Ericsson Limited
> Registered Office: Beech Hill, Clonskeagh, Dublin 4
> Registered Number in Ireland: 21679
>
>
> This communication is confidential and intended solely for the
> addressee(s). Any unauthorised review, use, disclosure or distribution
> is prohibited. If you believe this message has been sent to you in
> error, please notify the sender by replying to this transmission and
> delete the message without disclosing it. Thank you.
>
> LM Ericsson Limited does not enter into contracts or contractual
> obligations via electronic mail, unless otherwise agreed in writing
> between the parties concerned.
>
> E-mail including attachments is susceptible to data corruption,
> interruption, unauthorised amendment, tampering and viruses, and we
> only send and receive e-mails on the basis that we are not liable for
> any such corruption, interception, amendment, tampering or viruses or
> any consequences thereof.
>
>