On May 13, 2008, at 9:55 PM, michaelg wrote:
I am writing an article for IBM developerWorks on using Grails and
Geronimo
together. However, I am unable to deploy a Grails WAR to Geronimo.
I first tried it with Geronimo 2.1.1 with Jetty. The error I got was a
NoClassDefFound for
Hello, and thanks for answering. I solved the problem: I had the entity beans
in EntitiesES.jar and the session beans in EJBModelES.jar. When I did put
them together inside the same jar the problem dissapeared.
I don't know why this procedure solved the problem, so if someone knows about
Hello,
I have been running Grails 0.5+ applications on Geronimo 2.x and this
works w/o problem as long as you hide specific packages. Your
geronimo-web.xml should look like the following one:
?xml version=1.0 encoding=UTF-8?
web-app
David Jencks wrote:
On May 13, 2008, at 9:55 PM, michaelg wrote:
I am writing an article for IBM developerWorks on using Grails and
Geronimo
together. However, I am unable to deploy a Grails WAR to Geronimo.
I first tried it with Geronimo 2.1.1 with Jetty. The error I got was a
Hello all,
I have about 25 (currently - will probably increase over time) timer
beans that really only need to expose the method to schedule them.
But I haven't been able to figure out how to share one interface class
and still be able to inject the correct, particular timer out of the 25
(This will probably end up appearing twice eventually - sorry)
Hello all,
I have about 25 (currently - will probably increase over time) timer beans
that really only need to expose the method to schedule them.
But I haven't been able to figure out how to share one interface class and
still be
Hello, Gianny Damour and team. I want to list my questions and proposals to
the possible architecture and features of the Geronimo POJO cache that WADI
is going to implement soon.
Assume that we are exposing a POJO cache using GBean, so POJOCache is
available through JNDI (new
Hello again.
Just in case someone else needs to do this. And, I must say that it is
probably almost always a bad thing to do. In most cases, the need to
have the exact same interface exposed on a range of classes that perform
completely different functions should be rare. I just happen to
Hello again.
(This is a resend because I left out part of my first paragraph by accident)
Just in case someone else needs to do this. And, I must say that it is
probably almost always a bad thing to do. In most cases, the need to
have the exact same interface exposed on a range of classes
