WHAT? This seems a little to coarse to be taken lightly. I mean to say...
well exactly what I am saying. The current released versions of:
org.jboss.ejb.plugins.jrmp.interfaces.*HandleImpl
all do something like this:
----8<----
public EJBObject getEJBObject() {
...
... new InitialContext()...
...
}
---->8----
By not specifing any properties to the context, it assumes that the current
VM has properties set that will connect to the correct provider's url with
the correct initial context impl... which is poor assumption to be making.
It would be better/safer to save the beans provider url (and initial context
impl classname) in the created handle impl. This way, you could pass the
handle to any vm (with the correct classpath) and it would return an object
on the correct machine.
I don't know how to make this any clearer.
--jason
On Fri, 1 Dec 2000, marc fleury wrote:
> |
> |Hello, I noticed that the Handle implementations do not store any
> |information about the initial context to use, but rely on the target vm to
> |have java.naming.factory.initial & java.naming.provider.url set to the
> |correct value.
> |
> |I would recommend at least saving the java.naming.provider.url in the
> |handle, as the client should not assume which provider url the bean came
> |from.
>
> what are you trying to say?
>
> if you save the url, you save the url.
>
> marc
>
> |
> |--jason
> |
> |
> |
> |
> |
> |--
> |--------------------------------------------------------------
> |To subscribe: [EMAIL PROTECTED]
> |To unsubscribe: [EMAIL PROTECTED]
> |Problems?: [EMAIL PROTECTED]
> |
> |
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
