Hi there,
> Ok. But only one DS per deployed bean?
No, I have one DS per instance but more possible DS per deployed bean.
> Yes, you're wrong :-) They are always available in bean methods, even create
> methods.
Ok. I'll try again and see if it works.
> You don't get the environment entries from the entity context. Are you
> referring to getEnvironment()? That has been deprecated. Use the
> java:/comp/env JNDI namespace instead (i.e. new
> InitialContext().lookup("java:comp/env/jdbc/BeanDS")).
Yes, I've tried in the same manner as said, excepting the last part from the
lookup url part - jdbc/BeanDS. I though that I could get them without knowing
the whole JNDI path - through the getEnvironment method after the lookup:
try {
Context ctx = (Context) (new InitialContext()).lookup("java:comp/env");
Hashtable hash = ctx.getEnvironment();
//
// and print the existing keys ....
//
} catch (Exception e) {
e.printStackTrace();
}
> Sure you can. You are not hardcoding the name of the real pool, you are
> hardcoding the name of your reference to it. BIIIG difference. You can have
> "java:comp/env/jdbc/BeanDS" point to *either* "java:/HypersonicDS" or
> "java:/OracleDS" or.. etc. So the name can indeed be hardcoded. That's the
> whole point. I suggest that you look again into how environment entries and
> resource references work in EJB 1.1.
Ok, I'll.
Thanks for your support.
Best regards,
Adrian.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
