Ok, thanks for clarifying Peter!
The reason I believe that this is an anti-pattern comes from reading some
sources on the internet like the following:
http://www.jboss.org/community/wiki/ConfigDataSources
In clause "Configuring a DataSource for remote usage" it is said that:
anonymous wrote :
anonymous wrote : Is a Tomcat that runs on the same physical machine but in
another process than JBoss a 'remote' client?
Yes. Any Java app that runs in another java process (not the java process
running JBoss AS) is a remote client. And app that runs within the same java
process as JBoss AS is
Ok, thanks for the answer.
What I'm still not 100 % sure is what the term remote client suggests.
Is a Tomcat that runs on the same physical machine but in another process than
JBoss a 'remote' client?
And if this is so, how do you go about letting also JSP's and JSP Beans used in
Tomcat profi
Remote clients do not have access to JNDI entries in the java: namespace, thus
any items (such as data sources) that a remote client needs must be in the
global namespace. Of course, once the name is moved out of the java: namespace,
then even local clients need to look the name up in the global
