Btw, I'm not sure, if there's really a use case as the scope seems anything from memory to data sources or connections, but wondering if anybody ever heard of JSR 284 (Resource Management) being used?
I came across it by EC duty of voting on the ME RM (278) being dormant. And both JSRs mention each other. 284 went Final, but I'm not sure and also mentioned when voting if the scope and final solution would do EE any good?
Linda's PaaS document talks about Resource Managers, so I thought I'd ask.
Greetings from JustJava,
Having the full JDBC level Datasource definition is optional, and for cobtainers like Tomcat it may be more common to put such information in the web.xml, but even there I know from projects based on such containers, there are at least context.xml and server.xml where you may define such resources.
To be precise, Tomcat has data sources inside a <context> tag, which I recall also seems present if you define it in the web.xml instead. A global cobtext applies to all, while you may define them just for a web application level, too.
Full scale Java EE containers like WebLogic, JBoss or Glassfish have their own places, and one may only refer to the JNDI name of a datasource in other files.
JBoss has XML files with a series of <datasources> holding one or more <datasource> entries, so in those files unless defined elsewhere it's on a "root" level.
I cannot say, where it makes sense to define that for an individual session, but to be honest in most EE projects I came across, such location would only hold the logical DB source name, not its entire definition like server or JDBC driver.
Here the focus seems the <bean> so I'm not sure, if you'd have more than one session each with a different source or even DB type?;-) For definion in other places vendors among us may have to agree on an XML structure, that makes sense.
WernerAm 17.05.2012 21:06 schrieb "Reza Rahman" <reza_rahman@...>:
[javaee-spec users] [jsr342-experts] Re: resource definition metadata for administered objects