[BUILD] trunk: Failed for Revision: 922409

2010-03-12 Thread gawor 
Geronimo Revision: 922409 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100312/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100312/unit-test-reports
 
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.core:0.1-incubating-SNAPSHOT: 
checking for updates from jetty.oss.sonatype.org
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.core:0.1-incubating-SNAPSHOT: 
checking for updates from openqa-snapshots
[WARNING] repository metadata for: 'snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.core:0.1-incubating-SNAPSHOT' could 
not be retrieved from repository: openqa-snapshots due to an error: Error 
transferring file: Server returned HTTP response code: 502 for URL: 
http://nexus.openqa.org/content/repositories/snapshots/org/apache/aries/jndi/org.apache.aries.jndi.core/0.1-incubating-SNAPSHOT/maven-metadata.xml
[INFO] Repository 'openqa-snapshots' will be blacklisted
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.core:0.1-incubating-SNAPSHOT: 
checking for updates from codehaus.snapshots
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.core:0.1-incubating-SNAPSHOT: 
checking for updates from apache.snapshots
Downloading: 
http://repository.apache.org/snapshots/org/apache/aries/jndi/org.apache.aries.jndi.core/0.1-incubating-SNAPSHOT/org.apache.aries.jndi.core-0.1-incubating-20100312.185411-2.pom
2K downloaded  (org.apache.aries.jndi.core-0.1-incubating-20100312.185411-2.pom)
[INFO] snapshot org.apache.aries.jndi:jndi:0.1-incubating-SNAPSHOT: checking 
for updates from ops4j.snapshots
[INFO] snapshot org.apache.aries.jndi:jndi:0.1-incubating-SNAPSHOT: checking 
for updates from jetty.oss.sonatype.org
[INFO] snapshot org.apache.aries.jndi:jndi:0.1-incubating-SNAPSHOT: checking 
for updates from codehaus.snapshots
[INFO] snapshot org.apache.aries.jndi:jndi:0.1-incubating-SNAPSHOT: checking 
for updates from apache.snapshots
Downloading: 
http://repository.apache.org/snapshots/org/apache/aries/jndi/jndi/0.1-incubating-SNAPSHOT/jndi-0.1-incubating-20100312.185411-2.pom
3K downloaded  (jndi-0.1-incubating-20100312.185411-2.pom)
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.url:0.1-incubating-SNAPSHOT: 
checking for updates from ops4j.snapshots
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.url:0.1-incubating-SNAPSHOT: 
checking for updates from jetty.oss.sonatype.org
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.url:0.1-incubating-SNAPSHOT: 
checking for updates from codehaus.snapshots
[INFO] snapshot 
org.apache.aries.jndi:org.apache.aries.jndi.url:0.1-incubating-SNAPSHOT: 
checking for updates from apache.snapshots
Downloading: 
http://repository.apache.org/snapshots/org/apache/aries/jndi/org.apache.aries.jndi.url/0.1-incubating-SNAPSHOT/org.apache.aries.jndi.url-0.1-incubating-20100312.185411-2.pom
3K downloaded  (org.apache.aries.jndi.url-0.1-incubating-20100312.185411-2.pom)
[INFO] snapshot org.apache.aries:org.apache.aries.util:0.1-incubating-SNAPSHOT: 
checking for updates from ops4j.snapshots
[INFO] snapshot org.apache.aries:org.apache.aries.util:0.1-incubating-SNAPSHOT: 
checking for updates from jetty.oss.sonatype.org
[INFO] snapshot org.apache.aries:org.apache.aries.util:0.1-incubating-SNAPSHOT: 
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.aries:org.apache.aries.util:0.1-incubating-SNAPSHOT: 
checking for updates from apache.snapshots
Downloading: 
http://repository.apache.org/snapshots/org/apache/aries/org.apache.aries.util/0.1-incubating-SNAPSHOT/org.apache.aries.util-0.1-incubating-20100312.185411-2.pom
3K downloaded  (org.apache.aries.util-0.1-incubating-20100312.185411-2.pom)
Downloading: 
http://repository.apache.org/snapshots/org/apache/aries/jndi/org.apache.aries.jndi.core/0.1-incubating-SNAPSHOT/org.apache.aries.jndi.core-0.1-incubating-20100312.185411-2.jar
Downloading: 
http://repository.apache.org/snapshots/org/apache/aries/org.apache.aries.util/0.1-incubating-SNAPSHOT/org.apache.aries.util-0.1-incubating-20100312.185411-2.jar
[INFO] snapshot org.apache.geronimo.framework:geronimo-core:3.0-SNAPSHOT: 
checking for updates from ops4j.snapshots
19K downloaded  
(org.apache.aries.jndi.core-0.1-incubating-20100312.185411-2.jar)
[INFO] snapshot org.apache.geronimo.framework:geronimo-core:3.0-SNAPSHOT: 
checking for updates from jetty.oss.sonatype.org
Downloading: 
http://repository.apache.org/snapshots/org/apache/aries/jndi/org.apache.aries.jndi.url/0.1-incubating-SNAPSHOT/org.apache.aries.jndi.url-0.1-incubating-20100312.185411-2.jar
[INFO] snapshot org.apache.geronimo.framework:geronimo-core:3.0-SNAPSHOT: 
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:geronimo-core:3.0-SNAPSHOT: 
checking for updates from apache.snapshots
17K downloaded  (org.apache.aries

[jira] Assigned: (GERONIMO-5182) Fix compile errors caused by Jetty 8.0.0.M0 release

2010-03-12 Thread Kevan Miller (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevan Miller reassigned GERONIMO-5182:
--

Assignee: Kevan Miller

> Fix compile errors caused by Jetty 8.0.0.M0 release
> ---
>
> Key: GERONIMO-5182
> URL: https://issues.apache.org/jira/browse/GERONIMO-5182
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>Affects Versions: 3.0
>Reporter: Kevan Miller
>Assignee: Kevan Miller
> Fix For: 3.0
>
>
> There are multiple updates in the latest Jetty 8.0.0.M0 release which are 
> breaking the build

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-5182) Fix compile errors caused by Jetty 8.0.0.M0 release

2010-03-12 Thread Kevan Miller (JIRA) 
Fix compile errors caused by Jetty 8.0.0.M0 release
---

 Key: GERONIMO-5182
 URL: https://issues.apache.org/jira/browse/GERONIMO-5182
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 3.0
Reporter: Kevan Miller
 Fix For: 3.0


There are multiple updates in the latest Jetty 8.0.0.M0 release which are 
breaking the build

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Tomcat-parent-6.0.26.0 staging site is ready

2010-03-12 Thread Delos 
Hi,

I have set up a staging site for tomcat-parent-6.0.26.0, which is based on
new release of tomcat. Could anyone help to do a full TCK on this? Thanks in
advance!

The staging site URL
https://repository.apache.org/content/repositories/orgapachegeronimo-007/

-- 
Best Regards,

Delos

Re: time to use maven 2.2.1 for G2.1.5 daily build

2010-03-12 Thread Donald Woods 
+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
-

...

org.apache.maven.plugins
maven-enforcer-plugin


validate

enforce




[2.0.10,)






...


-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  > 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
> 
>

Re: Discussion: Possible fixes for GERONIMO-5180

2010-03-12 Thread Joe Bohn 
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

[BUILD] trunk: Failed for Revision: 922259

2010-03-12 Thread gawor 
Geronimo Revision: 922259 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100312/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100312/unit-test-reports
 
urls[11] = 
file:/home/geronimo/.m2/repository/org/apache/geronimo/ext/tomcat/jasper/7.0.0.0-SNAPSHOT/jasper-7.0.0.0-SNAPSHOT.jar
urls[12] = 
file:/home/geronimo/.m2/repository/org/apache/geronimo/specs/geronimo-jsp_2.2_spec/1.0-SNAPSHOT/geronimo-jsp_2.2_spec-1.0-SNAPSHOT.jar
urls[13] = 
file:/home/geronimo/.m2/repository/org/apache/geronimo/specs/geronimo-servlet_3.0_spec/1.0-SNAPSHOT/geronimo-servlet_3.0_spec-1.0-SNAPSHOT.jar
urls[14] = 
file:/home/geronimo/.m2/repository/org/apache/geronimo/ext/tomcat/juli/7.0.0.0-SNAPSHOT/juli-7.0.0.0-SNAPSHOT.jar
urls[15] = 
file:/home/geronimo/.m2/repository/org/apache/geronimo/ext/tomcat/shared/7.0.0.0-SNAPSHOT/shared-7.0.0.0-SNAPSHOT.jar
urls[16] = 
file:/home/geronimo/.m2/repository/org/apache/ant/ant/1.7.1/ant-1.7.1.jar
urls[17] = 
file:/home/geronimo/.m2/repository/org/apache/ant/ant-launcher/1.7.1/ant-launcher-1.7.1.jar
urls[18] = 
file:/home/geronimo/.m2/repository/org/eclipse/jdt/core/3.3.0-v_771/core-3.3.0-v_771.jar
urls[19] = 
file:/home/geronimo/.m2/repository/org/apache/geronimo/ext/tomcat/jasper-el/7.0.0.0-SNAPSHOT/jasper-el-7.0.0.0-SNAPSHOT.jar
urls[20] = 
file:/home/geronimo/.m2/repository/org/apache/geronimo/ext/tomcat/util/7.0.0.0-SNAPSHOT/util-7.0.0.0-SNAPSHOT.jar
urls[21] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/gmaven-mojo/1.0-rc-3/gmaven-mojo-1.0-rc-3.jar
urls[22] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/runtime/gmaven-runtime-api/1.0-rc-3/gmaven-runtime-api-1.0-rc-3.jar
urls[23] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/feature/gmaven-feature-api/1.0-rc-3/gmaven-feature-api-1.0-rc-3.jar
urls[24] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/runtime/gmaven-runtime-default/1.0-rc-3/gmaven-runtime-default-1.0-rc-3.jar
urls[25] = 
file:/home/geronimo/.m2/repository/org/slf4j/slf4j-api/1.5.0/slf4j-api-1.5.0.jar
urls[26] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/runtime/gmaven-runtime-1.5/1.0-rc-3/gmaven-runtime-1.5-1.0-rc-3.jar
urls[27] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/feature/gmaven-feature-support/1.0-rc-3/gmaven-feature-support-1.0-rc-3.jar
urls[28] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/runtime/gmaven-runtime-support/1.0-rc-3/gmaven-runtime-support-1.0-rc-3.jar
urls[29] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/maven/gmaven-common/1.0-rc-3/gmaven-common-1.0-rc-3.jar
urls[30] = 
file:/home/geronimo/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
urls[31] = 
file:/home/geronimo/.m2/repository/com/thoughtworks/qdox/qdox/1.6.3/qdox-1.6.3.jar
urls[32] = 
file:/home/geronimo/.m2/repository/org/codehaus/groovy/groovy-all-minimal/1.5.6/groovy-all-minimal-1.5.6.jar
urls[33] = 
file:/home/geronimo/.m2/repository/jline/jline/0.9.94/jline-0.9.94.jar
urls[34] = 
file:/home/geronimo/.m2/repository/org/apache/maven/shared/file-management/1.1/file-management-1.1.jar
urls[35] = 
file:/home/geronimo/.m2/repository/org/apache/maven/shared/maven-shared-io/1.0/maven-shared-io-1.0.jar
urls[36] = 
file:/home/geronimo/.m2/repository/commons-lang/commons-lang/2.3/commons-lang-2.3.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/home/geronimo/soft/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] org/apache/tomcat/util/scan/StandardJarScanner
org.apache.tomcat.util.scan.StandardJarScanner
[INFO] 
[INFO] Trace
java.lang.NoClassDefFoundError: org/apache/tomcat/util/scan/StandardJarScanner
at 
org.apache.jasper.compiler.JarScannerFactory.getJarScanner(JarScannerFactory.java:47)
at 
org.apache.jasper.compiler.TldLocationsCache.init(TldLocationsCache.java:193)
at 
org.apache.jasper.compiler.TldLocationsCache.getLocation(TldLocationsCache.java:155)
at 
org.apache.jasper.JspCompilationContext.getTldLocation(JspCompilationContext.java:552)
at 
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:383)
at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:448)
at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1398)
at org.apache.jasper.compiler.Parser.parse(Parser.java:131)
at 
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:237)
at 
org.apache.jasper.compiler.ParserController.parse(ParserController.java:103)
at org.apache.jasper.compiler.Compiler.generateJava

