Re: [announce] Welcome Apache Geronimo's newest committer - Rick McGuire
Congrats! :) geir Geir Magnusson Jr wrote: In recognition of his contributions and participation in the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Rick McGuire. Rick has contributed in many places, and is a pleasure to work with, and we look forward to his continued involvement as a committer. Please join us in congratulating Rick. The Apache Geronimo PMC
[jira] Created: (GERONIMO-1894) JPA @JoinTable annotation is not retained in runtime
JPA @JoinTable annotation is not retained in runtime Key: GERONIMO-1894 URL: http://issues.apache.org/jira/browse/GERONIMO-1894 Project: Geronimo Type: Bug Security: public (Regular issues) Components: specs Versions: 1.x Reporter: Andrus Adamchik Priority: Minor EJB3, JPA spec - @JoinTable annotation has no retention policy. This looks like a bug in the spec (there is no retention policy mentioned there), but this makes the annotation unusable as it is not preserved in runtime. Also the rest of the annotations have retention policy set to runtime, confirming again that this is a spec typo. Somebody please apply the attached patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1894) JPA @JoinTable annotation is not retained in runtime
[ http://issues.apache.org/jira/browse/GERONIMO-1894?page=all ] Andrus Adamchik updated GERONIMO-1894: -- Attachment: patch.txt JPA @JoinTable annotation is not retained in runtime Key: GERONIMO-1894 URL: http://issues.apache.org/jira/browse/GERONIMO-1894 Project: Geronimo Type: Bug Security: public(Regular issues) Components: specs Versions: 1.x Reporter: Andrus Adamchik Priority: Minor Attachments: patch.txt EJB3, JPA spec - @JoinTable annotation has no retention policy. This looks like a bug in the spec (there is no retention policy mentioned there), but this makes the annotation unusable as it is not preserved in runtime. Also the rest of the annotations have retention policy set to runtime, confirming again that this is a spec typo. Somebody please apply the attached patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1895) Issues with geronimo specs
Issues with geronimo specs -- Key: GERONIMO-1895 URL: http://issues.apache.org/jira/browse/GERONIMO-1895 Project: Geronimo Type: Bug Security: public (Regular issues) Components: specs Versions: 1.1 Reporter: Kevan Miller Priority: Blocker Fix For: 1.1 The following public/protected extensions have been added to the javax.mail.internet.* spec. You can't do that. They must be removed prior to 1.1 ship. javax.mail.internet.MimeBodyPart.MIME_DECODEFILENAME javax.mail.internet.MimeBodyPart.MIME_SETDEFAULTTEXTCHARSET javax.mail.internet.MimeUtility.getDefaultMIMECharset() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1894) JPA @JoinTable annotation is not retained in runtime
[ http://issues.apache.org/jira/browse/GERONIMO-1894?page=all ] Jeff Genender closed GERONIMO-1894: --- Resolution: Fixed Assign To: Jeff Genender Sendinggeronimo-spec-jpa/src/main/java/javax/persistence/JoinTable.java Transmitting file data . Committed revision 396128. JPA @JoinTable annotation is not retained in runtime Key: GERONIMO-1894 URL: http://issues.apache.org/jira/browse/GERONIMO-1894 Project: Geronimo Type: Bug Security: public(Regular issues) Components: specs Versions: 1.x Reporter: Andrus Adamchik Assignee: Jeff Genender Priority: Minor Attachments: patch.txt EJB3, JPA spec - @JoinTable annotation has no retention policy. This looks like a bug in the spec (there is no retention policy mentioned there), but this makes the annotation unusable as it is not preserved in runtime. Also the rest of the annotations have retention policy set to runtime, confirming again that this is a spec typo. Somebody please apply the attached patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1896) configs/client-builder requires activemq-core-3.2.1
configs/client-builder requires activemq-core-3.2.1 --- Key: GERONIMO-1896 URL: http://issues.apache.org/jira/browse/GERONIMO-1896 Project: Geronimo Type: Bug Security: public (Regular issues) Components: buildsystem Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1896) configs/client-deployer requires activemq-core-3.2.1
[ http://issues.apache.org/jira/browse/GERONIMO-1896?page=all ] Aaron Mulder updated GERONIMO-1896: --- Summary: configs/client-deployer requires activemq-core-3.2.1 (was: configs/client-builder requires activemq-core-3.2.1) Description: Should be 3.2.4 or whatever configs/client-deployer requires activemq-core-3.2.1 Key: GERONIMO-1896 URL: http://issues.apache.org/jira/browse/GERONIMO-1896 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.1 Should be 3.2.4 or whatever -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-1896) configs/client-deployer requires activemq-core-3.2.1
[ http://issues.apache.org/jira/browse/GERONIMO-1896?page=all ] Aaron Mulder resolved GERONIMO-1896: Resolution: Fixed Assign To: Aaron Mulder configs/client-deployer requires activemq-core-3.2.1 Key: GERONIMO-1896 URL: http://issues.apache.org/jira/browse/GERONIMO-1896 Project: Geronimo Type: Bug Security: public(Regular issues) Components: buildsystem Versions: 1.1 Reporter: Aaron Mulder Assignee: Aaron Mulder Fix For: 1.1 Should be 3.2.4 or whatever -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: how to get the latest stable build?
You can try: svn co https://svn.apache.org/repos/asf/geronimo/branches/1.1/ It's not quite stable yet but it's quickly moving in that direction. The 1.0 branch is more stable but will be obsolete shortly, so I'd recommend 1.1. Thanks, Aaron On 4/22/06, argyn [EMAIL PROTECTED] wrote: hello i'm totally new to Geronimo source code base. i'd like to play with org/apache/geronimo/security/jacc package. for that i need to checkout the latest stable code. how? thanks in advance argyn
where's JACC provider implementation?
i started looking into code in org.apache.geronimo.security.jacc http://geronimo.apache.org/api/org/apache/geronimo/security/jacc/package-summary.html package. basically, i want to figure out how to plug the custom JACC provider into Geronimo, so i need to look at the existing ones. where's your default jacc provider? thanks, argyn
Re: where's JACC provider implementation?
Look under the security module. argyn wrote: i started looking into code in org.apache.geronimo.security.jacc http://geronimo.apache.org/api/org/apache/geronimo/security/jacc/package-summary.html package. basically, i want to figure out how to plug the custom JACC provider into Geronimo, so i need to look at the existing ones. where's your default jacc provider? thanks, argyn
Re: how to get the latest stable build?
I thought someone (david jencks?) mentioned 1.2 branch. is it trunc? if it's not stable, then do you have a less unstable tag there for me to download? thanks argyn Aaron Mulder wrote: You can try: svn co https://svn.apache.org/repos/asf/geronimo/branches/1.1/ It's not quite stable yet but it's quickly moving in that direction. The 1.0 branch is more stable but will be obsolete shortly, so I'd recommend 1.1. Thanks, Aaron On 4/22/06, argyn [EMAIL PROTECTED] wrote: hello i'm totally new to Geronimo source code base. i'd like to play with org/apache/geronimo/security/jacc package. for that i need to checkout the latest stable code. how? thanks in advance argyn
Re: how to get the latest stable build?
David Jencks wrote: On Apr 22, 2006, at 3:49 PM, argyn wrote: I thought someone (david jencks?) mentioned 1.2 branch. is it trunc? if it's not stable, then do you have a less unstable tag there for me to download? You should look at 1.2 (==trunk) as it has the half of jacc plugability that I've had a chance to implement. svn co https://svn.apache.org/repos/asf/geronimo/trunk thanks david jencks i co'd trunk, and am trying to build and run it. it seems that there's not much info on building with maven2. thanks, argyn
Re: how to get the latest stable build?
m2 is not ready yet. Do a: maven m:co then a maven new argyn wrote: David Jencks wrote: On Apr 22, 2006, at 3:49 PM, argyn wrote: I thought someone (david jencks?) mentioned 1.2 branch. is it trunc? if it's not stable, then do you have a less unstable tag there for me to download? You should look at 1.2 (==trunk) as it has the half of jacc plugability that I've had a chance to implement. svn co https://svn.apache.org/repos/asf/geronimo/trunk thanks david jencks i co'd trunk, and am trying to build and run it. it seems that there's not much info on building with maven2. thanks, argyn
Directory Update (Jeff?)
All, While working on the plugins I found that our Directory is out of date (0.9.2 vs latest 0.9.3 on iBiblio). I also found that if we just take the latest of everything Directory-related it blows up (in particular, mina 0.9.0 doesn't work, but 0.8.2 appears to). Can someone test a good combination of all the Directory-related libs and update our etc/project.properties accordingly? Jeff, I think you did the original Directory integration, I'm not sure if you want to bite on this. It's not a huge deal if we ship G 1.1 a point release of Directory behind, but it would be nice if we could update. Thanks, Aaron
Re: Directory Update (Jeff?)
Yeah, I can take a look. Jeff Aaron Mulder wrote: All, While working on the plugins I found that our Directory is out of date (0.9.2 vs latest 0.9.3 on iBiblio). I also found that if we just take the latest of everything Directory-related it blows up (in particular, mina 0.9.0 doesn't work, but 0.8.2 appears to). Can someone test a good combination of all the Directory-related libs and update our etc/project.properties accordingly? Jeff, I think you did the original Directory integration, I'm not sure if you want to bite on this. It's not a huge deal if we ship G 1.1 a point release of Directory behind, but it would be nice if we could update. Thanks, Aaron
[jira] Reopened: (GERONIMO-1871) Unable to deploy Tapestry app due to classloading issue
[ http://issues.apache.org/jira/browse/GERONIMO-1871?page=all ] Jeff Genender reopened GERONIMO-1871: - Great fix Gianny. Can we please get in in 1.1? This is critical enough that I think this needs to be in the next release. Unable to deploy Tapestry app due to classloading issue --- Key: GERONIMO-1871 URL: http://issues.apache.org/jira/browse/GERONIMO-1871 Project: Geronimo Type: Bug Security: public(Regular issues) Components: kernel Versions: 1.2 Environment: Windows XP Reporter: Bryan Noll Assignee: Gianny Damour Priority: Critical Here is the stacktrace encountered when attempting to deploy a Tapestry application. Please scroll down to see more info after the stack trace. org.apache.hivemind.ApplicationRuntimeException: Error: Module hivemind is duplicated! Definition in jar:file:/C:/tools/geronimo-1.2-SNAPSHOT/config-store/42/war/WEB-INF/lib/hivemind-1.1.jar!/META-INF/hivemodule.xml has been ignored in favor of existing definition from jar:file:/C:/tools/geronimo-1.2-SNAPSHOT/config-store/42/war/WEB-INF/lib/hivemind-1.1.jar!/META-INF/hivemodule.xml. org.apache.hivemind.impl.StrictErrorHandler.error(StrictErrorHandler.java:39) org.apache.hivemind.impl.RegistryInfrastructureConstructor.addModuleDescriptor(RegistryInfrastructureConstructor.java:202) org.apache.hivemind.impl.RegistryBuilder.processModuleDescriptorProvider(RegistryBuilder.java:168) org.apache.hivemind.impl.RegistryBuilder.constructRegistry(RegistryBuilder.java:143) org.apache.tapestry.ApplicationServlet.constructRegistry(ApplicationServlet.java:253) org.apache.tapestry.ApplicationServlet.init(ApplicationServlet.java:194) org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915) org.apache.catalina.core.StandardContext.start(StandardContext.java:4176) org.apache.geronimo.tomcat.GeronimoStandardContext.access$101(GeronimoStandardContext.java:66) org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:270) org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31) org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:185) org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:287) org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke(generated) net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$7af7fb0d.addContext(generated) org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:416) org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:936) org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:325) org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:110) org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:132) org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:537) org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:208) org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans(Configuration.java:315) org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$$7f4b4a9b.invoke(generated) net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:178) org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:173) org.apache.geronimo.kernel.config.ConfigurationManagerImpl.start(ConfigurationManagerImpl.java:229)
Re: [jira] Closed: (GERONIMO-1871) Unable to deploy Tapestry app due to classloading issue
+1 absolutely Can you do it? -dain On Apr 22, 2006, at 7:36 PM, Jeff Genender wrote: Can we get this in 1.1? This is a pretty nasty bug. Jeff Gianny Damour (JIRA) wrote: [ http://issues.apache.org/jira/browse/GERONIMO-1871?page=all ] Gianny Damour closed GERONIMO-1871: --- Resolution: Fixed The problem was that the TCCL was set to the Tomcat WebAppClassLoader and not the Geronimo TomcatClassLoader. WebAppClassLoader was defining all the jars in WEB-INF/lib, its parent was TomcatClassLoader, which was also defining these jars. Hence this duplication. Unable to deploy Tapestry app due to classloading issue --- Key: GERONIMO-1871 URL: http://issues.apache.org/jira/browse/GERONIMO-1871 Project: Geronimo Type: Bug Security: public(Regular issues) Components: kernel Versions: 1.2 Environment: Windows XP Reporter: Bryan Noll Assignee: Gianny Damour Priority: Critical Here is the stacktrace encountered when attempting to deploy a Tapestry application. Please scroll down to see more info after the stack trace. org.apache.hivemind.ApplicationRuntimeException: Error: Module hivemind is duplicated! Definition in jar:file:/C:/tools/ geronimo-1.2-SNAPSHOT/config-store/42/war/WEB-INF/lib/ hivemind-1.1.jar!/META-INF/hivemodule.xml has been ignored in favor of existing definition from jar:file:/C:/tools/geronimo-1.2- SNAPSHOT/config-store/42/war/WEB-INF/lib/hivemind-1.1.jar!/META- INF/hivemodule.xml. org.apache.hivemind.impl.StrictErrorHandler.error (StrictErrorHandler.java:39) org.apache.hivemind.impl.RegistryInfrastructureConstructor.addModule Descriptor(RegistryInfrastructureConstructor.java:202) org.apache.hivemind.impl.RegistryBuilder.processModuleDescriptorProv ider(RegistryBuilder.java:168) org.apache.hivemind.impl.RegistryBuilder.constructRegistry (RegistryBuilder.java:143) org.apache.tapestry.ApplicationServlet.constructRegistry (ApplicationServlet.java:253) org.apache.tapestry.ApplicationServlet.init (ApplicationServlet.java:194) org.apache.catalina.core.StandardWrapper.loadServlet (StandardWrapper.java:1105) org.apache.catalina.core.StandardWrapper.load (StandardWrapper.java:932) org.apache.catalina.core.StandardContext.loadOnStartup (StandardContext.java:3915) org.apache.catalina.core.StandardContext.start (StandardContext.java:4176) org.apache.geronimo.tomcat.GeronimoStandardContext.access$101 (GeronimoStandardContext.java:66) org.apache.geronimo.tomcat.GeronimoStandardContext $SystemMethodValve.invoke(GeronimoStandardContext.java:270) org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke (GeronimoBeforeAfterValve.java:31) org.apache.geronimo.tomcat.GeronimoStandardContext.start (GeronimoStandardContext.java:185) org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:759) org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:739) org.apache.catalina.core.StandardHost.addChild(StandardHost.java: 524) org.apache.geronimo.tomcat.TomcatContainer.addContext (TomcatContainer.java:287) org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$ $9370b073.invoke(generated) net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java:118) org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java:800) org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java:57) org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java:36) org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java:96) org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$ $7af7fb0d.addContext(generated) org.apache.geronimo.tomcat.TomcatWebAppContext.doStart (TomcatWebAppContext.java:416) org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance (GBeanInstance.java:936) org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStar t(GBeanInstanceState.java:325) org.apache.geronimo.gbean.runtime.GBeanInstanceState.start (GBeanInstanceState.java:110) org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive( GBeanInstanceState.java:132) org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive (GBeanInstance.java:537) org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean (BasicKernel.java:208) org.apache.geronimo.kernel.config.Configuration.startRecursiveGBeans (Configuration.java:315) org.apache.geronimo.kernel.config.Configuration$$FastClassByCGLIB$ $7f4b4a9b.invoke(generated) net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) org.apache.geronimo.gbean.runtime.GBeanOperation.invoke
Re: [jira] Closed: (GERONIMO-1871) Unable to deploy Tapestry app due to classloading issue
Actually, the fix is already in 1.1 (I just checked via the Subversion Commits tab that the commit has not disappeared into the ether). Thanks, Gianny Dain Sundstrom wrote: +1 absolutely Can you do it? -dain On Apr 22, 2006, at 7:36 PM, Jeff Genender wrote: Can we get this in 1.1? This is a pretty nasty bug. Jeff Gianny Damour (JIRA) wrote: [ http://issues.apache.org/jira/browse/GERONIMO-1871?page=all ] Gianny Damour closed GERONIMO-1871: --- Resolution: Fixed The problem was that the TCCL was set to the Tomcat WebAppClassLoader and not the Geronimo TomcatClassLoader. WebAppClassLoader was defining all the jars in WEB-INF/lib, its parent was TomcatClassLoader, which was also defining these jars. Hence this duplication. Unable to deploy Tapestry app due to classloading issue --- Key: GERONIMO-1871 URL: http://issues.apache.org/jira/browse/GERONIMO-1871 Project: Geronimo Type: Bug Security: public(Regular issues) Components: kernel Versions: 1.2 Environment: Windows XP Reporter: Bryan Noll Assignee: Gianny Damour Priority: Critical
Re: Verbiage: Change configuration to module?
+1 Aaron Mulder wrote: All, How would you feel about referring to configurations (e.g. a group of GBeans with own ID and classloader) as a module instead? It seems like configuration can be confusing, as it more traditionally refers to a larger scope like an entire installation. For example, if you say you have two different WebLogic configurations or two different Apache (HTTP) configurations, you're saying either you have two installations, or you have two totally separate product configurations available for the same product installation. You're not saying you have an app and a database pool within one runtime, but that's what two different configurations presently would mean in relation to Geronimo. It seems like it would be clearer to say that a Geronimo installation loads many modules, and each module includes many components (GBeans). I'm not proposing that we go changing class names and stuff, but I'm proposing that we make a concerted effort in our documentation and presentations to present the name of the unit with an ID and classloader holding many components as a module. What do you think? Thanks, Aaron
