Yes, that should solve my problem.
In this case, the application name would be the servlet context path?
Another question: when the application is deployed in the server root url,
which would be the app name? ROOT?
Anyway, since this seems a small addition to an already existing heuristic, and
On Sat, May 23, 2009 at 1:16 AM, David Blevins david.blev...@visi.com wrote:
I'd rather avoid introducing any
container-specific solutions unless they're really necessary. I think
the closer we are to other ejb containers (likely application servers
themselves) the better so people won't run
Hi. First of all, sorry for the long post.
Some time has past since my last thread about programmatic database deployment
on the web application startup.
First of all, the application is Cyclos (http://project.cyclos.org), which have
the following requirements:
* The application is being
On May 22, 2009, at 11:13 AM, Luis Fernando Planella Gonzalez wrote:
* Several instances of the same application may be deployed in the
same server. So, even that the user could create a data source in
tomcat/conf/openejb.xml, he would have to change each application
instance's
On May 22, 2009, at 2:45 PM, Jacek Laskowski wrote:
Really interesting.
Interesting indeed. Like global ejb names, but worse.
I'd rather avoid introducing any
container-specific solutions unless they're really necessary. I think
the closer we are to other ejb containers (likely
