Agreed, the environment context should be regarded as read-only. This is a bug that needs correction. Could you file a JIRA issue?
I'm trying to figure out an alternative. Do you know if WebLogic supports binding to the initial and/or java: naming contexts?
Sure, I'll post the Jira issue. I just tested - initial context is bindable for WebLogic and java: is not.
By the way. Is it an issue that JBoss allows binding in the java:comp/env context?
"j2ee-1_4-fr-spec,page 99" wrote:
The JNDI java: namespace is commonly implemented as symbolic links to
other naming systems. Different underlying naming services may be used to store different kinds of objects, or even different instances of objects. It is up to a J2EE product to provide the necessary JNDI service providers for accessing the various objects defined in this specification.
This specification requires that the J2EE platform provide the ability to
perform lookup operations as described above. Different JNDI service providers may provide different capabilities, for instance, some service providers may provide only read-only access to the data in the name service.
There you go, Maxim. An answer from our CTO directly :-)
I'll work on this issue during this week. I'll keep you and the community posted through JIRA.
Can someone guide me to deploy the jBPM BPEL engine on weblogic?
Thanks in advance.
Totally wrong topic... please either start a new one or find a more appropriate one.....