[ANNOUNCE] Ashish Jain - Geronimo's newest committer
All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe
Re: [ANNOUNCE] Ashish Jain - Geronimo's newest committer
Congrats, Ashish! ~Jason Warner On Sun, Mar 14, 2010 at 4:44 PM, Joe Bohn joe.b...@earthlink.net wrote: All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe
Re: [ANNOUNCE] Ashish Jain - Geronimo's newest committer
Congrats, Ashish ! 2010/3/15 Jason Warner jaw...@gmail.com Congrats, Ashish! ~Jason Warner On Sun, Mar 14, 2010 at 4:44 PM, Joe Bohn joe.b...@earthlink.net wrote: All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe -- Ivan
Re: [ANNOUNCE] Ashish Jain - Geronimo's newest committer
Congrats, Ashish! 2010/3/15 Ivan xhh...@gmail.com Congrats, Ashish ! 2010/3/15 Jason Warner jaw...@gmail.com Congrats, Ashish! ~Jason Warner On Sun, Mar 14, 2010 at 4:44 PM, Joe Bohn joe.b...@earthlink.net wrote: All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe -- Ivan -- Lei Wang (Rex) rwonly AT apache.org
Re: time to use maven 2.2.1 for G2.1.5 daily build
hi, Donald, in http://maven.apache.org/developers/release/apache-release.html A prerequisite says: you must use Maven 2.2.1, as Maven 2.0.x cannot deploy over SCP to the ASF, and Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively. I think we have to use 2.2.1.. 2010/3/12 Donald Woods dwo...@apache.org +1 to using Genesis 2.0 as this lets us use Nexus to deploy artifacts (this was discussed in another thread awhile back.) -1 to requiring Maven 2.2.1, as Genesis 2.0 only requires 2.0.10 or later - https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-2.0/genesis-default-flava/pom.xml - ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId executions execution phasevalidate/phase goals goalenforce/goal /goals configuration rules requireMavenVersion version[2.0.10,)/version /requireMavenVersion /rules /configuration /execution /executions /plugin ... -Donald On 3/11/10 10:42 AM, Forrest Xia wrote: To use apache-release profile and maven release plugin to do release, I guess :-) Forrest On Thu, Mar 11, 2010 at 9:46 PM, Kevan Miller kevan.mil...@gmail.com mailto:kevan.mil...@gmail.com wrote: On Mar 11, 2010, at 3:54 AM, Rex Wang wrote: Hi Jarek, Could you help update the scripts? Read more of my mail... ;-) So, I assume *why* is because of the move to Genesis 2.0. So, brings up a new question... ;-) Why update G 2.1 to use Genesis 2.0? --kevan -- Lei Wang (Rex) rwonly AT apache.org
Re: [ANNOUNCE] Ashish Jain - Geronimo's newest committer
Congrats, Ashish ! On Mon, Mar 15, 2010 at 9:20 AM, Rex Wang rwo...@gmail.com wrote: Congrats, Ashish! 2010/3/15 Ivan xhh...@gmail.com Congrats, Ashish ! 2010/3/15 Jason Warner jaw...@gmail.com Congrats, Ashish! ~Jason Warner On Sun, Mar 14, 2010 at 4:44 PM, Joe Bohn joe.b...@earthlink.netwrote: All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe -- Ivan -- Lei Wang (Rex) rwonly AT apache.org -- Shawn
[jira] Commented: (GERONIMO-5146) Geronimo should provide a default encrypted password for trustStore and keyStore
[ https://issues.apache.org/jira/browse/GERONIMO-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845168#action_12845168 ] Rex Wang commented on GERONIMO-5146: rev 920174, rev923024 @ br21 rev923026 @ br22 rev923027 @ trunk Geronimo should provide a default encrypted password for trustStore and keyStore Key: GERONIMO-5146 URL: https://issues.apache.org/jira/browse/GERONIMO-5146 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 Attachments: 5146_21.patch, 5146_21_updated.patch, 5146_one_line_of_code.patch Geronimo should provide by default encrypted password for trustStore and keyStore. If this is not done than after applying the fix for GERONIMO-4896 it will be required by user to 1) first start the server w/o using JMXSecure Connector. 2) Use the deploy.bat encrypt functionality to encrypt the password 3) ShutDown and start the server with secure JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5146) Geronimo should provide a default encrypted password for trustStore and keyStore
[ https://issues.apache.org/jira/browse/GERONIMO-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5146. -- Resolution: Fixed Geronimo should provide a default encrypted password for trustStore and keyStore Key: GERONIMO-5146 URL: https://issues.apache.org/jira/browse/GERONIMO-5146 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5, 2.2.1, 3.0 Attachments: 5146_21.patch, 5146_21_updated.patch, 5146_one_line_of_code.patch Geronimo should provide by default encrypted password for trustStore and keyStore. If this is not done than after applying the fix for GERONIMO-4896 it will be required by user to 1) first start the server w/o using JMXSecure Connector. 2) Use the deploy.bat encrypt functionality to encrypt the password 3) ShutDown and start the server with secure JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [ANNOUNCE] Ashish Jain - Geronimo's newest committer
Congratulations! -Jack On Mon, Mar 15, 2010 at 9:39 AM, Shawn Jiang genspr...@gmail.com wrote: Congrats, Ashish ! On Mon, Mar 15, 2010 at 9:20 AM, Rex Wang rwo...@gmail.com wrote: Congrats, Ashish! 2010/3/15 Ivan xhh...@gmail.com Congrats, Ashish ! 2010/3/15 Jason Warner jaw...@gmail.com Congrats, Ashish! ~Jason Warner On Sun, Mar 14, 2010 at 4:44 PM, Joe Bohn joe.b...@earthlink.netwrote: All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe -- Ivan -- Lei Wang (Rex) rwonly AT apache.org -- Shawn
Re: Discussion: Possible fixes for GERONIMO-5180
I still don't quite understand Option 2. So what would be stored in this new attribute keystores1? If it still contains an instance of FileKeystoreInstance, then there is still a serialization problem. -Jack On Sat, Mar 13, 2010 at 5:20 PM, Ashish Jain ashja...@gmail.com wrote: Hi Joe, Thanks for your comments. The intent of using option #2 was to make use of getAttribute and also since modifying the KeystoreManager interface will not have any effect on any existing functionalities. However as you pointed out a get method w/o any return types may be misleading. Thanks Ashish On Fri, Mar 12, 2010 at 8:46 PM, Joe Bohn joe.b...@earthlink.net wrote: I don't know much about the details of the problem but it seems to me that you would either make the class serializable (option #1) or exclude it from serialization if it is not necessary. I don't see how this would impact any existing functions. So I guess I would vote for #1. I don't understand why you would want to have a get* method that doesn't return anything - but perhaps I'm missing the point of option #2. Joe Ashish Jain wrote: Hi ALL, I have opened up a JIRA GERONIMO-5180 on the unlockKeystore command failure if keystore is created with keytool.exe. I was trying to fix this issue which requires some changes in the class declaration or interface. Following code is being utilized to fix up the issue KeystoreInstance[] keystores=(KeystoreInstance[])kernel.getAttribute(abstractName,keystores); where abstractName is obtained through org.apache.geronimo.management.geronimo.KeystoreManager. However I hit the following exception: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableE xception: org.apache.geronimo.security.keystore.FileKeystoreInstance at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:172) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(RMIConnecti onImpl_Stub.java:400) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection. invoke(RMIConnector.java:984) There are 2 ways to fix this up. 1) Make the class org.apache.geronimo.security.keystore.FileKeystoreInstance serializable. 2) add a new variable in FileKeystoreManager and add a new method in KeystoreManager which does not return anything and just gives a call to getKeystores(). For example getKeystores1() as the new method in KeystoreManager and a new variable as keystores1. I shall prefer #2 over #1 as it should not have any effect on existing functionalities. Suggestions/advice/comments?? Thanks Ashish
Re: [ANNOUNCE] Ashish Jain - Geronimo's newest committer
Congratulations Ashish!! On Mon, Mar 15, 2010 at 3:14 AM, Joe Bohn joe.b...@earthlink.net wrote: All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe -- Vamsi
Re: [ANNOUNCE] Ashish Jain - Geronimo's newest committer
Congrats! Jarek On Sun, Mar 14, 2010 at 5:44 PM, Joe Bohn joe.b...@earthlink.net wrote: All, Please join me in welcoming Ashish Jain as the newest committer on the Apache Geronimo project. The Geronimo PMC is excited that Ashish has accepted our invitation. Congratulations Ashish and keep up the good work! Joe
Re: Discussion: Possible fixes for GERONIMO-5180
The serialization problem is popping up due to the return type associated with getKeystores(). But in the case of getKeystores1() there is no return variable. So it helps in overcoming this problem. On Mon, Mar 15, 2010 at 8:18 AM, Jack Cai greensi...@gmail.com wrote: I still don't quite understand Option 2. So what would be stored in this new attribute keystores1? If it still contains an instance of FileKeystoreInstance, then there is still a serialization problem. -Jack On Sat, Mar 13, 2010 at 5:20 PM, Ashish Jain ashja...@gmail.com wrote: Hi Joe, Thanks for your comments. The intent of using option #2 was to make use of getAttribute and also since modifying the KeystoreManager interface will not have any effect on any existing functionalities. However as you pointed out a get method w/o any return types may be misleading. Thanks Ashish On Fri, Mar 12, 2010 at 8:46 PM, Joe Bohn joe.b...@earthlink.net wrote: I don't know much about the details of the problem but it seems to me that you would either make the class serializable (option #1) or exclude it from serialization if it is not necessary. I don't see how this would impact any existing functions. So I guess I would vote for #1. I don't understand why you would want to have a get* method that doesn't return anything - but perhaps I'm missing the point of option #2. Joe Ashish Jain wrote: Hi ALL, I have opened up a JIRA GERONIMO-5180 on the unlockKeystore command failure if keystore is created with keytool.exe. I was trying to fix this issue which requires some changes in the class declaration or interface. Following code is being utilized to fix up the issue KeystoreInstance[] keystores=(KeystoreInstance[])kernel.getAttribute(abstractName,keystores); where abstractName is obtained through org.apache.geronimo.management.geronimo.KeystoreManager. However I hit the following exception: java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableE xception: org.apache.geronimo.security.keystore.FileKeystoreInstance at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:172) at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(RMIConnecti onImpl_Stub.java:400) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection. invoke(RMIConnector.java:984) There are 2 ways to fix this up. 1) Make the class org.apache.geronimo.security.keystore.FileKeystoreInstance serializable. 2) add a new variable in FileKeystoreManager and add a new method in KeystoreManager which does not return anything and just gives a call to getKeystores(). For example getKeystores1() as the new method in KeystoreManager and a new variable as keystores1. I shall prefer #2 over #1 as it should not have any effect on existing functionalities. Suggestions/advice/comments?? Thanks Ashish
How do annotation String array descriptions relate to xml descriptor language-plus-string descriptions?
In the common xml goo for ee6 there's a description group which has e.g. a description element which has a language attribute and text content. In the Connector annotation there's a corresponding description getter which returns a String[] Does anyone know how these relate, i.e. is the language encoded in the description string somehow? I haven't located any bits of spec that discuss this... thanks david jencks
