[jira] Closed: (GERONIMODEVTOOLS-579) java specs are not included into G server runtime by default

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMODEVTOOLS-579. - Fixed in latest build.Close it. java specs are not included into G server

[jira] Resolved: (GERONIMODEVTOOLS-504) advanced security section does not allow setting of credential store

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-504. Resolution: Fixed Fix Version/s: 2.1.5 Assignee: Delos

[jira] Created: (GERONIMO-4877) Modification to keystoreFile doesn't work for HTTPS connector

Modification to keystoreFile doesn't work for HTTPS connector - Key: GERONIMO-4877 URL: https://issues.apache.org/jira/browse/GERONIMO-4877 Project: Geronimo Issue Type: Bug

[jira] Assigned: (GERONIMO-4877) Modification to keystoreFile doesn't work for HTTPS connector

[ https://issues.apache.org/jira/browse/GERONIMO-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4877: - Assignee: Shawn Jiang Modification to keystoreFile doesn't work for HTTPS connector

[jira] Assigned: (GERONIMO-4850) WADI clustering: the application no node B will not start up when start up the node B.

[ https://issues.apache.org/jira/browse/GERONIMO-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4850: - Assignee: Shawn Jiang WADI clustering: the application no node B will not start up

[jira] Updated: (GERONIMO-4876) java.lang.Exception when I shutdown the server

[ https://issues.apache.org/jira/browse/GERONIMO-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin He updated GERONIMO-4876: - Priority: Minor (was: Major) java.lang.Exception when I shutdown the server

[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information

[ https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755386#action_12755386 ] viola.lu commented on GERONIMO-4855: hi, jeff, pls update your doc

[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information

[ https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755391#action_12755391 ] Shawn Jiang commented on GERONIMO-4855: --- Session Sticky does not resolve the

[jira] Commented: (GERONIMO-4850) WADI clustering: the application no node B will not start up when start up the node B.

[ https://issues.apache.org/jira/browse/GERONIMO-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755394#action_12755394 ] Shawn Jiang commented on GERONIMO-4850: --- When node-A (main node) is shutdown.

[jira] Resolved: (GERONIMO-4873) Unable creating a new JMS Resource Group via For another JMS provider... under IE

[ https://issues.apache.org/jira/browse/GERONIMO-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4873. Resolution: Fixed Fix Version/s: 3.0 2.2 Commit changes to 2.2 At revision:

[jira] Resolved: (GERONIMODEVTOOLS-453) JAXB Classes support for schema geronimo-login-config-2.0.xsd

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-453. Resolution: Fixed Fix Version/s: 2.1.5 Thanks Rodger! I pick up

[jira] Resolved: (GERONIMODEVTOOLS-455) Add Database pool wizard in GEP to enable application specific pools

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-455. Resolution: Fixed Fix Version/s: 2.1.5 Thanks Rodger! Although

[BUILD] trunk: Failed for Revision: 815175

Geronimo Revision: 815175 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test

[jira] Resolved: (GERONIMODEVTOOLS-456) Add Security Realm Wizard to GEP to deploy security realm directly from GEP

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-456. Resolution: Fixed Fix Version/s: 2.1.5 Thanks Rodger! This patch

[jira] Commented: (GERONIMO-4876) java.lang.Exception when I shutdown the server

[ https://issues.apache.org/jira/browse/GERONIMO-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755407#action_12755407 ] Chi Runhua commented on GERONIMO-4876: -- I encountered the same exception when

[jira] Resolved: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-283. Resolution: Fixed Fix Version/s: 2.1.5 Cool, Rodger! Shiva, I

Re: documentation is important too

RunHua Chi wrote: As for the examples that you mentioned, in my understanding, G Doc already has certain topics for those: 1. Database security realm, you may refer to http://cwiki.apache.org/GMOxDOC22/database-sql-realm.html Database security realm is something different, it is about

Re: documentation is important too

Well, I think it's something missing in Geronimo. You might want to file a JIRA for this one. https://issues.apache.org/jira/browse/GERONIMO And I am also interested in the struggle you experienced, as you mentioned earlier, it took you almost entire day to write it correct. Could you let us

[jira] Commented: (GERONIMO-4818) Can not configure username and password of logging in the server through ldap

[ https://issues.apache.org/jira/browse/GERONIMO-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755433#action_12755433 ] Chi Runhua commented on GERONIMO-4818: -- Doc for G2.2 updated accordingly.

[jira] Updated: (GERONIMO-4222) Database pool unusable after database unavailable for awhile

[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4222: --- Attachment: tranql-connector-postgresql-common-1.1.jar As David pointed out, there's no stardard

[jira] Created: (GERONIMO-4878) Geronimo doesnt protect access to its Derby databases

Geronimo doesnt protect access to its Derby databases - Key: GERONIMO-4878 URL: https://issues.apache.org/jira/browse/GERONIMO-4878 Project: Geronimo Issue Type: Bug Security Level:

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

+1 Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The corresponding

Geronimo Trunk compilation error with JDK5

Folks, Just noticed that G source cannot be build using JDK5 anymore due to the following error. This error will not happen with JDK6. Is this is the expected behavior? Regards, Lasantha [INFO] [INFO] Trace

Re: Geronimo Trunk compilation error with JDK5

Yes, right now we have to use Java 6 to compile trunk. -Jack On Tue, Sep 15, 2009 at 7:43 PM, Lasantha Ranaweera lasan...@opensource.lkwrote: Folks, Just noticed that G source cannot be build using JDK5 anymore due to the following error. This error will not happen with JDK6. Is this is the

[BUILD] trunk: Failed for Revision: 815305

Geronimo Revision: 815305 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

+1 Donald Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The

Re: [FYI]Summary list for G2.2 doc updates

Hi all, FYI. 2 more topics updated for G2.2 doc. 1. Replacing the default realm in G2.2 http://cwiki.apache.org/GMOxDOC22/replacing-default-realm-in-geronimo.html 2. Tomcat native clustering--Enable session affinity on how-to

[jira] Commented: (GERONIMO-4878) Geronimo doesnt protect access to its Derby databases

[ https://issues.apache.org/jira/browse/GERONIMO-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755485#action_12755485 ] Donald Woods commented on GERONIMO-4878: Duplicate of

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

+1 Joe Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at: https://repository.apache.org/content/repositories/geronimo-staging-005/ The

[jira] Resolved: (GERONIMO-4877) Modification to keystoreFile doesn't work for HTTPS connector

[ https://issues.apache.org/jira/browse/GERONIMO-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4877. --- Resolution: Fixed Fixed in 22 branch and trunk. Modification to keystoreFile doesn't

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

Actually, I think this is the file where you need to add your key - http://www.apache.org/dist/geronimo/KEYS Reference this old post/question which didn't generate much interest at the time for details: http://www.nabble.com/public-keys-for-releases-tt17538242s134.html#a17538242 Also, you

[jira] Closed: (GERONIMO-4683) Transaction.commit method signature isn't entirely correctly

[ https://issues.apache.org/jira/browse/GERONIMO-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun closed GERONIMO-4683. - Resolution: Invalid Assignee: Lin Sun Transaction.commit method signature isn't entirely

[BUILD] branches/2.2: Failed for Revision: 815286

Geronimo Revision: 815286 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915/build-0800.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915 [INFO] BUILD

[jira] Reopened: (GERONIMO-4683) Transaction.commit method signature isn't entirely correctly

[ https://issues.apache.org/jira/browse/GERONIMO-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun reopened GERONIMO-4683: --- I just realized that the SecurityException is also unchecked exception. So we are listing one but

Those jar files in each created jms resource adapter

Hi, Currently, I found many ActiveMQ related jar files are included in each jms resource folder. Since the activemq-broker is the parent classloader of the each created resource adapter, I thought we should not have those files there. If they could be removed, the size of the whole binary

Re: Those jar files in each created jms resource adapter

On Sep 15, 2009, at 7:57 AM, Ivan wrote: Hi, Currently, I found many ActiveMQ related jar files are included in each jms resource folder. Since the activemq-broker is the parent classloader of the each created resource adapter, I thought we should not have those files there. If they

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

+1 Jarek On Fri, Sep 11, 2009 at 12:38 PM, Guillaume Nodet gno...@gmail.com wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at:  

[BUILD] trunk: Failed for Revision: 815450

Geronimo Revision: 815450 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test

[VOTE] release geronimo-jpa_1.0_spec 1.1.2

After some discussion with the openjpa folks it seems like its a good idea to re-release our jpa 1 spec with an aritfactId of geronimo- jpa_1.0_spec rather than the original 3.0 version number. We don't really have a plan for what to do when jpa actually gets a 3.0 spec, but we don't have

[BUILD] branches/2.2: Failed for Revision: 815424

Geronimo Revision: 815424 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915/build-1400.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20090915 [INFO] BUILD

Re: [VOTE] release geronimo-jpa_1.0_spec 1.1.2

+1 Thanks for doing this. -Donald David Jencks wrote: After some discussion with the openjpa folks it seems like its a good idea to re-release our jpa 1 spec with an aritfactId of geronimo-jpa_1.0_spec rather than the original 3.0 version number. We don't really have a plan for what to do

Re: [VOTE] Release Blueprint 1.0.0 (4th try)

+1 On Sep 11, 2009, at 9:38 AM, Guillaume Nodet wrote: I've uploaded another 1.0.0 release of the blueprint project. I think I've addressed all the issues raised in the discussion thread. The staging repository is available at:

[RESULT] [VOTE] release jaspic implementation component 1.0

Vote passes with 5 +1 (dwoods, rmcguire, jgawor, djencks, kmiller) and no other votes I'll promote the staging repo and move the site. many thanks david jencks On Sep 10, 2009, at 7:08 PM, David Jencks wrote: It's time for the first release of our jaspic implementation for inclusion in g.

[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile

[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755804#action_12755804 ] David Jencks commented on GERONIMO-4222: Could you show the code you are using?

[RESULT] [VOTE] geronimo-jacc_1.1_spec version 1.0.2

vote passes with 5 +1 (dwoods, rmcguire, jgawor, kmiller, djencks) 1 -0 (gnodet) I'll promote the staging repo and move the site over. Meanwhile I've also fixed the license file in svn problem kevan noticed. thanks david jencks On Sep 10, 2009, at 5:16 PM, David Jencks wrote: I've built a

[VOTE] release geronimo's forked mavenized tomcat 6.0.20.0

For various reasons we are now using a forked copy of tomcat derived from the tomcat 6.0.20 release, built with maven, with maven dependencies, etc etc. The code changes from tomcat 6.0.20 are: r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1 line GERONIMO-4566 port

[BUILD] trunk: Failed for Revision: 815581

Geronimo Revision: 815581 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090915/unit-test

Re: [VOTE] xbean 3.6 3rd try

+1 given the updated checksums. --kevan On Sep 14, 2009, at 4:20 PM, Kevan Miller wrote: Looks good, except the md5/sha1 checksum errors. I'm -1 until they're fixed. --kevan On Sep 11, 2009, at 7:07 PM, David Jencks wrote: I've prepared a 3rd release candidate for xbean 3.6:

[jira] Resolved: (GERONIMO-4790) Migrate debug-views code to base on the up-to-date dojo

[ https://issues.apache.org/jira/browse/GERONIMO-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4790. Resolution: Fixed Fix Version/s: 3.0 Migrate debug-views code to base on the up-to-date

[jira] Resolved: (GERONIMO-4647) welcome files with servlet mappings

[ https://issues.apache.org/jira/browse/GERONIMO-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-4647. Resolution: Fixed David has ported the fix to our private build in r814083. So change to fixed

Re: Those jar files in each created jms resource adapter

Thanks, David ! Not sure if 2nd geronimo-activemq-ra is added, whether it would make the user feel confusion. 2009/9/15 David Jencks david_jen...@yahoo.com On Sep 15, 2009, at 7:57 AM, Ivan wrote: Hi, Currently, I found many ActiveMQ related jar files are included in each jms resource

[jira] Closed: (GERONIMO-4850) WADI clustering: the application no node B will not start up when start up the node B.

[ https://issues.apache.org/jira/browse/GERONIMO-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4850. - Resolution: Invalid I believe this is working as design. See comments in :

[jira] Closed: (GERONIMO-4858) Geronimo 2.2 doesn't add correct connector attributes to server.xml

[ https://issues.apache.org/jira/browse/GERONIMO-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4858. - Closing it. Geronimo 2.2 doesn't add correct connector attributes to server.xml

[jira] Closed: (GERONIMO-4856) Some abnormal conditions with Tomcat NIO HTTPS Connector

[ https://issues.apache.org/jira/browse/GERONIMO-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4856. - Closing it. Some abnormal conditions with Tomcat NIO HTTPS Connector

[jira] Closed: (GERONIMO-4853) Can't define tomcat connector with GBean.

[ https://issues.apache.org/jira/browse/GERONIMO-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4853. - Closing it. Can't define tomcat connector with GBean.

[jira] Closed: (GERONIMO-4859) Default JMX monitoring MBeans list should include JVM MBean.

[ https://issues.apache.org/jira/browse/GERONIMO-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4859. - Closing it. Default JMX monitoring MBeans list should include JVM MBean.

[jira] Resolved: (GERONIMO-4851) Server will get into abnormal status when trying to edit/delete Tomcat Connector HTTPS BIO network listener

[ https://issues.apache.org/jira/browse/GERONIMO-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4851. --- Resolution: Fixed This should have been fixed in another JIRA. Server will get into

[jira] Closed: (GERONIMO-4798) can't start server because of an error of Http11AprProtocol

[ https://issues.apache.org/jira/browse/GERONIMO-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4798. - Closing it. can't start server because of an error of Http11AprProtocol

[jira] Closed: (GERONIMO-4742) Connector portlets for Tomcat does not work

[ https://issues.apache.org/jira/browse/GERONIMO-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4742. - Closing it. Connector portlets for Tomcat does not work

[jira] Closed: (GERONIMO-4712) Some INFO log is not very good/useful.

[ https://issues.apache.org/jira/browse/GERONIMO-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4712. - Closing it. Some INFO log is not very good/useful. --

[jira] Closed: (GERONIMO-4851) Server will get into abnormal status when trying to edit/delete Tomcat Connector HTTPS BIO network listener

[ https://issues.apache.org/jira/browse/GERONIMO-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4851. - Closing it. Server will get into abnormal status when trying to edit/delete Tomcat Connector

[jira] Closed: (GERONIMO-4777) WADI clustering does not work with Jetty7

[ https://issues.apache.org/jira/browse/GERONIMO-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4777. - Closing it. WADI clustering does not work with Jetty7

[jira] Assigned: (GERONIMO-4846) form based security for the web application does not work with Jetty WADI clustering.

[ https://issues.apache.org/jira/browse/GERONIMO-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4846: - Assignee: (was: Shawn Jiang) Don't have time to look into it for now. form

[jira] Updated: (GERONIMO-4222) Database pool unusable after database unavailable for awhile

[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai updated GERONIMO-4222: --- Attachment: PGtrial.patch Attaching a modified trial patch that hard code the fatal error codes.

[jira] Resolved: (GERONIMODEVTOOLS-320) Provide facility to change id/pw associated with server instance (withing creating a new instance of the server)

[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-320. Resolution: Fixed Fix Version/s: 2.1.5 Although the function has

[jira] Resolved: (GERONIMO-4839) A non-existent EJB server also can run

[ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Du resolved GERONIMO-4839. --- Resolution: Fixed A non-existent EJB server also can run --

[jira] Closed: (GERONIMO-4839) A non-existent EJB server also can run

[ https://issues.apache.org/jira/browse/GERONIMO-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Du closed GERONIMO-4839. - The bug in openejb has been fixed, close it. A non-existent EJB server also can run

[jira] Commented: (GERONIMO-4855) Clustering can not work when the application needs login information

[ https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755874#action_12755874 ] viola.lu commented on GERONIMO-4855: Hi, i tried on tomcat also, its scenario and