[jira] Assigned: (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:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4983: - Assignee: Shawn Jiang (was: Ashish Jain) 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: Shawn Jiang 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] Assigned: (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:all-tabpanel
]
Shawn Jiang reassigned GERONIMO-4896:
-
Assignee: Shawn Jiang (was: Ashish Jain)
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: Shawn Jiang
Fix For: 2.1.5, 3.0, Wish List
Attachments: 4896.patch, 4896_updated.patch, 4896_updated_21.patch,
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] Assigned: (GERONIMO-5055) Informix tranql XA 1.2 snapshot leads to weird admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-5055: - Assignee: Shawn Jiang (was: Ashish Jain) Informix tranql XA 1.2 snapshot leads to weird admin console - Key: GERONIMO-5055 URL: https://issues.apache.org/jira/browse/GERONIMO-5055 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.5, 2.2.1 Environment: g215 and g221 tomcat assembly Reporter: Ashish Jain Assignee: Shawn Jiang Fix For: 2.1.5, 2.2.1 Attachments: 5055_21.patch Using Informix tranql XA 1.2 snapshot with g 215 and g221 leads to weird admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4620) Database Security Realm is removed from admin consonle after delete datasource it's based
[ https://issues.apache.org/jira/browse/GERONIMO-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12831349#action_12831349 ] Lu Jiang commented on GERONIMO-4620: As Ivan mentioned above,the expected behavior is that the security realm file is not to be deleted when you delete the datasource it depends on.So the realm file will stay in the ropository,but we should also keep the consistency on console,when click Security Realm on console ,the security realm file is expected to be showed. Database Security Realm is removed from admin consonle after delete datasource it's based -- Key: GERONIMO-4620 URL: https://issues.apache.org/jira/browse/GERONIMO-4620 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.0.3, 2.1.4, 2.2 Environment: os:winxp Reporter: viola.lu Assignee: Ivan Priority: Minor Fix For: 2.1.5, 2.2 Attachments: GERONIMO-4620(2).patch 1.Create a embedded database SecurityDatabase containing user and group tables 2.Create a datasource SecurityDS for this database 3.Create a security realm named SecurityRealm and choose datasource :SecurityDS 4.Delete SecurityDS datasource, meantime SecurityRealm is removed from admin console -security realm porlet, but under repository\console\realm folder, this realm still exists. So if i create the same one realm, erros in server.log , and cann't create new realm. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5124) No actions for JMS Resouces
[ https://issues.apache.org/jira/browse/GERONIMO-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lu Jiang closed GERONIMO-5124. -- Resolution: Fixed Fix Version/s: 2.2.1 Since this is not a feature of g 2.1.5,but a feature of g 2.2. So I will close this JIRA. If you want to use this feature,just try geronimo 2.2:) No actions for JMS Resouces --- Key: GERONIMO-5124 URL: https://issues.apache.org/jira/browse/GERONIMO-5124 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.5 Environment: OS:windows 7 x86 Geronimo:2.1.1.5-SNAPSHOT Reporter: Lu Jiang Fix For: 2.2.1 Click Console Navigation-Services-JMS Resources,then you will find all available JMS Resource Groups It's expected to privide actions for each JMS Resource like Browse,Send ,Purge.. But currently no links for the these operations are provided under column Actions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5123) Creating Geronimo Plugin is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lu Jiang closed GERONIMO-5123. -- Resolution: Cannot Reproduce This JIRA can not be reproduced in the latest build ,so close it. Creating Geronimo Plugin is not supported -- Key: GERONIMO-5123 URL: https://issues.apache.org/jira/browse/GERONIMO-5123 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1.5 Environment: OS: Windows 7 Architecture x86 Geronimo :2.1.5-SNAPSHOT Build 2010.02.01 Reporter: Lu Jiang 1.start geronimo 2. in admin console, click application - plugin 3.in Create Geronimo Plugin portlet, it's expected to list all available modules ,thus you can hoose a configuration in the current Geronimo server and click Export Plugin to create plugin. but currently,nothing is listed in the box for you to choose. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4620) Database Security Realm is removed from admin consonle after delete datasource it's based
[ https://issues.apache.org/jira/browse/GERONIMO-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-4620. -- Resolution: Fixed Database Security Realm is removed from admin consonle after delete datasource it's based -- Key: GERONIMO-4620 URL: https://issues.apache.org/jira/browse/GERONIMO-4620 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.0.3, 2.1.4, 2.2 Environment: os:winxp Reporter: viola.lu Assignee: Ivan Priority: Minor Fix For: 2.1.5, 2.2 Attachments: GERONIMO-4620(2).patch 1.Create a embedded database SecurityDatabase containing user and group tables 2.Create a datasource SecurityDS for this database 3.Create a security realm named SecurityRealm and choose datasource :SecurityDS 4.Delete SecurityDS datasource, meantime SecurityRealm is removed from admin console -security realm porlet, but under repository\console\realm folder, this realm still exists. So if i create the same one realm, erros in server.log , and cann't create new realm. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5055) Informix tranql XA 1.2 snapshot leads to weird admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-5055. - Resolution: Fixed Fix Version/s: 3.0 Committed the patch to 21,22,trunk. Thanks Ashish for the patch. Closing it. BTW: Please use 4 spaces instead of tab in the patch. Informix tranql XA 1.2 snapshot leads to weird admin console - Key: GERONIMO-5055 URL: https://issues.apache.org/jira/browse/GERONIMO-5055 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.5, 2.2.1 Environment: g215 and g221 tomcat assembly Reporter: Ashish Jain Assignee: Shawn Jiang Fix For: 2.1.5, 2.2.1, 3.0 Attachments: 5055_21.patch Using Informix tranql XA 1.2 snapshot with g 215 and g221 leads to weird admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5055) Informix tranql XA 1.2 snapshot leads to weird admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-5055: -- Attachment: 5055_22_en.patch Informix tranql XA 1.2 snapshot leads to weird admin console - Key: GERONIMO-5055 URL: https://issues.apache.org/jira/browse/GERONIMO-5055 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.5, 2.2.1 Environment: g215 and g221 tomcat assembly Reporter: Ashish Jain Assignee: Shawn Jiang Fix For: 2.1.5, 2.2.1, 3.0 Attachments: 5055_21.patch, 5055_22_en.patch Using Informix tranql XA 1.2 snapshot with g 215 and g221 leads to weird admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5055) Informix tranql XA 1.2 snapshot leads to weird admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12831398#action_12831398 ] Ashish Jain commented on GERONIMO-5055: --- Thanks Shawn for the review and commit. Uploading a patch for g22. This only takes care of English. I was not sure how to modify the properties file for chinese and japanese. Informix tranql XA 1.2 snapshot leads to weird admin console - Key: GERONIMO-5055 URL: https://issues.apache.org/jira/browse/GERONIMO-5055 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.5, 2.2.1 Environment: g215 and g221 tomcat assembly Reporter: Ashish Jain Assignee: Shawn Jiang Fix For: 2.1.5, 2.2.1, 3.0 Attachments: 5055_21.patch, 5055_22_en.patch Using Informix tranql XA 1.2 snapshot with g 215 and g221 leads to weird admin console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release geronimo-atinject_1.0_spec-1.0-beta - RC2
+1 On 2/8/2010 10:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq to the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the Inject Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-006/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-atinject_1.0_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-el_2.2_spec-1.0-beta - RC2
+1 On 2/8/2010 10:48 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq for the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the EL 2.2 Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-007/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-interceptor_1.1_spec-1.0.0-beta
+1 On 2/3/2010 10:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release a Beta of the Interceptor Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-073/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-interceptor_1.1_spec-1.0.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-el_1.0_spec-1.0.2 (2nd try)
+1 Passed mvn rat:check Was able to build it from the tag. JAR file has the required Notice/License files. I didn't perform any TCK testing on it. -Donald On 2/9/10 1:05 AM, Delos wrote: Hi, I'd like to release v1.0.2 of the EL（Expression Language）1.0 Spec API. Ivan has run the signature testing and some el related testcases. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-071/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.2/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards, Delos
[jira] Updated: (GERONIMO-5036) [OpenEJB] Unable to clear Sun JarFileFactory cache: warning after upgrading to Sun JDK 1.6.0 u18
[ https://issues.apache.org/jira/browse/GERONIMO-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-5036: --- Component/s: JVM-compatibility Affects Version/s: 2.1.4 Fix Version/s: 2.1.5 [OpenEJB] Unable to clear Sun JarFileFactory cache: warning after upgrading to Sun JDK 1.6.0 u18 Key: GERONIMO-5036 URL: https://issues.apache.org/jira/browse/GERONIMO-5036 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: JVM-compatibility, OpenEJB Affects Versions: 2.1.4, 2.2 Environment: Windows XP Reporter: Johannes Weberhofer Priority: Critical Fix For: 2.1.5, 2.2.1 After Upgrading to Sun JDK 1.6.0 u18 the above mentioned warning occures. The bug is filed in OPENEJB-1131, a fix has been provided in the openejb3 svn for ClassLoaderUtil.java with revision number 98 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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-tabpanelfocusedCommentId=12831470#action_12831470 ] Ashish Jain commented on GERONIMO-4795: --- I have written a new Timer gbean which will periodically scan the repository and will accordingly update the config.xml. The time interval in which the gbean will scan the repository is configurable. Please review the uploaded code. Thanks Ashish 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: 2.1.5 Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 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] Updated: (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:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Attachment: MultipleServer-1.0.jar 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: 2.1.5 Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 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] Updated: (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:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Attachment: plan.xml Attaching the MultipleServer-1.0.jar and the plan file. 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: 2.1.5 Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 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.
Adding servicemix improvements to the geronimo spec bundles.
The bundle version of the some of the geronimo spec jars have some issues when used in an OSGi environment with locating resources in the META-INF directories of other bundles. The servicemix project has solved this by repackaging the geronimo versions with the addition of a bundle Activator that watches for new bundles to be started and checks these new bundles for resources of interest, processing them at start time. This appears to work well for servicemix, and now that we're converting using these jars as bundles in Geronimo 3.0, we're going to be running into the same issues. This Jira issue has been opened to address the problem and attempt to merge what service mix has done back into the base Geronio projects: https://issues.apache.org/jira/browse/GERONIMO-5133 I've started looking at doing this, beginning with the activation spec, which should be one of the simpler ones to deal with. I immediately ran into a couple of issues I'd like some feedback on. 1) The servicemix project has core support project with some base classes that get copied into each bundlized jar file. The copying is not really an issue, but where is the appropriate place in the svn tree to host this. It's not really spec jar directly, but does end up contributing to a number of spec jars. I think it probably belongs in the spec tree, but I'd like some consensus before I create a new project there. 2) Servicemix does a lot of what it does by adding a subclass of one or more spec classes to the package. In some (most?) cases, this subclass cannot accomplish what it needs using the classes as implemented in the Geronimo version because of method/class access qualifiers. For example, in the activation bundle, Servicemix replaces the MailcapCommandMap class with one where two private methods have been made protected. Then it adds an additional OsgiMailcapCommandMap class to implement the additional processing required when this jar is loaded as a bundle. This modification to the MailcapCommandMap class will cause TCK problems because the additional protected methods will cause sigtest failures. Package scope for these methods would allow these to pass the sig tests, but this would require that the activator class and the subclass be package scope classes in the javax.activation package rather than segregated in a separate org.apache.geronimo.* package. So, using this, the modification would be - The base MailcapCommandMap class has two methods changed from private scope to package scope. - Two additional classes, javax.activation.Activator and javax.activation.OsgiMailcapCommandMap are added to the bundle. These classes will be defined with package scope so that they don't trigger sigtest failures. This is probably the simplest working solution I see. A more complicated solution would be to refactor a lot of the code from the MailcapCommandMap class into a separate worker class in an implementation-specific package that can be shared between the two versions, but I'm not sure there's much to be gained from making that big of a change. Rick
[jira] Updated: (GERONIMO-4040) Tutorials - AJAX with JSF
[ https://issues.apache.org/jira/browse/GERONIMO-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4040: -- Assignee: (was: Ashish Jain) Tutorials - AJAX with JSF - Key: GERONIMO-4040 URL: https://issues.apache.org/jira/browse/GERONIMO-4040 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop an AJAX with JSF tutorial addressing (when applicable) the following common topics. This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4057) Tutorials - Clone your server environment with plugins
[ https://issues.apache.org/jira/browse/GERONIMO-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4057: -- Assignee: (was: Ashish Jain) Tutorials - Clone your server environment with plugins -- Key: GERONIMO-4057 URL: https://issues.apache.org/jira/browse/GERONIMO-4057 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: documentation Affects Versions: 2.1, 2.1.1 Reporter: Hernan Cunico Geronimo v2.1 documentation, Tutorials section. Develop a tutorial for Cloning your server environment with plugins addressing the following common topics (use this list as the initial guideline). This document should also match the styling used in the existing tutorials. * Setting up Eclipse for Application development * Sample application overview _identify the different components_ * Prerequisites _external resources (i.e. databases, connection pools, JMS queues, etc)_ * Sample app creation _breakdown into multiple bullets_ * Deploy and Test the application See http://cwiki.apache.org/GMOxDOC21/tutorials.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5002) Attribute clusterName required in config-substitution.properties for geronoimo 2.1.5
[ https://issues.apache.org/jira/browse/GERONIMO-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain reassigned GERONIMO-5002: - Assignee: Ashish Jain Attribute clusterName required in config-substitution.properties for geronoimo 2.1.5 Key: GERONIMO-5002 URL: https://issues.apache.org/jira/browse/GERONIMO-5002 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.1.5 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5 After applying the fix for 2.1 branch through GERONIMO-4187 it is required to have the attribute clusterName added to config-substitution.properties -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release geronimo-el_1.0_spec-1.0.2 (2nd try)
I have run the signature testing and some el related testcases with the commands below: ./runtests signaturetest ./runttests com/sun/ts/tests/jsp/api/javax_el From the log files, all el related cases passed. If I did not miss any testcase, el package should pass the TCK. +1 在 2010年2月9日 下午9:48，Donald Woods dwo...@apache.org写道： +1 Passed mvn rat:check Was able to build it from the tag. JAR file has the required Notice/License files. I didn't perform any TCK testing on it. -Donald On 2/9/10 1:05 AM, Delos wrote: Hi, I'd like to release v1.0.2 of the EL（Expression Language）1.0 Spec API. Ivan has run the signature testing and some el related testcases. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-071/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.2/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards, Delos -- Ivan
[jira] Created: (GERONIMO-5139) Slim down the new sample DataCDInfo by using packages in server repository
Slim down the new sample DataCDInfo by using packages in server repository -- Key: GERONIMO-5139 URL: https://issues.apache.org/jira/browse/GERONIMO-5139 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: sample apps Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia The DataCDInfo built-out is a little big, so provide patches to make it slim by using packages in server repo. Of cause, some small updates as well. Please help commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5139) Slim down the new sample DataCDInfo by using packages in server repository
[ https://issues.apache.org/jira/browse/GERONIMO-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5139: -- Attachment: GERONIMO-5139_trunk.patch GERONIMO-5139_2.2branch.patch GERONIMO-5139_2.1branch.patch Slim down the new sample DataCDInfo by using packages in server repository -- Key: GERONIMO-5139 URL: https://issues.apache.org/jira/browse/GERONIMO-5139 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: GERONIMO-5139_2.1branch.patch, GERONIMO-5139_2.2branch.patch, GERONIMO-5139_trunk.patch The DataCDInfo built-out is a little big, so provide patches to make it slim by using packages in server repo. Of cause, some small updates as well. Please help commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5036) [OpenEJB] Unable to clear Sun JarFileFactory cache: warning after upgrading to Sun JDK 1.6.0 u18
[ https://issues.apache.org/jira/browse/GERONIMO-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller reassigned GERONIMO-5036: -- Assignee: Kevan Miller [OpenEJB] Unable to clear Sun JarFileFactory cache: warning after upgrading to Sun JDK 1.6.0 u18 Key: GERONIMO-5036 URL: https://issues.apache.org/jira/browse/GERONIMO-5036 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: JVM-compatibility, OpenEJB Affects Versions: 2.1.4, 2.2 Environment: Windows XP Reporter: Johannes Weberhofer Assignee: Kevan Miller Priority: Critical Fix For: 2.1.5, 2.2.1 After Upgrading to Sun JDK 1.6.0 u18 the above mentioned warning occures. The bug is filed in OPENEJB-1131, a fix has been provided in the openejb3 svn for ClassLoaderUtil.java with revision number 98 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5121) Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests
[ https://issues.apache.org/jira/browse/GERONIMO-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods resolved GERONIMO-5121. Resolution: Fixed Fix Version/s: 3.0 Rick applied the patches and I have created release candidates for them. Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests -- Key: GERONIMO-5121 URL: https://issues.apache.org/jira/browse/GERONIMO-5121 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: specs Reporter: Gurkan Erdogdu Assignee: Rick McGuire Fix For: 3.0 Attachments: atinject.patch, jcdi.patch Update geronimo-jcdi and geronimo-atinject to pass TCK Signature Tests. This includes David Jencks comments about serialize ids and enumeration ordering. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4946) Add optional OpenJPA2 plugin to server builds, but not the assemblies
[ https://issues.apache.org/jira/browse/GERONIMO-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4946: --- Affects Version/s: 2.2.1 2.1.5 2.1.3 2.1.4 Fix Version/s: (was: Wish List) 2.1.3 2.2 plugins updated to OpenJPA 2.0.0-beta and release candidates put up for a vote Add optional OpenJPA2 plugin to server builds, but not the assemblies - Key: GERONIMO-4946 URL: https://issues.apache.org/jira/browse/GERONIMO-4946 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Plugins Affects Versions: 2.1.3, 2.1.4, 2.1.5, 2.2, 2.2.1 Reporter: Donald Woods Assignee: Donald Woods Fix For: 2.1.3, 2.2 I'm trying to build a openjpa 2.0 plugin for 2.2, which would replace the existing openjpa 1.2 plugin when installed. https://svn.apache.org/repos/asf/geronimo/server/branches/2.2/plugins/openjpa2 The following works as expected: 1) when the new openjpa2 plugin and deployer are installed they replace the existing ones via the obsoletes directive in config.xml 2) the artifact-alias.properties and client-artifact-alias.properties are updated with: org.apache.geronimo.configs/openjpa//car=org.apache.geronimo.configs/openjpa2/2.2-SNAPSHOT/car org.apache.geronimo.configs/persistence-jpa10-deployer//car=org.apache.geronimo.configs/persistence-jpa20-deployer/2.2-SNAPSHOT/car Issues: 1) the offline-deployer-config.xml contains entries for the old openjpa and jpa10-deployer modules and the new openjpa2 and jpa20-deployer modules. I would have expected the old ones to be removed, as was done for the server config.xml 2) the openjeb module fails to load (even after server restart) using the new plugins, even though entries were added to artifact-alias.properties - aused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration gbean failed to start org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car reason: Missing dependency: org.apache.geronimo.configs/openjpa/2.2-SNAPSHOT/car at org.apache.geronimo.kernel.config.KernelConfigurationManager.load(KernelConfigurationManager.java:166) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Adding servicemix improvements to the geronimo spec bundles.
I think we should consider looking/using the code that was added to Aries to deal with this service lookup issue. It uses the extender patter to discover the META-INF/services resources in bundles and registers services in service registry for them (servicemix solution does not). So in most cases we wouldn't need to add an Activator to the spec bundle and the lookup for the actual implementation would happen via service registry API (so no additional API would be required to lookup the implementation classes as in servicemix solution). However, there might be some improvements that we might want to do in Aries implementation. For example, to delay class loading and instantiation as long as possible as it is done today in servicemix solution. And of course, some specs will need custom solutions. Jarek On Tue, Feb 9, 2010 at 9:36 AM, Rick McGuire rick...@gmail.com wrote: The bundle version of the some of the geronimo spec jars have some issues when used in an OSGi environment with locating resources in the META-INF directories of other bundles. The servicemix project has solved this by repackaging the geronimo versions with the addition of a bundle Activator that watches for new bundles to be started and checks these new bundles for resources of interest, processing them at start time. This appears to work well for servicemix, and now that we're converting using these jars as bundles in Geronimo 3.0, we're going to be running into the same issues. This Jira issue has been opened to address the problem and attempt to merge what service mix has done back into the base Geronio projects: https://issues.apache.org/jira/browse/GERONIMO-5133 I've started looking at doing this, beginning with the activation spec, which should be one of the simpler ones to deal with. I immediately ran into a couple of issues I'd like some feedback on. 1) The servicemix project has core support project with some base classes that get copied into each bundlized jar file. The copying is not really an issue, but where is the appropriate place in the svn tree to host this. It's not really spec jar directly, but does end up contributing to a number of spec jars. I think it probably belongs in the spec tree, but I'd like some consensus before I create a new project there. 2) Servicemix does a lot of what it does by adding a subclass of one or more spec classes to the package. In some (most?) cases, this subclass cannot accomplish what it needs using the classes as implemented in the Geronimo version because of method/class access qualifiers. For example, in the activation bundle, Servicemix replaces the MailcapCommandMap class with one where two private methods have been made protected. Then it adds an additional OsgiMailcapCommandMap class to implement the additional processing required when this jar is loaded as a bundle. This modification to the MailcapCommandMap class will cause TCK problems because the additional protected methods will cause sigtest failures. Package scope for these methods would allow these to pass the sig tests, but this would require that the activator class and the subclass be package scope classes in the javax.activation package rather than segregated in a separate org.apache.geronimo.* package. So, using this, the modification would be - The base MailcapCommandMap class has two methods changed from private scope to package scope. - Two additional classes, javax.activation.Activator and javax.activation.OsgiMailcapCommandMap are added to the bundle. These classes will be defined with package scope so that they don't trigger sigtest failures. This is probably the simplest working solution I see. A more complicated solution would be to refactor a lot of the code from the MailcapCommandMap class into a separate worker class in an implementation-specific package that can be shared between the two versions, but I'm not sure there's much to be gained from making that big of a change. Rick
Re: Adding servicemix improvements to the geronimo spec bundles.
My original intent was to put all the servicemix code directly in the geronimo spec project, but at that time, there has been a push back to avoid mixing the plain apis with some osgi concerns. I don't have much problems in moving this code back to geronimo or aries or anywhere else personally, or improving it (there are lots of things that could be improved). The only thing i'd like to avoid is to have 3 pieces of code doing similar things On Tue, Feb 9, 2010 at 15:36, Rick McGuire rick...@gmail.com wrote: The bundle version of the some of the geronimo spec jars have some issues when used in an OSGi environment with locating resources in the META-INF directories of other bundles. The servicemix project has solved this by repackaging the geronimo versions with the addition of a bundle Activator that watches for new bundles to be started and checks these new bundles for resources of interest, processing them at start time. This appears to work well for servicemix, and now that we're converting using these jars as bundles in Geronimo 3.0, we're going to be running into the same issues. This Jira issue has been opened to address the problem and attempt to merge what service mix has done back into the base Geronio projects: https://issues.apache.org/jira/browse/GERONIMO-5133 I've started looking at doing this, beginning with the activation spec, which should be one of the simpler ones to deal with. I immediately ran into a couple of issues I'd like some feedback on. 1) The servicemix project has core support project with some base classes that get copied into each bundlized jar file. The copying is not really an issue, but where is the appropriate place in the svn tree to host this. It's not really spec jar directly, but does end up contributing to a number of spec jars. I think it probably belongs in the spec tree, but I'd like some consensus before I create a new project there. 2) Servicemix does a lot of what it does by adding a subclass of one or more spec classes to the package. In some (most?) cases, this subclass cannot accomplish what it needs using the classes as implemented in the Geronimo version because of method/class access qualifiers. For example, in the activation bundle, Servicemix replaces the MailcapCommandMap class with one where two private methods have been made protected. Then it adds an additional OsgiMailcapCommandMap class to implement the additional processing required when this jar is loaded as a bundle. This modification to the MailcapCommandMap class will cause TCK problems because the additional protected methods will cause sigtest failures. Package scope for these methods would allow these to pass the sig tests, but this would require that the activator class and the subclass be package scope classes in the javax.activation package rather than segregated in a separate org.apache.geronimo.* package. So, using this, the modification would be - The base MailcapCommandMap class has two methods changed from private scope to package scope. - Two additional classes, javax.activation.Activator and javax.activation.OsgiMailcapCommandMap are added to the bundle. These classes will be defined with package scope so that they don't trigger sigtest failures. This is probably the simplest working solution I see. A more complicated solution would be to refactor a lot of the code from the MailcapCommandMap class into a separate worker class in an implementation-specific package that can be shared between the two versions, but I'm not sure there's much to be gained from making that big of a change. Rick -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: [VOTE] Release geronimo-el_1.0_spec-1.0.2 (2nd try)
The subversion tag does not match the contents of your source distribution (you've updated the LICENSE file in your source distribution). IMO, the source distribution is correct (and this is what we are really voting on). However, IMO the subversion tag should match the contents of your source distribution. So, will vote -1, until this is fixed. Otherwise, everything else looks good -- source, signatures/checksums, build. --kevan On Feb 9, 2010, at 1:05 AM, Delos wrote: Hi, I'd like to release v1.0.2 of the EL（Expression Language）1.0 Spec API. Ivan has run the signature testing and some el related testcases. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-071/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.2/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards, Delos
Re: [VOTE] Release geronimo-interceptor_1.1_spec-1.0.0-beta
+1 Source, signature/checksums, build -- all look good. --kevan On Feb 3, 2010, at 10:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release a Beta of the Interceptor Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-073/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-interceptor_1.1_spec-1.0.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-el_2.2_spec-1.0-beta - RC2
+1 Checked source, signature/checksums, build. All looked good. --kevan On Feb 8, 2010, at 10:48 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq for the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the EL 2.2 Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-007/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-atinject_1.0_spec-1.0-beta - RC2
+1 Verified source, signature/checksums, build. --kevan On Feb 8, 2010, at 10:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq to the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the Inject Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-006/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-atinject_1.0_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
[jira] Closed: (GERONIMO-5002) Attribute clusterName required in config-substitution.properties for geronoimo 2.1.5
[ https://issues.apache.org/jira/browse/GERONIMO-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-5002. - Resolution: Invalid Attribute clusterName required in config-substitution.properties for geronoimo 2.1.5 Key: GERONIMO-5002 URL: https://issues.apache.org/jira/browse/GERONIMO-5002 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Clustering Affects Versions: 2.1.5 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5 After applying the fix for 2.1 branch through GERONIMO-4187 it is required to have the attribute clusterName added to config-substitution.properties -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release geronimo-interceptor_1.1_spec-1.0.0-beta
+1 On Feb 3, 2010, at 7:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release a Beta of the Interceptor Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-073/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-interceptor_1.1_spec-1.0.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-atinject_1.0_spec-1.0-beta - RC2
+1 On Feb 8, 2010, at 7:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq to the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the Inject Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-006/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-atinject_1.0_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-atinject_1.0_spec-1.0-beta - RC2
+1 Jay Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq to the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the Inject Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-006/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-atinject_1.0_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-el_2.2_spec-1.0-beta - RC2
+1 Jay Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq for the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the EL 2.2 Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-007/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-interceptor_1.1_spec-1.0.0-beta
+1 Jay Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release a Beta of the Interceptor Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-073/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-interceptor_1.1_spec-1.0.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-el_2.2_spec-1.0-beta - RC2
Looking through the code and sun javaodoc http://javadoc.glassfish.org/javaee6/apidoc/ there are quite a few classes that are serializable but where not serialVersionUiD is specified in the javadoc. My preferred course of action would be to try to get Sun to include these in the javadoc so we can implement them. My next preferred course of action would be to extract the serialVersionUID values from the sun implementations and use them. Do we have any contacts at sun that could assure us that the values in the sun implementation happen to be correct? I imagine this applies also to the el 1.o spec although I haven't located the javadoc for that. thanks david jencks On Feb 8, 2010, at 7:48 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq for the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the EL 2.2 Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-007/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-interceptor_1.1_spec-1.0.0-beta
+1 source bundle builds for me and legal files look ok. No seriaizlable or enums to worry about :-) thanks david jencks On Feb 3, 2010, at 7:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release a Beta of the Interceptor Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-073/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-interceptor_1.1_spec-1.0.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-atinject_1.0_spec-1.0-beta - RC2
+1 builds from source bundle, legal files look ok, no seriailizable/enums to worry about. thanks david jencks On Feb 8, 2010, at 7:36 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release and as a prereq to the geronimo-jcdi_1.0_spec-1.0-beta release, I would like to release a Beta of the Inject Spec API. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-006/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-atinject_1.0_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-jcdi_1.0_spec-1.0-beta - RC2
On Feb 8, 2010, at 8:00 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release candidate 2 of a Beta of the Java Contexts and Dependency Injection (JCDI) JSR-299 Spec API. Note: This release depends upon 3 other votes in progress: geronimo-el_2.2_spec-1.0-beta Are you sure? When I try to build the source bundle I get... [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.geronimo.specs:geronimo-el_1.0_spec:jar:1.0.2 thanks david jencks geronimo-atinject_1.0_spec-1.0-beta geronimo-interceptor_1.1_spec-1.0.0-beta Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-008/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jcdi_1.0_spec-1.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-jcdi_1.0_spec-1.0-beta - RC2
OK, not sure what happened here, but the change went in r907919 and then the release plugin updated the artifact version in r907920 and created the tag in r907921 and the trunk code has the expected changes, but the tag doesn't?!?!?! I'll spin a RC3 tonight to fix the tag. URL: http://svn.apache.org/viewvc?rev=907919view=rev Log: upgrade to stagged geronimo-el_2.2_spec-1.0-beta Modified: geronimo/specs/trunk/geronimo-jcdi_1.0_spec/pom.xml Modified: geronimo/specs/trunk/geronimo-jcdi_1.0_spec/pom.xml URL: http://svn.apache.org/viewvc/geronimo/specs/trunk/geronimo-jcdi_1.0_spec/pom.xml?rev=907919r1=907918r2=907919view=diff == --- geronimo/specs/trunk/geronimo-jcdi_1.0_spec/pom.xml (original) +++ geronimo/specs/trunk/geronimo-jcdi_1.0_spec/pom.xml Tue Feb 9 03:52:58 2010 @@ -78,7 +78,7 @@ dependency groupIdorg.apache.geronimo.specs/groupId artifactIdgeronimo-el_2.2_spec/artifactId -version1.0-SNAPSHOT/version +version1.0-beta/version scopeprovided/scope /dependency dependency -Donald On 2/9/10 5:15 PM, David Jencks wrote: On Feb 8, 2010, at 8:00 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release candidate 2 of a Beta of the Java Contexts and Dependency Injection (JCDI) JSR-299 Spec API. Note: This release depends upon 3 other votes in progress: geronimo-el_2.2_spec-1.0-beta Are you sure? When I try to build the source bundle I get... [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.geronimo.specs:geronimo-el_1.0_spec:jar:1.0.2 thanks david jencks geronimo-atinject_1.0_spec-1.0-beta geronimo-interceptor_1.1_spec-1.0.0-beta Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-008/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jcdi_1.0_spec-1.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-jcdi_1.0_spec-1.0-beta - RC2 - canceled
Seems that the tag is somehow missing the changes from r907919 and 907920 (upgrade to el_2.2-1.0-beta), even though the tag was created as r907921 using the maven release plugin Will spin a RC3 tonight to fix the tag. -Donald On 2/8/10 11:00 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release candidate 2 of a Beta of the Java Contexts and Dependency Injection (JCDI) JSR-299 Spec API. Note: This release depends upon 3 other votes in progress: geronimo-el_2.2_spec-1.0-beta geronimo-atinject_1.0_spec-1.0-beta geronimo-interceptor_1.1_spec-1.0.0-beta Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-008/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jcdi_1.0_spec-1.0-beta Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
[jira] Updated: (GERONIMO-5139) Slim down the new sample DataCDInfo by using packages in server repository
[ https://issues.apache.org/jira/browse/GERONIMO-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5139: -- Attachment: (was: GERONIMO-5139_trunk.patch) Slim down the new sample DataCDInfo by using packages in server repository -- Key: GERONIMO-5139 URL: https://issues.apache.org/jira/browse/GERONIMO-5139 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: GERONIMO-5139_2.1branch.patch, GERONIMO-5139_2.2branch.patch, GERONIMO-5139_trunk.patch The DataCDInfo built-out is a little big, so provide patches to make it slim by using packages in server repo. Of cause, some small updates as well. Please help commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5139) Slim down the new sample DataCDInfo by using packages in server repository
[ https://issues.apache.org/jira/browse/GERONIMO-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5139: -- Attachment: (was: GERONIMO-5139_2.1branch.patch) Slim down the new sample DataCDInfo by using packages in server repository -- Key: GERONIMO-5139 URL: https://issues.apache.org/jira/browse/GERONIMO-5139 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: GERONIMO-5139_2.1branch.patch, GERONIMO-5139_2.2branch.patch, GERONIMO-5139_trunk.patch The DataCDInfo built-out is a little big, so provide patches to make it slim by using packages in server repo. Of cause, some small updates as well. Please help commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5139) Slim down the new sample DataCDInfo by using packages in server repository
[ https://issues.apache.org/jira/browse/GERONIMO-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5139: -- Attachment: (was: GERONIMO-5139_2.2branch.patch) Slim down the new sample DataCDInfo by using packages in server repository -- Key: GERONIMO-5139 URL: https://issues.apache.org/jira/browse/GERONIMO-5139 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: GERONIMO-5139_2.1branch.patch, GERONIMO-5139_2.2branch.patch, GERONIMO-5139_trunk.patch The DataCDInfo built-out is a little big, so provide patches to make it slim by using packages in server repo. Of cause, some small updates as well. Please help commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5139) Slim down the new sample DataCDInfo by using packages in server repository
[ https://issues.apache.org/jira/browse/GERONIMO-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5139: -- Attachment: GERONIMO-5139_trunk.patch GERONIMO-5139_2.2branch.patch GERONIMO-5139_2.1branch.patch Slim down the new sample DataCDInfo by using packages in server repository -- Key: GERONIMO-5139 URL: https://issues.apache.org/jira/browse/GERONIMO-5139 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: GERONIMO-5139_2.1branch.patch, GERONIMO-5139_2.2branch.patch, GERONIMO-5139_trunk.patch The DataCDInfo built-out is a little big, so provide patches to make it slim by using packages in server repo. Of cause, some small updates as well. Please help commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release geronimo-el_1.0_spec-1.0.2 (2nd try)
The staging repository is not synchronized with tags. I have recreated it in Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-009 In previous voting, Donald told me the license information for W3C and OMG can be removed, since they're already in the common LICENSE file of geronimo specs. So the tag content should be right. 在 2010年2月10日 上午1:26，Kevan Miller kevan.mil...@gmail.com写道： The subversion tag does not match the contents of your source distribution (you've updated the LICENSE file in your source distribution). IMO, the source distribution is correct (and this is what we are really voting on). However, IMO the subversion tag should match the contents of your source distribution. So, will vote -1, until this is fixed. Otherwise, everything else looks good -- source, signatures/checksums, build. --kevan On Feb 9, 2010, at 1:05 AM, Delos wrote: Hi, I'd like to release v1.0.2 of the EL（Expression Language）1.0 Spec API. Ivan has run the signature testing and some el related testcases. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-071/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.2/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards, Delos -- Best Regards, Delos
[jira] Commented: (GERONIMO-5139) Slim down the new sample DataCDInfo by using packages in server repository
[ https://issues.apache.org/jira/browse/GERONIMO-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12831825#action_12831825 ] Delos Dai commented on GERONIMO-5139: - Thanks Forrest! commit the patch for 2.1 with rev908308, for 2.2 with rev908309, for trunk with 908311 Slim down the new sample DataCDInfo by using packages in server repository -- Key: GERONIMO-5139 URL: https://issues.apache.org/jira/browse/GERONIMO-5139 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: sample apps Affects Versions: 2.1.5, 2.2.1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Attachments: GERONIMO-5139_2.1branch.patch, GERONIMO-5139_2.2branch.patch, GERONIMO-5139_trunk.patch The DataCDInfo built-out is a little big, so provide patches to make it slim by using packages in server repo. Of cause, some small updates as well. Please help commit. thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 908039
Geronimo Revision: 908039 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100209/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100209/unit-test-reports
[INFO] Checking legal files in: geronimo-jetty8-clustering-wadi-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/jetty8/geronimo-jetty8-clustering-wadi/target/geronimo-jetty8-clustering-wadi-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-jetty8-clustering-wadi/3.0-SNAPSHOT/geronimo-jetty8-clustering-wadi-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing
org/apache/geronimo/modules/geronimo-jetty8-clustering-wadi/3.0-SNAPSHOT/geronimo-jetty8-clustering-wadi-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO]
[INFO] Building Geronimo Plugins, Jetty 8 :: Clustering Builder for WADI Core
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] snapshot
org.apache.geronimo.modules:geronimo-jetty8-clustering-wadi:3.0-SNAPSHOT:
checking for updates from jetty.oss.sonatype.org
[INFO] snapshot
org.apache.geronimo.modules:geronimo-jetty8-clustering-wadi:3.0-SNAPSHOT:
checking for updates from ops4j.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-jetty8-clustering-wadi:3.0-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-jetty8-clustering-wadi:3.0-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 2.602 seconds
Time to generate code: 0.122 seconds
Time to compile code: 7.678 seconds
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty8/geronimo-jetty8-clustering-builder-wadi/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty8/geronimo-jetty8-clustering-builder-wadi/src/main/filtered-resources
[INFO] Copying 19 resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 1 source file to
/home/geronimo/geronimo/trunk/plugins/jetty8/geronimo-jetty8-clustering-builder-wadi/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty8/geronimo-jetty8-clustering-builder-wadi/src/test/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty8/geronimo-jetty8-clustering-builder-wadi/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@bf00bf0
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/jetty8/geronimo-jetty8-clustering-builder-wadi/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [bundle:bundle {execution: default-bundle}]
JVMDUMP006I Processing dump event systhrow, detail
java/lang/OutOfMemoryError - please wait.
JVMDUMP032I JVM requested Snap dump using
'/home/geronimo/geronimo/trunk/Snap.20100209.205012.23172.0001.trc' in response
to an event
JVMDUMP010I Snap dump written to
/home/geronimo/geronimo/trunk/Snap.20100209.205012.23172.0001.trc
JVMDUMP032I JVM requested Heap dump using
'/home/geronimo/geronimo/trunk/heapdump.20100209.205012.23172.0002.phd' in
response to an event
JVMDUMP010I Heap dump written to
/home/geronimo/geronimo/trunk/heapdump.20100209.205012.23172.0002.phd
JVMDUMP032I JVM requested Java dump using
'/home/geronimo/geronimo/trunk/javacore.20100209.205012.23172.0003.txt' in
response to an event
JVMDUMP010I Java dump written to
/home/geronimo/geronimo/trunk/javacore.20100209.205012.23172.0003.txt
JVMDUMP013I Processed dump event systhrow, detail
java/lang/OutOfMemoryError.
[INFO]
[ERROR] FATAL
[VOTE] Release geronimo-jcdi_1.0_spec-1.0-beta - RC3
To support the upcoming OpenWebBeans milestone release, I would like to release candidate 3 of a Beta of the Java Contexts and Dependency Injection (JCDI) JSR-299 Spec API. Note: This release depends upon 3 other votes in progress: geronimo-el_2.2_spec-1.0-beta geronimo-atinject_1.0_spec-1.0-beta geronimo-interceptor_1.1_spec-1.0.0-beta Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-010/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jcdi_1.0_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release geronimo-jcdi_1.0_spec-1.0-beta - RC3
+1 The tag now matches the expected svn code level (el_2.2 reference is fixed.) Passes mvn rat:check Was able to build from source tag. No TCK testing performed. -Donald On 2/9/10 10:11 PM, Donald Woods wrote: To support the upcoming OpenWebBeans milestone release, I would like to release candidate 3 of a Beta of the Java Contexts and Dependency Injection (JCDI) JSR-299 Spec API. Note: This release depends upon 3 other votes in progress: geronimo-el_2.2_spec-1.0-beta geronimo-atinject_1.0_spec-1.0-beta geronimo-interceptor_1.1_spec-1.0.0-beta Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-010/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jcdi_1.0_spec-1.0-beta/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
[jira] Reopened: (GERONIMO-4997) Can not connect to a ldap server in an anonymous way
[
https://issues.apache.org/jira/browse/GERONIMO-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lu Jiang reopened GERONIMO-4997:
Fail to verify it on latest 2.1.5 and 2.2.1-SNAPSHOT build.
But if use g 2.1.4 and replace geronimo-security-2.1.4.jar under
Geronimo_HOME/repository/org/apache/geronimo/framework/geronimo-security with
the one in the attachment(this jar file is provided by Ivan),I can connect to a
ldap server anonymously.
Can not connect to a ldap server in an anonymous way
Key: GERONIMO-4997
URL: https://issues.apache.org/jira/browse/GERONIMO-4997
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: security
Affects Versions: 2.1.4, 2.2
Environment: OS:Windows XP SP2
Server: Geronimo 2.2
JDK:1.6
Reporter: Lu Jiang
Priority: Minor
Fix For: 2.1.5, 2.2.1, 3.0
I tried to deploy an web application which uses Apache Directory Server for
user authentication.
So I created a realm file as follows and add a reference to this realm file
in deploy plan
module xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
environment
moduleId
groupIdconsole.realm/groupId
artifactIdtestLDAP/artifactId
version1.0/version
typecar/type
/moduleId
dependencies
dependency
groupIdorg.apache.geronimo.framework/groupId
artifactIdj2ee-security/artifactId
typecar/type
/dependency
/dependencies
/environment
gbean name=testLDAP
class=org.apache.geronimo.security.realm.GenericSecurityRealm
xsi:type=dep:gbeanType
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
attribute name=realmNametestLDAP/attribute
reference name=ServerInfo
nameServerInfo/name
/reference
xml-reference name=LoginModuleConfiguration
log:login-config
xmlns:log=http://geronimo.apache.org/xml/ns/loginconfig-2.0;
log:login-module control-flag=REQUIRED
wrap-principals=false
log:login-domain-nametestLDAP/log:login-domain-name
log:login-module-classorg.apache.geronimo.security.realm.providers.LDAPLoginModule/log:login-module-class
log:option
name=connectionURLldap://pages.test.com:389/log:option
log:option
name=roleBaseou=members,ou=testgroups,o=test.com/log:option
log:option
name=initialContextFactorycom.sun.jndi.ldap.LdapCtxFactory/log:option
log:option name=roleNamecn/log:option
log:option
name=roleSearchMatchinguniquemember={0}/log:option
log:option name=roleSearchSubtreefalse/log:option
log:option
name=userRoleNameuniquemember={0}/log:option
log:option name=authenticationsimple/log:option
log:option name=userSearchSubtreetrue/log:option
log:option
name=userBaseou=users,o=test.com/log:option
log:option
name=userSearchMatching(mail={0})/log:option
/log:login-module
/log:login-config
/xml-reference
/gbean
/module
It provides no connectionUsername and password ,because I intend to connect
the ldap server anonymously.
Eache time,I login the web application ,it will try to connect the Apache
directory server to authenticate users.
But a NullPointerException will always occur.
Caused by:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:770)
at
org.apache.geronimo.security.realm.providers.LDAPLoginModule.open(LDAPLoginModule.java:455)
at
org.apache.geronimo.security.realm.providers.LDAPLoginModule.authenticate(LDAPLoginModule.java:267)
at
org.apache.geronimo.security.realm.providers.LDAPLoginModule.login(LDAPLoginModule.java:186)
... 28 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4997) Can not connect to a ldap server in an anonymous way
[
https://issues.apache.org/jira/browse/GERONIMO-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lu Jiang updated GERONIMO-4997:
---
Attachment: geronimo-security-2.1.4.jar
Can not connect to a ldap server in an anonymous way
Key: GERONIMO-4997
URL: https://issues.apache.org/jira/browse/GERONIMO-4997
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: security
Affects Versions: 2.1.4, 2.2
Environment: OS:Windows XP SP2
Server: Geronimo 2.2
JDK:1.6
Reporter: Lu Jiang
Priority: Minor
Fix For: 2.1.5, 2.2.1, 3.0
Attachments: geronimo-security-2.1.4.jar
I tried to deploy an web application which uses Apache Directory Server for
user authentication.
So I created a realm file as follows and add a reference to this realm file
in deploy plan
module xmlns=http://geronimo.apache.org/xml/ns/deployment-1.2;
environment
moduleId
groupIdconsole.realm/groupId
artifactIdtestLDAP/artifactId
version1.0/version
typecar/type
/moduleId
dependencies
dependency
groupIdorg.apache.geronimo.framework/groupId
artifactIdj2ee-security/artifactId
typecar/type
/dependency
/dependencies
/environment
gbean name=testLDAP
class=org.apache.geronimo.security.realm.GenericSecurityRealm
xsi:type=dep:gbeanType
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
attribute name=realmNametestLDAP/attribute
reference name=ServerInfo
nameServerInfo/name
/reference
xml-reference name=LoginModuleConfiguration
log:login-config
xmlns:log=http://geronimo.apache.org/xml/ns/loginconfig-2.0;
log:login-module control-flag=REQUIRED
wrap-principals=false
log:login-domain-nametestLDAP/log:login-domain-name
log:login-module-classorg.apache.geronimo.security.realm.providers.LDAPLoginModule/log:login-module-class
log:option
name=connectionURLldap://pages.test.com:389/log:option
log:option
name=roleBaseou=members,ou=testgroups,o=test.com/log:option
log:option
name=initialContextFactorycom.sun.jndi.ldap.LdapCtxFactory/log:option
log:option name=roleNamecn/log:option
log:option
name=roleSearchMatchinguniquemember={0}/log:option
log:option name=roleSearchSubtreefalse/log:option
log:option
name=userRoleNameuniquemember={0}/log:option
log:option name=authenticationsimple/log:option
log:option name=userSearchSubtreetrue/log:option
log:option
name=userBaseou=users,o=test.com/log:option
log:option
name=userSearchMatching(mail={0})/log:option
/log:login-module
/log:login-config
/xml-reference
/gbean
/module
It provides no connectionUsername and password ,because I intend to connect
the ldap server anonymously.
Eache time,I login the web application ,it will try to connect the Apache
directory server to authenticate users.
But a NullPointerException will always occur.
Caused by:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:770)
at
org.apache.geronimo.security.realm.providers.LDAPLoginModule.open(LDAPLoginModule.java:455)
at
org.apache.geronimo.security.realm.providers.LDAPLoginModule.authenticate(LDAPLoginModule.java:267)
at
org.apache.geronimo.security.realm.providers.LDAPLoginModule.login(LDAPLoginModule.java:186)
... 28 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
