Re: [OSGi] Support for RFC 124?
Davanum Srinivas wrote: Folks, Any interest in support for RFC 124, A Component Model for OSGi? http://www.osgi.org/download/osgi-4.2-early-draft.pdf This is in addition to typical J2EE artifacts that we already support. thanks, dims Time, I think, to give this thread a kick. There are lots of different aspects to this, so I think we should first make an attempt at deciding what the target goal is here. RFC 124 (aka, the blueprint service) is inherently an OSGi thing, so first we need to address what it means to add OSGi to Geronimo. And, I think, in general, this really means OSGi as a Geronimo application programming model. This can have multiple meanings. One approach, already under discussion in the Whence Geronimo kernel? thread would be rearchitect the Geronimo kernel around OSGi bundles and the OSGi classloading model. In this mode, an application model should be fairly simple to add, though there may be some issues of bridging between the OSGi bundle world and the JEE programming model. Additions like the blueprint service might be directly usable within the Geronimo kernel for assembly and injection. Another approach would be to add an OSGi application container to Geronimo. This would allow OSGi/blueprint-based applications to be hosted on Geronimo, and there may be some Geronimo services that get exposed to the apps, but the apps run in their own separate environment. The container approach is, I believe, probably the easier path, but we I think we lose a lot of the advantages of the OSGi model in other places. Also, OSGi is working on a number of additional RFCs that will add different JEE concepts to the platform. I'd hate to think that Geronimo might need to maintain two versions of each of these pieces, one for the OSGi container and one for the non-OSGi world. Anyway, I think regardless of the implementation approach, we need to start discussing this in terms of what does it mean to host an OSGi application on Geronimo?. Here are a few questions that immediately come to mind: 1. How are applications deployed? Is there some higher-level deployment model than the bundle level? 2. What services are available Geronimo application environment? Blueprint is certainly one service, what others do we need? 3. How is the config-admin service managed? Do we need Geronimo console access and editting of config admin properties? 4. Are there any bridges from the OSGi world to the JEE world? For example, is is possible to export service registry instances to JNDI? I think this is a good starting point for discussing ideasI'm sure there are additional questions that will come up in the discussions. Rick
Unable to find org.apache.geronimo.connector.outbound.AbstractConnectionManager in geronimo source code
Hi All, I am searching class org.apache.geronimo.connector.outbound.AbstractConnectionManager in geronimo source code but somehow I am not able to find it. I have looked into svn as well and it does not seem to be present there as well. In eclipse I see .class file but not the .java file. This .class file seems to be coming from geronimo-connector-2.1.2.jar. I have downloaded/build the source from trunk so why does it still show 2.1.2??? Can someone please suggest where I can find the AbstractConnectionManager.java file? Thanks Ashish
Re: Unable to find org.apache.geronimo.connector.outbound.AbstractConnectionManager in geronimo source code
On Apr 1, 2009, at 4:16 AM, Ashish Jain wrote: Hi All, I am searching class org.apache.geronimo.connector.outbound.AbstractConnectionManager in geronimo source code but somehow I am not able to find it. I have looked into svn as well and it does not seem to be present there as well. In eclipse I see .class file but not the .java file. This .class file seems to be coming from geronimo- connector-2.1.2.jar. I have downloaded/build the source from trunk so why does it still show 2.1.2??? Can someone please suggest where I can find the AbstractConnectionManager.java file? The connector code and the transaction code are a geronimo component under https://svn.apache.org/repos/asf/geronimo/components/txmanager You want the most recent release: https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.2 thanks david jencks Thanks Ashish
Re: Unable to find org.apache.geronimo.connector.outbound.AbstractConnectionManager in geronimo source code
Thanks a lot David. On Wed, Apr 1, 2009 at 5:44 PM, David Jencks david_jen...@yahoo.com wrote: On Apr 1, 2009, at 4:16 AM, Ashish Jain wrote: Hi All, I am searching class org.apache.geronimo.connector.outbound.AbstractConnectionManager in geronimo source code but somehow I am not able to find it. I have looked into svn as well and it does not seem to be present there as well. In eclipse I see .class file but not the .java file. This .class file seems to be coming from geronimo-connector-2.1.2.jar. I have downloaded/build the source from trunk so why does it still show 2.1.2??? Can someone please suggest where I can find the AbstractConnectionManager.java file? The connector code and the transaction code are a geronimo component under https://svn.apache.org/repos/asf/geronimo/components/txmanager You want the most recent release: https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-2.1.2 thanks david jencks Thanks Ashish
WASCE release/roadmap
Hi Is there a release roadmap for WASCE (which is based on Geronimo)? When can we expect the next release of WASCE? Regards zambak -- View this message in context: http://www.nabble.com/WASCE-release-roadmap-tp22830770s134p22830770.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: [VOTE] Release Geronimo Server 2.1.4 RC2
too late to make a difference but as a gesture of encoragement +1 david jencks On Mar 26, 2009, at 3:20 PM, Joe Bohn wrote: All, I've prepared a second release candidate (RC2) of Geronimo Server 2.1.4 for your review and vote. The only differences from rc1 are: - addition of a missing license header in plugins/console/console- filter/src/main/resources/XSRF.js - removal of an extraneous (TBD) in README.txt The source for rc2 is Rev758842 from the following svn branch: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.4/ When the release vote is approved, I will svn mv the code to: https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/ An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.tar.gz OR http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-2.1.4-src.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/ contains the 10 server binary distributions to be released (framework, tomcat/ jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES, README, NOTICE, LICENSE, DISCLAIMER, and source code archives for the release. These extra txt files were included so that they could be leveraged by GEP if necessary (they are also included in the assembly images). For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-jetty6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-javaee5-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-tomcat6-minimal-2.1.4-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.4-dist-rc2/geronimo-framework-2.1.4-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.4-rc2/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo Server 2.1.4 [ ] 0 No opinion [ ] -1 Do not release Geronimo Server 2.1.4 (please provide rationale) The voting will be open for 72 hours or until sufficient input has been received and the tck results have been verified. Thanks, Joe
Thinking about a 2.2 release
I wonder if we should think about a 2.2 release based on javaee 5. Trunk has a lot of improvements over 2.1 and I think it would be good for our users to get something out before we do any really major osgi- related refactorings. It would be great if we could provide javaee 6 previews for the stuff we have done but this seems less essential to me at the moment given the rapidly receding timeline for the ee6 spec. Stuff that makes plugins a lot easier: -- transitive dependencies from maven in car-maven-plugin -- gbean annotations -- classloader-per-jar (not yet in trunk) updated external project support: jaspi support (still needs tck) jetty 7 (@eclipse, this will now be servlet 2.5 compliant) activemq 5 potential ee6 features: openejb ejb 3.1 support connector 1.6 support jetty 8 (proposed) servelt 3.0 support openjpa jpa 2.0 support (??? not sure how far along this is) I wonder if we can release these somewhat separately as early access plugins. what do people think? thanks david jencks
[BUILD] trunk: Failed for Revision: 761116
Geronimo Revision: 761116 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090401/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090401
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 35 minutes 30 seconds
[INFO] Finished at: Wed Apr 01 21:39:20 EDT 2009
[INFO] Final Memory: 681M/980M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090401/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:41.411
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:00:59.148)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.293)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.483)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.935)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:16.411)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:27.876)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:54.166)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.659)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:46.467)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:42.702)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:31.049)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:32.911)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:33.053)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:50.940)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:54.461)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.583)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.957)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.275)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:37.754) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.826)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
Re: Thinking about a 2.2 release
On Apr 1, 2009, at 11:40 AM, David Jencks wrote: I wonder if we should think about a 2.2 release based on javaee 5. Trunk has a lot of improvements over 2.1 and I think it would be good for our users to get something out before we do any really major osgi-related refactorings. It would be great if we could provide javaee 6 previews for the stuff we have done but this seems less essential to me at the moment given the rapidly receding timeline for the ee6 spec. A javaee 5 release using either OpenEJB 3.0.1 or 3.1.x would be good to see IMO. -David
Re: WASCE release/roadmap
For my observation, For a major release, WASCE is 3 months later than Geronimo. For a minor release, only one month around to have a WASCE release. Now Geronimo 2.1.4 is released, a followup WASCE release will be coming soon! Regards, Forrest
[jira] Created: (GERONIMO-4609) Console could not display correctly on Chinese platfrom
Console could not display correctly on Chinese platfrom --- Key: GERONIMO-4609 URL: https://issues.apache.org/jira/browse/GERONIMO-4609 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Environment: IBM JDK 1.6 Windows XP Reporter: Ivan The console could not display correctly on Chinese platfrom. Not sure from which daily build, it occured. Still investigate it now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
