I have also now tried with the deployment plan below, I know that a lot of the content is the same as what is in the deployment descriptors within the EAR itself, but I thought it was worth a shot.
<?xml version="1.0" encoding="UTF-8"?> <application xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2" xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-1.2" xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2"> <environment> <moduleId> <groupId>default</groupId> <artifactId>lunchinator</artifactId> <version>1.0</version> <type>ear</type> </moduleId> <dependencies> <dependency> <groupId>org.apache.geronimo.configs</groupId> <artifactId>system-database</artifactId> <type>car</type> </dependency> <dependency> <groupId>org.apache.geronimo.configs</groupId> <artifactId>openjpa</artifactId> <type>car</type> </dependency> </dependencies> </environment> <module> <moduleId> <groupId>default</groupId> <artifactId>lunchinatorWeb</artifactId> <version>1.0</version> <type>war</type> </moduleId> <web>lunchinatorWeb.war</web> <context-root>/lunchinator</context-root> </module> <module> <moduleId> <groupId>default</groupId> <artifactId>lunchinatorDomain</artifactId> <version>1.0</version> <type>jar</type> </moduleId> <ejb>lunchinatorDomain.jar</ejb> <!-- Note this must match the --> <openejb-jar xmlns="http://openejb.apache.org/xml/ns/openejb-jar-2.2"> <cmp-connection-factory> <resource-link>jdbc/dgreen</resource-link> </cmp-connection-factory> <persistence xmlns="http://java.sun.com/xml/ns/persistence" version="1.0"> <persistence-unit name="maketechnologies-com-lunchinator"> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider> <jta-data-source>jdbc/dgreen</jta-data-source> <non-jta-data-source>jdbc/dgreen</non-jta-data-source> <properties> <property name="openjpa.jdbc.DBDictionary" value="org.apache.openjpa.jdbc.sql.DerbyDictionary"/> <property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema(ForeignKeys=true)"/> <property name="openjpa.Sequence" value="table(Table=OPENJPASEQ, Increment=100)"/> </properties> </persistence-unit> </persistence> </openejb-jar> </module> <ext-module> <connector>dgreen</connector> <external-path>org.tranql/tranql-connector-derby-embed-xa/1.3/rar</external-path> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"> <resourceadapter> <outbound-resourceadapter> <connection-definition> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface> <connectiondefinition-instance> <name>jdbc/dgreen</name> <config-property-setting name="DatabaseName">dgreen</config-property-setting> <config-property-setting name="CreateDatabase">true</config-property-setting> <connectionmanager> <xa-transaction> <transaction-caching/> </xa-transaction> <single-pool> <max-size>100</max-size> <min-size>0</min-size> <blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds> <idle-timeout-minutes>30</idle-timeout-minutes> <match-one/> </single-pool> </connectionmanager> </connectiondefinition-instance> </connection-definition> </outbound-resourceadapter> </resourceadapter> </connector> </ext-module> </application> djencks wrote: > > I've never seen that before! > > 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 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 correct (I have compared >> them to >> those in the Daytrader sample app and they seem reasonable). When I >> deploy >> the EAR, everything proceeds smoothly, there are no errors on the >> console or >> in the logs and it concludes with the message: >> >> Deployed default/lunchinator.ear/1184371234828/jar >> >> Yet, on the Geronimo admin web console, there is no EAR file >> deployed, but >> default/lunchinator.ear/1184371234828/jar is running as an EJB JAR. >> This is >> of course not usable and I assume that I am doing something wrong >> in the >> deployment descriptors, but unfortunately I have no idea what... >> >> any ideas would be most welcome and I am happy to post my deployment >> descriptors if necessary, >> >> Thanks very much, >> >> Adam. >> -- >> View this message in context: http://www.nabble.com/Ear-deploys-as- >> an-EJB-JAR--tf4077518s134.html#a11589548 >> Sent from the Apache Geronimo - Users mailing list archive at >> Nabble.com. >> > > > -- View this message in context: http://www.nabble.com/Ear-deploys-as-an-EJB-JAR--tf4077518s134.html#a11695564 Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
