Re: How forgiving should we be about jndi component context names?

David Jencks wrote: The spec seems to indicate fairly clearly that a components jndi context is located in java:comp/env or at least java:comp However I believe it is popular to misspell this java:/comp/env Do we want to support this naming abuse? Make it configurable maybe? Is there a strict vs

Re: How forgiving should we be about jndi component context names?

I would just say print the warning once and remember you have already printed it. -dain -- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26 On Nov 10, 2004, at 12:33 PM, David Jencks wrote: We can't detect this until runtime when the name is looked up. i think printing a w

Re: How forgiving should we be about jndi component context names?

David Jencks wrote: We can't detect this until runtime when the name is looked up. i think printing a warning continually every time someone does a lookup is overkill. So, I think we have to allow it silently or prohibit it. It would depend on where in the java: namespace the component's contex

Re: How forgiving should we be about jndi component context names?

We can't detect this until runtime when the name is looked up. i think printing a warning continually every time someone does a lookup is overkill. So, I think we have to allow it silently or prohibit it. david jencks On Nov 10, 2004, at 9:29 AM, Erin Mulder wrote: David Jencks wrote: I tend to

Re: How forgiving should we be about jndi component context names?

David Jencks wrote: I tend to agree with you, but not supporting it if most other app servers do causes the opposite problem, that non-compliant apps that run elsewhere won't run on geronimo. In particular xpetstore seems to make use of this non-compliant behavior. Good point. Why not take th

Re: How forgiving should we be about jndi component context names?

I tend to agree with you, but not supporting it if most other app servers do causes the opposite problem, that non-compliant apps that run elsewhere won't run on geronimo. In particular xpetstore seems to make use of this non-compliant behavior. thanks david jencks On Nov 10, 2004, at 8:41 AM,

Re: How forgiving should we be about jndi component context names?

David Jencks wrote: However I believe it is popular to misspell this java:/comp/env Do we want to support this naming abuse? It would be convenient, but might cause applications to fail when ported to other app servers. If the spec is clear on the correct usage, then I think it's better to just

How forgiving should we be about jndi component context names?

The spec seems to indicate fairly clearly that a components jndi context is located in java:comp/env or at least java:comp However I believe it is popular to misspell this java:/comp/env Do we want to support this naming abuse? thanks david jencks