On Mon, Jun 13, 2011 at 11:35 AM, David Blevins wrote:
>
> On Jun 12, 2011, at 2:53 AM, Shawn Jiang wrote:
>
> > For leveraging openejb remote jndi system idea, I thought about it,
> to add "global/app xxx" "openejb/deployment/xxx" mapping in openejb so that
> when a jndi request comes, openej
On Jun 12, 2011, at 2:53 AM, Shawn Jiang wrote:
> For leveraging openejb remote jndi system idea, I thought about it, to
> add "global/app xxx" "openejb/deployment/xxx" mapping in openejb so that
> when a jndi request comes, openejb could return the requested object with
> following path
For leveraging openejb remote jndi system idea, I thought about it, to
add "global/app xxx" "openejb/deployment/xxx" mapping in openejb so that
when a jndi request comes, openejb could return the requested object with
following path
java:global/x name > "openejb/deployment/" na
I think we should use the openejb remote jndi system. We might need to modify
it. AFAIK the only things it makes sense to get to the app client are
environment entries and remote ejbs.
thanks
david jencks
On Jun 11, 2011, at 8:28 PM, Shawn Jiang wrote:
> Curretly, we only include the ea
Curretly, we only include the ear global and app context to application
client context. because applient is running in different VM other than
server itself. As a result, you can't use JNDI lookup to get the server
global/app reference in appclient.
Sure we want to add the global and app co