[jira] Updated: (GERONIMO-5146) Geronimo should provide a default encrypted password for trustStore and keyStore

2010-03-12 Thread Ashish Jain (JIRA) 

 [ 
https://issues.apache.org/jira/browse/GERONIMO-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Jain updated GERONIMO-5146:
--

Attachment: 5146_one_line_of_code.patch

> 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] Commented: (GERONIMO-5146) Geronimo should provide a default encrypted password for trustStore and keyStore

2010-03-12 Thread Ashish Jain (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844430#action_12844430
 ] 

Ashish Jain commented on GERONIMO-5146:
---

Hi Rex, After revision: 920171 in GERONIMO-5156 if a user wants to unlock the 
default keystore that is geronimo-default. It is required to have an entry in 
config-substitution.properties with the name 
geronimo-default=. I am uploading a patch file with the 
name 5146_one_line_of_code.patch. Kindly
review and apply.

Thanks
Ashish

> 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
>
>
> 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] Issue Comment Edited: (GERONIMO-5093) Create JAXB 2.2 spec jar

2010-03-12 Thread Shawn Jiang (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844428#action_12844428
 ] 

Shawn Jiang edited comment on GERONIMO-5093 at 3/12/10 8:58 AM:


There are problems in final jaxb 2.2 spec PDF:

