Page 1 of 1

About Question enthuware.oce-ejbd.v6.2.539 :

Posted: Tue May 03, 2011 9:00 am
by deadlock_gr
The second answer (marked as wrong) says:
It allows an enterprise bean to modify its environment properties without knowing about them at the development time.
The explanation says:
This is wrong because a bean cannot change its environment. It gets whatever the assembler/Deployer gives to it.
Although I agree the answer is wrong, I think that the explanation is wrong. The bean can change its environment overriding what the assembler / deployer have set by using InitialContext.rebind().
Is this correct or not?
http://download.oracle.com/javase/6/doc ... ntext.html

Re: About Question enthuware.oce-ejbd.v6.2.539 :

Posted: Tue May 03, 2011 7:45 pm
by admin
A container is only obligated to provide a read only namespace. Context.rebind() is not guaranteed to work.
HTH,
Paul.

Re: About Question enthuware.oce-ejbd.v6.2.539 :

Posted: Fri Jan 02, 2015 12:07 pm
by garfield
Can someone please elaborate on option 4. What does it mean "locate external information without prior knowledge of how the information is named and organized" ?

Re: About Question enthuware.oce-ejbd.v6.2.539 :

Posted: Fri Jan 02, 2015 9:02 pm
by admin
It basically means that you do not need to hardcode the names in your code. A bean can look up information from the JNDI namespace dynamically. The data in the JNDI itself can be changed by external systems.

Re: About Question enthuware.oce-ejbd.v6.2.539 :

Posted: Mon May 18, 2015 7:34 pm
by himaiMinh
In the explanation, what does ISV stands for? I could not find it from the spec.

Re: About Question enthuware.oce-ejbd.v6.2.539 :

Posted: Mon May 18, 2015 7:56 pm
by admin
Independent Software Vendors.