[jira] Resolved: (GERONIMO-3800) Results page of plugin install having issues handling array config
[ https://issues.apache.org/jira/browse/GERONIMO-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong resolved GERONIMO-3800. Resolution: Fixed This issue has been resolved and committed in trunk or apply Patch 3 in GERONIMO-3746. -Joseph Leong Results page of plugin install having issues handling array config -- Key: GERONIMO-3800 URL: https://issues.apache.org/jira/browse/GERONIMO-3800 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Reporter: Joseph Leong Assignee: Joseph Leong Priority: Minor The result page summarizing the installations that has occurred in the plugin installer is having issues handling the new config arrays. Will be fixed shortly with the master page at Jira 3746 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3816) roller-mysql-database has mysql dependency
[ https://issues.apache.org/jira/browse/GERONIMO-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566046#action_12566046 ] David Jencks commented on GERONIMO-3816: I'm not sure why we would change the groupId. Rather than requiring modifying the pom to build I think it would be OK to require using a profile named something like build-gpl-plugin and clearly stating the licensing consequences in the NOTICE file. roller-mysql-database has mysql dependency -- Key: GERONIMO-3816 URL: https://issues.apache.org/jira/browse/GERONIMO-3816 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Reporter: Kevan Miller The roller-mysql-database plugin has a hard dependency on MySQL. We have to remove this for licensing reasons. See explanation below. I plan on disabling the building of the roller-mysql-database plugin as well as removing the mysql dependency. We'll need to reach a decision on how we want to handle this long term. Here's more licensing info... MySQL is Licensed under the GPL license: http://www.mysql.com/company/legal/licensing/ MySQL is also available under a FLOSS exception: http://www.mysql.com/company/legal/licensing/foss-exception.html. The FLOSS exception only be applied to MySQL when it is used under an OSI-approved license. Neither license is deemed suitable by the Apache Software Foundation in ASF distributions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3800) Results page of plugin install having issues handling array config
[ https://issues.apache.org/jira/browse/GERONIMO-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566047#action_12566047 ] Joseph Leong commented on GERONIMO-3800: This issue has been resolved and committed in trunk or apply Patch 3 in GERONIMO-3746. -Joseph Leong Results page of plugin install having issues handling array config -- Key: GERONIMO-3800 URL: https://issues.apache.org/jira/browse/GERONIMO-3800 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Reporter: Joseph Leong Assignee: Joseph Leong Priority: Minor The result page summarizing the installations that has occurred in the plugin installer is having issues handling the new config arrays. Will be fixed shortly with the master page at Jira 3746 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3788) Plugin installer's continue form generating errors
[ https://issues.apache.org/jira/browse/GERONIMO-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Leong resolved GERONIMO-3788. Resolution: Fixed Proper document property assigned in javascript. Fix has been committed into trunk already or implementable via Patch 3 at GERONIMO-3746. -Joseph Leong Plugin installer's continue form generating errors -- Key: GERONIMO-3788 URL: https://issues.apache.org/jira/browse/GERONIMO-3788 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1 Environment: Ubuntu 7.10, Firefox 2.0.0.6 Reporter: Joseph Leong Assignee: Joseph Leong Fix For: 2.1.1 After installing plugin components, the Continue Form page that the user is being redirected to is generating errors. 500 -Error -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3818) Monitoring console should open individual graphs in actual new window rather than tabs in firefox
Monitoring console should open individual graphs in actual new window rather than tabs in firefox - Key: GERONIMO-3818 URL: https://issues.apache.org/jira/browse/GERONIMO-3818 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Monitoring console should open individual graphs in actual new window rather than tabs in firefox -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3730) monitoring plugin to support jmx connections in mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3730. - Resolution: Fixed Assignee: Erik B. Craig (was: Viet Hung Nguyen) JMX connection support is implemented and functional monitoring plugin to support jmx connections in mconsole Key: GERONIMO-3730 URL: https://issues.apache.org/jira/browse/GERONIMO-3730 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1 Reporter: Viet Hung Nguyen Assignee: Erik B. Craig There should be another collecting agent that does not use MEJB, but JMX instead. This should probably be a separate plugin than the existing agent because we do not want to pull in OpenEJB. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3803) monitoring plugin: agent-jmx does not provide the correct interface for mconsole
[ https://issues.apache.org/jira/browse/GERONIMO-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3803. - Resolution: Fixed monitoring plugin: agent-jmx does not provide the correct interface for mconsole Key: GERONIMO-3803 URL: https://issues.apache.org/jira/browse/GERONIMO-3803 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Environment: ubuntu Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Priority: Critical Attachments: geronimo-3803.patch the agent-jmx does not specify the right method signatures that the mconsole needs to run properly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
New portlet for ActiveMQ
Hi All, I would like to add an ActiveMQ portlet in admin console.The portlet will have informations like 1). Queues 2) Topics 3)Count of messages send to each queue/topic ,pending messages 4)Option to send messages to messages to queues/topics 5)Purge messages on queues/topics 6)Browse and send messages to queues/topics Please give me your suggestions on this. Also can somebody give me a contributer access for this. -- Best Regards, Anish Pathadan
[jira] Created: (GERONIMO-3817) mconsole should display axis labels
mconsole should display axis labels --- Key: GERONIMO-3817 URL: https://issues.apache.org/jira/browse/GERONIMO-3817 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Fix For: 2.1, 2.1.1 THe monitoring console is not currently displaying axis labels and should be doing so in some fashion -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3633) Monitoring client should auto redraw graphs/the page on any page that has graphs
[ https://issues.apache.org/jira/browse/GERONIMO-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3633. - Resolution: Fixed Assignee: Erik B. Craig Committed revision 618963 for branches/2.1 Committed revision 618967 for trunk Monitoring client should auto redraw graphs/the page on any page that has graphs Key: GERONIMO-3633 URL: https://issues.apache.org/jira/browse/GERONIMO-3633 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Reporter: Erik B. Craig Assignee: Erik B. Craig Monitoring client should auto redraw graphs/the page on any page that has graphs based on the snapshot duration of the server the graphs are pulled from. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3818) Monitoring console should open individual graphs in actual new window rather than tabs in firefox
[ https://issues.apache.org/jira/browse/GERONIMO-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3818. - Resolution: Fixed Committed revision 618963 for branches/2.1 Committed revision 618967 for trunk Monitoring console should open individual graphs in actual new window rather than tabs in firefox - Key: GERONIMO-3818 URL: https://issues.apache.org/jira/browse/GERONIMO-3818 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Monitoring console should open individual graphs in actual new window rather than tabs in firefox -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3817) mconsole should display axis labels
[ https://issues.apache.org/jira/browse/GERONIMO-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig resolved GERONIMO-3817. - Resolution: Fixed Committed revision 618963 for branches/2.1 Committed revision 618967 for trunk mconsole should display axis labels --- Key: GERONIMO-3817 URL: https://issues.apache.org/jira/browse/GERONIMO-3817 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.1, 2.1.1 Reporter: Erik B. Craig Fix For: 2.1, 2.1.1 THe monitoring console is not currently displaying axis labels and should be doing so in some fashion -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: New portlet for ActiveMQ
Hi Anish, I have added you as a Geronimo contributor. I suggest you create a JIRA so that we can track progress on this task. See if you can expand the JMS Resources portlet to provide these functions instead of creating a new portelt. ++Vamsi On Feb 6, 2008 4:41 PM, anish pathadan [EMAIL PROTECTED] wrote: Hi All, I would like to add an ActiveMQ portlet in admin console.The portlet will have informations like 1). Queues 2) Topics 3)Count of messages send to each queue/topic ,pending messages 4)Option to send messages to messages to queues/topics 5)Purge messages on queues/topics 6)Browse and send messages to queues/topics Please give me your suggestions on this. Also can somebody give me a contributer access for this. -- Best Regards, Anish Pathadan
Re: Geronimo v2.1 documentation
David Jencks wrote: Would it be possible to link to the in-progress 2.1 documentation from what I think is the main docs page http://geronimo.apache.org/documentation.html? Done! it should get reflected within the next hour or so. I'm also wondering whether there is some way to make the existence of http://cwiki.apache.org/GMOxDOC21/documentation.html more obvious from http://cwiki.apache.org/GMOxDOC21/ which seems to be what I always find when I look for the 2.1 docs. I just fixed this, it was caused by caused by a limitation in the autoexport plugin we use. index.html and documentation.html should display the same information, index actually does an include of documentation Are there plans to copy the parts of the 1.x and 2.0.x docs that are still relevant to the 2.1 docs? I think this did not happen completely for the 1.1 2.0 release. There are plans for a lot more than that ;-) I always try to carry over the parts that are still relevant and update them as needed. There is a lot of fish to fry so it would be great if we can all chip into the doc. At least from time to time ;-) Cheers! Hernan thanks david jencks On Jan 25, 2008, at 8:22 AM, Hernan Cunico wrote: Guys, I've been trying to get your attention around Geronimo 2.1 documentation since October last year. Apache Geronimo is as good as you can communicate it to the users. How do you expect the users to know all the beeps and whistles? Not a best way to tell the users HOW TO do things in Geronimo than by having a good documentation. How much of your time it would actually take to write up a page describing a component or module and how to use it? It's you writing the code, why not you writing about that code and how to use it!? There are tons of questions on the user@ and dev@ lists about how to perform basic (and some times not so basic) tasks and configurations, we get these all the time. This is a clear sign that we need to improve the way we document the things. For 2.1 the situation is even worse, we pretty much don't have any documentation and we can't continue developing documentation the way we've been doing in the past. The way it looks now, Geronimo 2.1 won't have supporting documentation. Let's discuss here what areas need to be covered and who can work on documenting them. It is your turn now. Cheers! Hernan Kevan Miller wrote: On Jan 10, 2008, at 5:14 PM, Hernan Cunico wrote: Hi All, some time ago I started to put together some topics for Geronimo v2.1 documentation. I tried to focus on the biggest new things we are offering now, topics we didn't have before and now we need to start from scratch. The Geronimo v2.1 documentation space is already available here http://cwiki.apache.org/GMOxDOC21/documentation.html The initial TOC includes: * Configuration changes * Deployment ** Deployment plan creator * Geronimo Administration Console enhancements * GShell * Monitoring * Pluggable console * Plugin infrastructure enhancements * RELEASE-NOTES-2.1.TXT * Sample applications * Security * Tooling * What's new? Each of these pages already contain a few lines with some initial thoughts. Need your input for adding topics to this list as well as developing them. There might be things we already had in 2.0x but we didn't cover it in the doc, pls need your comments on that as well. I think I'm finish covering *Deployment plan creator*, will do a refresh later on as new code gets in. I also created this place holder http://cwiki.apache.org/GMOxPMGT/geronimo-v21-list-of-functions-status.html under *Apache Geronimo Project Management* on the wiki so we can keep track there the features we have ready for prime time and those that are not so ready ;-) I could definitively use that info to build up a new set of docs, would also help users to see where we are at. Hernan, Thanks for this. Time to start pulling these docs together to prepare for release. It can't all be generated by Hernan. We'll need to chip in... --kevan
[jira] Commented: (GERONIMO-3812) Geronimo 2.0.2 misses ApacheDS (LDAP) function
[ https://issues.apache.org/jira/browse/GERONIMO-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566123#action_12566123 ] Sakari Maaranen commented on GERONIMO-3812: --- I also created a LDAP security realm with LDAPS URL and SSL protocol. This gives the following errors in geronimo.log: 2008-02-06 07:51:36,080 WARN SecurityRealmPortlet: Test login failed javax.security.auth.login.LoginException: LDAP Error at org.apache.geronimo.security.realm.providers.LDAPLoginModule.login(LDAPLoginModule.java:161) at org.apache.geronimo.console.util.KernelManagementHelper.testLoginModule(KernelManagementHelper.java:423) at org.apache.geronimo.console.util.PortletManager.testLoginModule(PortletManager.java:168) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.actionAttemptLogin(SecurityRealmPortlet.java:340) at org.apache.geronimo.console.securitymanager.realm.SecurityRealmPortlet.processAction(SecurityRealmPortlet.java:221) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) ... at java.lang.Thread.run(Thread.java:595) Caused by: javax.naming.CommunicationException: simple bind failed: localhost:636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target] at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:197) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2637) at com.sun.jndi.ldap.LdapCtx.init(LdapCtx.java:283) ... Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1584) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) ... Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:221) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:145) at sun.security.validator.Validator.validate(Validator.java:203) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172) ... Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:236) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216) ... I think it means that some way of setting up trusted certificates for LDAP security realms is needed. Otherwise Geronimo cannot connect to LDAPS, because it cannot trust the LDAPS certificate. Geronimo 2.0.2 misses ApacheDS (LDAP) function -- Key: GERONIMO-3812 URL: https://issues.apache.org/jira/browse/GERONIMO-3812 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation, Plugins Affects Versions: 2.0.2 Environment: Debian Linux, java version 1.5.0_14, geronimo-tomcat6-jee5-2.0.2 Reporter: Sakari Maaranen Geronimo documentation at http://cwiki.apache.org/GMOxDOC20/ldap-sample-application.html talks about org.apache.geronimo.configs/directory in system modules, but that does not exist in Geronimo 2.0.2. There is also a reference to Geronimo plugins. However, when I go to Plugins in the Geronimo console and search the geronimo-2.0.2 reposityory there is nothing related to ApacheDS or Directory. Like if the ApacheDS function was completely missing. The ApacheDS plugin should be added to the 2.0.2 plugin repository. The documentation should be updated to give the steps how to install ApacheDS with or without the plugin. The LDAP demo is useless if ApacheDS is unavailable. I found this much earlier discussion on the topic: http://www.mail-archive.com/dev@geronimo.apache.org/msg52749.html http://www.mail-archive.com/dev@geronimo.apache.org/msg55148.html
Re: Changes needed to the website upon PRC communication
agreed, Epiq did a fantastic job and they deserve credit. Paul On Feb 5, 2008, at 10:29 PM, Matt Hogstrom wrote: double ditto :) On Feb 5, 2008, at 9:08 PM, Kevan Miller wrote: I think the Geronimo G graphics merit the continued gratitude of the Geronimo project. I'd like to see our little thank you restored. Would you be ok with that? How do others feel? --kevan
Re: Geronimo v2.1 documentation
David Jencks wrote:
On Feb 5, 2008, at 4:31 PM, David Jencks wrote:
I also realize I don't know what the intended relationship between these
pages is and which one I'm supposed to work from and how (or if) to
It should not really matter from which page you start. We have two pages with the
same content because one (index) is the default landing page but actually does not
have content of its own. Index only has one line macro to include the content of
Documentation - {include:Documentation}
So why we have a second page? I just wanted to have Documentation listed on the breadcrumbs as well as made more sense all the documents hierarchically organized hanging from a Documentation parent page [ Home Apache Geronimo v2.1 Documentation ]
It's just a small detail but I think it makes the overall documentation looks better.
Downside, we have two pages displaying the same content and an autoexport plugin that
some times is not that auto.
affect the *documentation.html page. A few days ago I wrote up info on
a new jndi feature which shows up fine on the / page but not the
documentation.html.
For now, the Documentation page is mostly generated by hand. Most of the work
on the proposed TOC is just that, to list and discuss what contents to cover
instead of just start creating the pages in some particular order. As we start
to fill the documentation with content I'll start to mix in the Documentation
page some macros to automatically generate links to some sections.
Where did you put that doc? it's probably just matter of changing the parent
page.
Just in case, here is a doc for how the documentation is organized within the different spaces in Confluence.
http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html
Cheers!
Hernan
thanks
david jencks
...
Re: New portlet for ActiveMQ
This sounds great. I agree with Vamsi that it would be good to expand the current JMS resources portlet if possible. As I recall, it was left in a somewhat transitional state and contains a lot of unused code that could still be refactored. Best wishes, Paul On Feb 6, 2008, at 7:56 AM, Vamsavardhana Reddy wrote: Hi Anish, I have added you as a Geronimo contributor. I suggest you create a JIRA so that we can track progress on this task. See if you can expand the JMS Resources portlet to provide these functions instead of creating a new portelt. ++Vamsi On Feb 6, 2008 4:41 PM, anish pathadan [EMAIL PROTECTED] wrote: Hi All, I would like to add an ActiveMQ portlet in admin console.The portlet will have informations like 1). Queues 2) Topics 3)Count of messages send to each queue/topic ,pending messages 4)Option to send messages to messages to queues/topics 5)Purge messages on queues/topics 6)Browse and send messages to queues/topics Please give me your suggestions on this. Also can somebody give me a contributer access for this. -- Best Regards, Anish Pathadan
Re: Changes needed to the website upon PRC communication
I wish we'd have had this discussion in early November, lot of feedback ;-) I just restored the label and link as it was before the PRC communication. Cheers! Hernan David Jencks wrote: I agree thanks david jencks On Feb 5, 2008, at 6:08 PM, Kevan Miller wrote: On Nov 6, 2007, at 5:04 PM, Hernan Cunico wrote: Hi All, the Apache PRC has sent a communication to all PMC's about how we (I mean Apache projects in general) thank sponsors for their contributions to the projects on the project's website. This type of acknowledgment is not considered official from Apache, in fact gets in the way for promoting the official ASF Sponsorship and Thanks! programs. Going to a more concrete example on our website, we have a Powered By page. This page has a misleading title for a start; we have been carrying this one along for a very long time and I doubt it is up to date anyway. The Powered By page provides a list of companies rendering services and support for Apache Geronimo. So, at a minimum, we should change the page title to something more representative. The other acknowledgment we have is with Graphics by Epiq, these are folks who got voted for their designs when we overhauled the website and console. This one falls into the same category as the Powered By page for which the PRC communication seems to be specifically targeted to. The Search box also shows Powered by Google Search, however this might be a different case as this is an indicative of the type of search the user will actually run - external Google search on the Geronimo site. I just added the official ASF Sponsorship and ASF Thanks links to the Community menu box on the left as instructed in the PRC communication. We still need to determine how to deal with Powered By and Graphics by Epiq. The former should be at least renamed if not removed altogether, the latter should be removed I think. Hernan, I missed part of this note the first time. So, apologies... Regarding the Graphics by Epiq thank-you link we had on our web pages: the request from the ASF PRC was to track and monitor our Thank You pages. The basic idea is, make sure that we are giving thanks for something significant and don't give away advertising that is out of proportion to the donation. The PRC's intent is to encourage ASF Sponsorship, not to prevent a well-earned thank you. At least this is how I interpret the PRC request... I think the Geronimo G graphics merit the continued gratitude of the Geronimo project. I'd like to see our little thank you restored. Would you be ok with that? How do others feel? --kevan
Re: svn commit: r618968 - /geronimo/server/branches/2.1/pom.xml
On Feb 6, 2008, at 6:41 AM, [EMAIL PROTECTED] wrote: Author: gdamour Date: Wed Feb 6 03:41:48 2008 New Revision: 618968 URL: http://svn.apache.org/viewvc?rev=618968view=rev Log: Move to WADI 2.0-M8 release Cool. Thanks Gianny! So, we're ready to go? Gentle nudge to merge into trunk. --kevan
[jira] Created: (GERONIMO-3819) Update JMS Resources Portlet
Update JMS Resources Portlet Key: GERONIMO-3819 URL: https://issues.apache.org/jira/browse/GERONIMO-3819 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: console Reporter: anish pathadan Assignee: anish pathadan Update the JMS Resources portlet to include the following information from the JMS Provider 1.Count of messages send to each queue/topic ,pending messages 2.Option to send messages to messages to particular queues/topics 3.Purge messages from queues/topics 4.Browse and send messages to queues/topics -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3816) roller-mysql-database has mysql dependency
[ https://issues.apache.org/jira/browse/GERONIMO-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566133#action_12566133 ] Kevan Miller commented on GERONIMO-3816: Something for the project to discuss. I'll get a note out to dev@ roller-mysql-database has mysql dependency -- Key: GERONIMO-3816 URL: https://issues.apache.org/jira/browse/GERONIMO-3816 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Plugins Reporter: Kevan Miller The roller-mysql-database plugin has a hard dependency on MySQL. We have to remove this for licensing reasons. See explanation below. I plan on disabling the building of the roller-mysql-database plugin as well as removing the mysql dependency. We'll need to reach a decision on how we want to handle this long term. Here's more licensing info... MySQL is Licensed under the GPL license: http://www.mysql.com/company/legal/licensing/ MySQL is also available under a FLOSS exception: http://www.mysql.com/company/legal/licensing/foss-exception.html. The FLOSS exception only be applied to MySQL when it is used under an OSI-approved license. Neither license is deemed suitable by the Apache Software Foundation in ASF distributions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3812) Geronimo 2.0.2 misses ApacheDS (LDAP) function
[ https://issues.apache.org/jira/browse/GERONIMO-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566134#action_12566134 ] Sakari Maaranen commented on GERONIMO-3812: --- I solved the problem that was caused by missing configuration of trusted certificate authorities with the LDAP security realm. First, using Geronimo keystore tools, I created a new keystore and a private key in it. I signed it using Geronimo CA. Lastly I added my Geronimo CA certificate as a trusted certificate in the same keystore. I copied that keystore to ApacheDS and configured LDAPS with that. The original copy of the same keystore still remains in the Geronimo var/security/keystores/ directory. Before starting Geronimo I did the following: JAVA_OPTS=-Djavax.net.ssl.trustStore=geronimo-home/var/security/keystores/keystore-filename -Djavax.net.ssl.trustStorePassword=password export JAVA_OPTS cd geronimo-home bin/geronimo.sh start Now I have fully configured ApacheDS 1.0.2 standalone LDAPS with Geronimo 2.0.2. Not sure if using JAVA_OPTS is the best place for this configuration though. Geronimo should have way of setting the trusted certificate authorities keystore from the web console. Geronimo 2.0.2 misses ApacheDS (LDAP) function -- Key: GERONIMO-3812 URL: https://issues.apache.org/jira/browse/GERONIMO-3812 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation, Plugins Affects Versions: 2.0.2 Environment: Debian Linux, java version 1.5.0_14, geronimo-tomcat6-jee5-2.0.2 Reporter: Sakari Maaranen Geronimo documentation at http://cwiki.apache.org/GMOxDOC20/ldap-sample-application.html talks about org.apache.geronimo.configs/directory in system modules, but that does not exist in Geronimo 2.0.2. There is also a reference to Geronimo plugins. However, when I go to Plugins in the Geronimo console and search the geronimo-2.0.2 reposityory there is nothing related to ApacheDS or Directory. Like if the ApacheDS function was completely missing. The ApacheDS plugin should be added to the 2.0.2 plugin repository. The documentation should be updated to give the steps how to install ApacheDS with or without the plugin. The LDAP demo is useless if ApacheDS is unavailable. I found this much earlier discussion on the topic: http://www.mail-archive.com/dev@geronimo.apache.org/msg52749.html http://www.mail-archive.com/dev@geronimo.apache.org/msg55148.html Frankly, I don't think that the forward compatibility is so much an issue, but 2.0.2 completely lacking LDAP server. Would be better have it, even without forward compatibility. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-1930) Make security realm types into GBeans so they can be added in new/updated configurations
[ https://issues.apache.org/jira/browse/GERONIMO-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566140#action_12566140 ] Sakari Maaranen commented on GERONIMO-1930: --- One detail to remember here is to enable the truststoreFileName and password for these GBeans. It took me a couple of days to try to figure out how to configure the trusted security authorities keystore for my Secure LDAP(S) realm. In the end I had to use command line options for my JVM before starting Geronimo: -Djavax.net.ssl.trustStore=geronimo-home/var/security/keystores/keystore-filename -Djavax.net.ssl.trustStorePassword=password Would be nice to have those configurable with GBeans or a similar means. Preferrably with a web GUI. Make security realm types into GBeans so they can be added in new/updated configurations Key: GERONIMO-1930 URL: https://issues.apache.org/jira/browse/GERONIMO-1930 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console, security Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: New portlet for ActiveMQ
I have created a JIRA for this https://issues.apache.org/jira/browse/GERONIMO-3819 I will try to update the existing portlet with the new informations. Right now I am doing a research on how can I get the required information from ActiveMQ.Standalone ActiveMQ has a web console that shows these information.I think I might be able to reuse some of those things. On Feb 6, 2008 8:43 AM, Paul McMahan [EMAIL PROTECTED] wrote: This sounds great. I agree with Vamsi that it would be good to expand the current JMS resources portlet if possible. As I recall, it was left in a somewhat transitional state and contains a lot of unused code that could still be refactored. Best wishes, Paul On Feb 6, 2008, at 7:56 AM, Vamsavardhana Reddy wrote: Hi Anish, I have added you as a Geronimo contributor. I suggest you create a JIRA so that we can track progress on this task. See if you can expand the JMS Resources portlet to provide these functions instead of creating a new portelt. ++Vamsi On Feb 6, 2008 4:41 PM, anish pathadan [EMAIL PROTECTED] wrote: Hi All, I would like to add an ActiveMQ portlet in admin console.The portlet will have informations like 1). Queues 2) Topics 3)Count of messages send to each queue/topic ,pending messages 4)Option to send messages to messages to queues/topics 5)Purge messages on queues/topics 6)Browse and send messages to queues/topics Please give me your suggestions on this. Also can somebody give me a contributer access for this. -- Best Regards, Anish Pathadan -- Best Regards, Anish Pathadan
[jira] Created: (GERONIMO-3820) Secure LDAP (ldaps) trusted certificate authorities
Secure LDAP (ldaps) trusted certificate authorities --- Key: GERONIMO-3820 URL: https://issues.apache.org/jira/browse/GERONIMO-3820 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.0.2, 2.0.1, 2.0, 2.0-M7, 2.0-M6, 2.0-M5, 2.0-M4, 2.0-M3, 2.0-M2, 2.0-M1, 1.1.1 Environment: Integrating Geronimo with a SSL-enabled LDAP server Reporter: Sakari Maaranen When connecting to a LDAPS server, Geronimo refuses the connection because it cannot trust the server's certificate. This is simply because the trusted certificate authorities are not easily configurable with LDAP security realms. I had to use command line options for my JVM before starting Geronimo: -Djavax.net.ssl.trustStore=geronimo-home/var/security/keystores/keystore-filename -Djavax.net.ssl.trustStorePassword=password Would be nice to have those configurable with GBeans or a similar means, preferrably via a web GUI. More details in GERONIMO-3812 comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Inclusion of MySQL in roller-mysql-database plugin
All, I created a Jira to handle licensing issues involving the inclusion of MySQL in the roller-mysql-database plugin. See https://issues.apache.org/jira/browse/GERONIMO-3816 I've insured that we will no longer build the roller-mysql-database plugin in our source code. However, there are multiple ways of handling this problem. Would like to hear opinions from the project. Ultimately, it's the PMC's responsibility to oversee the licensing of our distributions and to oversee the way we handle dependencies on artifacts that are covered by excluded licenses. The ASF Licensing Policy (currently it's a draft policy, but I think we should be following the guidelines documented there) are located here -- http://www.apache.org/legal/3party.html Discussion of how to handle Prohibited Works is here -- http://people.apache.org/~rubys/3party.html#options Would be good for the project (in particular PMC) members to be familiar with these issues. Would like to hear how we think we should address this issue. As long as I feel the PMC is providing appropriate oversight, I'm happy with what ever decision we reach. --kevan
Re: Geronimo v2.1 documentation
David,
I just found the doc you created and updated the home page so it gets reflected.
Sorry for this back and forth, this is temporary.
Thanks for contributing with the doc.
Cheers!
Hernan
Hernan Cunico wrote:
David Jencks wrote:
On Feb 5, 2008, at 4:31 PM, David Jencks wrote:
I also realize I don't know what the intended relationship between
these pages is and which one I'm supposed to work from and how (or if) to
It should not really matter from which page you start. We have two pages
with the same content because one (index) is the default landing page
but actually does not have content of its own. Index only has one line
macro to include the content of Documentation - {include:Documentation}
So why we have a second page? I just wanted to have Documentation
listed on the breadcrumbs as well as made more sense all the documents
hierarchically organized hanging from a Documentation parent page [
Home Apache Geronimo v2.1 Documentation ]
It's just a small detail but I think it makes the overall documentation
looks better. Downside, we have two pages displaying the same content
and an autoexport plugin that some times is not that auto.
affect the *documentation.html page. A few days ago I wrote up info
on a new jndi feature which shows up fine on the / page but not the
documentation.html.
For now, the Documentation page is mostly generated by hand. Most of the
work on the proposed TOC is just that, to list and discuss what contents
to cover instead of just start creating the pages in some particular
order. As we start to fill the documentation with content I'll start to
mix in the Documentation page some macros to automatically generate
links to some sections.
Where did you put that doc? it's probably just matter of changing the
parent page.
Just in case, here is a doc for how the documentation is organized
within the different spaces in Confluence.
http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html
Cheers!
Hernan
thanks
david jencks
...
Re: [jira] Commented: (GERONIMO-1930) Make security realm types into GBeans so they can be added in new/updated configurations
There is a System Properties GBean that allows you to add system properties without having to set those on the command line. ++Vamsi On Feb 6, 2008 7:57 PM, Sakari Maaranen (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/GERONIMO-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566140#action_12566140] Sakari Maaranen commented on GERONIMO-1930: --- One detail to remember here is to enable the truststoreFileName and password for these GBeans. It took me a couple of days to try to figure out how to configure the trusted security authorities keystore for my Secure LDAP(S) realm. In the end I had to use command line options for my JVM before starting Geronimo: -Djavax.net.ssl.trustStore=geronimo-home/var/security/keystores/keystore-filename -Djavax.net.ssl.trustStorePassword=password Would be nice to have those configurable with GBeans or a similar means. Preferrably with a web GUI. Make security realm types into GBeans so they can be added in new/updated configurations Key: GERONIMO-1930 URL: https://issues.apache.org/jira/browse/GERONIMO-1930 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console, security Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r618968 - /geronimo/server/branches/2.1/pom.xml
Kevan Miller wrote: On Feb 6, 2008, at 6:41 AM, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Author: gdamour Date: Wed Feb 6 03:41:48 2008 New Revision: 618968 URL: http://svn.apache.org/viewvc?rev=618968view=rev http://svn.apache.org/viewvc?rev=618968view=rev Log: Move to WADI 2.0-M8 release Cool. Thanks Gianny! So, we're ready to go? Gentle nudge to merge into trunk. --kevan Is anybody else having problems downloading the 2.0-M8 artifacts? My 2.1 build is failing because it can't find these in the repos we include in our build (which currently does *not* include http://repository.codehaus.org/ ). We were getting 2.0-M7 from ibiblio (or maven central depending on your settings). Does someone need to take action to get 2.0-M8 mirrored there, will it get there eventually, or should we include the codehaus repo in our build? Joe
[jira] Created: (GERONIMO-3821) Update 2.1 to use OpenEJB 3.0-beta-2
Update 2.1 to use OpenEJB 3.0-beta-2 Key: GERONIMO-3821 URL: https://issues.apache.org/jira/browse/GERONIMO-3821 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: OpenEJB Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3769) artifactory 1.2.2 deployment is failing on 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3769. Resolution: Fixed fixed by moving the plexus dependency to configs/plugin. artifactory 1.2.2 deployment is failing on 2.1 -- Key: GERONIMO-3769 URL: https://issues.apache.org/jira/browse/GERONIMO-3769 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1 Reporter: Kevan Miller Assignee: Joe Bohn Fix For: 2.1 A deploy of artifactory is failing on 2.1. Same deploy works on 2.0.2. I'm seeing the following exceptions on the server: Second exception is most significant, I think: 2008-01-20 12:42:22,616 [ERROR] 0.0].[/artifactory] - Exception sending context initialized event to listener instance of class org.artifactory.webapp.servlet.ArtifactoryContextConfigurer org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'maven' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.artifactory.maven.Maven]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/codehaus/classworlds/NoSuchRealmException Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.artifactory.maven.Maven]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/codehaus/classworlds/NoSuchRealmException Caused by: java.lang.NoClassDefFoundError: org/codehaus/classworlds/NoSuchRealmException at org.codehaus.plexus.embed.Embedder.init(Embedder.java:62) at org.apache.maven.embedder.MavenEmbedder.start(MavenEmbedder.java:582) at org.artifactory.maven.Maven.init(Maven.java:99) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:85) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:170) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:773) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:716) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:386) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:144) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:279) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:360) at org.artifactory.webapp.servlet.ArtifactoryContextConfigurer.contextInitialized(ArtifactoryContextConfigurer.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3826) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4327) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:60) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:388) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:241) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at
[jira] Resolved: (GERONIMO-3796) Upgrade to 3.3 version of xbean-finder, xbean-naming, and xbean-reflect
[ https://issues.apache.org/jira/browse/GERONIMO-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3796. Resolution: Fixed Upgrade to 3.3 version of xbean-finder, xbean-naming, and xbean-reflect --- Key: GERONIMO-3796 URL: https://issues.apache.org/jira/browse/GERONIMO-3796 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn To eliminate snapshots and get on a consistent xbean delivery we need to upgrade xbean-finder, xbean-naming, and xbean-reflect to the 3.3 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3796) Upgrade to 3.3 version of xbean-finder, xbean-naming, and xbean-reflect
[ https://issues.apache.org/jira/browse/GERONIMO-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-3796: --- Fix Version/s: 2.1.1 2.1 Upgrade to 3.3 version of xbean-finder, xbean-naming, and xbean-reflect --- Key: GERONIMO-3796 URL: https://issues.apache.org/jira/browse/GERONIMO-3796 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1, 2.1.1 To eliminate snapshots and get on a consistent xbean delivery we need to upgrade xbean-finder, xbean-naming, and xbean-reflect to the 3.3 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3798) Upgrade Geronimo to newly released geronimo-transaction 2.1 and geronimo-connector 2.1 components
[ https://issues.apache.org/jira/browse/GERONIMO-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3798. Resolution: Fixed Fix Version/s: 2.1.1 2.1 Upgrade Geronimo to newly released geronimo-transaction 2.1 and geronimo-connector 2.1 components - Key: GERONIMO-3798 URL: https://issues.apache.org/jira/browse/GERONIMO-3798 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1, 2.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3787) Deployment on Minimal Assemblies fails complaining of a missing yoko dependency
[ https://issues.apache.org/jira/browse/GERONIMO-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-3787. Resolution: Fixed Fix Version/s: 2.1.1 2.1 Deployment on Minimal Assemblies fails complaining of a missing yoko dependency --- Key: GERONIMO-3787 URL: https://issues.apache.org/jira/browse/GERONIMO-3787 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn Fix For: 2.1, 2.1.1 Attachments: snoop.war I started the tomcat minimal assembly and attempted to deploy a simple web application. I hit the following error: tetra:~/g-images/trunk/geronimo-tomcat6-minimal-2.1-SNAPSHOT/bin bohn$ ./deploy.sh deploy ~/ServerApplications/snoop.war Using GERONIMO_BASE: /Users/bohn/g-images/trunk/geronimo-tomcat6-minimal-2.1-SNAPSHOT Using GERONIMO_HOME: /Users/bohn/g-images/trunk/geronimo-tomcat6-minimal-2.1-SNAPSHOT Using GERONIMO_TMPDIR: var/temp Using JRE_HOME:/System/Library/Frameworks/JavaVM.framework/Home org.apache.geronimo.kernel.config.LifecycleException: load of default/snoop/1201271106727/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:299) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:280) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:255) at org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConfiguration(KernelConfigurationManager.java:111) at org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastClassByCGLIB$$b117102f.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:867) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at
[jira] Closed: (GERONIMO-3769) artifactory 1.2.2 deployment is failing on 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller closed GERONIMO-3769. -- artifactory 1.2.2 deployment is failing on 2.1 -- Key: GERONIMO-3769 URL: https://issues.apache.org/jira/browse/GERONIMO-3769 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1 Reporter: Kevan Miller Assignee: Joe Bohn Fix For: 2.1 A deploy of artifactory is failing on 2.1. Same deploy works on 2.0.2. I'm seeing the following exceptions on the server: Second exception is most significant, I think: 2008-01-20 12:42:22,616 [ERROR] 0.0].[/artifactory] - Exception sending context initialized event to listener instance of class org.artifactory.webapp.servlet.ArtifactoryContextConfigurer org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'maven' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.artifactory.maven.Maven]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/codehaus/classworlds/NoSuchRealmException Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.artifactory.maven.Maven]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/codehaus/classworlds/NoSuchRealmException Caused by: java.lang.NoClassDefFoundError: org/codehaus/classworlds/NoSuchRealmException at org.codehaus.plexus.embed.Embedder.init(Embedder.java:62) at org.apache.maven.embedder.MavenEmbedder.start(MavenEmbedder.java:582) at org.artifactory.maven.Maven.init(Maven.java:99) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:85) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:170) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:773) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:716) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:386) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:144) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:279) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:360) at org.artifactory.webapp.servlet.ArtifactoryContextConfigurer.contextInitialized(ArtifactoryContextConfigurer.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3826) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4327) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:60) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:388) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:241) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at
branches/2.1 freeze notice
All, In preparation for our 2.1 release, please hold off on any commits to branches/2.1. If you have something that you feel absolutely *must* be fixed, please check with me. I'll be working on generating a 2.1 release candidate later this afternoon/eveniing. --kevan
[BUILD] 2.2: Failed for Revision: 618655
Geronimo Revision: 618655 built with tests included
See the full build-0900.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080206/build-0900.log
See the unit test reports at
http://geronimo.apache.org/maven/server/binaries/trunk/20080206/unit-test-reports
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 26 source files to
/home/geronimo/geronimo/trunk/plugins/console/console-core/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/plugins/console/console-core/target/console-core-2.2-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: console-core-2.2-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/console/console-core/target/console-core-2.2-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/plugins/console-core/2.2-SNAPSHOT/console-core-2.2-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, ActiveMQ :: Portlets
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/geronimo/geronimo/trunk/plugins/activemq/activemq-portlets/target/classes/META-INF
[INFO] Copying 2 files to
/home/geronimo/geronimo/trunk/plugins/activemq/activemq-portlets/target/classes/META-INF
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 33 source files to
/home/geronimo/geronimo/trunk/plugins/activemq/activemq-portlets/target/classes
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/groovy/groovy-mojo-support/1.0-alpha-3/groovy-mojo-support-1.0-alpha-3.pom
2K downloaded
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/groovy/groovy/1.0-alpha-3/groovy-1.0-alpha-3.pom
14K downloaded
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/groovy/groovy-mojo-common/1.0-alpha-3/groovy-mojo-common-1.0-alpha-3.pom
2K downloaded
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler-tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.pom
2K downloaded
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compilers/2.0-alpha-1/jspc-compilers-2.0-alpha-1.pom
1K downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/jasper-jdt/6.0.13/jasper-jdt-6.0.13.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/jasper-jdt/6.0.13/jasper-jdt-6.0.13.pom
279b downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/jasper-el/6.0.13/jasper-el-6.0.13.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/jasper-el/6.0.13/jasper-el-6.0.13.pom
490b downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/el-api/6.0.13/el-api-6.0.13.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/el-api/6.0.13/el-api-6.0.13.pom
254b downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/juli/6.0.13/juli-6.0.13.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/juli/6.0.13/juli-6.0.13.pom
252b downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/servlet-api/6.0.13/servlet-api-6.0.13.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/servlet-api/6.0.13/servlet-api-6.0.13.pom
253b downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/jsp-api/6.0.13/jsp-api-6.0.13.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/jsp-api/6.0.13/jsp-api-6.0.13.pom
633b downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/annotations-api/6.0.13/annotations-api-6.0.13.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/annotations-api/6.0.13/annotations-api-6.0.13.pom
254b downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/jasper-jdt/6.0.13/jasper-jdt-6.0.13.jar
Downloading:
http://download.java.net/maven/1//org.apache.tomcat/jars/jasper-jdt-6.0.13.jar
Downloading:
http://people.apache.org/repo/m2-incubating-repository//org/apache/tomcat/jasper-jdt/6.0.13/jasper-jdt-6.0.13.jar
Downloading:
http://repo1.maven.org/maven2/org/apache/tomcat/jasper-jdt/6.0.13/jasper-jdt-6.0.13.jar
1343K downloaded
Downloading:
http://repository.codehaus.org/org/apache/tomcat/jasper-el/6.0.13/jasper-el-6.0.13.jar
Downloading:
http://download.java.net/maven/1//org.apache.tomcat/jars/jasper-el-6.0.13.jar
Downloading:
http://people.apache.org/repo/m2-incubating
Re: branches/2.1 freeze notice
Kevan Miller wrote: All, In preparation for our 2.1 release, please hold off on any commits to branches/2.1. If you have something that you feel absolutely *must* be fixed, please check with me. I'll be working on generating a 2.1 release candidate later this afternoon/eveniing. --kevan Kevan, I was thinking that we would need to release the specs and move to the newer ones (including moving from using axis2-saaj-api to geronimo-saaj_1.3_spec) prior to creating a release candidate. Are you anticipating those changes prior to creating the candidate? I also think that we need to eliminate the JASPI snapshot in our root pom ... I think David had plans for that. There's also the problem that I posted about earlier regarding download of wadi* 2.0-M8 that we need to resolve or you can't build. Finally, I think we need to cleanup the NPE exception on shutdown (https://issues.apache.org/jira/browse/GERONIMO-3808). I think we need to resolve those 3 issues prior to creating a candidate. Joe
[BUILD] 2.1: Failed for Revision: 618634
Geronimo Revision: 618634 built with tests included
See the full build-0800.log file at
http://geronimo.apache.org/maven/server/binaries/2.1/20080206/build-0800.log
See the unit test reports at
http://geronimo.apache.org/maven/server/binaries/2.1/20080206/unit-test-reports
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 5 source files to
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-derby/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 1 source file to
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-derby/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-derby/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.derby.DerbySystemGBeanTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.369 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-derby/target/geronimo-derby-2.1-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: geronimo-derby-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-derby/target/geronimo-derby-2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-derby/2.1-SNAPSHOT/geronimo-derby-2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, System Database :: Timer
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-timer/target/classes/META-INF
[INFO] Copying 2 files to
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-timer/target/classes/META-INF
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 20 source files to
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-timer/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 5 source files to
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-timer/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-timer/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.timer.jdbc.DerbyJDBCWorkerPersistenceTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.055 sec
Running org.apache.geronimo.timer.TransactionalThreadPooledTimerTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.308 sec
Running org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.151 sec
Results :
Tests run: 23, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-timer/target/geronimo-timer-2.1-SNAPSHOT.jar
[INFO] [tools:verify-legal-files {execution: verify-legal-files}]
[INFO] Checking legal files in: geronimo-timer-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.1/plugins/system-database/geronimo-timer/target/geronimo-timer-2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-timer/2.1-SNAPSHOT/geronimo-timer-2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, System Database :: System Database
[INFO]task-segment: [install]
[INFO]
Downloading:
http://download.java.net/maven/1//org.tranql/poms/tranql-connector-derby-embed-xa-1.3.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//org/tranql/tranql-connector-derby-embed-xa/1.3/tranql-connector-derby-embed-xa-1.3.pom
Downloading:
http://repo1.maven.org/maven2/org/tranql/tranql-connector-derby-embed-xa/1.3/tranql-connector-derby-embed-xa-1.3.pom
866b downloaded
Downloading:
http://download.java.net/maven/1//org.tranql/poms/tranql-connector-derby-1.3.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//org
Re: Inclusion of MySQL in roller-mysql-database plugin
Hello all, It looks like MySQL has specifically granted an exception to their usual GPL license requirement for a list of FLOSS licenses - ASF 2.0 included: http://www.mysql.com/company/legal/licensing/foss-exception.html In fact, the Apache Portable Runtime library is the only specifically listed library/package listed on that exclusion page. So I think we could distribute the roller-mysql-database plugin if we wanted to - there is already a precedent at the ASF. Or, could we change the way that the plugin is built so that it just has a dependency on a MySQL driver being loaded in the repository? That way, we could give a fairly simple set of instructions on downloading the library from MySQL and loading the jar files into the repository before trying to load the plugin. In my personal setup, I already had a MySQL driver loaded - having one bundled just means that now I have two. I haven't played with creating any plugins yet, so I don't know if the system we have now allows for creating a plugin that doesn't bundle in the dependencies. Is that something that can be done? If we can build plugins that do not necessarily bundle in the dependencies then I think that would be the best way of handling plugins that would bring up licensing questions. If we cannot, then it looks like we will need to put some procedure in place to review plugins that include third party code before they can be hosted by us. Jay Kevan Miller wrote: All, I created a Jira to handle licensing issues involving the inclusion of MySQL in the roller-mysql-database plugin. See https://issues.apache.org/jira/browse/GERONIMO-3816 I've insured that we will no longer build the roller-mysql-database plugin in our source code. However, there are multiple ways of handling this problem. Would like to hear opinions from the project. Ultimately, it's the PMC's responsibility to oversee the licensing of our distributions and to oversee the way we handle dependencies on artifacts that are covered by excluded licenses. The ASF Licensing Policy (currently it's a draft policy, but I think we should be following the guidelines documented there) are located here -- http://www.apache.org/legal/3party.html Discussion of how to handle Prohibited Works is here -- http://people.apache.org/~rubys/3party.html#options Would be good for the project (in particular PMC) members to be familiar with these issues. Would like to hear how we think we should address this issue. As long as I feel the PMC is providing appropriate oversight, I'm happy with what ever decision we reach. --kevan
Re: Inclusion of MySQL in roller-mysql-database plugin
Kevan, Can you explain what is the exact problem in this case? As far as I know, the roller plugin doesn't actaully include or distribute the msql driver. The driver will be automatically downloaded at compile time (becuase it is specified as maven dependency) and when the plugin is installed (becuase it is specified as a plugin dependency). Is the automatic download the problem? If so, maybe we can remove the msql maven dependency and modify the plugin dependency to specify the driver as a prerequisite? Jarek On Feb 6, 2008 9:40 AM, Kevan Miller [EMAIL PROTECTED] wrote: All, I created a Jira to handle licensing issues involving the inclusion of MySQL in the roller-mysql-database plugin. See https://issues.apache.org/jira/browse/GERONIMO-3816 I've insured that we will no longer build the roller-mysql-database plugin in our source code. However, there are multiple ways of handling this problem. Would like to hear opinions from the project. Ultimately, it's the PMC's responsibility to oversee the licensing of our distributions and to oversee the way we handle dependencies on artifacts that are covered by excluded licenses. The ASF Licensing Policy (currently it's a draft policy, but I think we should be following the guidelines documented there) are located here -- http://www.apache.org/legal/3party.html Discussion of how to handle Prohibited Works is here -- http://people.apache.org/~rubys/3party.html#options Would be good for the project (in particular PMC) members to be familiar with these issues. Would like to hear how we think we should address this issue. As long as I feel the PMC is providing appropriate oversight, I'm happy with what ever decision we reach. --kevan
Web site update
Hi All, I added a section to the Getting Involved page. The idea is to explain how easy is to contribute to the project's documentation. http://cwiki.apache.org/GMOxSITE/get-involved.html I also added a very similar page to the wiki front page http://cwiki.apache.org/geronimo/how-to-contribute-to-the-projects-documentation.html Pls let me know what you think and how we can make it better. Cheers! Hernan
[jira] Commented: (GERONIMO-1930) Make security realm types into GBeans so they can be added in new/updated configurations
[ https://issues.apache.org/jira/browse/GERONIMO-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566184#action_12566184 ] David Jencks commented on GERONIMO-1930: I don't think it's appropriate for any of our existing login modules to be aware of a truststore because they all assume any certificate chain they see results from an already estabished ssl/tls connection. Thus, in order to get to the login module, the truststore must have been known by the connection machinery. So, generally the solution to this kind of problem should be to make the connection machinery aware of the geronimo keystore machinery, as is for instance done in the jetty integration. As Vamsi pointed out in a mailing list reply you can always use a SystemPropertiesGBean to set system properties if you can't make the connection machinery geronimo-keystore-aware. Make security realm types into GBeans so they can be added in new/updated configurations Key: GERONIMO-1930 URL: https://issues.apache.org/jira/browse/GERONIMO-1930 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console, security Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3820) Secure LDAP (ldaps) trusted certificate authorities
[ https://issues.apache.org/jira/browse/GERONIMO-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566186#action_12566186 ] David Jencks commented on GERONIMO-3820: I think the best solution would be to make customize apacheds to be aware of the geronimo keystore framework similar to what is done in the jetty integration. Secure LDAP (ldaps) trusted certificate authorities --- Key: GERONIMO-3820 URL: https://issues.apache.org/jira/browse/GERONIMO-3820 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 1.1.1, 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-M6, 2.0-M7, 2.0, 2.0.1, 2.0.2 Environment: Integrating Geronimo with a SSL-enabled LDAP server Reporter: Sakari Maaranen When connecting to a LDAPS server, Geronimo refuses the connection because it cannot trust the server's certificate. This is simply because the trusted certificate authorities are not easily configurable with LDAP security realms. I had to use command line options for my JVM before starting Geronimo: -Djavax.net.ssl.trustStore=geronimo-home/var/security/keystores/keystore-filename -Djavax.net.ssl.trustStorePassword=password Would be nice to have those configurable with GBeans or a similar means, preferrably via a web GUI. More details in GERONIMO-3812 comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Inclusion of MySQL in roller-mysql-database plugin
I'm pretty sure I don't completely understand the issues but... just because mysql has granted an exemption that means the tranql code is not automatically gpl (since it is asf 2.0 licensed) does not mean that the mysql binary can be distributed from the asf. IIUC the asf wants to only be involved in distributing code that is asf licensed or licensed under similar terms: the mysql driver is definitely not licensed under similar terms. So, it appears to be ok to have code to build the roller-mysql plugin at apache, but it should not be run without the user taking special steps that indicate they are aware of the licensing consequences and the result should not be distributed from apache. There's a lot of recent discussion on legal-discuss on this. thanks david jencks On Feb 6, 2008, at 8:07 AM, Jay D. McHugh wrote: Hello all, It looks like MySQL has specifically granted an exception to their usual GPL license requirement for a list of FLOSS licenses - ASF 2.0 included: http://www.mysql.com/company/legal/licensing/foss-exception.html In fact, the Apache Portable Runtime library is the only specifically listed library/package listed on that exclusion page. So I think we could distribute the roller-mysql-database plugin if we wanted to - there is already a precedent at the ASF. Or, could we change the way that the plugin is built so that it just has a dependency on a MySQL driver being loaded in the repository? That way, we could give a fairly simple set of instructions on downloading the library from MySQL and loading the jar files into the repository before trying to load the plugin. In my personal setup, I already had a MySQL driver loaded - having one bundled just means that now I have two. I haven't played with creating any plugins yet, so I don't know if the system we have now allows for creating a plugin that doesn't bundle in the dependencies. Is that something that can be done? If we can build plugins that do not necessarily bundle in the dependencies then I think that would be the best way of handling plugins that would bring up licensing questions. If we cannot, then it looks like we will need to put some procedure in place to review plugins that include third party code before they can be hosted by us. Jay Kevan Miller wrote: All, I created a Jira to handle licensing issues involving the inclusion of MySQL in the roller-mysql-database plugin. See https://issues.apache.org/jira/browse/GERONIMO-3816 I've insured that we will no longer build the roller-mysql- database plugin in our source code. However, there are multiple ways of handling this problem. Would like to hear opinions from the project. Ultimately, it's the PMC's responsibility to oversee the licensing of our distributions and to oversee the way we handle dependencies on artifacts that are covered by excluded licenses. The ASF Licensing Policy (currently it's a draft policy, but I think we should be following the guidelines documented there) are located here -- http://www.apache.org/legal/3party.html Discussion of how to handle Prohibited Works is here -- http:// people.apache.org/~rubys/3party.html#options Would be good for the project (in particular PMC) members to be familiar with these issues. Would like to hear how we think we should address this issue. As long as I feel the PMC is providing appropriate oversight, I'm happy with what ever decision we reach. --kevan
Re: Inclusion of MySQL in roller-mysql-database plugin
On Feb 6, 2008, at 8:15 AM, Jarek Gawor wrote: Kevan, Can you explain what is the exact problem in this case? As far as I know, the roller plugin doesn't actaully include or distribute the msql driver. The driver will be automatically downloaded at compile time (becuase it is specified as maven dependency) and when the plugin is installed (becuase it is specified as a plugin dependency). Is the automatic download the problem? If so, maybe we can remove the msql maven dependency and modify the plugin dependency to specify the driver as a prerequisite? At the moment I'd rather not distribute the plugin than make the maven dependencies inaccurate. I think using prerequisites is definitely an idea worth pursuing. thanks david jencks Jarek On Feb 6, 2008 9:40 AM, Kevan Miller [EMAIL PROTECTED] wrote: All, I created a Jira to handle licensing issues involving the inclusion of MySQL in the roller-mysql-database plugin. See https:// issues.apache.org/jira/browse/GERONIMO-3816 I've insured that we will no longer build the roller-mysql-database plugin in our source code. However, there are multiple ways of handling this problem. Would like to hear opinions from the project. Ultimately, it's the PMC's responsibility to oversee the licensing of our distributions and to oversee the way we handle dependencies on artifacts that are covered by excluded licenses. The ASF Licensing Policy (currently it's a draft policy, but I think we should be following the guidelines documented there) are located here -- http://www.apache.org/legal/3party.html Discussion of how to handle Prohibited Works is here -- http:// people.apache.org/~rubys/3party.html#options Would be good for the project (in particular PMC) members to be familiar with these issues. Would like to hear how we think we should address this issue. As long as I feel the PMC is providing appropriate oversight, I'm happy with what ever decision we reach. --kevan
Re: Geronimo v2.1 documentation
The TOC seems to be too Feature centric. As new users pickup Geronimo, we really need to focus on making their startup/learning curve as short and simple as possible. How about grouping the content based on its intended audience with cross-links between sections as needed - * Getting Started ** What's New/Changes from 2.0 ** Obtaining, Community Support, Opening JIRAs ** Using GShell * Developers ** Deployment plan creator ** Schema Docs (XSD to JavaDoc/HTML) ** Migrating apps from prior releases ** Pluggable Console ** Plugin Infrastructure ** Eclipse Plugin ** Sample Apps * Administrators ** Configuration ** Administration Console ** Security and LoginModule usage ** Resource Adapters (DB, JMS, ...) ** Server Instances/Custom Assemblies ** Clustering ** Monitoring ** Advanced GShell topics The ReleaseNotes are included in the assemblies, so no need to duplicate it in the docs. Anything on building from source or debuging a server in Eclipse should be kept in the GMOxDev wiki. Also, now that we have a start of a internationalized Admin Console, I'd keep the number of screen shots to a minimum, as to reduce the effort required for others wanting to translate the docs into other languages. -Donald Hernan Cunico wrote: Hi All, some time ago I started to put together some topics for Geronimo v2.1 documentation. I tried to focus on the biggest new things we are offering now, topics we didn't have before and now we need to start from scratch. The Geronimo v2.1 documentation space is already available here http://cwiki.apache.org/GMOxDOC21/documentation.html The initial TOC includes: * Configuration changes * Deployment ** Deployment plan creator * Geronimo Administration Console enhancements * GShell * Monitoring * Pluggable console * Plugin infrastructure enhancements * RELEASE-NOTES-2.1.TXT * Sample applications * Security * Tooling * What's new? Each of these pages already contain a few lines with some initial thoughts. Need your input for adding topics to this list as well as developing them. There might be things we already had in 2.0x but we didn't cover it in the doc, pls need your comments on that as well. I think I'm finish covering *Deployment plan creator*, will do a refresh later on as new code gets in. I also created this place holder http://cwiki.apache.org/GMOxPMGT/geronimo-v21-list-of-functions-status.html under *Apache Geronimo Project Management* on the wiki so we can keep track there the features we have ready for prime time and those that are not so ready ;-) I could definitively use that info to build up a new set of docs, would also help users to see where we are at. Cheers! Hernan smime.p7s Description: S/MIME Cryptographic Signature
Re: Web site update
Looks good. Maybe we can create a How to contribute to Samples and Testsuite at some point, as we need more users helping us with those -Donald Hernan Cunico wrote: Hi All, I added a section to the Getting Involved page. The idea is to explain how easy is to contribute to the project's documentation. http://cwiki.apache.org/GMOxSITE/get-involved.html I also added a very similar page to the wiki front page http://cwiki.apache.org/geronimo/how-to-contribute-to-the-projects-documentation.html Pls let me know what you think and how we can make it better. Cheers! Hernan smime.p7s Description: S/MIME Cryptographic Signature
Re: long-term buildability of released versions?
On Tue, Feb 05, 2008 at 01:23:33PM -0500, Jarek Gawor wrote: I've fixed 1) and 2) in trunk, branches/2.0, and branches/2.1. Thank you. I'm not sure about the other two. I tried surefire 2.3 and it works fine. I think it's low risk since it's only used during the build. --- maven-plugins/geronimo-maven-plugin/pom.xml (revision 615899) +++ maven-plugins/geronimo-maven-plugin/pom.xml (working copy) @@ -58,7 +58,7 @@ dependency groupIdorg.apache.maven.surefire/groupId artifactIdsurefire-api/artifactId -version2.1-SNAPSHOT/version +version2.3/version /dependency /dependencies jtidy looks as if it will be a problem, but we've made very good progress.
[jira] Commented: (GERONIMO-1930) Make security realm types into GBeans so they can be added in new/updated configurations
[ https://issues.apache.org/jira/browse/GERONIMO-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566221#action_12566221 ] Sakari Maaranen commented on GERONIMO-1930: --- You probably mean SystemPropertyGBean? I wonder why is it undocumented. Hardly anything on the web. Make security realm types into GBeans so they can be added in new/updated configurations Key: GERONIMO-1930 URL: https://issues.apache.org/jira/browse/GERONIMO-1930 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console, security Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: branches/2.1 freeze notice
Should we fix the following SNAPSHOT depends, which break offline builds in 2.1 or wait for 2.1.1? I can make the changes this afternoon... -Donald Kevan Miller wrote: All, In preparation for our 2.1 release, please hold off on any commits to branches/2.1. If you have something that you feel absolutely *must* be fixed, please check with me. I'll be working on generating a 2.1 release candidate later this afternoon/eveniing. --kevan smime.p7s Description: S/MIME Cryptographic Signature
[jira] Created: (GERONIMO-3822) Remove usage of jaspi spec for 2.1
Remove usage of jaspi spec for 2.1 -- Key: GERONIMO-3822 URL: https://issues.apache.org/jira/browse/GERONIMO-3822 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.1 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1 jaspi isn't done, we need to remove the existing bits for the 2.1 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Inclusion of MySQL in roller-mysql-database plugin
On Feb 6, 2008, at 11:07 AM, Jay D. McHugh wrote: Hello all, It looks like MySQL has specifically granted an exception to their usual GPL license requirement for a list of FLOSS licenses - ASF 2.0 included: http://www.mysql.com/company/legal/licensing/foss-exception.html In fact, the Apache Portable Runtime library is the only specifically listed library/package listed on that exclusion page. So I think we could distribute the roller-mysql-database plugin if we wanted to - there is already a precedent at the ASF. The MySQL FLOSS exception *only* applies when used under the terms of an OSI license. Apache allows it's software to be re-licensed under any license (open source or proprietary). The FLOSS exception prevents this. Or, could we change the way that the plugin is built so that it just has a dependency on a MySQL driver being loaded in the repository? That way, we could give a fairly simple set of instructions on downloading the library from MySQL and loading the jar files into the repository before trying to load the plugin. In my personal setup, I already had a MySQL driver loaded - having one bundled just means that now I have two. Yes. However, it should not be something which maven (or Geronimo) does automatically or implicitly (e.g. without the user's awareness). The user must be aware of his actions and the implications of these actions. I haven't played with creating any plugins yet, so I don't know if the system we have now allows for creating a plugin that doesn't bundle in the dependencies. Is that something that can be done? If we can build plugins that do not necessarily bundle in the dependencies then I think that would be the best way of handling plugins that would bring up licensing questions. If we cannot, then it looks like we will need to put some procedure in place to review plugins that include third party code before they can be hosted by us. Right. As long as there is an explicit user action that causes the download/installation to occur and as long as we make it clear to the user that this action is retrieving a GPL/FLOSS licensed artifact, we should be good. --kevan
Re: Inclusion of MySQL in roller-mysql-database plugin
On Feb 6, 2008, at 11:15 AM, Jarek Gawor wrote: Kevan, Can you explain what is the exact problem in this case? As far as I know, the roller plugin doesn't actaully include or distribute the msql driver. The driver will be automatically downloaded at compile time (becuase it is specified as maven dependency) and when the plugin is installed (becuase it is specified as a plugin dependency). Is the automatic download the problem? If so, maybe we can remove the msql maven dependency and modify the plugin dependency to specify the driver as a prerequisite? Yes. The automatic download is the issue. Just documenting the dependency is fine. --kevan
[jira] Closed: (GERONIMO-3822) Remove usage of jaspi spec for 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-3822. -- Resolution: Fixed rev 619101. Reopen if I missed something. Remove usage of jaspi spec for 2.1 -- Key: GERONIMO-3822 URL: https://issues.apache.org/jira/browse/GERONIMO-3822 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1 jaspi isn't done, we need to remove the existing bits for the 2.1 release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo v2.1 documentation
Donald Woods wrote: The TOC seems to be too Feature centric. As new users pickup Geronimo, we really need to focus on making their startup/learning curve as short and simple as possible. How about grouping the content based on its intended audience with cross-links between sections as needed - * Getting Started ** What's New/Changes from 2.0 ** Obtaining, Community Support, Opening JIRAs ** Using GShell * Developers ** Deployment plan creator ** Schema Docs (XSD to JavaDoc/HTML) ** Migrating apps from prior releases ** Pluggable Console ** Plugin Infrastructure ** Eclipse Plugin ** Sample Apps * Administrators ** Configuration ** Administration Console ** Security and LoginModule usage ** Resource Adapters (DB, JMS, ...) ** Server Instances/Custom Assemblies ** Clustering ** Monitoring ** Advanced GShell topics Yup, checking the latest updates it seems like we are heading in that direction. The ReleaseNotes are included in the assemblies, so no need to duplicate We generate the release notes from the wiki so we can keep them here or move the file to maybe GMOxPMGT space. it in the docs. Anything on building from source or debuging a server in Eclipse should be kept in the GMOxDev wiki. GMOxDev has lot of info and not all up to date. It wouldn't hurt to have the 2.1 specific build info under GMOxDOC21. I mean, the more the merrier Also, now that we have a start of a internationalized Admin Console, I'd keep the number of screen shots to a minimum, as to reduce the effort required for others wanting to translate the docs into other languages. Agreed, screen captures will become an issue, even for updating future releases. It's just that some times a screen shot saves you a lot of typing. Good comments, keep it coming ! Cheers! Hernan -Donald Hernan Cunico wrote: Hi All, some time ago I started to put together some topics for Geronimo v2.1 documentation. I tried to focus on the biggest new things we are offering now, topics we didn't have before and now we need to start from scratch. The Geronimo v2.1 documentation space is already available here http://cwiki.apache.org/GMOxDOC21/documentation.html The initial TOC includes: * Configuration changes * Deployment ** Deployment plan creator * Geronimo Administration Console enhancements * GShell * Monitoring * Pluggable console * Plugin infrastructure enhancements * RELEASE-NOTES-2.1.TXT * Sample applications * Security * Tooling * What's new? Each of these pages already contain a few lines with some initial thoughts. Need your input for adding topics to this list as well as developing them. There might be things we already had in 2.0x but we didn't cover it in the doc, pls need your comments on that as well. I think I'm finish covering *Deployment plan creator*, will do a refresh later on as new code gets in. I also created this place holder http://cwiki.apache.org/GMOxPMGT/geronimo-v21-list-of-functions-status.html under *Apache Geronimo Project Management* on the wiki so we can keep track there the features we have ready for prime time and those that are not so ready ;-) I could definitively use that info to build up a new set of docs, would also help users to see where we are at. Cheers! Hernan
[jira] Commented: (GERONIMO-3808) NPE during server shutdown
[
https://issues.apache.org/jira/browse/GERONIMO-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566283#action_12566283
]
David Jencks commented on GERONIMO-3808:
I don't know how to prove it but I suspect we didn't see this before only by
accidentally shutting down the java:comp gbean before the global context gbean.
I think we could fix this by modifying the JavaCompContextGBean something like
this:
private static final Context EMPTY_CONTEXT;
static {
try {
EMPTY_CONTEXT = new ImmutableContext(Collections.emptyMap());
} catch (NamingException e) {
throw new RuntimeException(Won't happen, e);
}
}
protected Context getContext() {
Context context = RootContext.getComponentContext();
if (context == null) {
return EMPTY_CONTEXT;
}
return context;
}
However this obscures the rather serious error of accessing java:comp from a
thread in which it has not been properly initialized. I'd rather throw a more
informative exception than the NPE but not supply an empty context.
NPE during server shutdown
--
Key: GERONIMO-3808
URL: https://issues.apache.org/jira/browse/GERONIMO-3808
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Kevan Miller
Fix For: 2.1
Anybody else seeing these exceptions during server shutdown?
java.lang.NullPointerException
at
org.apache.xbean.naming.context.ContextFlyweight.listBindings(ContextFlyweight.java:92)
at
org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:88)
at
org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:71)
at
org.apache.xbean.naming.context.AbstractContext.isEmpty(AbstractContext.java:449)
at
org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:138)
at
org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:123)
at
org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:387)
at
org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:377)
at
org.apache.geronimo.gjndi.KernelContextGBean.removeBinding(KernelContextGBean.java:206)
at
org.apache.geronimo.gjndi.KernelContextGBean$ContextLifecycleListener.stopping(KernelContextGBean.java:103)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppingEvent(BasicLifecycleMonitor.java:188)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$400(BasicLifecycleMonitor.java:44)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppingEvent(BasicLifecycleMonitor.java:258)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:167)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316)
at
org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668)
at
org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645)
at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Web site update
I'll take on the samples. Who can take on the Testsuite Cheers! Hernan Donald Woods wrote: Looks good. Maybe we can create a How to contribute to Samples and Testsuite at some point, as we need more users helping us with those -Donald Hernan Cunico wrote: Hi All, I added a section to the Getting Involved page. The idea is to explain how easy is to contribute to the project's documentation. http://cwiki.apache.org/GMOxSITE/get-involved.html I also added a very similar page to the wiki front page http://cwiki.apache.org/geronimo/how-to-contribute-to-the-projects-documentation.html Pls let me know what you think and how we can make it better. Cheers! Hernan
Re: branches/2.1 freeze notice
On Feb 6, 2008, at 10:54 AM, Joe Bohn wrote: Kevan Miller wrote: All, In preparation for our 2.1 release, please hold off on any commits to branches/2.1. If you have something that you feel absolutely *must* be fixed, please check with me. I'll be working on generating a 2.1 release candidate later this afternoon/eveniing. --kevan Kevan, I was thinking that we would need to release the specs and move to the newer ones (including moving from using axis2-saaj-api to geronimo-saaj_1.3_spec) prior to creating a release candidate. Are you anticipating those changes prior to creating the candidate? I also think that we need to eliminate the JASPI snapshot in our root pom ... I think David had plans for that. David is working on the jaspi changes. Regarding specs, yes, I'm going to be working on getting the specs released. There's also the problem that I posted about earlier regarding download of wadi* 2.0-M8 that we need to resolve or you can't build. Yes. Finally, I think we need to cleanup the NPE exception on shutdown (https://issues.apache.org/jira/browse/GERONIMO-3808 ). I'd be happy to see it fixed. And we can certainly require that it be fixed... Anybody gotten to the bottom of it? --kevan
Re: branches/2.1 freeze notice
On Feb 6, 2008, at 1:26 PM, Donald Woods wrote: Should we fix the following SNAPSHOT depends, which break offline builds in 2.1 or wait for 2.1.1? I can make the changes this afternoon... We won't be releasing with direct SNAPSHOT dependencies. These will all be updated as part of the release process. It may be that the release plugin could be used to detect improper, transitive SNAPSHOT dependencies. If you have specific proposals, would be happy to hear about them. --kevan
[jira] Commented: (GERONIMO-1930) Make security realm types into GBeans so they can be added in new/updated configurations
[ https://issues.apache.org/jira/browse/GERONIMO-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566295#action_12566295 ] Kevan Miller commented on GERONIMO-1930: You probably mean SystemPropertyGBean? I wonder why is it undocumented. Hardly anything on the web. Is a very good idea. Could you raise a Jira? Maybe if you learn about it, you could kickstart a little documentation for it? Make security realm types into GBeans so they can be added in new/updated configurations Key: GERONIMO-1930 URL: https://issues.apache.org/jira/browse/GERONIMO-1930 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: console, security Affects Versions: 1.1 Reporter: Aaron Mulder Fix For: 1.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] 2.1: Failed for Revision: 619098
Geronimo Revision: 619098 built with tests included See the full build-1400.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080206/build-1400.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/2.1/20080206/unit-test-reports at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.codehaus.wadi:wadi-core:jar:2.0-M8 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-core \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-core \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-clustering-wadi:jar:2.1-SNAPSHOT 2) org.codehaus.wadi:wadi-core:jar:2.0-M8 2) org.codehaus.wadi:wadi-aop:jar:2.0-M8 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-aop \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-aop \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-clustering-wadi:jar:2.1-SNAPSHOT 2) org.codehaus.wadi:wadi-aop:jar:2.0-M8 3) org.codehaus.wadi:wadi-group:jar:2.0-M8 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-group \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-group \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-clustering-wadi:jar:2.1-SNAPSHOT 2) org.codehaus.wadi:wadi-group:jar:2.0-M8 4) org.codehaus.wadi:wadi-tribes:jar:2.0-M8 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-tribes \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.wadi -DartifactId=wadi-tribes \ -Dversion=2.0-M8 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-clustering-wadi:jar:2.1-SNAPSHOT 2) org.codehaus.wadi:wadi-tribes:jar:2.0-M8 -- 4 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-clustering-wadi:jar:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[RESULT] [VOTE] Release specs (Passed)
Since Guillaume is away (hopefully on a well-earned holiday), I'm calling this vote, in his stead. This vote passes with 8 +1 votes and no others. Note that I'm counting Guillaume as a '+1', although he didn't explicitly state this. I'll start distributing the binaries. --kevan On Feb 1, 2008, at 6:04 AM, Guillaume Nodet wrote: Third try ... Tags are here: http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-activation_1.1_spec-1.0.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-annotation_1.0_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ejb_3.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-el_1.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-interceptor_3.0_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-connector_1.5_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-j2ee-management_1.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jacc_1.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxr_1.0_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jaxrpc_1.1_spec-2.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jms_1.1_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jpa_3.0_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jsp_2.1_spec-1.0.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-jta_1.1_spec-1.1.1/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-saaj_1.3_spec-1.0.0/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-servlet_2.5_spec-1.1.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-ws-metadata_2.0_spec-1.1.2/ http://svn.apache.org/viewvc/geronimo/specs/tags/specs-1.4/ Staging repo is http://people.apache.org/~gnodet/staging/geronimo-specs/ I'm calling a single vote, as it is imho easier, but if there is any concern, I can create other vote threads if needed. [ ] +1 release these specs [ ] -1 another problem ? FYI, I won't be able for the next two weeks, so I won't be able to close the votes and move the specs to their final location. Hopefully someone can do it (provided that this vote is ok). -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Assigned: (GERONIMO-3808) NPE during server shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-3808: -- Assignee: David Jencks NPE during server shutdown -- Key: GERONIMO-3808 URL: https://issues.apache.org/jira/browse/GERONIMO-3808 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Assignee: David Jencks Fix For: 2.1 Anybody else seeing these exceptions during server shutdown? java.lang.NullPointerException at org.apache.xbean.naming.context.ContextFlyweight.listBindings(ContextFlyweight.java:92) at org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:88) at org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:71) at org.apache.xbean.naming.context.AbstractContext.isEmpty(AbstractContext.java:449) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:138) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:123) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:387) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:377) at org.apache.geronimo.gjndi.KernelContextGBean.removeBinding(KernelContextGBean.java:206) at org.apache.geronimo.gjndi.KernelContextGBean$ContextLifecycleListener.stopping(KernelContextGBean.java:103) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppingEvent(BasicLifecycleMonitor.java:188) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$400(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppingEvent(BasicLifecycleMonitor.java:258) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:167) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo v2.1 documentation
Hi, I have prepared following list of tutorials *(developer guide)* items. Initial task will be two work on two items from each bullet. This will enable to cover most of the topics initially and later the concentration will be on increasing the count of articles in each category. Each article will start with basics of each API used and later step by step explanation of the application development. This will enable the developers to find all the information and references at one place. This will in turn help to improve the Usability and Consumabiltiy of Geronimo. The timeframe for the complete list will be around 6 months considering the fact that it involves quite a good amount of learning. Although the initial task will be to complete 2 articles in each category. The environment will be AG 2.1, GEP 2.1, WTP 2.0.1, Eclipse 3.3 SDK and Windows XP. The list is as follows: *Java Server Faces* Developing a web application with JSF. AJAX with JSF. Using JSP Immediate Expressions to access JSF. UI development with JSF. JSF application that created, deletes, update and delete operations against database ttables. *Web Application* Web application for JMS access. Web Application for EJB access. Web Application for JDBC access. *Application Client* Application client accessing EJB. *Web Services* Building JAX-WS pojo web service Building JAX-WS EJB stateless session bean web services. RESTFUL Web Services SAAJ Web Services MTOM Web Services WS Addressing. *Annotations* JAX-WS web service and client using annotations. *Java Persistence API* Using Java Persistence API in application client. Working with JSF and JPA. *EJB* Stateless Session Bean Stateful Session Bean Message Driven Bean. Container Managed Persistence with JPA Bean Managed Persistence with JPA Regarding Portlets, Geronimo extensions there is still more info that needs to be collected. Please provide you comments and suggestions. Thanks Ashish On Feb 7, 2008 12:44 AM, Hernan Cunico [EMAIL PROTECTED] wrote: Donald Woods wrote: The TOC seems to be too Feature centric. As new users pickup Geronimo, we really need to focus on making their startup/learning curve as short and simple as possible. How about grouping the content based on its intended audience with cross-links between sections as needed - * Getting Started ** What's New/Changes from 2.0 ** Obtaining, Community Support, Opening JIRAs ** Using GShell * Developers ** Deployment plan creator ** Schema Docs (XSD to JavaDoc/HTML) ** Migrating apps from prior releases ** Pluggable Console ** Plugin Infrastructure ** Eclipse Plugin ** Sample Apps * Administrators ** Configuration ** Administration Console ** Security and LoginModule usage ** Resource Adapters (DB, JMS, ...) ** Server Instances/Custom Assemblies ** Clustering ** Monitoring ** Advanced GShell topics Yup, checking the latest updates it seems like we are heading in that direction. The ReleaseNotes are included in the assemblies, so no need to duplicate We generate the release notes from the wiki so we can keep them here or move the file to maybe GMOxPMGT space. it in the docs. Anything on building from source or debuging a server in Eclipse should be kept in the GMOxDev wiki. GMOxDev has lot of info and not all up to date. It wouldn't hurt to have the 2.1 specific build info under GMOxDOC21. I mean, the more the merrier Also, now that we have a start of a internationalized Admin Console, I'd keep the number of screen shots to a minimum, as to reduce the effort required for others wanting to translate the docs into other languages. Agreed, screen captures will become an issue, even for updating future releases. It's just that some times a screen shot saves you a lot of typing. Good comments, keep it coming ! Cheers! Hernan -Donald Hernan Cunico wrote: Hi All, some time ago I started to put together some topics for Geronimo v2.1 documentation. I tried to focus on the biggest new things we are offering now, topics we didn't have before and now we need to start from scratch. The Geronimo v2.1 documentation space is already available here http://cwiki.apache.org/GMOxDOC21/documentation.html The initial TOC includes: * Configuration changes * Deployment ** Deployment plan creator * Geronimo Administration Console enhancements * GShell * Monitoring * Pluggable console * Plugin infrastructure enhancements * RELEASE-NOTES-2.1.TXT * Sample applications * Security * Tooling * What's new? Each of these pages already contain a few lines with some initial thoughts. Need your input for adding topics to this list as well as developing them. There might be things we already had in 2.0x but we didn't cover it in the doc, pls need your comments on that
Re: Geronimo v2.1 documentation
Hi Ashish, this is great news !!! Thanks for your interest in contributing to the project documentation. Documenting these topics will certainly help addressing some of the usability issues. Welcome aboard! Cheers! Hernan Ashish Jain wrote: Hi, I have prepared following list of tutorials *(developer guide)* items. Initial task will be two work on two items from each bullet. This will enable to cover most of the topics initially and later the concentration will be on increasing the count of articles in each category. Each article will start with basics of each API used and later step by step explanation of the application development. This will enable the developers to find all the information and references at one place. This will in turn help to improve the Usability and Consumabiltiy of Geronimo. The timeframe for the complete list will be around 6 months considering the fact that it involves quite a good amount of learning. Although the initial task will be to complete 2 articles in each category. The environment will be AG 2.1, GEP 2.1, WTP 2.0.1, Eclipse 3.3 SDK and Windows XP. The list is as follows: *Java Server Faces* Developing a web application with JSF. AJAX with JSF. Using JSP Immediate Expressions to access JSF. UI development with JSF. JSF application that created, deletes, update and delete operations against database ttables. *Web Application* Web application for JMS access. Web Application for EJB access. Web Application for JDBC access. *Application Client* Application client accessing EJB. *Web Services* Building JAX-WS pojo web service Building JAX-WS EJB stateless session bean web services. RESTFUL Web Services SAAJ Web Services MTOM Web Services WS Addressing. *Annotations* JAX-WS web service and client using annotations. *Java Persistence API* Using Java Persistence API in application client. Working with JSF and JPA. *EJB* Stateless Session Bean Stateful Session Bean Message Driven Bean. Container Managed Persistence with JPA Bean Managed Persistence with JPA Regarding Portlets, Geronimo extensions there is still more info that needs to be collected. Please provide you comments and suggestions. Thanks Ashish On Feb 7, 2008 12:44 AM, Hernan Cunico [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Donald Woods wrote: The TOC seems to be too Feature centric. As new users pickup Geronimo, we really need to focus on making their startup/learning curve as short and simple as possible. How about grouping the content based on its intended audience with cross-links between sections as needed - * Getting Started ** What's New/Changes from 2.0 ** Obtaining, Community Support, Opening JIRAs ** Using GShell * Developers ** Deployment plan creator ** Schema Docs (XSD to JavaDoc/HTML) ** Migrating apps from prior releases ** Pluggable Console ** Plugin Infrastructure ** Eclipse Plugin ** Sample Apps * Administrators ** Configuration ** Administration Console ** Security and LoginModule usage ** Resource Adapters (DB, JMS, ...) ** Server Instances/Custom Assemblies ** Clustering ** Monitoring ** Advanced GShell topics Yup, checking the latest updates it seems like we are heading in that direction. The ReleaseNotes are included in the assemblies, so no need to duplicate We generate the release notes from the wiki so we can keep them here or move the file to maybe GMOxPMGT space. it in the docs. Anything on building from source or debuging a server in Eclipse should be kept in the GMOxDev wiki. GMOxDev has lot of info and not all up to date. It wouldn't hurt to have the 2.1 specific build info under GMOxDOC21. I mean, the more the merrier Also, now that we have a start of a internationalized Admin Console, I'd keep the number of screen shots to a minimum, as to reduce the effort required for others wanting to translate the docs into other languages. Agreed, screen captures will become an issue, even for updating future releases. It's just that some times a screen shot saves you a lot of typing. Good comments, keep it coming ! Cheers! Hernan -Donald Hernan Cunico wrote: Hi All, some time ago I started to put together some topics for Geronimo v2.1 documentation. I tried to focus on the biggest new things we are offering now, topics we didn't have before and now we need to start from scratch. The Geronimo v2.1 documentation space is already available here http://cwiki.apache.org/GMOxDOC21/documentation.html The initial TOC includes:
[jira] Closed: (GERONIMO-3808) NPE during server shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-3808. -- Resolution: Fixed Fixed in 2.1 rev 619155 and trunk rev 619158 by using a dependency to make the java:comp context shut down before the global context starts trying to unbind stuff. Also provided a better error message in case someone tries to use java:comp in an uninitialized (non-javaee) thread. NPE during server shutdown -- Key: GERONIMO-3808 URL: https://issues.apache.org/jira/browse/GERONIMO-3808 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: Kevan Miller Assignee: David Jencks Fix For: 2.1 Anybody else seeing these exceptions during server shutdown? java.lang.NullPointerException at org.apache.xbean.naming.context.ContextFlyweight.listBindings(ContextFlyweight.java:92) at org.apache.xbean.naming.context.ContextFederation.getFederatedBindings(ContextFederation.java:88) at org.apache.xbean.naming.context.AbstractFederatedContext.getBindings(AbstractFederatedContext.java:71) at org.apache.xbean.naming.context.AbstractContext.isEmpty(AbstractContext.java:449) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:138) at org.apache.xbean.naming.context.WritableContext.removeBinding(WritableContext.java:123) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:387) at org.apache.xbean.naming.context.AbstractContext.removeDeepBinding(AbstractContext.java:377) at org.apache.geronimo.gjndi.KernelContextGBean.removeBinding(KernelContextGBean.java:206) at org.apache.geronimo.gjndi.KernelContextGBean$ContextLifecycleListener.stopping(KernelContextGBean.java:103) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireStoppingEvent(BasicLifecycleMonitor.java:188) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$400(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireStoppingEvent(BasicLifecycleMonitor.java:258) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:167) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:180) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:563) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:423) at org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:316) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:668) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:645) at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper$1.run(MainConfigurationBootstrapper.java:76) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Passing Object from actionAfterView of one handler to the actionBeforeView portion of another handler
Hi All, In a handler page specifically AssemblyViewHandler.java in the plugin-portlets, I'm in the actionAfterView portion and at the end it returns to INDEX_MODE - is there anyway to pass an object with it so i can getParameter that object in the actionBeforeView portion of the Index handler? I've tried to set the attribute there, but i don't think it applies when going to the INDEX_MODE page... Thanks! the best, Joseph Leong
[jira] Updated: (GERONIMO-3807) ERROR's logged during plugin installation for non-existent plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-3807: --- Fix Version/s: (was: 2.1) Wish List If you wipe the geronimo plugins out of your local maven repo you need to remove the ~/.m2/repository/geronimo-plugins.xml file as well. As plugins are built the file will be recreated and the new plugins added. You can also regenerate the file by running mvn org.apache.geronimo.buildsupport:car-maven-plugin:create-pluginlist I think this is basically in need of more documentation rather than a code change. ERROR's logged during plugin installation for non-existent plugins -- Key: GERONIMO-3807 URL: https://issues.apache.org/jira/browse/GERONIMO-3807 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1 Reporter: Kevan Miller Fix For: Wish List I brought up the console screen to install plugins and had a number of ERROR's logged of the following form: 21:36:07,628 ERROR [PluginInstallerGBean] Cannot install plugin org.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/2.2-SNAPSHOT/car on Geronimo 2.1-SNAPSHOT 21:36:07,722 ERROR [PluginInstallerGBean] Cannot install plugin org.apache.geronimo.framework/j2ee-system/2.2-SNAPSHOT/car on Geronimo 2.1-SNAPSHOT 21:36:07,723 ERROR [PluginInstallerGBean] Cannot install plugin org.apache.geronimo.framework/xmlbeans/2.2-SNAPSHOT/car on Geronimo 2.1-SNAPSHOT ... Presumably because the 2.2-SNAPSHOT plugins were registered in ~/.m2/repository/geronimo-plugins.xml, but they are not in my repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3823) Document the SystemPropertyGBean
Document the SystemPropertyGBean Key: GERONIMO-3823 URL: https://issues.apache.org/jira/browse/GERONIMO-3823 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: deployment, documentation, JVM-compatibility, security, startup/shutdown Environment: Setting JVM system properties Reporter: Sakari Maaranen Priority: Minor Currently the org.apache.geronimo.webservices.SystemPropertyGBean is completely undocumented. It could be a handy configuration tool for various purposes. A short explanation how it works, what is its declaration scope (JVM, module, realm, etc), a couple examples and maybe even some words of warning would be useful for many. Where to insert those SystemPropertyuGBean configurations? Is it possible to compromise the system with carelessly set properties? Where to get info on which properties can be changed runtime and which may require server restart? What is the right place for this documentation? It's very simple GBean actually. There are just the propertyName and propertyValue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: branches/2.1 freeze notice
I just performed a quick scan for direct snapshot dependencies in branches/2.1, here's the list (excluding jacc spec and ejbcontainer-tests): ./buildsupport/testsuite-maven-plugin/pom.xml: jtidy 8.0-SNAPSHOT ./plugins/monitoring/agent-jmx/pom.xml: xbean-naming 3.4-SNAPSHOT ./testsuite/pom.xml: maven-surefire-plugin 2.3-SNAPSHOT ./buildsupport/geronimo-maven-plugin/pom.xml surefire-api 2.1-SNAPSHOT Jarek On Feb 6, 2008 2:22 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Feb 6, 2008, at 1:26 PM, Donald Woods wrote: Should we fix the following SNAPSHOT depends, which break offline builds in 2.1 or wait for 2.1.1? I can make the changes this afternoon... We won't be releasing with direct SNAPSHOT dependencies. These will all be updated as part of the release process. It may be that the release plugin could be used to detect improper, transitive SNAPSHOT dependencies. If you have specific proposals, would be happy to hear about them. --kevan
online deployer log.debug messages
Using G2.0.3-SNAPSHOT Tomcat server, I am finding it impossible to make online-deployer log.debug messages appear in the log. I tried changing the Log Level in LogManagerPortlet to ALL, change the log4j.appender.CONSOLE.Threshold and log4j.appender.FILE.Threshold, but nothing seems to make the log.debug messages appear in geronimo.log. What am I missing?
Re: svn commit: r619186 - in /geronimo/server/branches/2.1: framework/modules/geronimo-commands/pom.xml plugins/jaxws/geronimo-jaxws-builder/pom.xml plugins/openejb/geronimo-openejb/src/main/resources
[EMAIL PROTECTED] wrote: Author: gawor Date: Wed Feb 6 14:29:04 2008 New Revision: 619186 URL: http://svn.apache.org/viewvc?rev=619186view=rev Log: updated openejb version in geronimo-dependency.xml and moved gshell-maven-plugin to root pom (eliminating snapshot dependency) Thanks for catching these openejb 3.0.0-SNAPSHOT references I missed. Joe
[jira] Created: (GERONIMO-3824) ProtocolDecoderException is thrown if the response does not specify Content-Length but is not chunked
ProtocolDecoderException is thrown if the response does not specify Content-Length but is not chunked - Key: GERONIMO-3824 URL: https://issues.apache.org/jira/browse/GERONIMO-3824 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee I've been testing AHC against different servers, and found an interesting case. I configured AHC not to reuse connections (which makes AHC insert Connection: close in its requests). Then I pointed to a main index.jsp page for a Tomcat 5.5.25 installation. What I noticed then is the server does not chunk the content nor sends the Content-Length header. It simply closes the connection to terminate. This is not a good thing to do, but it is not exactly illegal either, it appears according to the spec. In this case, however, the protocol codec gets confused, and throws a StringIndexOutOfBoundsException. HttpResponseDecoder makes an explicit assumption that you either chunk the response or specify the Content-Length header. Please see HttpResponseCoder.processContent(), and notice the lack of the else clause. As a result, HttpResponseCoder transitions to the STATE_CONTENT_READ state, and thinks it is done with the response (although the content is null). But HttpResponseDecoder gets invoked again right away, and that second entry into doDecode() is what throws the exception. Please see the following call stack. I think at least we should be able to handle a case where the server terminates a response without specifying the Content-Length header... org.apache.mina.filter.codec.ProtocolDecoderException: java.lang.StringIndexOutOfBoundsException (Hexdump: omitted) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:164) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.filter.support.SSLHandler.flushScheduledEvents(SSLHandler.java:275) at org.apache.mina.filter.SSLFilter.messageReceived(SSLFilter.java:427) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.common.support.AbstractIoFilterChain$HeadFilter.messageReceived(AbstractIoFilterChain.java:499) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.fireMessageReceived(AbstractIoFilterChain.java:293) at org.apache.mina.transport.socket.nio.SocketIoProcessor.read(SocketIoProcessor.java:228) at org.apache.mina.transport.socket.nio.SocketIoProcessor.process(SocketIoProcessor.java:198) at org.apache.mina.transport.socket.nio.SocketIoProcessor.access$400(SocketIoProcessor.java:45) at org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(SocketIoProcessor.java:485) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:803) Caused by: java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1088) at org.apache.ahc.codec.HttpDecoder.decodeStatus(HttpDecoder.java:145) at org.apache.ahc.codec.HttpResponseDecoder.processStatus(HttpResponseDecoder.java:276) at org.apache.ahc.codec.HttpResponseDecoder.doDecode(HttpResponseDecoder.java:61) at org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:157) ... 19 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[AsyncHttpClient] protocol codec throws exception if Content-Length is not specified
While testing AHC against different servers, I encountered an interesting case. I configured AHC not to reuse connections so connections get closed every time. When I pointed AHC to one server (based on Tomcat 5.5.25), the server sent a response which was not chunked but Content-Length was missing. The server simply closed the connection to terminate the response. This is not a good thing to do, but it is not exactly illegal either per spec. The RFC 2616 says the server closing the connection is one way of determining the message body length. HttpResponseDecoder makes an explicit assumption that you either have a chunked response or Content-Length header must exist. As a result, a protocol decoder exception gets thrown eventually. I think at least we should be able to handle a case where the server terminates a response without specifying the Content-Length header, e.g. by detecting the extra CRLF or by some other means. Thoughts? Thanks, Sangjin
[jira] Commented: (GERONIMO-3824) ProtocolDecoderException is thrown if the response does not specify Content-Length but is not chunked
[ https://issues.apache.org/jira/browse/GERONIMO-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566424#action_12566424 ] Sangjin Lee commented on GERONIMO-3824: --- It was easier to reproduce than I first thought. Just install the latest Tomcat 5.5.x (5.5.26), and point to the index page. You'll get this exception... ProtocolDecoderException is thrown if the response does not specify Content-Length but is not chunked - Key: GERONIMO-3824 URL: https://issues.apache.org/jira/browse/GERONIMO-3824 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee I've been testing AHC against different servers, and found an interesting case. I configured AHC not to reuse connections (which makes AHC insert Connection: close in its requests). Then I pointed to a main index.jsp page for a Tomcat 5.5.25 installation. What I noticed then is the server does not chunk the content nor sends the Content-Length header. It simply closes the connection to terminate. This is not a good thing to do, but it is not exactly illegal either, it appears according to the spec. In this case, however, the protocol codec gets confused, and throws a StringIndexOutOfBoundsException. HttpResponseDecoder makes an explicit assumption that you either chunk the response or specify the Content-Length header. Please see HttpResponseCoder.processContent(), and notice the lack of the else clause. As a result, HttpResponseCoder transitions to the STATE_CONTENT_READ state, and thinks it is done with the response (although the content is null). But HttpResponseDecoder gets invoked again right away, and that second entry into doDecode() is what throws the exception. Please see the following call stack. I think at least we should be able to handle a case where the server terminates a response without specifying the Content-Length header... org.apache.mina.filter.codec.ProtocolDecoderException: java.lang.StringIndexOutOfBoundsException (Hexdump: omitted) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:164) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.filter.support.SSLHandler.flushScheduledEvents(SSLHandler.java:275) at org.apache.mina.filter.SSLFilter.messageReceived(SSLFilter.java:427) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.common.support.AbstractIoFilterChain$HeadFilter.messageReceived(AbstractIoFilterChain.java:499) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.fireMessageReceived(AbstractIoFilterChain.java:293) at org.apache.mina.transport.socket.nio.SocketIoProcessor.read(SocketIoProcessor.java:228) at org.apache.mina.transport.socket.nio.SocketIoProcessor.process(SocketIoProcessor.java:198) at org.apache.mina.transport.socket.nio.SocketIoProcessor.access$400(SocketIoProcessor.java:45) at org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(SocketIoProcessor.java:485) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:803) Caused by: java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1088) at org.apache.ahc.codec.HttpDecoder.decodeStatus(HttpDecoder.java:145) at org.apache.ahc.codec.HttpResponseDecoder.processStatus(HttpResponseDecoder.java:276) at org.apache.ahc.codec.HttpResponseDecoder.doDecode(HttpResponseDecoder.java:61) at org.apache.mina.filter.codec.CumulativeProtocolDecoder.decode(CumulativeProtocolDecoder.java:133) at
[BUILD] 2.2: Failed for Revision: 619241
Geronimo Revision: 619241 built with tests included See the full build-2100.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080206/build-2100.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/trunk/20080206 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 30 minutes 14 seconds [INFO] Finished at: Wed Feb 06 21:37:47 EST 2008 [INFO] Final Memory: 304M/998M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080206/logs-2100-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080206/logs-2100-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 70.662 sec FAILURE!
[jira] Updated: (GERONIMO-3824) ProtocolDecoderException is thrown if the response does not specify Content-Length but is not chunked
[ https://issues.apache.org/jira/browse/GERONIMO-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated GERONIMO-3824: -- Attachment: GERONIMO-3824.patch I have a proposed fix for this. The idea is to keep looping to add all the remaining contents from the buffer. We do this until the session is closed by the server to terminate the response. The ProtocolDecoder.finishDecode() provides a natural point where one can complete the response when session is getting closed. I was able to reproduce the problem against a vanilla Tomcat 5.5.26 installation, and verify the fix. Please review the fix, and apply it if you find it acceptable. Also, you may want to propagate this change to the version of AHC in the sandbox based on the mina trunk. FYI, the mina trunk now has a very nice notion of state-machine classes that express these decoding states succinctly. This problem can be handled by a state named ConsumeToEndOfSessionDecodingState, and that's where I got the hint from... ProtocolDecoderException is thrown if the response does not specify Content-Length but is not chunked - Key: GERONIMO-3824 URL: https://issues.apache.org/jira/browse/GERONIMO-3824 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee Attachments: GERONIMO-3824.patch I've been testing AHC against different servers, and found an interesting case. I configured AHC not to reuse connections (which makes AHC insert Connection: close in its requests). Then I pointed to a main index.jsp page for a Tomcat 5.5.25 installation. What I noticed then is the server does not chunk the content nor sends the Content-Length header. It simply closes the connection to terminate. This is not a good thing to do, but it is not exactly illegal either, it appears according to the spec. In this case, however, the protocol codec gets confused, and throws a StringIndexOutOfBoundsException. HttpResponseDecoder makes an explicit assumption that you either chunk the response or specify the Content-Length header. Please see HttpResponseCoder.processContent(), and notice the lack of the else clause. As a result, HttpResponseCoder transitions to the STATE_CONTENT_READ state, and thinks it is done with the response (although the content is null). But HttpResponseDecoder gets invoked again right away, and that second entry into doDecode() is what throws the exception. Please see the following call stack. I think at least we should be able to handle a case where the server terminates a response without specifying the Content-Length header... org.apache.mina.filter.codec.ProtocolDecoderException: java.lang.StringIndexOutOfBoundsException (Hexdump: omitted) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:164) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.filter.support.SSLHandler.flushScheduledEvents(SSLHandler.java:275) at org.apache.mina.filter.SSLFilter.messageReceived(SSLFilter.java:427) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) at org.apache.mina.common.support.AbstractIoFilterChain$HeadFilter.messageReceived(AbstractIoFilterChain.java:499) at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) at org.apache.mina.common.support.AbstractIoFilterChain.fireMessageReceived(AbstractIoFilterChain.java:293) at org.apache.mina.transport.socket.nio.SocketIoProcessor.read(SocketIoProcessor.java:228) at org.apache.mina.transport.socket.nio.SocketIoProcessor.process(SocketIoProcessor.java:198) at org.apache.mina.transport.socket.nio.SocketIoProcessor.access$400(SocketIoProcessor.java:45) at org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(SocketIoProcessor.java:485) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) at
