On 11/07/2004 5:24 AM, David Jencks wrote:
Since it is unlikely that anyone will be running more than one
TransactionManager/XATerminator in a geronimo server, perhaps this
should be made a little clearer by specifying the WorkManager
directly in the ResourceAdapter config and constructing a
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-263
Here is an overview of the issue:
-
Message:
The following issue has been re-assigned.
Assignee: David Jencks (mailto:[EMAIL PROTECTED])
-
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-169
Here is an overview of the issue:
Message:
The following issue has been closed.
Resolver: David Jencks
Date: Sat, 10 Jul 2004 9:42 PM
EJB 1.1. and 2.0 dtd based dds are now transformed into schema based 2.1 dds
during deployment. See SchemaConversionUtils in the specs/schema module
Message:
The following issue has been re-assigned.
Assignee: David Jencks (mailto:[EMAIL PROTECTED])
-
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-170
Here is an overview of the issue:
Thank you for getting Doug Lea's feedback on this. At the moment, we
are constructing all Executors in two places, soon to be collapsed to
one, so I don't think adding an Executors class will gain us
anything. It certainly looks like the 1.5 concurrent package will make
life much easier when
Message:
The following issue has been closed.
Resolver: David Jencks
Date: Sun, 11 Jul 2004 1:59 PM
Should be fixed although I don't have a test.
-
View the issue:
Message:
The following issue has been closed.
Resolver: David Jencks
Date: Sun, 11 Jul 2004 3:03 PM
I applied the if for outboundResourceAdapter. I don't think the if for
adminObject is necessary. If I'm wrong please reopen or let me know.
The geronimo configuration for
On Saturday, July 10, 2004, at 06:57 PM, Gianny Damour wrote:
On 11/07/2004 5:24 AM, David Jencks wrote:
Since it is unlikely that anyone will be running more than one
TransactionManager/XATerminator in a geronimo server, perhaps this
should be made a little clearer by specifying the
I keep forgetting to send an email on this.
Based on conventions laid out in JSR 77 all attributes should start
with a lower case letter. We had originally started with attributes
having an upper-case first character to match the JMX standard MBean
conventions, but since JSR 77 is required and
10 matches
Mail list logo
