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 :
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
Hi!
I have a problem with the look up of a database resource.
I have the following setup:
One standalone Tomcat 5.x
One standalone JBoss 4.x
They are both running on the same pyhsical host machine.
The Jboss is configured with a datasource *-ds.xml. This can be used by the
EJB's running insid
First of all, thanks for the replies!
I'm also not convinced that my problems are based on ajax configuration,
since I removed them all from the xml's.
If I change the delegate member accessibility to protected, the error goes away
(There comes a different error for me though which I did not had
Hi!
I have a problem since migrating to SEAM 2.0.
When I start up my Webapp i get the following error.
00:27:12,890 INFO [Contexts] starting up: org.jboss.seam.web.ajax4jsfFilter
| 00:27:12,921 ERROR [[/x]] Exception sending context initialized event
to listener instance of class org.jb