1, There's no TOC in the doc, it's hard to navigate the content.
2, The content is not intact.   At least, the changes log section of 2.2 spec 
is exactly the same with that of 2.0 spec.


Does anyone know how to report these problems to JCP ?  

  was (Author: genspring):
The problems exists in final jaxb 2.2 spec PDF:

1, there's no TOC, it's hard to navigate the content.
2, The content is not intact.   At least, the changes log section of 2.2 spec 
is exactly the same with that of 2.2 spec.


Does anyone know how to report these problems to JCP ?  
  
> Create JAXB 2.2 spec jar
> 
>
> Key: GERONIMO-5093
> URL: https://issues.apache.org/jira/browse/GERONIMO-5093
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: javaee6, specs
>Affects Versions: 3.0
>Reporter: Rick McGuire
>Assignee: Shawn Jiang
> Fix For: 3.0
>
>
> A new version of the jaxb specs is needed for the 2.2 level. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-5093) Create JAXB 2.2 spec jar

2010-03-12 Thread Shawn Jiang (JIRA) 

[ 
https://issues.apache.org/jira/browse/GERONIMO-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844428#action_12844428
 ] 

Shawn Jiang commented on GERONIMO-5093:
---

The problems exists in final jaxb 2.2 spec PDF:

1, there's no TOC, it's hard to navigate the content.
2, The content is not intact.   At least, the changes log section of 2.2 spec 
is exactly the same with that of 2.2 spec.


Does anyone know how to report these problems to JCP ?  

> Create JAXB 2.2 spec jar
> 
>
> Key: GERONIMO-5093
> URL: https://issues.apache.org/jira/browse/GERONIMO-5093
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: javaee6, specs
>Affects Versions: 3.0
>Reporter: Rick McGuire
>Assignee: Shawn Jiang
> Fix For: 3.0
>
>
> A new version of the jaxb specs is needed for the 2.2 level. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Discussion: Possible fixes for GERONIMO-5180

2010-03-12 Thread Ashish Jain 
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