Hi,

Is it possible with Orion for servlets (and EJBs) to call EJBs when they are
assembled in different applications deployed across different servers?   If
so, how?  Calling EJBs across applications is useful as we use EJBs to
implement common business processes that are to be shared and used across
multiple applications dispersed across our enterprise. 

It used to be possible before J2EE as one could instantiate an
InitialContext specifying the factory and url (obtained dynamically through
a configuration mechanism) - now with J2EE one must not specify any
arguments when instantiating the InitialContext thereby delegating this
mapping to the application server.

Thanks, Jeff

-----Original Message-----
From: Karl Avedal [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 10, 2000 3:14 AM
To: Orion-Interest
Cc: Orion-Interest
Subject: Re: Problems with JNDI context


Hello Klaus,

If you could post the relevant parts of your configuration files I think it
will
help alot.

A common problem when not finding EJBs from JSPs is that they're not in the
same
application, but as I understand it, it's all in one application already?

Well, if you give me the configuration files relevant to your application, I
think we can solve it. If you don't want to post them to this forum you can
mail
them to me.

Regards,
Karl Avedal

[EMAIL PROTECTED] wrote:

> We have some strange results when trying to sew our application together.
>
> Calling our EJBs from JSP pages worked fine for the EJB dev team, but when
> merging the different modules together to make one application after
> initial development of base modules didnt work to fine.
>
> We merged a Webapplication and an ejb application to one, and synchronized
> the configuration.
>
> But now it seems when browsing the JNDI context within JSP there is no
beans
> deployed, but when using a java client we get access to the beans, and can
> browse the JNDI context ????
>
> Anyone have any ideas??
>
> /Klaus

Reply via email to