[jira] Updated: (GERONIMO-615) RMIClassLoaderSpiImpl.normalizeCodebase(..) generates MalformedURLExceptions unnecessarily

[ http://issues.apache.org/jira/browse/GERONIMO-615?page=all ] John Sisson updated GERONIMO-615: - Fix Version: 1.1 (was: 1.2) > RMIClassLoaderSpiImpl.normalizeCodebase(..) generates MalformedURLExceptions > unnecessarily > -

Re: Commit configId to moduleId?

On May 5, 2006, at 3:05 PM, Dain Sundstrom wrote: I think now is the time to discuss if we want to commit the change from configId to moduleId. If we decide to commit the patch, the timing of the actual commit will be determined by Kevan to have the smallest impact on the TCK. The patch

Re: Thinking about 1.2 and moving forward

+1. I think trying to merge 1.1 to the current 1.2 trunk would be a nightmare, indeed. Moving aside 1.2 and making the 1.1 copy a new trunk is the best decision, IMHO. Matt Hogstrom wrote: > I think we're at the point where 1.1 needs to bake for a bit and we'll > release it in a few weeks. Since

Re: Thinking about 1.2 and moving forward

Hmm.. seems inevitable I guess. As for the M2 work done so far, I understand we'd have to *move* it from the old trunk to the new trunk (not exactly doing it all over again). Since it's the 2nd time around, I hope we can run through it this time within a week. Cheers Prasad On 5/7/06, Jeff Gene

Re: Thinking about 1.2 and moving forward

I was thinking about Java One as there will be ample time for folks to get together and it seemed like a good idea to have a branch for them to work in. Aaron's note in a separate thread is a good reminder that 1.1 has lots of work that needs to be completed as well. Hopefully well be able to

Re: Thinking about 1.2 and moving forward

I'm afraid it will take several weeks to merge the 1.2 changes into 1.1 and result in something that vaguely works. I also think we have more than enough to do to get 1.1 out the door. Hopefully I'm wrong on both these counts. thanks david jencks On May 7, 2006, at 3:19 PM, Matt Hogstrom w

Fairly big problem with tomcat integration

I've run into a couple fair-sized problems with the tomcat integration and I'm not sure how to proceed. The problems are: 1. commons-modeler 1.1 is broken for use in a jsr-77 compliant environment. The BaseModelMBean has a method ObjectName getObjectName() which is used in preference to a

[jira] Closed: (GERONIMO-1975) security builder should trim everything

[ http://issues.apache.org/jira/browse/GERONIMO-1975?page=all ] David Jencks closed GERONIMO-1975: -- Resolution: Fixed fixed in rev 404878 > security builder should trim everything > --- > > Key: GERONIM

Re: Fairly big problem with tomcat integration

David, Could u please post a message on [EMAIL PROTECTED], let's see if we can get someone there to push out a release for us. thanks, dims On 5/7/06, David Jencks <[EMAIL PROTECTED]> wrote: I've run into a couple fair-sized problems with the tomcat integration and I'm not sure how to proceed.

Re: Fairly big problem with tomcat integration

I have a similar concern with *Connectors. The attributes of the connectors should be set only via GBeans. But using Jconsole one could easily modify the attributes of the tomcat connector Mbeans, thereby creating an inconsistent state and unpredictable behavior. It is very easy to mistake one

[jira] Created: (GERONIMO-1996) Serialization failure during deployment leaves a config.ser in the repository but doesn't write a config.info causing problems later.

Serialization failure during deployment leaves a config.ser in the repository but doesn't write a config.info causing problems later. - Key: GERONIMO-1996

Re: Thinking about 1.2 and moving forward

--- Jacek Laskowski <[EMAIL PROTECTED]> wrote: > On 5/6/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > > I'm consolidating here my recollections of discussion on the list > about what to do. The idea that > > made the most sense to me was to move the current trunk to another > branch and cop

[jira] Updated: (GERONIMO-1996) Serialization failure during deployment leaves a config.ser in the repository but doesn't write a config.info causing problems later.

[ http://issues.apache.org/jira/browse/GERONIMO-1996?page=all ] John Sisson updated GERONIMO-1996: -- Attachment: jira-g-1996.zip Small Maven 2 project (to reproduce problem) for an ear containing an EJB that causes a NullPointerException to be thrown du

[jira] Closed: (GERONIMO-1977) Remove corba spec & javamail spec from rmi-naming

[ http://issues.apache.org/jira/browse/GERONIMO-1977?page=all ] David Jencks closed GERONIMO-1977: -- Resolution: Fixed applied with additions in rev 404911. Made the mail spec a dependency of geronimo-mail module. > Remove corba spec & javamail s

[jira] Created: (GERONIMO-1997) Not possible to account for startup time in --long startup output due to configurations showing 0s

Not possible to account for startup time in --long startup output due to configurations showing 0s -- Key: GERONIMO-1997 URL: http://issues.apache.org/jira/browse/GERONIMO-1997 P

Re: Fairly big problem with tomcat integration

On May 7, 2006, at 6:56 PM, anita kulshreshtha wrote: I have a similar concern with *Connectors. The attributes of the connectors should be set only via GBeans. But using Jconsole one could easily modify the attributes of the tomcat connector Mbeans, thereby creating an inconsistent state a