[jira] Closed: (GERONIMO-402) disentangle package relationships in openejb

[ http://nagoya.apache.org/jira/browse/GERONIMO-402?page=history ] David Jencks closed GERONIMO-402: - Assign To: David Jencks Resolution: Fixed Fix Version: 1.0-M3 Thanks to David Blevins for removing the dependencies on the deployment

[jira] Resolved: (GERONIMO-464) Split out common geronimo-security.xsd processing code

[ http://nagoya.apache.org/jira/browse/GERONIMO-464?page=history ] David Jencks resolved GERONIMO-464: --- Resolution: Fixed Fix Version: 1.0-M3 (was: 1.0-M2) Security schema moved to security-builder module. Schema

[jira] Closed: (GERONIMO-464) Split out common geronimo-security.xsd processing code

[ http://nagoya.apache.org/jira/browse/GERONIMO-464?page=history ] David Jencks closed GERONIMO-464: - not sure why this didn't get closed with last action... Split out common geronimo-security.xsd processing code

Documentation Update

I've added a chapter on the basic development/deployment requirements and tools. This makes: - about, install, basics - JDBC pools and JMS connection factories and destinations - security, including realms and HTTPS - development and deployment overview/tools - Web application WARs,

Re: svn commit: rev 57121 - geronimo/trunk/modules/jetty-builder/src/java/org/apache/geronimo/jetty/deployment

[EMAIL PROTECTED] wrote: Author: adc Date: Tue Nov 9 19:14:42 2004 New Revision: 57121 Modified: geronimo/trunk/modules/jetty-builder/src/java/org/apache/geronimo/jetty/deployment/JettyModuleBuilder.java Log: Temporary fix Er, for what? :-) -- Jeremy

[jira] Reopened: (GERONIMO-465) new deployer only works in a single configuration

[ http://nagoya.apache.org/jira/browse/GERONIMO-465?page=history ] Jeremy Boynes reopened GERONIMO-465: Still broken - can we test this next time new deployer only works in a single configuration -

[jira] Closed: (GERONIMO-465) new deployer only works in a single configuration

[ http://nagoya.apache.org/jira/browse/GERONIMO-465?page=history ] Jeremy Boynes closed GERONIMO-465: -- Resolution: Fixed This was fixed, just that the error messages made it look like it wasn't new deployer only works in a single configuration

Re: Logging problems

On Nov 5, 2004, at 1:29 PM, Dain Sundstrom wrote: Log4j GBeans Our current log4j gbeans attempt to control the creation of log objects, priories... basically the log4j configuration. The problem I have found is any application can come along and reset the current log4j configuration and

[jira] Created: (GERONIMO-466) Expose additional attributes on the current web container GBean implementation

Expose additional attributes on the current web container GBean implementation -- Key: GERONIMO-466 URL: http://nagoya.apache.org/jira/browse/GERONIMO-466 Project: Apache Geronimo Type: Wish

[jira] Updated: (GERONIMO-466) Expose additional attributes on the current web container GBean implementation

[ http://nagoya.apache.org/jira/browse/GERONIMO-466?page=history ] Lester T. Ecarma updated GERONIMO-466: -- Attachment: JettyContainerImpl.java.patch Expose additional attributes on the current web container GBean implementation

[jira] Created: (GERONIMO-467) ejbRemove does not work for CMP with MTM relationship

ejbRemove does not work for CMP with MTM relationship - Key: GERONIMO-467 URL: http://nagoya.apache.org/jira/browse/GERONIMO-467 Project: Apache Geronimo Type: Bug Components: OpenEJB Versions: 1.0-M2

Re: WSConfigBuilderTest

well, then it's better to get the EJB tests running. it's commented out right now. thanks, dims On Wed, 10 Nov 2004 18:57:53 +0600, Srinath Perera [EMAIL PROTECTED] wrote: Hi Dims; What the test should do is to create GBean using WSConfigBuilder, and try to test them. I was not sure how to

Build of latest version

Re: Logging problems

On Nov 10, 2004, at 12:29 AM, Dain Sundstrom wrote: On Nov 5, 2004, at 1:29 PM, Dain Sundstrom wrote: Log4j GBeans Our current log4j gbeans attempt to control the creation of log objects, priories... basically the log4j configuration. The problem I have found is any application can come along

[jira] Assigned: (GERONIMO-155) [proposal] XML resolving for kernel - containerwide Parser

[ http://nagoya.apache.org/jira/browse/GERONIMO-155?page=history ] Alan Cabrera reassigned GERONIMO-155: - Assign To: David Jencks (was: Alan Cabrera) This is an old issue; my bad. David has strong feelings on what should be done w/ this.

[BULK] Re: Logging problems

Geir Magnusson Jr wrote: What are the repercussions for existing users? Speaking as one (1) existing user, it means I have to rip out things that were working (log4j.xml, system-plan.xml, and daily logs) and figure out how to get back to the state I was in before with the new code. About

How forgiving should we be about jndi component context names?

The spec seems to indicate fairly clearly that a components jndi context is located in java:comp/env or at least java:comp However I believe it is popular to misspell this java:/comp/env Do we want to support this naming abuse? thanks david jencks

Re: Logging problems

Dain Sundstrom wrote: On Nov 5, 2004, at 1:29 PM, Dain Sundstrom wrote: Log4j GBeans Our current log4j gbeans attempt to control the creation of log objects, priories... basically the log4j configuration. The problem I have found is any application can come along and reset the current log4j

Re: How forgiving should we be about jndi component context names?

David Jencks wrote: However I believe it is popular to misspell this java:/comp/env Do we want to support this naming abuse? It would be convenient, but might cause applications to fail when ported to other app servers. If the spec is clear on the correct usage, then I think it's better to just

Re: How forgiving should we be about jndi component context names?

I tend to agree with you, but not supporting it if most other app servers do causes the opposite problem, that non-compliant apps that run elsewhere won't run on geronimo. In particular xpetstore seems to make use of this non-compliant behavior. thanks david jencks On Nov 10, 2004, at 8:41

Any Other Changes Today?

So we're targeting a M3 release today. Does anyone else have pending changes they want to get in, or can we assume that it will be critical bugfixes only at this point? Thanks, Aaron

[jira] Created: (GERONIMO-469) Should allow lookup of java:/comp as well as java:comp

Should allow lookup of java:/comp as well as java:comp -- Key: GERONIMO-469 URL: http://nagoya.apache.org/jira/browse/GERONIMO-469 Project: Apache Geronimo Type: Bug Components: naming Versions: 1.0-M2

[jira] Closed: (GERONIMO-469) Should allow lookup of java:/comp as well as java:comp

[ http://nagoya.apache.org/jira/browse/GERONIMO-469?page=history ] David Jencks closed GERONIMO-469: - Resolution: Fixed Fix Version: 1.0-M3 fixed Should allow lookup of java:/comp as well as java:comp

Re: How forgiving should we be about jndi component context names?

I would just say print the warning once and remember you have already printed it. -dain -- Dain Sundstrom Chief Architect Gluecode Software 310.536.8355, ext. 26 On Nov 10, 2004, at 12:33 PM, David Jencks wrote: We can't detect this until runtime when the name is looked up. i think printing a

Re: Logging problems

On Nov 10, 2004, at 10:34 AM, Bruce Snyder wrote: Any reason why the Log4J configs are using a properties file rather than XML? We do use the ${property} replacement stuff in properties version, so the log file location is relative to geronimo home, but if the xml version supports that we could

[jira] Assigned: (GERONIMO-422) SimpleSecurityRealm.options and ConfigurationEntryRealmLocal.options seem redundant

[ http://nagoya.apache.org/jira/browse/GERONIMO-422?page=history ] Aaron Mulder reassigned GERONIMO-422: - Assign To: Aaron Mulder SimpleSecurityRealm.options and ConfigurationEntryRealmLocal.options seem redundant

[jira] Closed: (GERONIMO-466) Expose additional attributes on the current web container GBean implementation

[ http://nagoya.apache.org/jira/browse/GERONIMO-466?page=history ] Jeremy Boynes closed GERONIMO-466: -- Resolution: Won't Fix I don't think we need this. The listeners are all deployed as GBeans and should be managed through their management

Hold SVN Commits Please

I'm testing the current SVN before tagging as M3... please don't check anything in for a bit... Will send another note when tag is complete. Thanks, Aaron

Re: FYI - Created JIRA Infrastructure issue INFRA-117

If someone has time at ApacheCon (I am unable to attend), could they please discuss the mailing list archive search problem with an infrastructure person? This problem makes it difficult for new developers to Geronimo as they can't search for topics in the mailing list archives. In September