Jacek Laskowski wrote:
Well, first when I said "new to Geronimo", I meant *really* new to
Geronimo. :-) Second,
I use the O'Reilly EJB 3.0 book which is excellent but has a bit of a
JBoss slant (for obvious reasons).
On Dec 28, 2007 4:11 PM, Garth Keesler <email@example.com> wrote:
I am new to Geronimo coming from VS2005 and C#. I have a Postgres DB
configured in the pool as OES and working correctly using the dbtester
sample app. I want to change the persistance of the Bank app from Derby
to Postgres and have not yet figured out the magic to make it happen.
The tables are correctly loaded in the OES database. Below is the
BankPool.xml I modified (obviously incorrectly) and I could use some
pointers. It mavens and installs okay but I get a "lifecycle operation
failed" when attempting to start in the console.
I think the file misses
and that's why the resource cannot be deployed and either can the app.
On the other hand, you mentioned it had worked fine using the dbtester
so it was indeed deployed already via the Geronimo console, wasn't it?
If so, the resource is global so your app should merely declare
dependency to the BankPool and be fine with it.
Could you tell us more about how you access the db? Is it JPA
application? What's persistence.xml? Are there any stack traces on the
Geronimo console (on the command line not in the Geronimo web
console)? Describe the steps you used to make
Second, the Bank sample app is located at
make it work initially, I just follow the instructions to the letter.
This includes creating and loading a Derby database. After that, a
maven command followed by a Geronimo console deploy and it works like a
Third, I have a postgres database already created and loaded with the
same tables/data req'd by the Bank app. It has been added to the DB
pool and works correctly, having been tested using the "dbtester" app
in the same site as the Bank app.
The persistence.xml file gets downloaded when the Bank app is extracted
for building so it comes with the kit. It is an "important" file
according to the EJB3.0 book and is used to describe the persistence
mappings to be used by the app server when running the app (best I can
do on this).
I've gotten to the point in playing with the files that I have to
remove/redeploy GMO every time since it seems to install correctly but
then won't display the ear as being deployed. I can't deploy the sample
app again because it conflicts with an already-installed app even tho
it doesn't show up in the GMO console.
I've heard of JBoss Seam but don't have a clue what it is. :-) I don't
think I'm running it.
You can find some pointers in Running JBoss Seam 2.0.0.GA on Geronimo 2.1 
I'm starting the process over again and I'll capture errors in a file
to attach ASAP.
Any help appreciated...
<?xml version="1.0" encoding="UTF-8"?>
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.