[jira] [Commented] (GERONIMO-6129) Improvements for Admin Console navigation
[ https://issues.apache.org/jira/browse/GERONIMO-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091632#comment-13091632 ] Shenghao Fang commented on GERONIMO-6129: - Hi Ivan, It requires adding a 'page' entry in the 'pages.xml' (attached) to make the installed plugin be visible in admin console in the initial implementation. But it is possible to give a default category for the plugins that are not defined in 'pages.xml' as you suggested. > Improvements for Admin Console navigation > - > > Key: GERONIMO-6129 > URL: https://issues.apache.org/jira/browse/GERONIMO-6129 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shenghao Fang >Priority: Minor > Attachments: navigation.patch, pages.xml, user-pages.xml > > > Make 2 improvements for Admin Console navigation: > 1) Centralized configuration file for portlet category >The portlet category is hard-coded in the gbean attribute 'pageTitle' in > 'plan.xml' of each portlet in current implementation. It makes the category > configuration distributed in multiple files which are hard to maintain. >This improvement targets to keep only title in 'pageTitle' and provide a > centralized configuration file for portlet category. It also enables runtime > configuration. > 2) User based navigation tree >This improvement is a part of > [GERONIMO-5675|https://issues.apache.org/jira/browse/GERONIMO-5675]. But it > provides more flexible configuration which makes the basic tree and the > advanced tree can be customized independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6129) Improvements for Admin Console navigation
[ https://issues.apache.org/jira/browse/GERONIMO-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shenghao Fang updated GERONIMO-6129: Attachment: navigation.patch user-pages.xml pages.xml Initial patch and the default configuration files are attached. Some known issues: 1) Access '/console' will still be redirected to '/console/0/Welcome'. The correct location should be '/console/Welcome' since the page title is changed to 'Welcome'. '/console/Welcome' need to be accessed manually for test purpose. 2) 'Welcome' page is not loaded properly. Access '/console/Welcome' will lead to a blank page in the right frame. > Improvements for Admin Console navigation > - > > Key: GERONIMO-6129 > URL: https://issues.apache.org/jira/browse/GERONIMO-6129 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shenghao Fang >Priority: Minor > Attachments: navigation.patch, pages.xml, user-pages.xml > > > Make 2 improvements for Admin Console navigation: > 1) Centralized configuration file for portlet category >The portlet category is hard-coded in the gbean attribute 'pageTitle' in > 'plan.xml' of each portlet in current implementation. It makes the category > configuration distributed in multiple files which are hard to maintain. >This improvement targets to keep only title in 'pageTitle' and provide a > centralized configuration file for portlet category. It also enables runtime > configuration. > 2) User based navigation tree >This improvement is a part of > [GERONIMO-5675|https://issues.apache.org/jira/browse/GERONIMO-5675]. But it > provides more flexible configuration which makes the basic tree and the > advanced tree can be customized independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6129) Improvements for Admin Console navigation
[ https://issues.apache.org/jira/browse/GERONIMO-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091623#comment-13091623 ] Ivan commented on GERONIMO-6129: I guess that one of the reasons for keeping the category in the title is that, once a console-plugin is installed, it will be automatically added in the admin console. If a centralized configuration file is provided, is it possible to do this ? I mean, users could install the console plugin on an existing server, it will automatically included in the admin console, and a new category will be added in the centralized configuration file if required. > Improvements for Admin Console navigation > - > > Key: GERONIMO-6129 > URL: https://issues.apache.org/jira/browse/GERONIMO-6129 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shenghao Fang >Priority: Minor > > Make 2 improvements for Admin Console navigation: > 1) Centralized configuration file for portlet category >The portlet category is hard-coded in the gbean attribute 'pageTitle' in > 'plan.xml' of each portlet in current implementation. It makes the category > configuration distributed in multiple files which are hard to maintain. >This improvement targets to keep only title in 'pageTitle' and provide a > centralized configuration file for portlet category. It also enables runtime > configuration. > 2) User based navigation tree >This improvement is a part of > [GERONIMO-5675|https://issues.apache.org/jira/browse/GERONIMO-5675]. But it > provides more flexible configuration which makes the basic tree and the > advanced tree can be customized independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6130) spring sample "webflow-richfaces-showcase" can't be accessed successfully
[ https://issues.apache.org/jira/browse/GERONIMO-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li updated GERONIMO-6130: -- Attachment: geronimo.log > spring sample "webflow-richfaces-showcase" can't be accessed successfully > - > > Key: GERONIMO-6130 > URL: https://issues.apache.org/jira/browse/GERONIMO-6130 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: myfaces >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > Attachments: geronimo.log > > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "webflow-richfaces-showcase", modify the pom.xml > file which under trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > web application: webflow-richfaces-showcase-1.0.0-BUILD-SNAPSHOT.war under > \webflow-richfaces-showcase\target folder > 5.Deploy and start the webflow-richfaces-showcase application via admin > console succuessfully > 6.When access this application via firefox 3.6.20, HTTP Status 500 error > happened. > 7.geronimo.log file is attached for detail. > 8.For apache-tomcat-7.0.20, this web application runs successfully. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6130) spring sample "webflow-richfaces-showcase" can't be accessed successfully
spring sample "webflow-richfaces-showcase" can't be accessed successfully - Key: GERONIMO-6130 URL: https://issues.apache.org/jira/browse/GERONIMO-6130 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: myfaces Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor 1.Use Aug 23 build of Geronimo server,start the server if it's not started 2.Download spring sample from svn: https://src.springframework.org/svn/spring-samples 3.According to sample named "webflow-richfaces-showcase", modify the pom.xml file which under trunk folder: Change the element of spring vesion from 3.0.0.RELEASE to 3.0.6.RELEASE 4.Build this sample successfully using cmd : mvn clean package, then can find web application: webflow-richfaces-showcase-1.0.0-BUILD-SNAPSHOT.war under \webflow-richfaces-showcase\target folder 5.Deploy and start the webflow-richfaces-showcase application via admin console succuessfully 6.When access this application via firefox 3.6.20, HTTP Status 500 error happened. 7.geronimo.log file is attached for detail. 8.For apache-tomcat-7.0.20, this web application runs successfully. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6129) Improvements for Admin Console navigation
Improvements for Admin Console navigation - Key: GERONIMO-6129 URL: https://issues.apache.org/jira/browse/GERONIMO-6129 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Reporter: Shenghao Fang Assignee: Shenghao Fang Priority: Minor Make 2 improvements for Admin Console navigation: 1) Centralized configuration file for portlet category The portlet category is hard-coded in the gbean attribute 'pageTitle' in 'plan.xml' of each portlet in current implementation. It makes the category configuration distributed in multiple files which are hard to maintain. This improvement targets to keep only title in 'pageTitle' and provide a centralized configuration file for portlet category. It also enables runtime configuration. 2) User based navigation tree This improvement is a part of [GERONIMO-5675|https://issues.apache.org/jira/browse/GERONIMO-5675]. But it provides more flexible configuration which makes the basic tree and the advanced tree can be customized independently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: BVal and searchWiredBudles=false
That was perfect, btw. Thanks so much! I really love that whole bundles setup. Being able to patch a file or two is so incredibly useful. -David On Aug 24, 2011, at 10:25 PM, Rex Wang wrote: > commit At revision: 1161387 > Please check if that is what you want. > > -Rex > > 2011/8/25 David Blevins > Checked in a potential fix for the bean validation tests that fail with the > following issue: > >java.lang.NullPointerException >at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:626) >at > org.apache.bval.jsr303.xml.ValidationParser.getSchema(ValidationParser.java:144) > > Fixed version does no classpath scanning for the schema: > > > https://svn.apache.org/repos/asf/geronimo/bundles/trunk/bval-jsr303/src/main/java/org/apache/bval/jsr303/xml/ValidationParser.java > > I don't think I setup the bundle correctly as it pulls in all the transitive > dependencies, which is definitely not right. If someone can take a peek, > that would be great. > > -David > > > > > -- > Lei Wang (Rex) > rwonly AT apache.org
[jira] [Commented] (GERONIMO-6127) "schema export unsuccessful" error happened for spring sample "travel"
[ https://issues.apache.org/jira/browse/GERONIMO-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091555#comment-13091555 ] Jarek Gawor commented on GERONIMO-6127: --- Can you retry with adding org.apache.xbean.osgi.bundle.util.BundleResourceHelper.convertResourceUrls=true property to etc/system.properties and restarting the server? > "schema export unsuccessful" error happened for spring sample "travel" > --- > > Key: GERONIMO-6127 > URL: https://issues.apache.org/jira/browse/GERONIMO-6127 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi, persistence >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > Attachments: geronimo.log > > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "travel", modify the pom.xml file which under > trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > web application: travel.war under \travel\target folder > 5.Deploy the travel application via admin console succuessfully > 6.Try to start this application but error happened: > 2011-08-26 10:12:52,156 ERROR [SchemaExport] schema export unsuccessful > java.lang.UnsupportedOperationException: The user must supply a JDBC > connection > at > org.hibernate.connection.UserSuppliedConnectionProvider.getConnection(UserSuppliedConnectionProvider.java:54) > at > org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:51) > at > org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:263) > at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:219) > at > org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:370) > at > org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1842) > at > org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:902) > at > org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) > at > org.apache.geronimo.persistence.PersistenceUnitGBean.(PersistenceUnitGBean.java:153) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:527) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:555) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) > at > org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:45) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:234) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBea
[jira] [Resolved] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang resolved GERONIMODEVTOOLS-764. Resolution: Fixed Change the status to Resolved. > Control the OSGI bundle's start level in GEP > > > Key: GERONIMODEVTOOLS-764 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, > Eclipse3.6SR1&SR2 >Reporter: Yi Xiao >Assignee: Yi Xiao > Labels: OSGI, startLevel > Fix For: 3.0 > > Attachments: controlBundleStartLevel_764.patch, > controlBundleStartLevel_764_1.patch, defaultStartLevel.jpg, > singleStartLevel.jpg > > > 1 Provide a UI interface to control all the bundles' start level > 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMODEVTOOLS-764) Control the OSGI bundle's start level in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091553#comment-13091553 ] Han Hong Fang commented on GERONIMODEVTOOLS-764: Commit the changes at revision: 1161984 to show the popup menu only when the selection is standalone OSGi bundle. > Control the OSGI bundle's start level in GEP > > > Key: GERONIMODEVTOOLS-764 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-764 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, > Eclipse3.6SR1&SR2 >Reporter: Yi Xiao >Assignee: Yi Xiao > Labels: OSGI, startLevel > Fix For: 3.0 > > Attachments: controlBundleStartLevel_764.patch, > controlBundleStartLevel_764_1.patch, defaultStartLevel.jpg, > singleStartLevel.jpg > > > 1 Provide a UI interface to control all the bundles' start level > 2 Control the specific bundle's start level easily -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6127) "schema export unsuccessful" error happened for spring sample "travel"
[ https://issues.apache.org/jira/browse/GERONIMO-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu updated GERONIMO-6127: --- Summary: "schema export unsuccessful" error happened for spring sample "travel" (was: "schema export unsuccessful" error and "Unable to build EntityManagerFactory" error happened for spring sample "travel" ) > "schema export unsuccessful" error happened for spring sample "travel" > --- > > Key: GERONIMO-6127 > URL: https://issues.apache.org/jira/browse/GERONIMO-6127 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi, persistence >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > Attachments: geronimo.log > > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "travel", modify the pom.xml file which under > trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > web application: travel.war under \travel\target folder > 5.Deploy the travel application via admin console succuessfully > 6.Try to start this application but error happened: > 2011-08-26 10:12:52,156 ERROR [SchemaExport] schema export unsuccessful > java.lang.UnsupportedOperationException: The user must supply a JDBC > connection > at > org.hibernate.connection.UserSuppliedConnectionProvider.getConnection(UserSuppliedConnectionProvider.java:54) > at > org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:51) > at > org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:263) > at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:219) > at > org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:370) > at > org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1842) > at > org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:902) > at > org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) > at > org.apache.geronimo.persistence.PersistenceUnitGBean.(PersistenceUnitGBean.java:153) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:527) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:555) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) > at > org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:45) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:234) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:56
[jira] [Commented] (GERONIMO-6127) "schema export unsuccessful" error and "Unable to build EntityManagerFactory" error happened for spring sample "travel"
[ https://issues.apache.org/jira/browse/GERONIMO-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091547#comment-13091547 ] viola.lu commented on GERONIMO-6127: pls add hibernate.transaction.manager_lookup_class = org.hibernate.transaction.JBossTransactionManagerLookup to your persistence.xml properties > "schema export unsuccessful" error and "Unable to build EntityManagerFactory" > error happened for spring sample "travel" > > > Key: GERONIMO-6127 > URL: https://issues.apache.org/jira/browse/GERONIMO-6127 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi, persistence >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > Attachments: geronimo.log > > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "travel", modify the pom.xml file which under > trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > web application: travel.war under \travel\target folder > 5.Deploy the travel application via admin console succuessfully > 6.Try to start this application but error happened: > 2011-08-26 10:12:52,156 ERROR [SchemaExport] schema export unsuccessful > java.lang.UnsupportedOperationException: The user must supply a JDBC > connection > at > org.hibernate.connection.UserSuppliedConnectionProvider.getConnection(UserSuppliedConnectionProvider.java:54) > at > org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:51) > at > org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:263) > at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:219) > at > org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:370) > at > org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1842) > at > org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:902) > at > org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) > at > org.apache.geronimo.persistence.PersistenceUnitGBean.(PersistenceUnitGBean.java:153) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:527) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:555) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) > at > org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:45) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:234) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) >
[jira] [Updated] (GERONIMO-6128) spring sample "webflow-primefaces-showcase" can't be started successfully
[ https://issues.apache.org/jira/browse/GERONIMO-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li updated GERONIMO-6128: -- Attachment: geronimo.log > spring sample "webflow-primefaces-showcase" can't be started successfully > - > > Key: GERONIMO-6128 > URL: https://issues.apache.org/jira/browse/GERONIMO-6128 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi, Tomcat >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > Attachments: geronimo.log > > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "webflow-primefaces-showcase", modify the pom.xml > file which under trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > web application: webflow-primefaces-showcase-1.0.0-BUILD-SNAPSHOT.war under > \webflow-primefaces-showcase\target folder > 5.Deploy the webflow-primefaces-showcase application via admin console > succuessfully > 6.Try to start this application but error happened: > Lifecycle operation failed > 7.geronimo.log file is attached for detail. > 8.For apache-tomcat-7.0.20, this web application runs successfully. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6128) spring sample "webflow-primefaces-showcase" can't be started successfully
spring sample "webflow-primefaces-showcase" can't be started successfully - Key: GERONIMO-6128 URL: https://issues.apache.org/jira/browse/GERONIMO-6128 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: osgi, Tomcat Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor Attachments: geronimo.log 1.Use Aug 23 build of Geronimo server,start the server if it's not started 2.Download spring sample from svn: https://src.springframework.org/svn/spring-samples 3.According to sample named "webflow-primefaces-showcase", modify the pom.xml file which under trunk folder: Change the element of spring vesion from 3.0.0.RELEASE to 3.0.6.RELEASE 4.Build this sample successfully using cmd : mvn clean package, then can find web application: webflow-primefaces-showcase-1.0.0-BUILD-SNAPSHOT.war under \webflow-primefaces-showcase\target folder 5.Deploy the webflow-primefaces-showcase application via admin console succuessfully 6.Try to start this application but error happened: Lifecycle operation failed 7.geronimo.log file is attached for detail. 8.For apache-tomcat-7.0.20, this web application runs successfully. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6127) "schema export unsuccessful" error and "Unable to build EntityManagerFactory" error happened for spring sample "travel"
[ https://issues.apache.org/jira/browse/GERONIMO-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li updated GERONIMO-6127: -- Attachment: geronimo.log > "schema export unsuccessful" error and "Unable to build EntityManagerFactory" > error happened for spring sample "travel" > > > Key: GERONIMO-6127 > URL: https://issues.apache.org/jira/browse/GERONIMO-6127 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi, persistence >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > Attachments: geronimo.log > > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "travel", modify the pom.xml file which under > trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > web application: travel.war under \travel\target folder > 5.Deploy the travel application via admin console succuessfully > 6.Try to start this application but error happened: > 2011-08-26 10:12:52,156 ERROR [SchemaExport] schema export unsuccessful > java.lang.UnsupportedOperationException: The user must supply a JDBC > connection > at > org.hibernate.connection.UserSuppliedConnectionProvider.getConnection(UserSuppliedConnectionProvider.java:54) > at > org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:51) > at > org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:263) > at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:219) > at > org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:370) > at > org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1842) > at > org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:902) > at > org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) > at > org.apache.geronimo.persistence.PersistenceUnitGBean.(PersistenceUnitGBean.java:153) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:527) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:555) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) > at > org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) > at > org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:45) > at > org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:234) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicK
[jira] [Created] (GERONIMO-6127) "schema export unsuccessful" error and "Unable to build EntityManagerFactory" error happened for spring sample "travel"
"schema export unsuccessful" error and "Unable to build EntityManagerFactory" error happened for spring sample "travel" Key: GERONIMO-6127 URL: https://issues.apache.org/jira/browse/GERONIMO-6127 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: osgi, persistence Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor Attachments: geronimo.log 1.Use Aug 23 build of Geronimo server,start the server if it's not started 2.Download spring sample from svn: https://src.springframework.org/svn/spring-samples 3.According to sample named "travel", modify the pom.xml file which under trunk folder: Change the element of spring vesion from 3.0.0.RELEASE to 3.0.6.RELEASE 4.Build this sample successfully using cmd : mvn clean package, then can find web application: travel.war under \travel\target folder 5.Deploy the travel application via admin console succuessfully 6.Try to start this application but error happened: 2011-08-26 10:12:52,156 ERROR [SchemaExport] schema export unsuccessful java.lang.UnsupportedOperationException: The user must supply a JDBC connection at org.hibernate.connection.UserSuppliedConnectionProvider.getConnection(UserSuppliedConnectionProvider.java:54) at org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:51) at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:263) at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:219) at org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:370) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1842) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:902) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74) at org.apache.geronimo.persistence.PersistenceUnitGBean.(PersistenceUnitGBean.java:153) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) at java.lang.reflect.Constructor.newInstance(Constructor.java:527) at org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:958) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:555) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:45) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:234) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:569) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:462) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:226) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
Re: [VOTE] release YOKO 1.3 - 1st attempt.
my own +1 :-) Forrest On Fri, Aug 26, 2011 at 10:25 AM, Shawn Jiang wrote: > +1 > > > On Thu, Aug 25, 2011 at 10:12 PM, Forrest Xia wrote: > >> [VOTE] release YOKO 1.3 - 1st attempt. >> >> This is a bug fixes release for Java EE 6 compliance: >> >> The fixes in this release are: >> YOKO-434 When reading a value object from a GIOP stream, yoko does not >> determine if a source value object class had a writeObject method, it uses >> the target value object class. >> YOKO-435 TypeCode is not created correctly from a java class, especially >> for array classes >> YOKO-436 Yoko should supply a SendingContextRuntime CodeBase object as a >> service context in the first request and reply message on a connection so >> the other orb can do meta calls >> >> The artifacts up for vote are: >> 1. >> https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.tar.gz >> 2. >> https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.zip >> >> The staging repository is: >> https://repository.apache.org/content/repositories/orgapachegeronimo-066 >> >> The source tag is: >> https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.3/ >> >> Vote will be open for 72 hours. >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Forrest >> > > > > -- > Shawn >
Re: [VOTE] release YOKO 1.3 - 1st attempt.
+1 On Thu, Aug 25, 2011 at 10:12 PM, Forrest Xia wrote: > [VOTE] release YOKO 1.3 - 1st attempt. > > This is a bug fixes release for Java EE 6 compliance: > > The fixes in this release are: > YOKO-434 When reading a value object from a GIOP stream, yoko does not > determine if a source value object class had a writeObject method, it uses > the target value object class. > YOKO-435 TypeCode is not created correctly from a java class, especially > for array classes > YOKO-436 Yoko should supply a SendingContextRuntime CodeBase object as a > service context in the first request and reply message on a connection so > the other orb can do meta calls > > The artifacts up for vote are: > 1. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.tar.gz > 2. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.zip > > The staging repository is: > https://repository.apache.org/content/repositories/orgapachegeronimo-066 > > The source tag is: > https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.3/ > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Forrest > -- Shawn
Re: [VOTE] release YOKO 1.3 - 1st attempt.
+1 -- Best regards, Han Hong Fang (Janet) hanhongfang AT apache.org
Re: [VOTE] release YOKO 1.3 - 1st attempt.
+1 2011/8/26 Rex Wang > rat:check, build pass, > > +1 > > > > 2011/8/25 Forrest Xia > >> [VOTE] release YOKO 1.3 - 1st attempt. >> >> This is a bug fixes release for Java EE 6 compliance: >> >> The fixes in this release are: >> YOKO-434 When reading a value object from a GIOP stream, yoko does not >> determine if a source value object class had a writeObject method, it uses >> the target value object class. >> YOKO-435 TypeCode is not created correctly from a java class, especially >> for array classes >> YOKO-436 Yoko should supply a SendingContextRuntime CodeBase object as a >> service context in the first request and reply message on a connection so >> the other orb can do meta calls >> >> The artifacts up for vote are: >> 1. >> https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.tar.gz >> 2. >> https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.zip >> >> The staging repository is: >> https://repository.apache.org/content/repositories/orgapachegeronimo-066 >> >> The source tag is: >> https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.3/ >> >> Vote will be open for 72 hours. >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Forrest >> > > > > -- > Lei Wang (Rex) > rwonly AT apache.org > -- Ivan
Re: [VOTE] release YOKO 1.3 - 1st attempt.
rat:check, build pass, +1 2011/8/25 Forrest Xia > [VOTE] release YOKO 1.3 - 1st attempt. > > This is a bug fixes release for Java EE 6 compliance: > > The fixes in this release are: > YOKO-434 When reading a value object from a GIOP stream, yoko does not > determine if a source value object class had a writeObject method, it uses > the target value object class. > YOKO-435 TypeCode is not created correctly from a java class, especially > for array classes > YOKO-436 Yoko should supply a SendingContextRuntime CodeBase object as a > service context in the first request and reply message on a connection so > the other orb can do meta calls > > The artifacts up for vote are: > 1. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.tar.gz > 2. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.zip > > The staging repository is: > https://repository.apache.org/content/repositories/orgapachegeronimo-066 > > The source tag is: > https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.3/ > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Forrest > -- Lei Wang (Rex) rwonly AT apache.org
[BUILD] branches/2.2: Failed for Revision: 1161792
Geronimo Revision: 1161792 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110825/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110825/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] [Resolved] (GERONIMO-5779) Provide a tool for diagnosing OSGi resolver problems
[ https://issues.apache.org/jira/browse/GERONIMO-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5779. --- Resolution: Fixed In revision 1161696 I committed additional improvements to the diagnose command. It now considers direct and indirect package uses dependencies to analyze "package uses conflicts" problems. > Provide a tool for diagnosing OSGi resolver problems > > > Key: GERONIMO-5779 > URL: https://issues.apache.org/jira/browse/GERONIMO-5779 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > > Provide (Karaf shell, admin console, or command line) tool for diagnosing > OSGi resolver problems. Or expose the "diag" command found in Equinox console > in Karaf shell. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-5779) Provide a tool for diagnosing OSGi resolver problems
[ https://issues.apache.org/jira/browse/GERONIMO-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reopened GERONIMO-5779: --- The diagnose command fails to analyze some more complex scenarios when "package uses conflict" problem is detected. > Provide a tool for diagnosing OSGi resolver problems > > > Key: GERONIMO-5779 > URL: https://issues.apache.org/jira/browse/GERONIMO-5779 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > > Provide (Karaf shell, admin console, or command line) tool for diagnosing > OSGi resolver problems. Or expose the "diag" command found in Equinox console > in Karaf shell. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6123) spring sample "jpetstore" can't be deployed successfully
[ https://issues.apache.org/jira/browse/GERONIMO-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091178#comment-13091178 ] Jarek Gawor commented on GERONIMO-6123: --- I believe I saw a similar exception when deploying our show-me-money or counter samples. > spring sample "jpetstore" can't be deployed successfully > > > Key: GERONIMO-6123 > URL: https://issues.apache.org/jira/browse/GERONIMO-6123 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "jpetstore", modify the pom.xml file which under > trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > web application: org.springframework.samples.jpetstore-1.0.0-SNAPSHOT.war > under \jpetstore\trunk\org.springframework.samples.jpetstore\target folder > 5.Start HSQLDB via "db\hsqldb\server.bat" > 6.Deploy this web application via admin console, but find this application > can'be deployed: > The application was not deployed. > Could not fully load class: > org.apache.struts.taglib.html.JavascriptValidatorTag > due to:org.apache.commons.validator.ValidatorResources > in classLoader: > org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@5b995b99 > java.lang.NoClassDefFoundError: Could not fully load class: > org.apache.struts.taglib.html.JavascriptValidatorTag > due to:org.apache.commons.validator.ValidatorResources > in classLoader: > org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@5b995b99 > at org.apache.xbean.finder.ClassFinder.(ClassFinder.java:136) > at > org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGBeans(JspModuleBuilderExtension.java:164) > at > org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:700) > at > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:763) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) > at > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) > at java.lang.Thread.run(Thread.java:736) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] branches/2.2: Failed for Revision: 1161643
Geronimo Revision: 1161643 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110825/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110825/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] [Created] (GERONIMO-6126) deploy of the Spring petclinic.war sample app fails
deploy of the Spring petclinic.war sample app fails
---
Key: GERONIMO-6126
URL: https://issues.apache.org/jira/browse/GERONIMO-6126
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 3.0
Reporter: Kevan Miller
Fix For: 3.0
Deploying the petclinic.war app on Geroimo 3.0 fails as follows:
{code}
$ ./deploy deploy ~/spring/spring-samples/petclinic/trunk/target/petclinic.war
Using GERONIMO_HOME:
/Users/kevan/geronimo/server/trunk/assemblies/geronimo-tomcat7-javaee6/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME:
/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home
2011-08-25 11:37:05,880 ERROR [DeployTool] Error:
org.apache.geronimo.common.DeploymentException: Unable to deploy petclinic.war:
Problems encountered parsing web.xml: [
No servlet matching servlet mappings for default]
at
org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:43)
at
org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:148)
at
org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:124)
at
org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:171)
at
org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64)
at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at
org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:32)
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] release YOKO 1.3 - 1st attempt.
+1 On Thu, Aug 25, 2011 at 10:42 PM, Kevan Miller wrote: > Here's my +1. Thanks Forrest!!! > > Signatures, checksums, RAT, build, binaries, license/notice files all look > good to me. > > --kevan > > On Aug 25, 2011, at 10:12 AM, Forrest Xia wrote: > > > [VOTE] release YOKO 1.3 - 1st attempt. > > > > This is a bug fixes release for Java EE 6 compliance: > > > > The fixes in this release are: > > YOKO-434 When reading a value object from a GIOP stream, yoko does not > determine if a source value object class had a writeObject method, it uses > the target value object class. > > YOKO-435 TypeCode is not created correctly from a java class, especially > for array classes > > YOKO-436 Yoko should supply a SendingContextRuntime CodeBase object as a > service context in the first request and reply message on a connection so > the other orb can do meta calls > > > > The artifacts up for vote are: > > 1. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.tar.gz > > 2. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.zip > > > > The staging repository is: > > https://repository.apache.org/content/repositories/orgapachegeronimo-066 > > > > The source tag is: > > https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.3/ > > > > Vote will be open for 72 hours. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Forrest > > -- viola Apache Geronimo
Re: [VOTE] release YOKO 1.3 - 1st attempt.
Here's my +1. Thanks Forrest!!! Signatures, checksums, RAT, build, binaries, license/notice files all look good to me. --kevan On Aug 25, 2011, at 10:12 AM, Forrest Xia wrote: > [VOTE] release YOKO 1.3 - 1st attempt. > > This is a bug fixes release for Java EE 6 compliance: > > The fixes in this release are: > YOKO-434 When reading a value object from a GIOP stream, yoko does not > determine if a source value object class had a writeObject method, it uses > the target value object class. > YOKO-435 TypeCode is not created correctly from a java class, especially for > array classes > YOKO-436 Yoko should supply a SendingContextRuntime CodeBase object as a > service context in the first request and reply message on a connection so the > other orb can do meta calls > > The artifacts up for vote are: > 1. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.tar.gz > 2. > https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.zip > > The staging repository is: > https://repository.apache.org/content/repositories/orgapachegeronimo-066 > > The source tag is: > https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.3/ > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Forrest
[jira] [Commented] (GERONIMO-6124) spring sample "task-basic" can't be deployed successfully because no deployer is able to handle it
[ https://issues.apache.org/jira/browse/GERONIMO-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091027#comment-13091027 ] Kevan Miller commented on GERONIMO-6124: task-basic is a Java SE jar. It's meant to be run as a main() method (e.g. java -cp target/org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar org.springframework.samples.task.basic.annotation.AnnotationDemo). So, there's nothing that an app server is going to do with the jar... That error message could be updated a bit to possibly make things clearer... In this case, there is no "J2EE descriptor". Should change that to Java EE and message should take OSGi into account, also. > spring sample "task-basic" can't be deployed successfully because no deployer > is able to handle it > -- > > Key: GERONIMO-6124 > URL: https://issues.apache.org/jira/browse/GERONIMO-6124 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Priority: Minor > > 1.Use Aug 23 build of Geronimo server,start the server if it's not started > 2.Download spring sample from svn: > https://src.springframework.org/svn/spring-samples > 3.According to sample named "task-basic", modify the pom.xml file which under > trunk folder: Change the element of spring vesion from > 3.0.0.RELEASE to > 3.0.6.RELEASE > 4.Build this sample successfully using cmd : mvn clean package, then can find > the application: org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar > under \task-basic\trunk\target folder > 5.Deploy this application via admin console, but find this application can'be > deployed and the error message displayed: > The application was not deployed. > Cannot deploy the requested application module because no deployer is able to > handle it. This can happen if you have omitted the J2EE deployment > descriptor, disabled a deployer module, or if, for example, you are trying to > deploy an EJB module on a minimal Geronimo server that does not have EJB > support installed. > (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) > org.apache.geronimo.common.DeploymentException: Cannot deploy the requested > application module because no deployer is able to handle it. This can happen > if you have omitted the J2EE deployment descriptor, disabled a deployer > module, or if, for example, you are trying to deploy an EJB module on a > minimal Geronimo server that does not have EJB support installed. > (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:243) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) > at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) > at > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) > at > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) > at java.lang.Thread.run(Thread.java:736) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[VOTE] release YOKO 1.3 - 1st attempt.
[VOTE] release YOKO 1.3 - 1st attempt. This is a bug fixes release for Java EE 6 compliance: The fixes in this release are: YOKO-434 When reading a value object from a GIOP stream, yoko does not determine if a source value object class had a writeObject method, it uses the target value object class. YOKO-435 TypeCode is not created correctly from a java class, especially for array classes YOKO-436 Yoko should supply a SendingContextRuntime CodeBase object as a service context in the first request and reply message on a connection so the other orb can do meta calls The artifacts up for vote are: 1. https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.tar.gz 2. https://repository.apache.org/content/repositories/orgapachegeronimo-066/org/apache/yoko/yoko/1.3/yoko-1.3-source-release.zip The staging repository is: https://repository.apache.org/content/repositories/orgapachegeronimo-066 The source tag is: https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.3/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Forrest
[jira] [Closed] (YOKO-435) TypeCode is not created correctly from a java class, especially for array classes
[ https://issues.apache.org/jira/browse/YOKO-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed YOKO-435. closed for 1.3 release > TypeCode is not created correctly from a java class, especially for array > classes > - > > Key: YOKO-435 > URL: https://issues.apache.org/jira/browse/YOKO-435 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: orb core >Affects Versions: v1.2.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: v1.3.0 > > > Two problems with creating a TypeCode from a java class: > - the full class name is used instead of the simple name, the name is > supposed to be the name in the enclosing context, i.e. the package, so the > SimpleName is appropriate (although oracle seems to include the '.' before > the simple name) > - array classes need to be a value box around a sequence around the component > type. > Fix is not tested on multi-dimensional arrays. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (YOKO-436) Yoko should supply a SendingContextRuntime CodeBase object as a service context in the first request and reply message on a connection so the other orb can do meta calls
[ https://issues.apache.org/jira/browse/YOKO-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed YOKO-436. Resolution: Fixed Fix Version/s: (was: v1.2.0) v1.3.0 closed for 1.3 release > Yoko should supply a SendingContextRuntime CodeBase object as a service > context in the first request and reply message on a connection so the other > orb can do meta calls > - > > Key: YOKO-436 > URL: https://issues.apache.org/jira/browse/YOKO-436 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: orb core >Affects Versions: v1.2.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: v1.3.0 > > > YOKO-434 got yoko to do a meta call when the repository id didn't match up. > We need to let the other orb do meta calls for the same reason. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (YOKO-434) When reading a value object from a GIOP stream, yoko does not determine if a source value object class had a writeObject method, it uses the target value object class.
[ https://issues.apache.org/jira/browse/YOKO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed YOKO-434. Resolution: Fixed Closed for 1.3 release > When reading a value object from a GIOP stream, yoko does not determine if a > source value object class had a writeObject method, it uses the target value > object class. > --- > > Key: YOKO-434 > URL: https://issues.apache.org/jira/browse/YOKO-434 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: orb core >Affects Versions: v1.1.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: v1.3.0 > > Attachments: YOKO-434-test.diff, YOKO-434-test2.diff > > > When a value object is serialized into a GIOP message, the existence of a > writeObject method on the source value object class determines whether 2 > bytes (stream format version and whether defaultWriteFields were called) are > written to the output stream, and the value object fields start at the next 4 > byte boundary. However when the value object is read in, the existence of a > writeObject method on the target class is used to determine whether to expect > these 2 bytes. There is no reason to expect that these writeObject methods' > existence will be the same on the source and target classes. For instance > the oracle BitSet class has a writeObject method but the Harmony and IBM jdk > BitSet classes do not. > I have not yet found a way to determine from the stream whether the source > class had a writeObject method other than trying both possibilities and > picking the first result that works. This requires adding mark capabilities > to the yoko InputStream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YOKO-434) When reading a value object from a GIOP stream, yoko does not determine if a source value object class had a writeObject method, it uses the target value object class.
[ https://issues.apache.org/jira/browse/YOKO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated YOKO-434: - Fix Version/s: (was: v1.2.0) v1.3.0 > When reading a value object from a GIOP stream, yoko does not determine if a > source value object class had a writeObject method, it uses the target value > object class. > --- > > Key: YOKO-434 > URL: https://issues.apache.org/jira/browse/YOKO-434 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: orb core >Affects Versions: v1.1.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: v1.3.0 > > Attachments: YOKO-434-test.diff, YOKO-434-test2.diff > > > When a value object is serialized into a GIOP message, the existence of a > writeObject method on the source value object class determines whether 2 > bytes (stream format version and whether defaultWriteFields were called) are > written to the output stream, and the value object fields start at the next 4 > byte boundary. However when the value object is read in, the existence of a > writeObject method on the target class is used to determine whether to expect > these 2 bytes. There is no reason to expect that these writeObject methods' > existence will be the same on the source and target classes. For instance > the oracle BitSet class has a writeObject method but the Harmony and IBM jdk > BitSet classes do not. > I have not yet found a way to determine from the stream whether the source > class had a writeObject method other than trying both possibilities and > picking the first result that works. This requires adding mark capabilities > to the yoko InputStream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (YOKO-434) When reading a value object from a GIOP stream, yoko does not determine if a source value object class had a writeObject method, it uses the target value object class.
[ https://issues.apache.org/jira/browse/YOKO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reopened YOKO-434: -- Change fixed version > When reading a value object from a GIOP stream, yoko does not determine if a > source value object class had a writeObject method, it uses the target value > object class. > --- > > Key: YOKO-434 > URL: https://issues.apache.org/jira/browse/YOKO-434 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: orb core >Affects Versions: v1.1.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: v1.3.0 > > Attachments: YOKO-434-test.diff, YOKO-434-test2.diff > > > When a value object is serialized into a GIOP message, the existence of a > writeObject method on the source value object class determines whether 2 > bytes (stream format version and whether defaultWriteFields were called) are > written to the output stream, and the value object fields start at the next 4 > byte boundary. However when the value object is read in, the existence of a > writeObject method on the target class is used to determine whether to expect > these 2 bytes. There is no reason to expect that these writeObject methods' > existence will be the same on the source and target classes. For instance > the oracle BitSet class has a writeObject method but the Harmony and IBM jdk > BitSet classes do not. > I have not yet found a way to determine from the stream whether the source > class had a writeObject method other than trying both possibilities and > picking the first result that works. This requires adding mark capabilities > to the yoko InputStream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YOKO-435) TypeCode is not created correctly from a java class, especially for array classes
[ https://issues.apache.org/jira/browse/YOKO-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated YOKO-435: - Fix Version/s: (was: v1.2.0) v1.3.0 > TypeCode is not created correctly from a java class, especially for array > classes > - > > Key: YOKO-435 > URL: https://issues.apache.org/jira/browse/YOKO-435 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: orb core >Affects Versions: v1.2.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: v1.3.0 > > > Two problems with creating a TypeCode from a java class: > - the full class name is used instead of the simple name, the name is > supposed to be the name in the enclosing context, i.e. the package, so the > SimpleName is appropriate (although oracle seems to include the '.' before > the simple name) > - array classes need to be a value box around a sequence around the component > type. > Fix is not tested on multi-dimensional arrays. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (YOKO-434) When reading a value object from a GIOP stream, yoko does not determine if a source value object class had a writeObject method, it uses the target value object class.
[ https://issues.apache.org/jira/browse/YOKO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed YOKO-434. Resolution: Fixed Fix Version/s: v1.2.0 > When reading a value object from a GIOP stream, yoko does not determine if a > source value object class had a writeObject method, it uses the target value > object class. > --- > > Key: YOKO-434 > URL: https://issues.apache.org/jira/browse/YOKO-434 > Project: Yoko - CORBA Server > Issue Type: Bug > Security Level: public(Regular issues) > Components: orb core >Affects Versions: v1.1.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: v1.2.0 > > Attachments: YOKO-434-test.diff, YOKO-434-test2.diff > > > When a value object is serialized into a GIOP message, the existence of a > writeObject method on the source value object class determines whether 2 > bytes (stream format version and whether defaultWriteFields were called) are > written to the output stream, and the value object fields start at the next 4 > byte boundary. However when the value object is read in, the existence of a > writeObject method on the target class is used to determine whether to expect > these 2 bytes. There is no reason to expect that these writeObject methods' > existence will be the same on the source and target classes. For instance > the oracle BitSet class has a writeObject method but the Harmony and IBM jdk > BitSet classes do not. > I have not yet found a way to determine from the stream whether the source > class had a writeObject method other than trying both possibilities and > picking the first result that works. This requires adding mark capabilities > to the yoko InputStream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] branches/2.2: Failed for Revision: 1161503
Geronimo Revision: 1161503 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110825/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110825/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.openejb -DartifactId=ejb31-api-experimental -Dversion=3.1.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT 2) org.apache.openejb:ejb31-api-experimental:jar:3.1.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.testsupport:test-ejb-j2ee_1.3:ejb:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] [Commented] (GERONIMO-6125) The dojo tree should consider a tree entry which has no child as a leaf node.
[ https://issues.apache.org/jira/browse/GERONIMO-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090928#comment-13090928 ] Rex Wang commented on GERONIMO-6125: fix at revision: 1161495 > The dojo tree should consider a tree entry which has no child as a leaf node. > - > > Key: GERONIMO-6125 > URL: https://issues.apache.org/jira/browse/GERONIMO-6125 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > Attachments: leaf-node.PNG > > > please see the screen shot in the attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6125) The dojo tree should consider a tree entry which has no child as a leaf node.
[ https://issues.apache.org/jira/browse/GERONIMO-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-6125. Resolution: Fixed > The dojo tree should consider a tree entry which has no child as a leaf node. > - > > Key: GERONIMO-6125 > URL: https://issues.apache.org/jira/browse/GERONIMO-6125 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > Attachments: leaf-node.PNG > > > please see the screen shot in the attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6125) The dojo tree should consider a tree entry which has no child as a leaf node.
[ https://issues.apache.org/jira/browse/GERONIMO-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-6125: --- Attachment: leaf-node.PNG > The dojo tree should consider a tree entry which has no child as a leaf node. > - > > Key: GERONIMO-6125 > URL: https://issues.apache.org/jira/browse/GERONIMO-6125 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Rex Wang >Assignee: Rex Wang > Fix For: 3.0 > > Attachments: leaf-node.PNG > > > please see the screen shot in the attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6125) The dojo tree should consider a tree entry which has no child as a leaf node.
The dojo tree should consider a tree entry which has no child as a leaf node. - Key: GERONIMO-6125 URL: https://issues.apache.org/jira/browse/GERONIMO-6125 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 3.0 Reporter: Rex Wang Assignee: Rex Wang Fix For: 3.0 please see the screen shot in the attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5734) Enable sharelib in osgi based geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090867#comment-13090867 ] Ivan commented on GERONIMO-5734: I made a mistake in the patch, so far, seems that if we would make the share library work, one ways is to generate the export packages and use require-bundle. Another possible way might be check the eclipse buddy policy. > Enable sharelib in osgi based geronimo > --- > > Key: GERONIMO-5734 > URL: https://issues.apache.org/jira/browse/GERONIMO-5734 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0 > Environment: geronimo 3.0 >Reporter: Ashish Jain >Assignee: Ivan > Fix For: 3.0 > > Attachments: > 0003-GERONIMO-5734-Enable-sharelib-in-osgi-based-geronimo.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6124) spring sample "task-basic" can't be deployed successfully because no deployer is able to handle it
spring sample "task-basic" can't be deployed successfully because no deployer is able to handle it -- Key: GERONIMO-6124 URL: https://issues.apache.org/jira/browse/GERONIMO-6124 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor 1.Use Aug 23 build of Geronimo server,start the server if it's not started 2.Download spring sample from svn: https://src.springframework.org/svn/spring-samples 3.According to sample named "task-basic", modify the pom.xml file which under trunk folder: Change the element of spring vesion from 3.0.0.RELEASE to 3.0.6.RELEASE 4.Build this sample successfully using cmd : mvn clean package, then can find the application: org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar under \task-basic\trunk\target folder 6.Deploy this application via admin console, but find this application can'be deployed and the error message displayed: The application was not deployed. Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) org.apache.geronimo.common.DeploymentException: Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:243) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6124) spring sample "task-basic" can't be deployed successfully because no deployer is able to handle it
[ https://issues.apache.org/jira/browse/GERONIMO-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tina Li updated GERONIMO-6124: -- Description: 1.Use Aug 23 build of Geronimo server,start the server if it's not started 2.Download spring sample from svn: https://src.springframework.org/svn/spring-samples 3.According to sample named "task-basic", modify the pom.xml file which under trunk folder: Change the element of spring vesion from 3.0.0.RELEASE to 3.0.6.RELEASE 4.Build this sample successfully using cmd : mvn clean package, then can find the application: org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar under \task-basic\trunk\target folder 5.Deploy this application via admin console, but find this application can'be deployed and the error message displayed: The application was not deployed. Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) org.apache.geronimo.common.DeploymentException: Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:243) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) was: 1.Use Aug 23 build of Geronimo server,start the server if it's not started 2.Download spring sample from svn: https://src.springframework.org/svn/spring-samples 3.According to sample named "task-basic", modify the pom.xml file which under trunk folder: Change the element of spring vesion from 3.0.0.RELEASE to 3.0.6.RELEASE 4.Build this sample successfully using cmd : mvn clean package, then can find the application: org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar under \task-basic\trunk\target folder 6.Deploy this application via admin console, but find this application can'be deployed and the error message displayed: The application was not deployed. Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) org.apache.geronimo.common.DeploymentException: Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (moduleFile=D:\testServer\0823\geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin\geronimo-tomcat7-javaee6-3.0-SNAPSHOT\var\temp\geronimo-deployer7355734105222365838.tmpdir\org.springframework.samples.task.basic-1.0.0-SNAPSHOT.jar) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:243) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140)
[jira] [Updated] (GERONIMO-6122) Support Stateless and Singleton EJB as JAX-RS root resource classes, providers and Application subclasses
[ https://issues.apache.org/jira/browse/GERONIMO-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Blevins updated GERONIMO-6122: Summary: Support Stateless and Singleton EJB as JAX-RS root resource classes, providers and Application subclasses (was: Support Stateless and Statefull EJB as JAX-RS root resource classes, providers and Application subclasses) > Support Stateless and Singleton EJB as JAX-RS root resource classes, > providers and Application subclasses > - > > Key: GERONIMO-6122 > URL: https://issues.apache.org/jira/browse/GERONIMO-6122 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: javaee6 >Affects Versions: 3.0 >Reporter: viola.lu >Assignee: Ivan >Priority: Minor > Fix For: 3.0.1 > > > From JAX-RS spec 1.1 > In a product that also supports EJB, an implementation MUST support use of > stateless and singleton > session beans as root resource classes, providers and Application subclasses. > JAX-RS annotations > MAY be applied to a bean's local interface or directly to a no-interface > bean. If an Exception- > Mapper for a EJBException or subclass is not included with an application > then exceptions thrown > by an EJB resource class or provider method MUST be treated as EJB > application exceptions: the > embedded cause of the EJBException MUST be unwrapped and processed as > described in section > 3.3.4. > Now geronimo recognize javax.ws.rs.URIinfo as EJB resource in a stateless > EJB, so failed to get Uriinfo > Run Restfulorder samples can give more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6123) spring sample "jpetstore" can't be deployed successfully
spring sample "jpetstore" can't be deployed successfully Key: GERONIMO-6123 URL: https://issues.apache.org/jira/browse/GERONIMO-6123 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: osgi Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor 1.Use Aug 23 build of Geronimo server,start the server if it's not started 2.Download spring sample from svn: https://src.springframework.org/svn/spring-samples 3.According to sample named "jpetstore", modify the pom.xml file which under trunk folder: Change the element of spring vesion from 3.0.0.RELEASE to 3.0.6.RELEASE 4.Build this sample successfully using cmd : mvn clean package, then can find web application: org.springframework.samples.jpetstore-1.0.0-SNAPSHOT.war under \jpetstore\trunk\org.springframework.samples.jpetstore\target folder 5.Start HSQLDB via "db\hsqldb\server.bat" 6.Deploy this web application via admin console, but find this application can'be deployed: The application was not deployed. Could not fully load class: org.apache.struts.taglib.html.JavascriptValidatorTag due to:org.apache.commons.validator.ValidatorResources in classLoader: org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@5b995b99 java.lang.NoClassDefFoundError: Could not fully load class: org.apache.struts.taglib.html.JavascriptValidatorTag due to:org.apache.commons.validator.ValidatorResources in classLoader: org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@5b995b99 at org.apache.xbean.finder.ClassFinder.(ClassFinder.java:136) at org.apache.geronimo.jasper.deployment.JspModuleBuilderExtension.addGBeans(JspModuleBuilderExtension.java:164) at org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.addGBeans(TomcatModuleBuilder.java:700) at org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.addGBeans(SwitchingModuleBuilder.java:174) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:763) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:255) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:883) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) at org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) at java.lang.Thread.run(Thread.java:736) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
