Re: [Discussion] How about upgrade Dojo version to 1.4.0 for Geronimo 3.0?
Agree , we should test the functions that were using old dojo to see if they are still working after upgrading to dojo 1.4.0. On Wed, Jan 6, 2010 at 2:54 PM, Ivan wrote: > Is the new version compatable with the old one ? If yes, I think we could > upgrade it. > > 2010/1/6 Delos > > Hi, >> >> Dojo 1.4.0 has released on Dec.15. How about upgrade Dojo version to >> 1.4.0 for Geronimo 3.0? >> >> Some new Widgets are provided, such as EnhancedDataGrid; meanswhile a lot >> of refactoring work makes it faster than before. >> >> BTW, for you to feel the improvement of Dojo 1.4.0, I have uploaded a demo >> of pluto 2.0 and Dojo 1.4.0 here >> https://svn.apache.org/repos/asf/geronimo/sandbox/delos/portlet+dojo/portlet-dojo1.4.0-demo.zip. >> >> >> Steps to run demo >> 1. Extract the zip >> 2. launch "bin/startup.sh" or bin/startup.bat" >> 3. visit "http://localhost:8080/pluto/portal/BundlePage“, you will see a >> portlet showing OSGI bundles with dojo 1.4.0 widgets >> >> Upgrade to Dojo 1.4.0, any comments? >> >> Thanks! >> -- >> Best Regards, >> >> Delos >> > > > > -- > Ivan > -- Shawn
[jira] Commented: (GERONIMO-5008) Create util methods for all the Geronimo components
[ https://issues.apache.org/jira/browse/GERONIMO-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797018#action_12797018 ] Ivan commented on GERONIMO-5008: Move all the util methods in geronimo-kernel/util package, and currently, there are three util class, which are FileUtils,IOUtils,JarUtils. Commit the changes to trunk At revision: 896339. > Create util methods for all the Geronimo components > --- > > Key: GERONIMO-5008 > URL: https://issues.apache.org/jira/browse/GERONIMO-5008 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan >Priority: Minor > Fix For: 3.0 > > > Create util methods for all the Geronimo components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r896318 - in /geronimo/server/branches/2.1/framework/modules: geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java geronimo-deploy-tool/src/main/ja
Thanks Ivan! I've configured SVN accordingly.
-Jack
On Wed, Jan 6, 2010 at 3:05 PM, Ivan wrote:
> Hi, Jack:
> I found a link for it in our wiki, it might be useful.
> http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html
>
> 2010/1/6 Jack Cai
>>
>> Thanks Jarek for catching that!
>>
>> I've set the svn:keywords properties of those new files now. I've also
>> configured my SVN to use enable-auto-props to add these properties
>> automatically in future.
>>
>> -Jack
>>
>> On Wed, Jan 6, 2010 at 12:39 PM, Jarek Gawor wrote:
>> > Jack,
>> >
>> > I think you also need to add svn:keywords svn property to these new
>> > files so that Rev and Date keywords get expanded properly.
>> >
>> > Jarek
>> >
>> > On Tue, Jan 5, 2010 at 11:16 PM, wrote:
>> >> Author: caijunj
>> >> Date: Wed Jan 6 04:16:46 2010
>> >> New Revision: 896318
>> >>
>> >> URL: http://svn.apache.org/viewvc?rev=896318&view=rev
>> >> Log:
>> >> GERONIMO-3003 - Fix the revision and date field in two new files
>> >>
>> >> Modified:
>> >>
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>> >>
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>> >>
>> >> Modified:
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>> >> URL:
>> >> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java?rev=896318&r1=896317&r2=896318&view=diff
>> >>
>> >> ==
>> >> ---
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>> >> (original)
>> >> +++
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>> >> Wed Jan 6 04:16:46 2010
>> >> @@ -18,7 +18,7 @@
>> >>
>> >>
>> >> /**
>> >> - * @version $Rev: 515007 $ $Date: 2007-03-06 18:26:41 +1100 (Tue, 06
>> >> Mar 2007) $
>> >> + * @version $Rev$ $Date$
>> >> */
>> >> public class EncryptCommandMetaData extends BaseCommandMetaData {
>> >> public static final CommandMetaData META_DATA = new
>> >> EncryptCommandMetaData();
>> >>
>> >> Modified:
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>> >> URL:
>> >> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java?rev=896318&r1=896317&r2=896318&view=diff
>> >>
>> >> ==
>> >> ---
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>> >> (original)
>> >> +++
>> >> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>> >> Wed Jan 6 04:16:46 2010
>> >> @@ -31,7 +31,7 @@
>> >> /**
>> >> * The CLI command to encrypt a given string.
>> >> *
>> >> - * @version $Rev: 617588 $ $Date: 2008-02-02 02:20:07 +0800 (Sat, 02
>> >> Feb 2008) $
>> >> + * @version $Rev$ $Date$
>> >> */
>> >> public class CommandEncrypt extends AbstractCommand {
>> >>
>> >>
>> >>
>> >>
>> >
>
>
>
> --
> Ivan
>
Re: svn commit: r896318 - in /geronimo/server/branches/2.1/framework/modules: geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java geronimo-deploy-tool/src/main/ja
Hi, Jack:
I found a link for it in our wiki, it might be useful.
http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html
2010/1/6 Jack Cai
> Thanks Jarek for catching that!
>
> I've set the svn:keywords properties of those new files now. I've also
> configured my SVN to use enable-auto-props to add these properties
> automatically in future.
>
> -Jack
>
> On Wed, Jan 6, 2010 at 12:39 PM, Jarek Gawor wrote:
> > Jack,
> >
> > I think you also need to add svn:keywords svn property to these new
> > files so that Rev and Date keywords get expanded properly.
> >
> > Jarek
> >
> > On Tue, Jan 5, 2010 at 11:16 PM, wrote:
> >> Author: caijunj
> >> Date: Wed Jan 6 04:16:46 2010
> >> New Revision: 896318
> >>
> >> URL: http://svn.apache.org/viewvc?rev=896318&view=rev
> >> Log:
> >> GERONIMO-3003 - Fix the revision and date field in two new files
> >>
> >> Modified:
> >>
>
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
> >>
>
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
> >>
> >> Modified:
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
> >> URL:
> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java?rev=896318&r1=896317&r2=896318&view=diff
> >>
> ==
> >> ---
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
> (original)
> >> +++
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
> Wed Jan 6 04:16:46 2010
> >> @@ -18,7 +18,7 @@
> >>
> >>
> >> /**
> >> - * @version $Rev: 515007 $ $Date: 2007-03-06 18:26:41 +1100 (Tue, 06
> Mar 2007) $
> >> + * @version $Rev$ $Date$
> >> */
> >> public class EncryptCommandMetaData extends BaseCommandMetaData {
> >> public static final CommandMetaData META_DATA = new
> EncryptCommandMetaData();
> >>
> >> Modified:
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
> >> URL:
> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java?rev=896318&r1=896317&r2=896318&view=diff
> >>
> ==
> >> ---
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
> (original)
> >> +++
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
> Wed Jan 6 04:16:46 2010
> >> @@ -31,7 +31,7 @@
> >> /**
> >> * The CLI command to encrypt a given string.
> >> *
> >> - * @version $Rev: 617588 $ $Date: 2008-02-02 02:20:07 +0800 (Sat, 02
> Feb 2008) $
> >> + * @version $Rev$ $Date$
> >> */
> >> public class CommandEncrypt extends AbstractCommand {
> >>
> >>
> >>
> >>
> >
>
--
Ivan
Re: svn commit: r896318 - in /geronimo/server/branches/2.1/framework/modules: geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java geronimo-deploy-tool/src/main/ja
Thanks Jarek for catching that!
I've set the svn:keywords properties of those new files now. I've also
configured my SVN to use enable-auto-props to add these properties
automatically in future.
-Jack
On Wed, Jan 6, 2010 at 12:39 PM, Jarek Gawor wrote:
> Jack,
>
> I think you also need to add svn:keywords svn property to these new
> files so that Rev and Date keywords get expanded properly.
>
> Jarek
>
> On Tue, Jan 5, 2010 at 11:16 PM, wrote:
>> Author: caijunj
>> Date: Wed Jan 6 04:16:46 2010
>> New Revision: 896318
>>
>> URL: http://svn.apache.org/viewvc?rev=896318&view=rev
>> Log:
>> GERONIMO-3003 - Fix the revision and date field in two new files
>>
>> Modified:
>>
>> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>>
>> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>>
>> Modified:
>> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>> URL:
>> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java?rev=896318&r1=896317&r2=896318&view=diff
>> ==
>> ---
>> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>> (original)
>> +++
>> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>> Wed Jan 6 04:16:46 2010
>> @@ -18,7 +18,7 @@
>>
>>
>> /**
>> - * @version $Rev: 515007 $ $Date: 2007-03-06 18:26:41 +1100 (Tue, 06 Mar
>> 2007) $
>> + * @version $Rev$ $Date$
>> */
>> public class EncryptCommandMetaData extends BaseCommandMetaData {
>> public static final CommandMetaData META_DATA = new
>> EncryptCommandMetaData();
>>
>> Modified:
>> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>> URL:
>> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java?rev=896318&r1=896317&r2=896318&view=diff
>> ==
>> ---
>> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>> (original)
>> +++
>> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>> Wed Jan 6 04:16:46 2010
>> @@ -31,7 +31,7 @@
>> /**
>> * The CLI command to encrypt a given string.
>> *
>> - * @version $Rev: 617588 $ $Date: 2008-02-02 02:20:07 +0800 (Sat, 02 Feb
>> 2008) $
>> + * @version $Rev$ $Date$
>> */
>> public class CommandEncrypt extends AbstractCommand {
>>
>>
>>
>>
>
[jira] Commented: (GERONIMO-5011) EJB Web Service security not working at all in G 2.2
[ https://issues.apache.org/jira/browse/GERONIMO-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797015#action_12797015 ] Ivan commented on GERONIMO-5011: Hi, Łukasz At the first glance at it, I think you might need a securty setting in the deployment plan, which would define the mapping relation between the role and user/group principal. There are some samples in the testsuite, please refer to https://svn.apache.org/repos/asf/geronimo/server/branches/2.2/testsuite/webservices-testsuite/jaxws-tests/jaxws-ejb-sec > EJB Web Service security not working at all in G 2.2 > > > Key: GERONIMO-5011 > URL: https://issues.apache.org/jira/browse/GERONIMO-5011 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 > Environment: Geronimo 2.2 with Tomcat 6, Windows XP, Java 6 >Reporter: Łukasz Budnik >Priority: Blocker > Attachments: secure-ejb-web-service.zip > > > EJB Web Service security was working in 2.1.x. Now, there are exceptions > thrown. > openejb-jar.xml: > > > HelloWebService > > geronimo-admin > CONFIDENTIAL > BASIC > > > > Causes the following errors in log: > org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car > 2010-01-04 14:37:18,213 INFO [OpenEJB] Auto-deploying ejb HelloWebService: > EjbDeployment(deployment-id=secure-ejb-web-service/HelloWebService) > 2010-01-04 14:37:18,229 INFO [config] Enterprise application > "org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car" loaded. > 2010-01-04 14:37:19,041 ERROR [EjbModuleBuilder] > AxisModuleBuilderExtension.initContext() failed: Duplicate contextID > registered! > org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car?EJBModule=org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car,J2EEApplication=null,j2eeType=StatelessSessionBean,name=HelloWebService > org.apache.geronimo.common.DeploymentException: Duplicate contextID > registered! > org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car?EJBModule=org.xh.studies.ws.ejb/secure-ejb-web-service/0.0.1-SNAPSHOT/car,J2EEApplication=null,j2eeType=StatelessSessionBean,name=HelloWebService > at > org.apache.geronimo.j2ee.deployment.EARContext.addSecurityContext(EARContext.java:128) > at > org.apache.geronimo.axis.builder.AxisModuleBuilderExtension.initContext(AxisModuleBuilderExtension.java:165) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.initContext(EjbModuleBuilder.java:541) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:592) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:136) > 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:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) > 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:619) > 2010-01-04 14:37:19,041 ERROR [EjbModuleBuilder] > GeronimoSecurityBuilderImpl.addGBeans() failed: Unknown pattern type: null > java.lang.IllegalArgumentException: Unknown pattern type: null > at > org.apache.geronimo.gbean.ReferencePatterns.(ReferencePatterns.java:44) > at > org.apache.geronimo.gbean.GBeanData.setReferencePatterns(GBeanData.java:173) > at > org.apache.geronimo.gbean.GBeanData.setReferencePattern(GBeanData.java:165) > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:220) > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.addGBeans(GeronimoSecurityBuilderImpl.java:150) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.addGBeans(EjbModuleBuilder.java:816) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARC
Re: [Discussion] How about upgrade Dojo version to 1.4.0 for Geronimo 3.0?
Is the new version compatable with the old one ? If yes, I think we could upgrade it. 2010/1/6 Delos > Hi, > > Dojo 1.4.0 has released on Dec.15. How about upgrade Dojo version to > 1.4.0 for Geronimo 3.0? > > Some new Widgets are provided, such as EnhancedDataGrid; meanswhile a lot > of refactoring work makes it faster than before. > > BTW, for you to feel the improvement of Dojo 1.4.0, I have uploaded a demo > of pluto 2.0 and Dojo 1.4.0 here > https://svn.apache.org/repos/asf/geronimo/sandbox/delos/portlet+dojo/portlet-dojo1.4.0-demo.zip. > > > Steps to run demo > 1. Extract the zip > 2. launch "bin/startup.sh" or bin/startup.bat" > 3. visit "http://localhost:8080/pluto/portal/BundlePage“, you will see a > portlet showing OSGI bundles with dojo 1.4.0 widgets > > Upgrade to Dojo 1.4.0, any comments? > > Thanks! > -- > Best Regards, > > Delos > -- Ivan
[Discussion] How about upgrade Dojo version to 1.4.0 for Geronimo 3.0?
Hi, Dojo 1.4.0 has released on Dec.15. How about upgrade Dojo version to 1.4.0 for Geronimo 3.0? Some new Widgets are provided, such as EnhancedDataGrid; meanswhile a lot of refactoring work makes it faster than before. BTW, for you to feel the improvement of Dojo 1.4.0, I have uploaded a demo of pluto 2.0 and Dojo 1.4.0 here https://svn.apache.org/repos/asf/geronimo/sandbox/delos/portlet+dojo/portlet-dojo1.4.0-demo.zip. Steps to run demo 1. Extract the zip 2. launch "bin/startup.sh" or bin/startup.bat" 3. visit "http://localhost:8080/pluto/portal/BundlePage“, you will see a portlet showing OSGI bundles with dojo 1.4.0 widgets Upgrade to Dojo 1.4.0, any comments? Thanks! -- Best Regards, Delos
[jira] Commented: (GERONIMO-5012) "Redeploy application" in Web console does not work (G2.2)
[ https://issues.apache.org/jira/browse/GERONIMO-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797010#action_12797010 ] Ivan commented on GERONIMO-5012: Hi, Łukasz It is a bug in Geronimo, and I think it should exist for a long time. However, you could add a empty ejb-jar.xml file in the META-INF folder to workaround it. The reason is that Geronimo finds the module ID according to the standard Java EE deployment file it finds. e.g. Once it found a ejb-jar.xml in the META-INF folder, it would check the openejb-jar.xml file. But in EJB 3.0, ejb-jar.xml is not a must file. Thanks for pointing it out ! Ivan > "Redeploy application" in Web console does not work (G2.2) > -- > > Key: GERONIMO-5012 > URL: https://issues.apache.org/jira/browse/GERONIMO-5012 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Environment: G 2.2 with Tomcat 6, Windows XP, Java 6 >Reporter: Łukasz Budnik >Priority: Minor > > When using http://localhost/console/portal/Applications/Deploy%20New to > redeploy the application I keep getting the following message: > Unable to identify modules to replace. Check if it has already been stopped > or undeployed. > null > (no exceptions logged in geronimo.out) > I have to uninstall the application using > http://localhost/console/portal/Applications/Web%20App%20WARs or > http://localhost/console/portal/Applications/EJB%20JARs and then deploy it > from the scratch. > not a blocker, but quite annoying. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r896318 - in /geronimo/server/branches/2.1/framework/modules: geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java geronimo-deploy-tool/src/main/ja
Jack,
I think you also need to add svn:keywords svn property to these new
files so that Rev and Date keywords get expanded properly.
Jarek
On Tue, Jan 5, 2010 at 11:16 PM, wrote:
> Author: caijunj
> Date: Wed Jan 6 04:16:46 2010
> New Revision: 896318
>
> URL: http://svn.apache.org/viewvc?rev=896318&view=rev
> Log:
> GERONIMO-3003 - Fix the revision and date field in two new files
>
> Modified:
>
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
>
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
>
> Modified:
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
> URL:
> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java?rev=896318&r1=896317&r2=896318&view=diff
> ==
> ---
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
> (original)
> +++
> geronimo/server/branches/2.1/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/deployer/EncryptCommandMetaData.java
> Wed Jan 6 04:16:46 2010
> @@ -18,7 +18,7 @@
>
>
> /**
> - * @version $Rev: 515007 $ $Date: 2007-03-06 18:26:41 +1100 (Tue, 06 Mar
> 2007) $
> + * @version $Rev$ $Date$
> */
> public class EncryptCommandMetaData extends BaseCommandMetaData {
> public static final CommandMetaData META_DATA = new
> EncryptCommandMetaData();
>
> Modified:
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
> URL:
> http://svn.apache.org/viewvc/geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java?rev=896318&r1=896317&r2=896318&view=diff
> ==
> ---
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
> (original)
> +++
> geronimo/server/branches/2.1/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandEncrypt.java
> Wed Jan 6 04:16:46 2010
> @@ -31,7 +31,7 @@
> /**
> * The CLI command to encrypt a given string.
> *
> - * @version $Rev: 617588 $ $Date: 2008-02-02 02:20:07 +0800 (Sat, 02 Feb
> 2008) $
> + * @version $Rev$ $Date$
> */
> public class CommandEncrypt extends AbstractCommand {
>
>
>
>
[jira] Commented: (GERONIMO-3003) Encrypt password strings in deployment plans
[
https://issues.apache.org/jira/browse/GERONIMO-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796974#action_12796974
]
Jack Cai commented on GERONIMO-3003:
Commited the encrypt command patch to 2.1 branch at Rev 896103 and 2.2 branch
at Rev 896316.
TODO:
1. Trunk update
2. GShell equivalent
3. Doc update
> Encrypt password strings in deployment plans
>
>
> Key: GERONIMO-3003
> URL: https://issues.apache.org/jira/browse/GERONIMO-3003
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: deployment
>Affects Versions: Wish List
>Reporter: Aman Nanner
>Priority: Minor
> Fix For: Wish List
>
> Attachments: GERONIMO-3003-2.2-2.patch, GERONIMO-3003.cmd.21.patch,
> GERONIMO-3003.cmd.22.patch, GERONIMO-3003.patch, GERONIMO-3003_21.patch
>
>
> Geronimo currently has a feature where password strings in the config.xml get
> encrypted using the {{org.apache.geronimo.util.EncryptionManager}}. This
> encryption is performed in the
> {{org.apache.geronimo.system.configuration.GBeanOverride}} class.
> It would be desirable to have the same encryption applied to the password
> strings in deployment plans (e.g. datasource or JMS deployment plans within
> an EAR). Even though the plans are only used during the deployment process,
> and not at runtime, the plans are left with plaintext password strings
> sitting in them. It would be nice if the deployment process could internally
> encrypt the strings and then write back out the deployment plan to the file
> system. Also, this means that the deployment process will require the
> ability to decrypt strings that are already in encrypted format in the plan
> (in the case of redeployment, for example).
> More discussion of this feature can be found in the following mailing list
> thread:
> http://www.mail-archive.com/u...@geronimo.apache.org/msg05859.html
> I would suggest that an appropriate spot to perform the encryption is in the
> {{org.apache.geronimo.j2ee.deployment.EARConfigBuilder}} class, perhaps in
> the following code just before the file is written to a temporary file:
>
> if (gerModule.isSetAltDd()) {
> // the the url of the alt dd
> try {
> altVendorDDs.put(path,
> DeploymentUtil.toTempFile(earFile, gerModule.getAltDd().getStringValue()));
> } catch (IOException e) {
> throw new DeploymentException("Invalid alt vendor
> dd url: " + gerModule.getAltDd().getStringValue(), e);
> }
>
> However, somebody more familiar with the design might be able to suggest a
> better solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] GEP 2.2 release - RC1
Hope all PMC members can see the thread, could you help to review the release candidate and give your vote? Thanks very much! 2010/1/5 Rex Wang > +1 > thanks! > > > 2010/1/4 Delos > > Hi everyone, Please review and vote on the release of the Geronimo Eclipse >> Plugin 2.2 RC1. >> >> The deployable zip file is here: >> >> > >> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-deployable.zip >> >> The update site zip file is here: >> >> > >> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip >> >> The current svn location is here (revision number 894784): >> >> > >> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/2.2 >> >> The future svn location will be here (when approved): >> >> > >> https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/2.2 >> >> If you would like to review and/or comment on the release notes, they are >> here: >> >> > >> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/PLUGIN_RELEASE-NOTES-2.2.txt >> >> There is a rudimentary set of install instructions available at the URL >> below that will hopefully describe the necessary prereq(s) and steps >> required to install and run the GEP: >> >> > >> http://cwiki.apache.org/GMOxDOC22/how-to-install-geronimo-eclipse-plugin.html >> >> In an effort to get more people to review and vote I'd recommend going >> through this quick but useful tutorial demonstrating some of the >> capabilities of the GEP: >> >> > >> http://cwiki.apache.org/GMOxDOC22/5-minute-tutorial-on-enterprise-application-development-with-eclipse-and-geronimo.html >> >> Finally, I've created a Staging Site that can be used to test the update >> manager functions (i.e., p2 in Ganymede or Galileo) of Eclipse for >> downloading the GEP itself. This is also documented in the instructions, but >> you must use the staging site created for this vote at: >> >> > >> http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC1/staging_site/updates/ >> >> Please let me know if there are any questions and/or problems. The voteis >> open for 72 hours and will conclude on Thuresday (Jan 7,2010) at 9:00 AM >> ET. >> >> [ ] +1 Release Geronimo Eclipse Plugin 2.2 >> [ ] +0 No opinion >> [ ] -1 Don't release Geronimo Eclipse Plugin 2.2 >> >> Thanks in advance! >> >> -- >> Best Regards, >> >> Delos >> > > > > -- > -- > Lei Wang (Rex) > rwonly AT apache.org > -- Best Regards, Delos
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796751#action_12796751 ] Ashish Jain commented on GERONIMO-4795: --- Can someone help review and provide comments over the patch? > Multiple Server Instances: Uninstalling an application does not remove the > entry from config.xml of other server instances > -- > > Key: GERONIMO-4795 > URL: https://issues.apache.org/jira/browse/GERONIMO-4795 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: commands >Affects Versions: 2.1.3, 2.1.4 > Environment: Windows XP G 214 >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: Wish List > > Attachments: GERONIMO-4795.patch > > > 1) Setup another geronimo instance out of the same installation directory. > 2) Deploy an applicaton to one instance. This will result in entry being > created in config.xml for both the instances > 3) Undeploy the application. This results in entry being removed from > config.xml of one instance and other instance > still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4892) Farm Deployment Error if deploy more than one applications
[
https://issues.apache.org/jira/browse/GERONIMO-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796748#action_12796748
]
Ashish Jain commented on GERONIMO-4892:
---
Can someone help review and provide comments over the patch?
> Farm Deployment Error if deploy more than one applications
> --
>
> Key: GERONIMO-4892
> URL: https://issues.apache.org/jira/browse/GERONIMO-4892
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
>Affects Versions: 2.1.4, 2.2
> Environment: oS: winxp and win2003
>Reporter: viola.lu
>Assignee: Ashish Jain
> Fix For: 2.1.5, 2.2
>
> Attachments: 4892.patch, GERONIMO-4892_updated.patch, LOGS_4892.rar,
> TwoFarm.zip
>
>
> Win2003 as master node( NODE2) with config.xml
> ...
>
> name="org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node1"
> gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE1
> propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
> name="extendedJMXConnectorInfo">
> class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo"
> xmlns="" xmlns:ns10="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0";
> xmlns:ns12="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns14="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns16="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns8_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns6_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns6="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns8="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns16_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns14_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns12_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns10_="http://geronimo.apache.org/xml/ns/attributes-1.2";>
> system
> manager
> rmi
> 9.186.10.167
> 1099
> JMXConnector
> false
>
>
>
>
> ${ClusterNodeName}
>
>
> ${FarmName}
>
>
> ...
> WinXP as node 1
> WinXp. as node 1
> ..
>
> name="org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=GBean,name=Node2"
> gbeanInfo="org.apache.geronimo.farm.config.BasicNodeInfo">
> NODE2
> propertyEditor="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfoEditor"
> name="extendedJMXConnectorInfo">
> class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo"
> xmlns="" xmlns:ns20="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns10="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns22="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0";
> xmlns:ns12="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns14="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns16="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns18="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns19="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns6_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns4="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns6="http://geronimo.apache.org/xml/ns/plugins-1.3";
> xmlns:ns7="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns8="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns18_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns9="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns16_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns14_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns12_="http://geronimo.apache.org/xml/ns/attributes-1.2";
> xmlns:ns22_="http://geronimo.apache.org/xml/ns/attributes-1.2";>
> system
> manager
> rmi
> 9.186.10.67
> 1099
> JMXConnector
> false
>
>
>
>
> ${ClusterNodeName}
>
>
> ${FarmName}
>
>
> ..
> 1.Following doc
> http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html to farm
> deploy apps
> with command:
> deploy.bat --user system --password manager deploy --targets
> org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/
[jira] Commented: (GERONIMO-4896) Commands to a Secure JMX Connector require the SSL keyStorePassword to be specified on command line
[
https://issues.apache.org/jira/browse/GERONIMO-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796749#action_12796749
]
Ashish Jain commented on GERONIMO-4896:
---
Can someone help review and provide comments over the patch?
> Commands to a Secure JMX Connector require the SSL keyStorePassword to be
> specified on command line
> ---
>
> Key: GERONIMO-4896
> URL: https://issues.apache.org/jira/browse/GERONIMO-4896
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 2.1.5, 2.2, 3.0
>Reporter: Kevan Miller
>Assignee: Ashish Jain
> Fix For: 2.1.5, 3.0, Wish List
>
> Attachments: JavaAgent.jar, JvmOpts.java
>
>
> To my knowledge, it is not possible to run a Geronimo command (e.g. deploy.sh
> deploy or gsh geronimo/stop-server) to a server with a secure JMX Connector
> (running SSL, without specifying the following Java system properties on the
> command line:
>javax.net.ssl.keyStore and javax.net.ssl.keyStorePassword
> For example:
> {code}
> export GERONIMO_HOME=~/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
> export
> JAVA_OPTS="-Djavax.net.ssl.keyStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
> -Djavax.net.ssl.keyStorePassword=secret
> -Djavax.net.ssl.trustStore=$GERONIMO_HOME/var/security/keystores/geronimo-default
> -Djavax.net.ssl.trustStorePassword=secret"
> $GERONIMO_HOME/bin/deploy.sh -u system -p manager --secure list-modules
> --stopped
> {code}
> javax.net.ssl.keyStorePassword causes a problem, since this means the
> keyStorePassword is available, in-the-clear, to someone inspecting executing
> processes. For example while a deploy command was active, someone could run
> 'ps auxww | grep deployer.jar' and discover the keyStorePassword for the
> KeyStore.
> Geronimo should provide a mechanism, whereby users can specify the
> keyStorePassword without making that secret available to anyone inspecting
> processes running on the current system. Ideally, the password could be
> encrypted/obfuscated within a file (just as passwords can be
> encrypted/obfuscated in var/config/config.xml).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4983) In debug mode Properties file login module reurns loginsucceeded as true for non existent users and null password
[ https://issues.apache.org/jira/browse/GERONIMO-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796750#action_12796750 ] Ashish Jain commented on GERONIMO-4983: --- Can someone help review and provide comments over the patch? > In debug mode Properties file login module reurns loginsucceeded as true for > non existent users and null password > - > > Key: GERONIMO-4983 > URL: https://issues.apache.org/jira/browse/GERONIMO-4983 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1.4, 2.2 > Environment: windows Xp, eclipse >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.1.5, 2.2.1 > > Attachments: GERONIMO-4983.patch > > > While debugging one of the login fallback code I see that > PropertiesFileLoginModule.java returns loginsucceeded as true for a > non-existent user and null password. > This happens under the following use case. > In the BasicAuthenticator Code I have the following > String username=header.substring(10); > String password=null; > principal = context.getRealm().authenticate(username, password); > In the login method of PropertiesFileLoginModule as per the above usecase we > will have > realPassword as null and password as null as a result "if > (!checkPassword(realPassword, password))" > will be skipped and hence resulting in loginSucceeded=true. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4844) There is an error after undeploy the application and deploy the application again when configure WADI clustering,
[ https://issues.apache.org/jira/browse/GERONIMO-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796747#action_12796747 ] Ashish Jain commented on GERONIMO-4844: --- Can someone help review and provide comments over the patches? > There is an error after undeploy the application and deploy the application > again when configure WADI clustering, > -- > > Key: GERONIMO-4844 > URL: https://issues.apache.org/jira/browse/GERONIMO-4844 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.1.4, 2.2 > Environment: windows:sp2 > jdk1.6 >Reporter: liangkun >Assignee: Shawn Jiang > Fix For: 2.1.5 > > Attachments: GERONIMO-4844.patch > > > I deploy the application cviewer.war after undeploy it when configure the > WADI clustering ,the there is an error: > org.apache.geronimo.common.DeploymentException: Unable to deploy > cviewer-2.1.1.2.war: Module com.ibm.wasce.samples/cviewer/2.1.1.2/car already > exists in the server. Try to undeploy it first or use the redeploy command. > at > org.apache.geronimo.deployment.cli.CommandDeploy.runCommand(CommandDeploy.java:45) > at > org.apache.geronimo.deployment.cli.CommandDistribute.executeOnline(CommandDistribute.java:139) > at > org.apache.geronimo.deployment.cli.CommandDistribute.execute(CommandDistribute.java:125) > at > org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:168) > at > org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45) > at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at > org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31) > However,actually,there are no any module in the server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Newly created doc not visible in http://cwiki.apache.org/GMOxDOC21/
Thanks Joe problem seems to be fixed now. On Tue, Jan 5, 2010 at 1:05 AM, Joe Bohn wrote: > I just did a manual export of the Geronimo 2.1 pages but it will take some > time before it is available. Let's see if that fixes the issue. > > Joe > > > Ashish Jain wrote: > >> Sorry folks there is still a problem.It seems to be related to >> autoexport pluginOnce hernan and another time Joe has fixed this issue. >> Here are some old references to the same problem. >> >> >> http://old.nabble.com/New-child-page-added-to-AG-2.1-not-visible-on-index-page-tt18666514s134.html >> >> http://old.nabble.com/Is-autoexport-from-Confluence-to-static-sites-working--td18953184s134.html >> >> Thanks >> Ashish >> >> On Mon, Dec 28, 2009 at 10:43 PM, Ashish Jain > ashja...@gmail.com>> wrote: >> >>The problem seems to be incorrect usage of scrollbar.the problem >>is fixed now... >> >> >>On Sat, Dec 26, 2009 at 4:41 AM, David Jencks >>mailto:david_jen...@yahoo.com>> wrote: >> >>On Dec 25, 2009, at 12:36 PM, Ashish Jain wrote: >> >> Hi, >>> >>>I have created a new doc >>>http://cwiki.apache.org/GMOxDOC21/tomcat-native-clustering.html. >>>However it is not visible in the url >>>http://cwiki.apache.org/GMOxDOC21/ under clustering. Can >>>someone help me fix this?? >>> >>> I think you need to edit the index page by hand to add a link at >>an appropriate location. >> >>david jencks >> >> Thanks >>>Ashish >>> >> >> >> >> >
[jira] Resolved: (GERONIMO-5014) JSR-303 api needs to update the ElementDescriptor section to fit the latest spec
[ https://issues.apache.org/jira/browse/GERONIMO-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller resolved GERONIMO-5014. Resolution: Fixed Patch applied. Thanks Mark! I added a license header to Scope.java. > JSR-303 api needs to update the ElementDescriptor section to fit the latest > spec > > > Key: GERONIMO-5014 > URL: https://issues.apache.org/jira/browse/GERONIMO-5014 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Kevan Miller > Attachments: GERONIMO-5014.patch > > > there have been a few changes in the spec. > I made all changes to make agimatec-validator (which currently uses the RI) > compile against our spec api. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5014) JSR-303 api needs to update the ElementDescriptor section to fit the latest spec
[ https://issues.apache.org/jira/browse/GERONIMO-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller reassigned GERONIMO-5014: -- Assignee: Kevan Miller > JSR-303 api needs to update the ElementDescriptor section to fit the latest > spec > > > Key: GERONIMO-5014 > URL: https://issues.apache.org/jira/browse/GERONIMO-5014 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg >Assignee: Kevan Miller > Attachments: GERONIMO-5014.patch > > > there have been a few changes in the spec. > I made all changes to make agimatec-validator (which currently uses the RI) > compile against our spec api. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4970) Remove those specs and impl which are shipped by JRE 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4970: --- Component/s: osgi > Remove those specs and impl which are shipped by JRE 1.6 > > > Key: GERONIMO-4970 > URL: https://issues.apache.org/jira/browse/GERONIMO-4970 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Ivan > Fix For: 3.0 > > Attachments: GERONIMO-4970-1.patch, GERONIMO-4970-2.patch > > > Since Geronimo 3.0 could only run 1.6+, I think we do not need to keep those > spec APIs and impl which are shipped by JRE, including JAXB API, JAXB Impl, > JAXWS, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5014) JSR-303 api needs to update the ElementDescriptor section to fit the latest spec
[ https://issues.apache.org/jira/browse/GERONIMO-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated GERONIMO-5014: Attachment: GERONIMO-5014.patch > JSR-303 api needs to update the ElementDescriptor section to fit the latest > spec > > > Key: GERONIMO-5014 > URL: https://issues.apache.org/jira/browse/GERONIMO-5014 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Mark Struberg > Attachments: GERONIMO-5014.patch > > > there have been a few changes in the spec. > I made all changes to make agimatec-validator (which currently uses the RI) > compile against our spec api. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5014) JSR-303 api needs to update the ElementDescriptor section to fit the latest spec
JSR-303 api needs to update the ElementDescriptor section to fit the latest spec Key: GERONIMO-5014 URL: https://issues.apache.org/jira/browse/GERONIMO-5014 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: specs Reporter: Mark Struberg there have been a few changes in the spec. I made all changes to make agimatec-validator (which currently uses the RI) compile against our spec api. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
An argument for more Geronimo releases
First my congratulations to the Geronimo team for the new version. A grep on the release notes tells you the number of Issues Resolved: 666 D:\downloads>grep "\[GERO" RELEASE_NOTES-2.2.txt | wc -l 666 An amazing amount of work. Thank you. So, no wonder the release took nine months. But I think this is a very long time for an open source project's releases. I'd wish that there be more Geronimo releases, about one each month, with some bug fixes and some new features. So, like there is jdk1.6.0_17 and apache-tomcat-6.0.20 there might one day be geronimo-tomcat6-javaee5-2.2.20 + http://en.wikipedia.org/wiki/Release_early,_release_often + new features + bugfixes get out faster, development is more lively + user feedback is more current + the development team is forced to more automate the release process + the project is more alive with more new versions on the front page + I'm a version junky ;-) I hope you forgive me who has never contributed for making such an argument. Thanks, Juergen -- View this message in context: http://old.nabble.com/An-argument-for-more-Geronimo-releases-tp27025361s134p27025361.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Closed: (GERONIMO-4999) Document Update: Tomcate Native Clustering after fix applied to 2.1 through GERONIMO-4187
[ https://issues.apache.org/jira/browse/GERONIMO-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-4999. - Resolution: Fixed > Document Update: Tomcate Native Clustering after fix applied to 2.1 through > GERONIMO-4187 > - > > Key: GERONIMO-4999 > URL: https://issues.apache.org/jira/browse/GERONIMO-4999 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 2.1.5 >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.1.5 > > > After applying the fix to 2.1 branch through GERONIMO-4187 there is a need to > modify the documentation. The new configuration will look something like this > TomcatCluster > class="org.apache.geronimo.tomcat.cluster.CatalinaClusterGBean"> > name="className">org.apache.catalina.ha.tcp.SimpleTcpCluster > > > TomcatClusterListenerChain > > > ReplicationValve > > > TomcatChannel > > > TomcatClusterManager > > > > > > class="org.apache.geronimo.tomcat.cluster.ClusterManagerGBean"> > name="className">org.apache.catalina.ha.session.DeltaManager > name=somename > > expireSessionsOnShutdown=false > useDirtyFlag=true > notifyListenersOnReplication=true > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: About server.xml support and app-per-port sample breaks on G 2.2
Hi, Forrest: There might be a bug there, for workaround it, please add segment below to the config.xml file : -> Catalina Catalina <- After that, you could start up the server, but you could not edit those connectors created before the server starting, however, you are still able to add new connectors. Thanks for reporting this ! 2010/1/5 Forrest Xia > > > On Mon, Jan 4, 2010 at 5:36 PM, Ivan wrote: > >> >> >> 2010/1/4 Forrest Xia >> >>> I did a simple version change(change to 2.2:) to the app-per-port sample >>> and make it packaged as a plugin, then try to install and start it in G 2.2. >>> >>> >>> It fails, I understand the failure on tomcat assembly is caused by the >>> new server.xml support, but don't understand why it fails on Jetty assembly >>> as well. >>> >>> What I am trying is to update app-per-port sample to demo the new >>> server.xml support feature(originated from >>> http://old.nabble.com/Finishing-up-tomcat-server.xml-configuration-work...-ts24471974s134.html#a24471974). >>> >>> >>> My thought is to modify the server.xml directly to add an additional >>> with different connectors and engine, so that the app-per-port >>> samples can achieve the same result as before: war1 on a port, war2 on >>> another port, both in the same server instance. >>> >>> Unfortunately, it does not work on G 2.2 either. Cause TomcatServerGBean >>> would throw IllegalStateException when more than one service defined in >>> server.xml. >>> >>> So far, my understanding to the server.xml support feature, which cannot >>> do these things: >>> 1. define multiple >>> 2. define >>> 3. define jndi resources >>> 4. define realms >>> >> >> The item 2,3,4 are NOT supported, item 1 should be supported. >> > > You can try to define two , and see what happens when starting > the server. There will be an IllegalStateException thrown out. The code lays > in TomcatServerGBean.java. > > If multiple services are supposed to support, I will open a JIRA to track > it. thanks! > > Forrest > > > > -- Ivan
