Originally posted by Anu Tilwalli:
The Enterprise bean environment mechanism tries to achieve which of the following objectives?
1) It allows to users of an Enterprise bean to customize its business logic without modifying the source code.
2) It allows an enterprise bean to modify its environment properties without knowing about them at the development time.
3) t allows an enterprise bean to customize its container in a standard way.
4) It allows an enterprise bean to locate external information without prior knowledge of how the information is named and organized in the target operational environment.
The correct answer to this question is 1,4.
Can anyone give me example of the 1. How can we modify business logic w/o modifying the code. Seconly, why is 2) not in the correct list. Are env properties same as env entries?
Originally posted by Gregg Bolinger:
This is like saying:
"I want to buy a house. Which one should I buy?"
There is absolutely no possible way to answer this question with the information given.
Originally posted by Nguyen Long:
I deal woth this by apcking my app to an ear file, and above is a place where Jboss put tmp application file, you could copy and paste your changed jsp directly to that folder. (your application name will be tmpxxxxYOUR_APLLICATION_NAME.ear)
Originally posted by Mark Garland:
What about if you tell Eclipse to deploy in an exploded fashion.
If compressed into a single WAR, the container probably notices the timestamp change and simply reloaded the app.
If exploded into a directory, perhaps the container will just reload that file.
P.S. I'm new to EJB, so sorry if this sounds a little naive.
Originally posted by Ankur Sharma:
What I can tell you to go through the given below link and check out new feature of JDK 1.5 (Tiger)....
New Changes in JDK 1.5 Tiger Version
Also check out this link to find out the new features in JDK 1.4 from it's earlier versions.
New Features in JDK 1.4