[jira] Created: (GERONIMO-2125) Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path
Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path - Key: GERONIMO-2125 URL: http://issues.apache.org/jira/browse/GERONIMO-2125 Project: Geronimo Type: Bug Security: public (Regular issues) Components: deployment Versions: 1.1 Environment: 1.1-rc1 Reporter: Mario Ruebsam A working EAR for Geronimo 1.0 with this structure: app.ear/ app.jar cpa.jar found.jar webclient.war The util JARs are referenced from the webclient.war/META-INF/MANIFEST.MF Class-Path: app.jar cpa.jar found.jar Deployment of this EAR in G 1.1-rc1 result in ClassNotFoundExceptions because of the missing classes in the JARs which are not found. Putting the JARs into the webclient.war/WEB-INF/lib worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2151) geronino should ignore .DS_Store files in the deploy dir
[ http://issues.apache.org/jira/browse/GERONIMO-2151?page=comments#action_12417806 ] Mario Ruebsam commented on GERONIMO-2151: - Geronimo should igrone all files and directories starting with '.' and for some apps and compaibility issues _ in the deploy dir. Some people like to checkout their apps so .svn or .cvs directories could also ignored this way. geronino should ignore .DS_Store files in the deploy dir Key: GERONIMO-2151 URL: http://issues.apache.org/jira/browse/GERONIMO-2151 Project: Geronimo Type: Improvement Security: public(Regular issues) Components: Hot Deploy Dir Versions: 1.1 Environment: osx Reporter: Christoph Sturm Priority: Minor osx stores extended file attributes in a dir called .DS_Store. after copying a war file to the geronimo deploy dir with the finder it creates the .DS_Store file, and geronimo tries to deploy it: 14:47:48,065 INFO [Hot Deployer] Deploying .DS_Store 14:47:48,284 ERROR [Hot Deployer] Unable to deploy: org.apache.xmlbeans.XmlException: /Users/christophsturm/Projects/geronimo-1.1/deploy/.DS_Store:1: error: Illegal XML character: 0x0 org.apache.xmlbeans.impl.piccolo.io.IllegalCharException: Illegal XML character: 0x0 at org.apache.xmlbeans.impl.piccolo.xml.UTF8XMLDecoder.decode(UTF8XMLDecoder.java:196) at org.apache.xmlbeans.impl.piccolo.xml.XMLStreamReader$FastStreamDecoder.read(XMLStreamReader.java:762) at org.apache.xmlbeans.impl.piccolo.xml.XMLStreamReader.read(XMLStreamReader.java:162) at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yy_refill(PiccoloLexer.java:3469) at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:3953) at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290) at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400) at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714) at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3354) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1267) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1254) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:309) at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:656) at org.apache.geronimo.deployment.xmlbeans.XmlBeansUtil.parse(XmlBeansUtil.java:74) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:326) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:263) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$$f226e5bd.getDeploymentPlan(generated) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:232) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:124) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:852) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:106) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:60) at java.lang.Thread.run(Thread.java:613) I think it would be best if the auto deployer would just ignore all files starting with a dot. -- This message is automatically generated
[jira] Commented: (GERONIMO-2125) Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path
[ http://issues.apache.org/jira/browse/GERONIMO-2125?page=comments#action_12419936 ] Mario Ruebsam commented on GERONIMO-2125: - I analyzed my problem a bit further with your example. In 1.0 you could add one or more utility jars to the ear. If one of these files depend on another jar, you don't have to add a classpath entry into the manifest file of this utility jar. The entry must only exist in the war or the ejb-jar referencing the jar on top of the other utlity jars. In 1.1 it works only if every utility jar contain a classpath entry to the other used jar's. Extending your example with two new jars: web.war depends on tools.jar in the ear root, tools.jar depends on found.jar also in the ear root in 1.0 you need a classpath entry in web.war too tools.jar in 1.1 you need a classpath entry in web.war too tools.jar and an entry in tools.jar too found.jar If the new behaviour in 1.1 is correct (I'm not familiar with the spec), then it is difficult to include 3rd party jars which depend on each other but doesn't have a correct classpath entry. The only way then is to use the repository and dependecies or path the manifest in the 3rd party jars. Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path - Key: GERONIMO-2125 URL: http://issues.apache.org/jira/browse/GERONIMO-2125 Project: Geronimo Type: Bug Security: public(Regular issues) Components: deployment Versions: 1.1 Environment: 1.1 release Reporter: Mario Ruebsam Assignee: David Jencks Priority: Blocker Fix For: 1.2, 1.1.1 Attachments: ear-1.0-SNAPSHOT.ear, manifestcp-itest.jar A working EAR for Geronimo 1.0 with this structure: app.ear/ app.jar cpa.jar found.jar webclient.war The util JARs are referenced from the webclient.war/META-INF/MANIFEST.MF Class-Path: app.jar cpa.jar found.jar Deployment of this EAR in G 1.1-rc1 result in ClassNotFoundExceptions because of the missing classes in the JARs which are not found. Putting the JARs into the webclient.war/WEB-INF/lib worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2125) Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path
[ http://issues.apache.org/jira/browse/GERONIMO-2125?page=comments#action_12420014 ] Mario Ruebsam commented on GERONIMO-2125: - Everything is ok in this example as long the ejb.jar is existent. If the ejb.jar is removed from the ear and the application.xml, the class org.apache.geronimo.itest.TestServlet could not be load. Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path - Key: GERONIMO-2125 URL: http://issues.apache.org/jira/browse/GERONIMO-2125 Project: Geronimo Type: Bug Security: public(Regular issues) Components: deployment Versions: 1.1 Environment: 1.1 release Reporter: Mario Ruebsam Assignee: David Jencks Priority: Blocker Fix For: 1.2, 1.1.1 Attachments: ear-1.0-SNAPSHOT.ear, ear-1.0-SNAPSHOT.ear, manifestcp-itest-v2.jar, manifestcp-itest.jar A working EAR for Geronimo 1.0 with this structure: app.ear/ app.jar cpa.jar found.jar webclient.war The util JARs are referenced from the webclient.war/META-INF/MANIFEST.MF Class-Path: app.jar cpa.jar found.jar Deployment of this EAR in G 1.1-rc1 result in ClassNotFoundExceptions because of the missing classes in the JARs which are not found. Putting the JARs into the webclient.war/WEB-INF/lib worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2125) Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path
[ http://issues.apache.org/jira/browse/GERONIMO-2125?page=all ] Mario Ruebsam updated GERONIMO-2125: Attachment: ear-1.0-SNAPSHOT.ear ear without the ejb.jar Classpath entries in the web app archive META-INF/MANIFEST.MF are not added to the wep app class path - Key: GERONIMO-2125 URL: http://issues.apache.org/jira/browse/GERONIMO-2125 Project: Geronimo Type: Bug Security: public(Regular issues) Components: deployment Versions: 1.1 Environment: 1.1 release Reporter: Mario Ruebsam Assignee: David Jencks Priority: Blocker Fix For: 1.2, 1.1.1 Attachments: ear-1.0-SNAPSHOT.ear, ear-1.0-SNAPSHOT.ear, ear-1.0-SNAPSHOT.ear, manifestcp-itest-v2.jar, manifestcp-itest.jar A working EAR for Geronimo 1.0 with this structure: app.ear/ app.jar cpa.jar found.jar webclient.war The util JARs are referenced from the webclient.war/META-INF/MANIFEST.MF Class-Path: app.jar cpa.jar found.jar Deployment of this EAR in G 1.1-rc1 result in ClassNotFoundExceptions because of the missing classes in the JARs which are not found. Putting the JARs into the webclient.war/WEB-INF/lib worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2188) Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle
[ http://issues.apache.org/jira/browse/GERONIMO-2188?page=comments#action_12421535 ] Mario Ruebsam commented on GERONIMO-2188: - CommitBeforeAutoCommit = true is a setting in the database pool deployment plan and should only be set for drivers that don't commit when calling setAutoCommit on the connection and this AutoCommit value changed. further discussion about the problem here: http://www.mail-archive.com/user@geronimo.apache.org/msg03450.html JDBC drivers with that problem are: MySQL, MaxDB, PostgreSQL and for what I can see and test atm Oracle with some connection types. I don't know if the OracleXADataSource support the CommitBeforeAutoCommit setting in the deployment plan. Need to configure CommitBeforeAutoCommit=true for Database Commits in Oracle Key: GERONIMO-2188 URL: http://issues.apache.org/jira/browse/GERONIMO-2188 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: connector Affects Versions: 1.1.1 Reporter: Krishnakumar B Assigned To: Donald Woods We have to configure CommitBeforeAutCommit=true property exclusively in the database connection pool plan, to have the ejb -based transactions immediately committed for oracle database. Otherwise it only commits transaction when the server shuts-down. This problem is not faces with Derby database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1939) Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer
[ http://issues.apache.org/jira/browse/GERONIMO-1939?page=all ] Mario Ruebsam updated GERONIMO-1939: Attachment: embedSVG.js This JavaScript code must be placed in a JavaScript file on the server, not in the document itself, calling the method insertEmbedSVG(...) will embed the Adobe SVG ActiveX. This external source JS embedding is workaround for the patent issue. Server Info portlet doesn't display the 'Server Memory Usage' live graph on Internet Explorer - Key: GERONIMO-1939 URL: http://issues.apache.org/jira/browse/GERONIMO-1939 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.1 Reporter: Chris Cardona Attachments: embedSVG.js I've tested it to work on Firefox v1.5.0.2 but the graph doesn't show up on IE v6.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1801) Restart/Shutdown functionality for Geronimo when using Java Service Wrapper
Restart/Shutdown functionality for Geronimo when using Java Service Wrapper --- Key: GERONIMO-1801 URL: http://issues.apache.org/jira/browse/GERONIMO-1801 Project: Geronimo Type: New Feature Security: public (Regular issues) Components: startup/shutdown Versions: 1.x Environment: Windows, Linux, Mac OS X, Solaris, HP-UX Reporter: Mario Ruebsam Priority: Minor If running Geronimo with Java Service Wrapper (also mentioned in GERONIMO-693), easy restart/shutdown functionality could be added to the JSW configuration by adding the following lines to the Java Service Wrapper wrapper.conf. # Filter settings. Add parameters as needed starting from 1 wrapper.filter.trigger.1=JSWRestartGeronimo wrapper.filter.action.1=RESTART wrapper.filter.trigger.2=JSWShutdownGeronimo wrapper.filter.action.2=SHUTDOWN wrapper.filter.trigger.3=java.lang.OutOfMemoryError wrapper.filter.action.3=RESTART The Servlet/JSP code for triggering shutdown/restart is then very simple by printing an output to the standard out or err e.g. System.out.println(JSWRestartGeronimo); or System.out.println(JSWShutdownGeronimo); Also the java.lang.OutOfMemoryError which is not easy to catch in the JVM can be handled this way using the JSW. If added to some JSW configuration scripts packaged with Geronimo the above configuration should also described in the JSW section in the current documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1452) Config.xml refers to the wrong JMX remote service gbean (Fix included)
[ http://issues.apache.org/jira/browse/GERONIMO-1452?page=comments#action_12374316 ] Mario Ruebsam commented on GERONIMO-1452: - Yes ist works with Jetty, to set the RMI port to 1098 in the above example the URL for the JMXService must be changed too: attribute name=urlservice:jmx:rmi://0.0.0.0:1098/jndi/rmi://0.0.0.0:1098/JMXConnector/attribute Config.xml refers to the wrong JMX remote service gbean (Fix included) -- Key: GERONIMO-1452 URL: http://issues.apache.org/jira/browse/GERONIMO-1452 Project: Geronimo Type: Bug Security: public(Regular issues) Components: core Versions: 1.0 Environment: Geronimo 1.0, Windows XP Reporter: Lin Sun Assignee: John Sisson Priority: Minor Fix For: 1.2, 1.1 I 'd like to change the default RMI port 1099 to 1098 due to a port conflict. I made all the changes I can think of in config.xml but got the following error during startup: 11:00:19,651 WARN [0/car,J2EEServer=geronimo,j2eeType=GBean,name=JMXService] Fa ilure in JMXConnector service:jmx:rmi://localhost/jndi/rmi:/JMXConnector 11:00:19,651 ERROR [GBeanInstanceState] Error while starting; GBean is now in th e FAILED state: objectName=geronimo.server:J2EEApplication=null,J2EEModule=gero nimo/j2ee-security/1.0/car,J2EEServer=geronimo,j2eeType=GBean,name=JMXService java.io.IOException: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 9.37.242.136; nested exc eption is: java.net.ConnectException: Connection refused: connect] at mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ er.java:152) at org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav a:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI nstance.java:936) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart (GBeanInstanceState.java:325) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta nceState.java:110) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G BeanInstanceState.java:132) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI nstance.java:537) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi cKernel.java:208) at org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans( Configuration.java:315) at org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$$7f 4b4a9b.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:835) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 178) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java: 173) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.start(Conf igurationManagerImpl.java:142) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl$$FastClass ByCGLIB$$fbed85d2.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod Invoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio n.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. java:800) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5 7) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat ionInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro xyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.ConfigurationManager$$EnhancerByCGL IB$$518f71dc.start(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:337) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:86) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:462) The fix is to replace: gbean name=JMXConnector with gbean name=JMXService I can start geronimo with rmi port 1098 with the above gbean name change in config.xml. I am running with tomcat, but i think the fix should be applied to jetty as well. -- This message is automatically generated by JIRA. - If you think it was sent
[jira] Commented: (GERONIMO-2093) Console database pool always gets NPE on deploy
[ http://issues.apache.org/jira/browse/GERONIMO-2093?page=comments#action_12415995 ] Mario Ruebsam commented on GERONIMO-2093: - The NPE appeared in 1.1-20060607. The problem is fixed in 1.1-rc1. No more NPE while displaying or saving deployment plan. Console database pool always gets NPE on deploy --- Key: GERONIMO-2093 URL: http://issues.apache.org/jira/browse/GERONIMO-2093 Project: Geronimo Type: Bug Security: public(Regular issues) Components: console Versions: 1.1 Environment: Release Candidate 6/7/2006 Reporter: Aaron Mulder Assignee: Aaron Mulder Priority: Blocker Fix For: 1.1 Reported on the user mailing list: 09:40:40,375 ERROR [DatabasePoolPortlet] Unable to save connection pool java.lang.NullPointerException at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.save(DatabasePoolPortlet.java:876) at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.processAction(DatabasePoolPortlet.java:338) ... Looks like perhaps rarFile is null? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2118) Deploying and starting web application in console shows successful even on start exceptions.
Deploying and starting web application in console shows successful even on start exceptions. Key: GERONIMO-2118 URL: http://issues.apache.org/jira/browse/GERONIMO-2118 Project: Geronimo Type: Bug Security: public (Regular issues) Components: console Versions: 1.1 Environment: 1.1-rc1 Reporter: Mario Ruebsam Priority: Minor When deploying and starting a web application through the Geronimo console Install New Applications feature, the web app is deployed and the console states The application was successfully started even when the application was not started because of an Exception (e.g. org.apache.geronimo.gbean.InvalidConfigurationException). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2121) Unable to resolve resource reference to db pool error when deploying web application as EAR
Unable to resolve resource reference to db pool error when deploying web application as EAR --- Key: GERONIMO-2121 URL: http://issues.apache.org/jira/browse/GERONIMO-2121 Project: Geronimo Type: Bug Security: public (Regular issues) Components: deployment Versions: 1.1 Environment: 1.1-rc1, jdk 1.4.2 Reporter: Mario Ruebsam Deployment of an web application inside of an EAR shows the following error: Error: Unable to distribute eiservice.ear: Unable to resolve resource reference 'jdbc/default' (Could not find resource 'jdbc/default'. Perhaps it has not yet been configured, or your application does not have a dependency declared for that resource module?) The dependency to the db connector and the resource reference is set correct into the geronimo-web.xml file. The deployment work when the WAR is deployed standalone. The deployment work also when the dependency setting to the db connector: dep:dependency dep:groupIdcoderesearch-jdbc/dep:groupId dep:artifactIdei-service-default/dep:artifactId dep:version2.3/dep:version dep:typerar/dep:type /dep:dependency is declared in the geronimo-application.xml. Used plans and descriptors geronimo-web.xml: ?xml version=1.0 encoding=UTF-8? web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-1.1; xmlns:naming=http://geronimo.apache.org/xml/ns/naming; dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1; dep:moduleId dep:groupIdcoderesearch/dep:groupId dep:artifactIdei-service/dep:artifactId dep:version2.3/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdcoderesearch/dep:groupId dep:artifactIdei-service/dep:artifactId dep:version2.3/dep:version dep:typecar/dep:type /dep:dependency dep:dependency dep:groupIdcoderesearch-jdbc/dep:groupId dep:artifactIdei-service-default/dep:artifactId dep:version2.3/dep:version dep:typerar/dep:type /dep:dependency dep:dependency dep:groupIdcommons-email/dep:groupId dep:artifactIdcommons-email/dep:artifactId dep:version1.0/dep:version dep:typejar/dep:type /dep:dependency dep:dependency dep:groupIdcommons-codec/dep:groupId dep:artifactIdcommons-codec/dep:artifactId dep:version1.3/dep:version dep:typejar/dep:type /dep:dependency dep:dependency dep:groupIdcommons-httpclient/dep:groupId dep:artifactIdcommons-httpclient/dep:artifactId dep:version3.0/dep:version dep:typejar/dep:type /dep:dependency dep:dependency dep:groupIdcommons-fileupload/dep:groupId dep:artifactIdcommons-fileupload/dep:artifactId dep:version1.0/dep:version dep:typejar/dep:type /dep:dependency /dep:dependencies dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment context-root/CODERESEARCH.client/ei-service/context-root naming:resource-ref naming:ref-namejdbc/default/naming:ref-name naming:resource-linkjdbc/default/naming:resource-link /naming:resource-ref /web-app web.xml: ?xml version=1.0 encoding=ISO-8859-1? web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd; version=2.4 servlet display-nameMainServlet/display-name servlet-nameMainServlet/servlet-name servlet-classcom.coderesearch.abp.found.srv.MainServlet/servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameMainServlet/servlet-name url-pattern/*/url-pattern /servlet-mapping env-entry env-entry-nameserver/ServerType/env-entry-name env-entry-typejava.lang.String/env-entry-type env-entry-valueGeronimo/Jetty/env-entry-value /env-entry resource-ref res-ref-namejdbc/default/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeShareable/res-sharing-scope /resource-ref /web-app db deploy plan: ?xml version=1.0 encoding=UTF-8? connector xmlns=http://geronimo.apache.org/xml/ns/j2ee/connector-1.1; dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1; dep:moduleId dep:groupIdcoderesearch-jdbc/dep:groupId dep:artifactIdei-service-default/dep:artifactId dep:version2.3/dep:version dep:typerar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdpostgresql/dep:groupId dep:artifactIdpostgresql/dep:artifactId
[jira] Created: (GERONIMODEVTOOLS-173) Geronimo Little-G release with Jetty don't start within Eclipse
Geronimo Little-G release with Jetty don't start within Eclipse --- Key: GERONIMODEVTOOLS-173 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-173 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Windows XP, JDK 6, Eclipse 3.3 Europa Reporter: Mario Ruebsam Geronimo Little-G release with Jetty don't start within Eclipse. It requires the bin/jpa.jar and lib/geronimo-transfromer-2.0-SNAPSHOT.jar from the standard server release. JPA should not be an requirement to start the Little-G server in Eclipse. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
