No, this is not the desired behavior. I believe this is related
to the bugs Rickard was complaining about in the JAR URL handlers in the
JDK. The redeployment behavior was supposed to be fixed for the final
release. Rickard, is this indeed one of the things on your plate? If
not, it should be assigned - I think there's a bug in Bugzilla.
Aaron
On Wed, 29 Nov 2000, Scott M Stark wrote:
> If I redeploy an entity bean in a running jboss server(2.0 Final) and there is
> a change in of the env-entry values in the ejb-jar.xml descriptor, the bean
> does not see the updated value. For example, if I redeploy a bean and there
> is a change
>
> from:
> <env-entry>
> <env-entry-name>projectRootContextName</env-entry-name>
> <env-entry-type>java.lang.String</env-entry-type>
> <env-entry-value>java:com.dscape.ProjectDirContext</env-entry-value>
> </env-entry>
>
> to:
> <env-entry>
> <env-entry-name>projectRootContextName</env-entry-name>
> <env-entry-type>java.lang.String</env-entry-type>
> <env-entry-value>dscape:ProjectDirContext</env-entry-value>
> </env-entry>
>
> Any attempt to lookup projectRootContextName in the java:comp/env context still
> sees the old value. This is the code being used to perform the lookup:
>
> InitialContext initContext = new InitialContext();
> Context envCtx = (Context) initContext.lookup("java:comp/env");
> String projectRootContextName = (String) envCtx.lookup("projectRootContextName");
>
> Is this the desired behavior?
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
