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 application
On Fri, May 22, 2009 at 11:09 PM, David Blevins wrote:
> Then you could simply leave the
> blank and configure a datasource for each application in your openejb.xml
> file.
Interesting. I thought that leaving these elements blank would violate
the spec (I thought they're required) but I've jus
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 META-INF/pe
Hi Siegfried,
Constructed jar looks fine. The deployment error is rather strange.
Obviously the lookup and undeploy won't succeed until the deploy
works, so we'll tackle that first.
The error "Check that the directory is writable and that there is
enough disk space" is throw by the VM w
Going to answer this in your first email regarding not being able to
deploy.
-David
On May 21, 2009, at 7:13 PM, siegfried wrote:
How do I undeploy?
This the undeploy does not work. I did a google search and found some
references in jira but it looks like they had all been fixed.
Thanks,
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 rewritte
