[jira] [Created] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
Not search wired bundles in bundle classloader by default - Key: GERONIMO-6132 URL: https://issues.apache.org/jira/browse/GERONIMO-6132 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: osgi Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 >From the testing result, it seems that all the functions works well without >searching wired bundles. Also, considering that all kinds of Java EE >applications are installed as one bundle, including EAR package, it should not >an issue for user application to finding the resources in the same application. I am thinking to change the codes in xbean and geronimo-hook, by default, wired bundles will not be searched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Fwd: Trunk beta release
Forward this to geronimo community too. Do we want to pick up the fixes in Geronimo Connector 3.1.1-SNAPSHOT for coming geronimo 3.0 beta release ? On Sun, Aug 28, 2011 at 6:36 PM, Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Swapped over to Geronimo connector 3.1 - most stuff looks ok, but the > TransactionRollbackCauseTest unit test fails with this earlier version. We > had previously upgraded to 2.2.2-SNAPSHOT to support the rollback cause: > http://svn.apache.org/viewvc?view=revision&revision=1097964 - I then > upgraded to 3.1.1-SNAPSHOT after that. > > What's the view here - should we go for 3.1 and change/comment out the test > until a newer connector is published, or is it preferably to try and get a > newer version of the connector published. > > Jon > > On Sat, Aug 27, 2011 at 8:45 AM, Jonathan Gallimore < > jonathan.gallim...@gmail.com> wrote: > > > I'll give trunk a try with connector 3.1.1 today and report back. I did a > > fair bit of work on the connector support in openejb, and just went for > the > > latest snapshot of geronimo connector at the time. I think 3.1.1 will > > probably be fine. > > > > If everyone is happy then I'll kick of the release process for a beta > once > > xbean is published. Please shout if there's any problem with that. > > > > Jon > > On Aug 27, 2011 2:13 AM, "Shawn Jiang" wrote: > > > Thank you for volunteering ! Geronimo will publish xbean soon. But is > > > connector 3.1.1-SNAPSHOT a must-have ? > > > > > > can we use connector 3.1.1 for the openejb beta for now ? > > > > > > -- Forwarded message -- > > > From: Shawn Jiang > > > Date: Sat, Aug 27, 2011 at 9:11 AM > > > Subject: Re: Trunk beta release > > > To: d...@openejb.apache.org, dev@geronimo.apache.org > > > > > > > > > Thank you for volunteering ! Geronimo will publish xbean soon. But is > > > connector 3.1.1-SNAPSHOT > > > > > > > > > On Sat, Aug 27, 2011 at 3:06 AM, Jonathan Gallimore < > > > jonathan.gallim...@gmail.com> wrote: > > > > > >> I think it would be great to get some kind of alpha/beta/milestone > > release > > >> out. > > >> > > >> We deliberately keep the examples on a different version number to > > openejb, > > >> as there shouldn't be any dependency there, but we create an examples > > zip > > >> at > > >> release time as well as everything else I believe. > > >> > > >> I'm not too sure about javaee-api - obviously it follows the javaee > > >> version. > > >> My guess is we could choose to push that at the same time as the > > everything > > >> else as well. > > >> > > >> I think we'd need xbean and geronimo connector publishing first. > > >> > > >> I'm happy to volunteer to do the release work, if that's any help. > > >> > > >> Jon > > >> On Aug 26, 2011 7:15 AM, "Shawn Jiang" wrote: > > >> > Anyway, let's start to do this and figure how rough the trunk is > step > > by > > >> > step. the first step would be to clean the snapshot depencencies up: > > >> > > > >> > 3.8-SNAPSHOT > > >> > > > >> > > >> > > > 1.1.1-SNAPSHOT > > >> > > > 3.1.1-SNAPSHOT > > >> > > > >> > > > >> > There are also some internal compoents that are using different > > version > > >> then > > >> > 4.0.0-SNAPSHOT. > > >> > > > >> > 6.0-SNAPSHOT > > >> > > > >> > some samples in trunk are using 1.1-SNAPSHOT, But I can find part of > > them > > >> > are still 1.0-SNAPSHOT. > > >> > > > >> > I'm not sure what's the pratice to release javaee-api and samples > when > > >> they > > >> > don't share the same version with trunk. > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > On Fri, Aug 26, 2011 at 1:58 PM, David Blevins < > > david.blev...@gmail.com > > >> >wrote: > > >> > > > >> >> I suspect that even if we get started now, it will still be a few > > weeks > > >> >> before we see anything. It's been over a year on trunk with no > > release. > > >> >> It's going to be rough. > > >> >> > > >> >> Best case scenario, we get two releases out before October. Worst > > case > > >> >> scenario, we wait too long to start and don't get any. > > >> >> > > >> >> -David > > >> >> > > >> >> On Aug 25, 2011, at 10:49 PM, Shawn Jiang wrote: > > >> >> > > >> >> > Don't know if geronimo can wait until javaone. We could release a > > >> >> openejb > > >> >> > m1/beta1, and then release a m2/beta2 for javaone. > > >> >> > > > >> >> > On Fri, Aug 26, 2011 at 12:21 PM, Romain Manni-Bucau > > >> >> > wrote: > > >> >> > > > >> >> >> maybe we should wait just before javaone? > > >> >> >> > > >> >> >> - Romain > > >> >> >> > > >> >> >> 2011/8/26 Shawn Jiang > > >> >> >> > > >> >> >>> Geronimo is going to make a beta release. Let's discuss a > openejb > > >> >> >> trunk > > >> >> >>> release again. > > >> >> >>> > > >> >> >>> On Tue, Jul 12, 2011 at 9:00 AM, David Blevins < > > >> >> david.blev...@gmail.com > > >> >> wrote: > > >> >> >>> > > >> >> Would be excellent if we could get a beta ready before this > > >> >> >> presentation > > >> >> >>> on > > >> >> the
Re: [jira] [Created] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
+1 to make searchWiredBundles default value to false in the code. The xbean API users could specify the searchWriedbundle in constructor when needed. Geroniom server user still have a chance to use system properties to turn it on when needed. On Mon, Aug 29, 2011 at 3:17 PM, Ivan (JIRA) wrote: > Not search wired bundles in bundle classloader by default > - > > Key: GERONIMO-6132 > URL: https://issues.apache.org/jira/browse/GERONIMO-6132 > Project: Geronimo > Issue Type: Improvement > Security Level: public (Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > From the testing result, it seems that all the functions works well without > searching wired bundles. Also, considering that all kinds of Java EE > applications are installed as one bundle, including EAR package, it should > not an issue for user application to finding the resources in the same > application. > I am thinking to change the codes in xbean and geronimo-hook, by default, > wired bundles will not be searched. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > -- Shawn
[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=13092685#comment-13092685 ] Radim Kolar commented on GERONIMO-6129: --- ADD Monitoring and Plan creator to BASIC view. These are often used. > 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] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated GERONIMODEVTOOLS-759: - Attachment: OSGIBundleDeploy_759_noIDPersist.patch the patch not persist the bundle id in GEP side > Using the new APIs to manage the bundles status both in GEP and Server side > > > Key: GERONIMODEVTOOLS-759 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0 > Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, > Eclipse3.6SR1&SR2 >Reporter: Yi Xiao >Assignee: Jarek Gawor > Labels: OSGI, bundle > Fix For: 3.0 > > Attachments: OSGIBundleDeploy.patch, > OSGIBundleDeploy_759_noIDPersist.patch, > OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch, > OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch > > > This improvement depends on the server's modules, so, if the server side does > not update timely, it may cause the GEP compile failure! -- 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: 1162733
Geronimo Revision: 1162733 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110829/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110829/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
[VOTE PASSED] release YOKO 1.3 - 1st attempt.
The vote passed with: +1 Kevan, Viola, Rex, Ivan, Janet, Shawn, and me I will promote the repo shortly. Forrest On Fri, Aug 26, 2011 at 10:30 AM, Forrest Xia wrote: > 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 >> > >
[jira] [Commented] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092903#comment-13092903 ] Jarek Gawor commented on GERONIMODEVTOOLS-706: -- First of all, this is a nice feature but I do have a few comments / questions: 1) The implementation seems to be limited to one active terminal even though an user could define more than one Geronimo 3 servers. 2) The implementation seems to only support ssh-ing to a local machine. Remote ssh must be supported. 3) There should be an option (if there's one already) to right click on the server and open a ssh terminal to the server - so that users can access the terminal at any time. 4) What's GeronimoServerDelegate.addCommand() and .excuteCommands()? > Consider enabling Karaf shell in Eclipse console > > > Key: GERONIMODEVTOOLS-706 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0-M2 >Reporter: Jarek Gawor >Assignee: Ted Kirby > Attachments: enableKarafShell_706.patch, > enableKarafShell_706_m0.patch, karafSSHTerminal.jpg > > > (If possible) I think it would be pretty nice to have an option to enable and > access Karaf shell directly in Eclipse console window. If that can be done > make sure to start Geronimo server with > -Djline.terminal=jline.UnsupportedTerminal option. -- 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: 1162903
Geronimo Revision: 1162903 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110829/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110829/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
Fw: [VOTE] Release Apache OpenWebBeans-1.1.1
FYI: the OWB community is currently Voting on the new release. This might also be interesting for geronimo3 and tomee I guess ;) have fun! LieGrue, strub --- On Mon, 8/29/11, Mark Struberg wrote: > From: Mark Struberg > Subject: [VOTE] Release Apache OpenWebBeans-1.1.1 > To: d...@openwebbeans.apache.org, u...@openwebbeans.apache.org > Date: Monday, August 29, 2011, 9:16 PM > Hi! > > I'd like to call a VOTE on releasing Apache > OpenWebBeans-1.1.1 . > > This is a bugfix release of OpenWebBeans-1.1.x, thus no > branch has been created. > The ReleaseNotes are available online: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310844&version=12316311 > > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapacheopenwebbeans-072/ > > SVN source tag (1085208): > https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.1.1/ > > Source release: > https://repository.apache.org/content/repositories/orgapacheopenwebbeans-072/org/apache/openwebbeans/openwebbeans/1.1.1/openwebbeans-1.1.1-source-release.zip > > Binary release: > https://repository.apache.org/content/repositories/orgapacheopenwebbeans-072/org/apache/openwebbeans/openwebbeans-distribution/1.1.1/openwebbeans-distribution-1.1.1-binary.tar.gz > > PGP release key 2FDB81B1 > http://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS > > Vote will be open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 veto (and reason why) > > > txs and LieGrue, > strub >
Re: Trunk beta release
It would be great if we could release 3.1.1-SNAPSHOT. Transaction failure getCause() is a long awaited feature. On Aug 29, 2011, at 12:35 AM, Shawn Jiang wrote: > Forward this to geronimo community too. > > Do we want to pick up the fixes in Geronimo Connector 3.1.1-SNAPSHOT for > coming geronimo 3.0 beta release ? > > On Sun, Aug 28, 2011 at 6:36 PM, Jonathan Gallimore < > jonathan.gallim...@gmail.com> wrote: > >> Swapped over to Geronimo connector 3.1 - most stuff looks ok, but the >> TransactionRollbackCauseTest unit test fails with this earlier version. We >> had previously upgraded to 2.2.2-SNAPSHOT to support the rollback cause: >> http://svn.apache.org/viewvc?view=revision&revision=1097964 - I then >> upgraded to 3.1.1-SNAPSHOT after that. >> >> What's the view here - should we go for 3.1 and change/comment out the test >> until a newer connector is published, or is it preferably to try and get a >> newer version of the connector published. >> >> Jon >> >> On Sat, Aug 27, 2011 at 8:45 AM, Jonathan Gallimore < >> jonathan.gallim...@gmail.com> wrote: >> >>> I'll give trunk a try with connector 3.1.1 today and report back. I did a >>> fair bit of work on the connector support in openejb, and just went for >> the >>> latest snapshot of geronimo connector at the time. I think 3.1.1 will >>> probably be fine. >>> >>> If everyone is happy then I'll kick of the release process for a beta >> once >>> xbean is published. Please shout if there's any problem with that. >>> >>> Jon >>> On Aug 27, 2011 2:13 AM, "Shawn Jiang" wrote: Thank you for volunteering ! Geronimo will publish xbean soon. But is connector 3.1.1-SNAPSHOT a must-have ? can we use connector 3.1.1 for the openejb beta for now ? -- Forwarded message -- From: Shawn Jiang Date: Sat, Aug 27, 2011 at 9:11 AM Subject: Re: Trunk beta release To: d...@openejb.apache.org, dev@geronimo.apache.org Thank you for volunteering ! Geronimo will publish xbean soon. But is connector 3.1.1-SNAPSHOT On Sat, Aug 27, 2011 at 3:06 AM, Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > I think it would be great to get some kind of alpha/beta/milestone >>> release > out. > > We deliberately keep the examples on a different version number to >>> openejb, > as there shouldn't be any dependency there, but we create an examples >>> zip > at > release time as well as everything else I believe. > > I'm not too sure about javaee-api - obviously it follows the javaee > version. > My guess is we could choose to push that at the same time as the >>> everything > else as well. > > I think we'd need xbean and geronimo connector publishing first. > > I'm happy to volunteer to do the release work, if that's any help. > > Jon > On Aug 26, 2011 7:15 AM, "Shawn Jiang" wrote: >> Anyway, let's start to do this and figure how rough the trunk is >> step >>> by >> step. the first step would be to clean the snapshot depencencies up: >> >> 3.8-SNAPSHOT >> > > >>> >> 1.1.1-SNAPSHOT >> >>> 3.1.1-SNAPSHOT >> >> >> There are also some internal compoents that are using different >>> version > then >> 4.0.0-SNAPSHOT. >> >> 6.0-SNAPSHOT >> >> some samples in trunk are using 1.1-SNAPSHOT, But I can find part of >>> them >> are still 1.0-SNAPSHOT. >> >> I'm not sure what's the pratice to release javaee-api and samples >> when > they >> don't share the same version with trunk. >> >> >> >> >> >> >> >> >> On Fri, Aug 26, 2011 at 1:58 PM, David Blevins < >>> david.blev...@gmail.com >> wrote: >> >>> I suspect that even if we get started now, it will still be a few >>> weeks >>> before we see anything. It's been over a year on trunk with no >>> release. >>> It's going to be rough. >>> >>> Best case scenario, we get two releases out before October. Worst >>> case >>> scenario, we wait too long to start and don't get any. >>> >>> -David >>> >>> On Aug 25, 2011, at 10:49 PM, Shawn Jiang wrote: >>> Don't know if geronimo can wait until javaone. We could release a >>> openejb m1/beta1, and then release a m2/beta2 for javaone. On Fri, Aug 26, 2011 at 12:21 PM, Romain Manni-Bucau wrote: > maybe we should wait just before javaone? > > - Romain > > 2011/8/26 Shawn Jiang > >> Geronimo is going to make a beta release. Let's discuss a >> openejb > trunk >> release again. >> >> On Tue, Jul 12, 2011 at 9:00 AM, David Blevins < >>> david.blev...@gmail.com >>> wrote: >> >>> Would be excellent if we could get a beta ready before
[BUILD] branches/2.2: Failed for Revision: 1163046
Geronimo Revision: 1163046 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110829/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110829/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] [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=13093350#comment-13093350 ] Tina Li commented on GERONIMO-6123: --- For apache-tomcat-7.0.20, this application can be deployed successfully,but can't started successfully. The reason is missing dependency, add the missed dependency to pom.xml: org.slf4j slf4j-api 1.6.2 Then build this application again following the above steps and this application can be started and accessed successfully on apache-tomcat-7.0.20. > 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
[jira] [Commented] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093352#comment-13093352 ] Yi Xiao commented on GERONIMODEVTOOLS-706: -- Thank you for your comments, Jarek. 1) Yes, now I just limit to one active terminal, if user switch to connect to another server, must stop current one. 2) Yes, only support local machine now, I can add a field in server page to connect to remote server. 3) em, it's a good idea. 4) The methods will be used on modifying and saving server page configurations(not done yet), Should be removed in the patch, sorry~ > Consider enabling Karaf shell in Eclipse console > > > Key: GERONIMODEVTOOLS-706 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0-M2 >Reporter: Jarek Gawor >Assignee: Ted Kirby > Attachments: enableKarafShell_706.patch, > enableKarafShell_706_m0.patch, karafSSHTerminal.jpg > > > (If possible) I think it would be pretty nice to have an option to enable and > access Karaf shell directly in Eclipse console window. If that can be done > make sure to start Geronimo server with > -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (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=13093350#comment-13093350 ] Tina Li edited comment on GERONIMO-6123 at 8/30/11 1:28 AM: 1)For apache-tomcat-7.0.20, this application can be deployed successfully,but can't started successfully. The reason is missing dependency, add the missed dependency to pom.xml: org.slf4j slf4j-api 1.6.2 Then build this application again following the above steps and this application can be started and accessed successfully on apache-tomcat-7.0.20. 2)Try to deploy this appliction again on geronimo server, this application still can't be deployed and the problem still existed. was (Author: lylyuchen): For apache-tomcat-7.0.20, this application can be deployed successfully,but can't started successfully. The reason is missing dependency, add the missed dependency to pom.xml: org.slf4j slf4j-api 1.6.2 Then build this application again following the above steps and this application can be started and accessed successfully on apache-tomcat-7.0.20. > 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
[jira] [Commented] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093375#comment-13093375 ] Jarek Gawor commented on GERONIMODEVTOOLS-706: -- 1) Why limit the connection to one server? 2) You already know where the server is running. Should be part of the server information already. No need for a separate field, etc. > Consider enabling Karaf shell in Eclipse console > > > Key: GERONIMODEVTOOLS-706 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0-M2 >Reporter: Jarek Gawor >Assignee: Ted Kirby > Attachments: enableKarafShell_706.patch, > enableKarafShell_706_m0.patch, karafSSHTerminal.jpg > > > (If possible) I think it would be pretty nice to have an option to enable and > access Karaf shell directly in Eclipse console window. If that can be done > make sure to start Geronimo server with > -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6095) Info displayed incomplete of Default Server in Monitoring on admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093377#comment-13093377 ] Shenghao Fang commented on GERONIMO-6095: - Hi Tina, The issue you described is obviously another issue that should not be tracked by this JIRA. Please file it in a new JIRA, thanks. > Info displayed incomplete of Default Server in Monitoring on admin console > -- > > Key: GERONIMO-6095 > URL: https://issues.apache.org/jira/browse/GERONIMO-6095 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >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 >Assignee: Shenghao Fang >Priority: Minor > Fix For: 3.0 > > Attachments: GERONIMO-6095-1.patch, GERONIMO-6095.patch > > > 1. Use the July 26's build of geronimo-3.0 snapshot > 2. Go to the "Monitoring" porlet on admin console > 3. Click the 'Enable Query' link associated with this default server, server > works well > 4. Click the 'Edit' link associated with the default server but found no > default protocol was choosed and the values of "Username" and "Password" are > null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Is it possible for Axis2 community to do a 1.6.1 release for geronimo ?
Hello Devs, Geronimo is going to do a release soon, we are now using Axis2 1.6.1-SNAPSHOT. Is it possible for Axis2 community to do a 1.6.1 release for us ? On Tue, Aug 23, 2011 at 3:46 PM, Ivan wrote: > Hi, Andreas, thanks for following this, and do you plan to review those > JIRAs recently ? Geronimo community hopes to release 3.0 recently, if you > are busy with other stuffs, is it possible to have Axis2 1.6.1 release ? > Thanks. > > > 2011/8/11 Ivan > >> Thanks, Andreas. >> >> >> 2011/8/11 Andreas Veithen >> >>> Done. >>> >>> Andreas >>> >>> On Tue, Jul 26, 2011 at 05:16, Ivan wrote: >>> > Hi, Geronimo is trying to switch to use 1.6.1-SNAPSHOT, while it looks >>> that >>> > some codes are also required to merge from trunk, Could you help to >>> merge >>> > the changes to 1.6.1-SNAPSHOT ? Thanks >>> > ---> >>> > Revision: 1068985 >>> > AXIS2-4952 >>> > Scope dynamic ports to the instance of the service that did the >>> > addPort(...). Add TDD Unit test and flag to revert to previous >>> behavior of >>> > sharing dynamic ports across services. >>> > Revision: 1069659 >>> > Message: >>> > AXIS2-4938 >>> > Patch submitted by Katherine Sanders. >>> BindingProvider.getEndpointReference >>> > should put reference parameters from WSDL in returned EPR. >>> > Revision: 1069898 >>> > AXIS2-4948 >>> > Patch contributed by Katherine Sanders. Wrong WSDL location returned >>> by >>> > BindingProvider; was using the local filesystem path instead of the >>> endpoint >>> > URL. >>> > Revision: 1075057 >>> > Prevent index out of bounds exception, or any exception, from >>> attempting to >>> > log. Add TDD/UT for same. >>> > Revision: 1096530 >>> > On JAX-WS Client, treat local exceptions (e.g. ConnectException) as a >>> > SOAPFault, driving the JAX-WS handler handleFault methods and throwing >>> a >>> > SOAPFAultException back through the client invocation. Also provide a >>> > property to revert to previous behavior of creating an empty message, >>> > driving the JAX-WS handler handleMessage methods, and throwing a >>> > WebServiceException back through the client invocation. >>> > Revision: 1096557 >>> > Two changes in JAX-WS Endpoint implementation (1) Override >>> > setEndpointContext method, (2) Add logic to throw an exception if >>> endpoint >>> > publishing is disabled by a property (publishing is enabled by >>> default); per >>> > JSR-109 5.3.3 dynamically publishing endpoints in a server environment >>> is >>> > non portable and should be disabled. A server runtime can use the >>> property >>> > to disabled dynamically publishing JAX-WS endpoints via >>> Endpoint.publish >>> > methods. >>> > Revision: 1103336 >>> > AXIS2-5021: Committed patch provided by Ivan (xuhaihong). >>> > Revision: 1136177 >>> > AXIS2-5067: Committed patch provided by Ivan (xuhaihong), with minor >>> > changes. This implements the saveChanges method and calculates the >>> correct >>> > content type for a SOAPMessage. >>> > >>> > >>> > 2011/7/13 Ivan >>> >> >>> >> Hi, devs, I just uploaded a patch for AXIS2-5023. If possible, please >>> help >>> >> to review it first, as I am not quite confident for the changes for >>> this >>> >> jira, although it seems to work now. >>> >> Thanks. >>> >> >>> >> 2011/7/12 Ivan >>> >>> >>> >>> OK, I forget to reply to Axis2 mail list again ... >>> >>> >>> >>> 2011/7/12 Ivan >>> >>> >>> 2011/7/12 Andreas Veithen >>> > >>> > The changes for Neethi 3.0.x (including the three changes mentioned >>> in >>> > your mail) should now be included in the latest 1.6.1-SNAPSHOT >>> build. >>> > The release vote for Neethi 3.0.1 has started a couple of hours >>> ago. >>> > Once that release is complete, we can switch to the Neethi 3.0.1 >>> > release version on the 1.6 branch and Axis2 1.6.1 will be ready for >>> > release. >>> > >>> Thanks, Andreas, I will try to switch to Axis2 1.6.1-SNAPSHOT >>> soon. >>> >>> > >>> > Regarding the list of JIRA issues, if I understand this correctly, >>> the >>> > Geronimo project has a sort of patching mechanism so that they are >>> not >>> > on the critical path for the Geronimo release, which means that we >>> > have the time to review them properly and first apply them to the >>> > trunk, without delaying any Geronimo release. Can you confirm this? >>> >>> Hmm, I would say that the patching mechanism used now is somewhat >>> a >>> 'temporary' solution, and it is not expected to do that. Geronimo >>> needs to >>> bundle the axis2 components, that gave us a chance to modify codes. >>> We do hope that those patches could be reviewed and included in >>> Axis2 >>> code base. And yes, they work well now, but it is better to have >>> your Axis2 >>> experts' view for them. Also, from other sides, most of them are >>> related to >>> JAX-WS 2.2 support. I guess that they are also important for Axis2 >>> ;-) >>> Anyway, it depends on your
Fwd: Is it possible for Axis2 community to do a 1.6.1 release for geronimo ?
Hello Devs, Geronimo is going to do a release soon, we are now using Axis2 1.6.1-SNAPSHOT. Is it possible for Axis2 community to do a 1.6.1 release for us ? On Tue, Aug 23, 2011 at 3:46 PM, Ivan wrote: > Hi, Andreas, thanks for following this, and do you plan to review those > JIRAs recently ? Geronimo community hopes to release 3.0 recently, if you > are busy with other stuffs, is it possible to have Axis2 1.6.1 release ? > Thanks. > > > 2011/8/11 Ivan > >> Thanks, Andreas. >> >> >> 2011/8/11 Andreas Veithen >> >>> Done. >>> >>> Andreas >>> >>> On Tue, Jul 26, 2011 at 05:16, Ivan wrote: >>> > Hi, Geronimo is trying to switch to use 1.6.1-SNAPSHOT, while it looks >>> that >>> > some codes are also required to merge from trunk, Could you help to >>> merge >>> > the changes to 1.6.1-SNAPSHOT ? Thanks >>> > ---> >>> > Revision: 1068985 >>> > AXIS2-4952 >>> > Scope dynamic ports to the instance of the service that did the >>> > addPort(...). Add TDD Unit test and flag to revert to previous >>> behavior of >>> > sharing dynamic ports across services. >>> > Revision: 1069659 >>> > Message: >>> > AXIS2-4938 >>> > Patch submitted by Katherine Sanders. >>> BindingProvider.getEndpointReference >>> > should put reference parameters from WSDL in returned EPR. >>> > Revision: 1069898 >>> > AXIS2-4948 >>> > Patch contributed by Katherine Sanders. Wrong WSDL location returned >>> by >>> > BindingProvider; was using the local filesystem path instead of the >>> endpoint >>> > URL. >>> > Revision: 1075057 >>> > Prevent index out of bounds exception, or any exception, from >>> attempting to >>> > log. Add TDD/UT for same. >>> > Revision: 1096530 >>> > On JAX-WS Client, treat local exceptions (e.g. ConnectException) as a >>> > SOAPFault, driving the JAX-WS handler handleFault methods and throwing >>> a >>> > SOAPFAultException back through the client invocation. Also provide a >>> > property to revert to previous behavior of creating an empty message, >>> > driving the JAX-WS handler handleMessage methods, and throwing a >>> > WebServiceException back through the client invocation. >>> > Revision: 1096557 >>> > Two changes in JAX-WS Endpoint implementation (1) Override >>> > setEndpointContext method, (2) Add logic to throw an exception if >>> endpoint >>> > publishing is disabled by a property (publishing is enabled by >>> default); per >>> > JSR-109 5.3.3 dynamically publishing endpoints in a server environment >>> is >>> > non portable and should be disabled. A server runtime can use the >>> property >>> > to disabled dynamically publishing JAX-WS endpoints via >>> Endpoint.publish >>> > methods. >>> > Revision: 1103336 >>> > AXIS2-5021: Committed patch provided by Ivan (xuhaihong). >>> > Revision: 1136177 >>> > AXIS2-5067: Committed patch provided by Ivan (xuhaihong), with minor >>> > changes. This implements the saveChanges method and calculates the >>> correct >>> > content type for a SOAPMessage. >>> > >>> > >>> > 2011/7/13 Ivan >>> >> >>> >> Hi, devs, I just uploaded a patch for AXIS2-5023. If possible, please >>> help >>> >> to review it first, as I am not quite confident for the changes for >>> this >>> >> jira, although it seems to work now. >>> >> Thanks. >>> >> >>> >> 2011/7/12 Ivan >>> >>> >>> >>> OK, I forget to reply to Axis2 mail list again ... >>> >>> >>> >>> 2011/7/12 Ivan >>> >>> >>> 2011/7/12 Andreas Veithen >>> > >>> > The changes for Neethi 3.0.x (including the three changes mentioned >>> in >>> > your mail) should now be included in the latest 1.6.1-SNAPSHOT >>> build. >>> > The release vote for Neethi 3.0.1 has started a couple of hours >>> ago. >>> > Once that release is complete, we can switch to the Neethi 3.0.1 >>> > release version on the 1.6 branch and Axis2 1.6.1 will be ready for >>> > release. >>> > >>> Thanks, Andreas, I will try to switch to Axis2 1.6.1-SNAPSHOT >>> soon. >>> >>> > >>> > Regarding the list of JIRA issues, if I understand this correctly, >>> the >>> > Geronimo project has a sort of patching mechanism so that they are >>> not >>> > on the critical path for the Geronimo release, which means that we >>> > have the time to review them properly and first apply them to the >>> > trunk, without delaying any Geronimo release. Can you confirm this? >>> >>> Hmm, I would say that the patching mechanism used now is somewhat >>> a >>> 'temporary' solution, and it is not expected to do that. Geronimo >>> needs to >>> bundle the axis2 components, that gave us a chance to modify codes. >>> We do hope that those patches could be reviewed and included in >>> Axis2 >>> code base. And yes, they work well now, but it is better to have >>> your Axis2 >>> experts' view for them. Also, from other sides, most of them are >>> related to >>> JAX-WS 2.2 support. I guess that they are also important for Axis2 >>> ;-) >>> Anyway, it depends on your
[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=13093390#comment-13093390 ] Shenghao Fang commented on GERONIMO-6129: - Hi Ivan, I suppose that we would provide default configuration pages.xml and user-page.xml. All pages will be included in pages.xml and will be filtered by the list of registered portlets. So it will not be an issue if a user only installs some of the portlests and installs others later. I'm not sure whether we have the scenario that we would provide new portlets which are not included in the major release of current version. If such scenario exists, it does needs to be considered. Another choice is that we can provide all the access to the system user by default by hard-coding instead of by user-pages.xml. > 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
Question about TransactionManger replacement and initialization
If we would like use third-party TransactionManager such as Bitronix TransactionManger instead of geronimo default transaction manger implementation, and Hibernate as their persistence layer. It's better if third-party TransactionManger can be initialized in Application context, But can we replace geronimo default transaction manger with a third-party on geronimo 2.1.5? I tried to create BitronixTransactionMangerGBean , BitronixTransactionSynchronizationRegistryGBean and change TransactionManger gbean defintion in transaction plugins plan.xml , but server failed to start coz of JCA ,system-database start failure, i think it's difficult to replace geronimo transaction manager. or Bind the third-party TransactoinManger into our jndi tree with another different name (java:bintronixmanager,java:comp/env/BintronixUserTransaction, end-user can lookup it in its application code, but when build PersitenceUnitGBean , its reference TransactionManager refers to TransactionManagerImpl (geronimo default transaction manger). Is there other way to make this happen? I Appreciate your help! -- viola Apache Geronimo
[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=13093419#comment-13093419 ] Tina Li commented on GERONIMO-6127: --- Hi Jarek, According to your comments, I added org.apache.xbean.osgi.bundle.util.BundleResourceHelper.convertResourceUrls=true property to etc/system.properties and found server can't be started successfully. No warning or error message but the starting process of modules seemes blocked. > "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.startRecu
[jira] [Issue Comment Edited] (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=13093443#comment-13093443 ] Tina Li edited comment on GERONIMO-6127 at 8/30/11 5:20 AM: Hi Jarek, 1) Server started successfully finally and the cost: Booting Geronimo Kernel (in Java 1.6.0)... Module 1/63 org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car started in .000s Module 2/63 org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car started in .125s Module 3/63 org.apache.geronimo.framework/plugin/3.0-SNAPSHOT/car started in 3.734s Module 4/63 org.apache.geronimo.framework/j2ee-security/3.0-SNAPSHOT/car started in .156s Module 5/63 org.apache.geronimo.framework/server-security-config/3.0-SNAPSHOT/ ar started in .031s Module 6/63 org.apache.geronimo.framework/bundle-recorder/3.0-SNAPSHOT/car started in .000s Module 7/63 org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT car started in .125s Module 8/63 org.apache.geronimo.configs/j2ee-server/3.0-SNAPSHOT/car started in .016s Module 9/63 org.apache.geronimo.configs/j2ee-deployer/3.0-SNAPSHOT/car started in .079s Module 10/63 org.apache.geronimo.configs/bval-deployer/3.0-SNAPSHOT/car started in 1.938s Module 11/63 org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car started in .125s Module 12/63 org.apache.geronimo.configs/system-database/3.0-SNAPSHOT/car started in 2.141s Module 13/63 org.apache.geronimo.configs/openjpa2/3.0-SNAPSHOT/car started in .000s Module 14/63 org.apache.geronimo.configs/openejb/3.0-SNAPSHOT/car started in 3.813s Module 15/63 org.apache.geronimo.configs/jasper/3.0-SNAPSHOT/car started in .015s Module 16/63 org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car started in 4.344s Module 17/63 org.apache.geronimo.configs/connector-deployer-1_6/3.0-SNAPSHOT/ca started in .032s Module 18/63 org.apache.geronimo.configs/tomcat7-deployer/3.0-SNAPSHOT/car started in .032s Module 19/63 org.apache.geronimo.configs/web-extender/3.0-SNAPSHOT/car started in .016s Module 20/63 org.apache.geronimo.configs/hot-deployer/3.0-SNAPSHOT/car started in .016s Module 21/63 org.apache.geronimo.configs/remote-deploy-tomcat/3.0-SNAPSHOT/car started in 3.906s Module 22/63 org.apache.geronimo.configs/jasper-deployer/3.0-SNAPSHOT/car started in .000s Module 23/63 org.apache.geronimo.configs/myfaces/3.0-SNAPSHOT/car started in .000s Module 24/63 org.apache.geronimo.configs/myfaces-deployer/3.0-SNAPSHOT/car started in 2.953s Module 25/63 org.apache.geronimo.configs/aries/3.0-SNAPSHOT/car started in .000s Module 26/63 org.apache.geronimo.configs/aries-deployer/3.0-SNAPSHOT/car started in .000s Module 27/63 org.apache.geronimo.configs/persistence-jpa20-deployer/3.0-SNAPSHO /car started in .015s Module 28/63 org.apache.geronimo.plugins/pluto-support/3.0-SNAPSHOT/car started in .015s Module 29/63 org.apache.geronimo.plugins/console-tomcat/3.0-SNAPSHOT/car started in 4.062s Module 30/63 org.apache.geronimo.plugins/plugin-console-tomcat/3.0-SNAPSHOT/car started in 4.062s Module 31/63 org.apache.geronimo.plugins.monitoring/mconsole-ds/3.0-SNAPSHOT/ca started in .063s Module 32/63 org.apache.geronimo.plugins.monitoring/mconsole-tomcat/3.0-SNAPSHO /car started in 10.079s Module 33/63 org.apache.geronimo.configs/activemq-broker-blueprint/3.0-SNAPSHOT car started in 1.031s Module 34/63 org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car started in .187s Module 35/63 org.apache.geronimo.plugins/activemq-console-tomcat/3.0-SNAPSHOT/c rstarted in 2.187s Module 36/63 org.apache.geronimo.plugins/debugviews-console-tomcat/3.0-SNAPSHOT car started in 2.579s Module 37/63 org.apache.geronimo.plugins/sysdb-console-tomcat/3.0-SNAPSHOT/car started in 3.406s Module 38/63 org.apache.geronimo.plugins/openejb-console-tomcat/3.0-SNAPSHOT/ca started in 15.625s Module 39/63 org.apache.geronimo.configs/openejb-deployer/3.0-SNAPSHOT/car started in .047s Module 40/63 org.apache.geronimo.configs/openejb-corba-deployer/3.0-SNAPSHOT/ca started in .063s Module 41/63 org.apache.geronimo.configs/j2ee-corba-yoko/3.0-SNAPSHOT/car started in .438s Module 42/63 org.apache.geronimo.configs/openwebbeans-deployer/3.0-SNAPSHOT/car started in .015s Module 43/63 org.apache.geronimo.plugins.monitoring/agent-ds/3.0-SNAPSHOT/car started in .453s Module 44/63 org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car started in 2.281s Module 45/63 org.apache.geronimo.plugins.monitoring/agent-car-jmx/3.0-SNAPSHOT/ ar started in .016s Module 46/63 org.apache.geronimo.configs/welcome-tomcat/3.0-SNAPSHOT/car started in 2.297s Module 47/63 org.apache.geronimo.configs/javamail/3.0-SNAPSHOT/car start
[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=13093443#comment-13093443 ] Tina Li commented on GERONIMO-6127: --- Hi Jarek, 1) Server started successfully finally and the cost: Booting Geronimo Kernel (in Java 1.6.0)... Module 1/63 org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car started in .000s Module 2/63 org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car started in .125s Module 3/63 org.apache.geronimo.framework/plugin/3.0-SNAPSHOT/car started in 3.734s Module 4/63 org.apache.geronimo.framework/j2ee-security/3.0-SNAPSHOT/car started in .156s Module 5/63 org.apache.geronimo.framework/server-security-config/3.0-SNAPSHOT/ ar started in .031s Module 6/63 org.apache.geronimo.framework/bundle-recorder/3.0-SNAPSHOT/car started in .000s Module 7/63 org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT car started in .125s Module 8/63 org.apache.geronimo.configs/j2ee-server/3.0-SNAPSHOT/car started in .016s Module 9/63 org.apache.geronimo.configs/j2ee-deployer/3.0-SNAPSHOT/car started in .079s Module 10/63 org.apache.geronimo.configs/bval-deployer/3.0-SNAPSHOT/car started in 1.938s Module 11/63 org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car started in .125s Module 12/63 org.apache.geronimo.configs/system-database/3.0-SNAPSHOT/car started in 2.141s Module 13/63 org.apache.geronimo.configs/openjpa2/3.0-SNAPSHOT/car started in .000s Module 14/63 org.apache.geronimo.configs/openejb/3.0-SNAPSHOT/car started in 3.813s Module 15/63 org.apache.geronimo.configs/jasper/3.0-SNAPSHOT/car started in .015s Module 16/63 org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car started in 4.344s Module 17/63 org.apache.geronimo.configs/connector-deployer-1_6/3.0-SNAPSHOT/ca started in .032s Module 18/63 org.apache.geronimo.configs/tomcat7-deployer/3.0-SNAPSHOT/car started in .032s Module 19/63 org.apache.geronimo.configs/web-extender/3.0-SNAPSHOT/car started in .016s Module 20/63 org.apache.geronimo.configs/hot-deployer/3.0-SNAPSHOT/car started in .016s Module 21/63 org.apache.geronimo.configs/remote-deploy-tomcat/3.0-SNAPSHOT/car started in 3.906s Module 22/63 org.apache.geronimo.configs/jasper-deployer/3.0-SNAPSHOT/car started in .000s Module 23/63 org.apache.geronimo.configs/myfaces/3.0-SNAPSHOT/car started in .000s Module 24/63 org.apache.geronimo.configs/myfaces-deployer/3.0-SNAPSHOT/car started in 2.953s Module 25/63 org.apache.geronimo.configs/aries/3.0-SNAPSHOT/car started in .000s Module 26/63 org.apache.geronimo.configs/aries-deployer/3.0-SNAPSHOT/car started in .000s Module 27/63 org.apache.geronimo.configs/persistence-jpa20-deployer/3.0-SNAPSHO /car started in .015s Module 28/63 org.apache.geronimo.plugins/pluto-support/3.0-SNAPSHOT/car started in .015s Module 29/63 org.apache.geronimo.plugins/console-tomcat/3.0-SNAPSHOT/car started in 4.062s Module 30/63 org.apache.geronimo.plugins/plugin-console-tomcat/3.0-SNAPSHOT/car started in 4.062s Module 31/63 org.apache.geronimo.plugins.monitoring/mconsole-ds/3.0-SNAPSHOT/ca started in .063s Module 32/63 org.apache.geronimo.plugins.monitoring/mconsole-tomcat/3.0-SNAPSHO /car started in 10.079s Module 33/63 org.apache.geronimo.configs/activemq-broker-blueprint/3.0-SNAPSHOT car started in 1.031s Module 34/63 org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car started in .187s Module 35/63 org.apache.geronimo.plugins/activemq-console-tomcat/3.0-SNAPSHOT/c rstarted in 2.187s Module 36/63 org.apache.geronimo.plugins/debugviews-console-tomcat/3.0-SNAPSHOT car started in 2.579s Module 37/63 org.apache.geronimo.plugins/sysdb-console-tomcat/3.0-SNAPSHOT/car started in 3.406s Module 38/63 org.apache.geronimo.plugins/openejb-console-tomcat/3.0-SNAPSHOT/ca started in 15.625s Module 39/63 org.apache.geronimo.configs/openejb-deployer/3.0-SNAPSHOT/car started in .047s Module 40/63 org.apache.geronimo.configs/openejb-corba-deployer/3.0-SNAPSHOT/ca started in .063s Module 41/63 org.apache.geronimo.configs/j2ee-corba-yoko/3.0-SNAPSHOT/car started in .438s Module 42/63 org.apache.geronimo.configs/openwebbeans-deployer/3.0-SNAPSHOT/car started in .015s Module 43/63 org.apache.geronimo.plugins.monitoring/agent-ds/3.0-SNAPSHOT/car started in .453s Module 44/63 org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car started in 2.281s Module 45/63 org.apache.geronimo.plugins.monitoring/agent-car-jmx/3.0-SNAPSHOT/ ar started in .016s Module 46/63 org.apache.geronimo.configs/welcome-tomcat/3.0-SNAPSHOT/car started in 2.297s Module 47/63 org.apache.geronimo.configs/javamail/3.0-SNAPSHOT/car started in .016s Module 48/63 org.apache.geronimo.pl
[jira] [Issue Comment Edited] (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=13093443#comment-13093443 ] Tina Li edited comment on GERONIMO-6127 at 8/30/11 5:21 AM: Hi Jarek, 1) Server started successfully finally and the cost: Booting Geronimo Kernel (in Java 1.6.0)... Module 1/63 org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car started in .000s Module 2/63 org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car started in .125s Module 3/63 org.apache.geronimo.framework/plugin/3.0-SNAPSHOT/car started in 3.734s Module 4/63 org.apache.geronimo.framework/j2ee-security/3.0-SNAPSHOT/car started in .156s Module 5/63 org.apache.geronimo.framework/server-security-config/3.0-SNAPSHOT/ ar started in .031s Module 6/63 org.apache.geronimo.framework/bundle-recorder/3.0-SNAPSHOT/car started in .000s Module 7/63 org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT car started in .125s Module 8/63 org.apache.geronimo.configs/j2ee-server/3.0-SNAPSHOT/car started in .016s Module 9/63 org.apache.geronimo.configs/j2ee-deployer/3.0-SNAPSHOT/car started in .079s Module 10/63 org.apache.geronimo.configs/bval-deployer/3.0-SNAPSHOT/car started in 1.938s Module 11/63 org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car started in .125s Module 12/63 org.apache.geronimo.configs/system-database/3.0-SNAPSHOT/car started in 2.141s Module 13/63 org.apache.geronimo.configs/openjpa2/3.0-SNAPSHOT/car started in .000s Module 14/63 org.apache.geronimo.configs/openejb/3.0-SNAPSHOT/car started in 3.813s Module 15/63 org.apache.geronimo.configs/jasper/3.0-SNAPSHOT/car started in .015s Module 16/63 org.apache.geronimo.configs/tomcat7/3.0-SNAPSHOT/car started in 4.344s Module 17/63 org.apache.geronimo.configs/connector-deployer-1_6/3.0-SNAPSHOT/ca started in .032s Module 18/63 org.apache.geronimo.configs/tomcat7-deployer/3.0-SNAPSHOT/car started in .032s Module 19/63 org.apache.geronimo.configs/web-extender/3.0-SNAPSHOT/car started in .016s Module 20/63 org.apache.geronimo.configs/hot-deployer/3.0-SNAPSHOT/car started in .016s Module 21/63 org.apache.geronimo.configs/remote-deploy-tomcat/3.0-SNAPSHOT/car started in 3.906s Module 22/63 org.apache.geronimo.configs/jasper-deployer/3.0-SNAPSHOT/car started in .000s Module 23/63 org.apache.geronimo.configs/myfaces/3.0-SNAPSHOT/car started in .000s Module 24/63 org.apache.geronimo.configs/myfaces-deployer/3.0-SNAPSHOT/car started in 2.953s Module 25/63 org.apache.geronimo.configs/aries/3.0-SNAPSHOT/car started in .000s Module 26/63 org.apache.geronimo.configs/aries-deployer/3.0-SNAPSHOT/car started in .000s Module 27/63 org.apache.geronimo.configs/persistence-jpa20-deployer/3.0-SNAPSHO /car started in .015s Module 28/63 org.apache.geronimo.plugins/pluto-support/3.0-SNAPSHOT/car started in .015s Module 29/63 org.apache.geronimo.plugins/console-tomcat/3.0-SNAPSHOT/car started in 4.062s Module 30/63 org.apache.geronimo.plugins/plugin-console-tomcat/3.0-SNAPSHOT/car started in 4.062s Module 31/63 org.apache.geronimo.plugins.monitoring/mconsole-ds/3.0-SNAPSHOT/ca started in .063s Module 32/63 org.apache.geronimo.plugins.monitoring/mconsole-tomcat/3.0-SNAPSHO /car started in 10.079s Module 33/63 org.apache.geronimo.configs/activemq-broker-blueprint/3.0-SNAPSHOT car started in 1.031s Module 34/63 org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car started in .187s Module 35/63 org.apache.geronimo.plugins/activemq-console-tomcat/3.0-SNAPSHOT/c rstarted in 2.187s Module 36/63 org.apache.geronimo.plugins/debugviews-console-tomcat/3.0-SNAPSHOT car started in 2.579s Module 37/63 org.apache.geronimo.plugins/sysdb-console-tomcat/3.0-SNAPSHOT/car started in 3.406s Module 38/63 org.apache.geronimo.plugins/openejb-console-tomcat/3.0-SNAPSHOT/ca started in 15.625s Module 39/63 org.apache.geronimo.configs/openejb-deployer/3.0-SNAPSHOT/car started in .047s Module 40/63 org.apache.geronimo.configs/openejb-corba-deployer/3.0-SNAPSHOT/ca started in .063s Module 41/63 org.apache.geronimo.configs/j2ee-corba-yoko/3.0-SNAPSHOT/car started in .438s Module 42/63 org.apache.geronimo.configs/openwebbeans-deployer/3.0-SNAPSHOT/car started in .015s Module 43/63 org.apache.geronimo.plugins.monitoring/agent-ds/3.0-SNAPSHOT/car started in .453s Module 44/63 org.apache.geronimo.configs/mejb/3.0-SNAPSHOT/car started in 2.281s Module 45/63 org.apache.geronimo.plugins.monitoring/agent-car-jmx/3.0-SNAPSHOT/ ar started in .016s Module 46/63 org.apache.geronimo.configs/welcome-tomcat/3.0-SNAPSHOT/car started in 2.297s Module 47/63 org.apache.geronimo.configs/javamail/3.0-SNAPSHOT/car start
[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=13093453#comment-13093453 ] Jarek Gawor commented on GERONIMO-6127: --- Was the exception same or different (or no exception) from before (before setting the property)? > "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:569) > at > org.apache.geronimo.kernel.basic.Basi
[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=13093457#comment-13093457 ] Ivan commented on GERONIMO-5734: Commit changes to trunk at rev.1163089, might need to print some warning messages if felix runtime is used. > 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] [Commented] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
[ https://issues.apache.org/jira/browse/GERONIMO-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093461#comment-13093461 ] Ivan commented on GERONIMO-6132: Open a JIRA on xbean https://issues.apache.org/jira/browse/XBEAN-183, and commit the changes to trunk. > Not search wired bundles in bundle classloader by default > - > > Key: GERONIMO-6132 > URL: https://issues.apache.org/jira/browse/GERONIMO-6132 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > From the testing result, it seems that all the functions works well without > searching wired bundles. Also, considering that all kinds of Java EE > applications are installed as one bundle, including EAR package, it should > not an issue for user application to finding the resources in the same > application. > I am thinking to change the codes in xbean and geronimo-hook, by default, > wired bundles will not be searched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
[ https://issues.apache.org/jira/browse/GERONIMO-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093462#comment-13093462 ] Ivan commented on GERONIMO-6132: Commit changes to trunk at r1163094 > Not search wired bundles in bundle classloader by default > - > > Key: GERONIMO-6132 > URL: https://issues.apache.org/jira/browse/GERONIMO-6132 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > From the testing result, it seems that all the functions works well without > searching wired bundles. Also, considering that all kinds of Java EE > applications are installed as one bundle, including EAR package, it should > not an issue for user application to finding the resources in the same > application. > I am thinking to change the codes in xbean and geronimo-hook, by default, > wired bundles will not be searched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Release Discussion] ship maintenance releases of application-0.2.2 / util-0.2.1 / blueprint-0.3.2 ?
Hi Devs,
Geronimo 3.0-beta has passed the Java EE 6 full profile tck, and is going
to release soon. But some dependencies are from Aries project, so we are
requesting your supports to release the following 3 components with the
important fixes to our users. Could anybody please help?
*1. **org.apache.aries.application/0.2.2-SNAPSHOT*
ARIES-521: handles zip files without directory entries
ARIES-635: Move the resource bundle to the right directory
ARIES-638: Logging improvements for AriesApplicationManagerImpl
ARIES-667: OBRAriesResolver can return bundle information for bundles with
higher version than expected
ARIES-689: Application OBR resolution fails for optional imports
ARIES-734: Back port improvements made to resolution error messages in OBR
application resolver
*2. org.apache.aries.util/0.2.1-SNAPSHOT*
ARIES-667: OBRAriesResolver can return bundle information for bundles with
higher version than expected
*3. org.apache.aries.blueprint/0.3.2-SNAPSHOT*
ARIES-727 support syntax : ${a+b} in blueprint-ext
regards,
--
Lei Wang (Rex)
rwonly AT apache.org
Re: Question about TransactionManger replacement and initialization
On Aug 29, 2011, at 8:00 PM, viola lu wrote: > If we would like use third-party TransactionManager such as Bitronix > TransactionManger instead of geronimo default transaction manger > implementation, and Hibernate as their persistence layer. It's better if > third-party TransactionManger can be initialized in Application context, > > But can we replace geronimo default transaction manger with a third-party > on geronimo 2.1.5? I tried to create BitronixTransactionMangerGBean , > BitronixTransactionSynchronizationRegistryGBean and change TransactionManger > gbean defintion in transaction plugins plan.xml , but server failed to start > coz of JCA ,system-database start failure, i think it's difficult to replace > geronimo transaction manager. What's the error? Do you care about transaction recovery? IMO how recovery is initiated is not well specified in the spec and I rather doubt other transaction managers do exactly as the geronimo one does. However with enough information on what the tm expects we should be able to get it to work. Ignoring recovery should make the problem simpler. > > or Bind the third-party TransactoinManger into our jndi tree with another > different name (java:bintronixmanager,java:comp/env/BintronixUserTransaction, > end-user can lookup it in its application code, but when build > PersitenceUnitGBean , its reference TransactionManager refers to > TransactionManagerImpl (geronimo default transaction manger). I don't recommend this. thanks david jencks > > Is there other way to make this happen? I > > Appreciate your help! > > > -- > viola > > Apache Geronimo >
