Hi!

> Right.  In fact, I would say that it's meaningless to give clients
> access to a special java: namespace since those name spaces are only
> meaningful (as far as I know) from the perspective of an enterprise bean
> or servlet.

Incorrect. It is actually possible to make this work for app clients too.
See the latest J2EE spec for details.

> However, if I'm writing an application client, and I deploy a bean with
> an external JNDI name with java:, I don't think the server-provided
> context that holds that name should interpret it any differently than
> foo/bar.

As Chris said, this is not possible since JNDI gets hold of that name before
it is handed to our JNDI implementation, and since it looks like a
"protocol:" URL it will treat it as one. Sorry, no go.

> No, I realize that you are always using JNDI to lookup beans.  I also
> understand that the java: name space (or java:comp/env) has a special
> meaning when inside a J2EE container.

Correct.

> However, that namespace is different for each enterprise bean or each
> web container.  I'm not expecting any of those things to be available to
> application clients.

To be precise it's the "java:comp/env" namespace that is bean specific (yes,
the current impl we have is buggy since it makes the entire java: namespace
bean specific. I.e. there could be a binding "java:comp/logger" that is the
same for all beans. I will look into this later on).

> However, when I deploy a bean, I thought that I could give it any name I
> liked.  In this case, it was java:comp/env/ejb/<name>.  In this way, I
> can call things the same no matter what code I'm writing.

Yes, that would be nice but unfortunately it doesn't currently work because
of above reason.

> I'll see if I can change my clients.  It may not be a big deal.  I'm
> just trying to understand this more full.

I hope things are clear now.

Again, later on *we will support* java: in application clients too (since it
is mandated by latest spec!)

/Rickard




--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to