Thanks Dave,
You were absolutely right - removing the Non JTA Data source fixed the
problem, and when I upgraded my Geronimo 2.0 server to the latest build, the
deployer did not like the way that I had specified the external path, but
using the complex type format fixed this problem also.
I am using the following geronimo-application.xml to deploy an EAR file. The
EAR deploys and starts OK, but the datasource that it creates is called
jdbc/LunchinatorDataSource i.e. this is literally the string that shows up
in the admin console, not LunchinatorDataSource. What is more, the
to start with.
thanks
david jencks
On Jul 13, 2007, at 8:11 PM, Adam OGorman wrote:
Hello,
I am trying to migrate an application to Geronimo 2.0 (actually
WASCE2.0),
it is an EAR that contains a WAR and an EJB Jar module. I believe
that I
have the Geronimo deployment descriptors
!
I think that seeing a list of what's in your ear, the application.xml
file (if its there), the geronimo plan(s), and exactly how you are
deploying would be most helpful to start with.
thanks
david jencks
On Jul 13, 2007, at 8:11 PM, Adam OGorman wrote:
Hello,
I am trying
Hello everyone, I am actually using a version of WASCE2.0 (with embedded
derby) that is based on Geronimo 2.0 M4. I am trying to deploy an EAR (that
contains a WAR and a JAR, the JAR speaks to the datasource). The deployment
error that I keep hitting is the following:
Error: Unable to
