-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David
Jencks
Sent: Monday, June 16, 2003 12:32 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
I've modified the deployment system to allow
On Monday, June 16, 2003, at 10:57 PM, Bill Burke wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
David
Jencks
Sent: Monday, June 16, 2003 12:32 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
On Tuesday, June 17, 2003, at 12:58 AM, Bill Burke wrote:
Not sure I like this idea. Tell me why we need to support 3.2 and 3.0
descriptors in 4.0? I'd much rather a 3.2 component crap out
gracefully in
4.0 than have to maintain 3 separate configuration mechanisms.
I wish we could get rid of
On Tuesday, June 17, 2003, at 12:36 AM, Bill Burke wrote:
Why? Because everybody is very familiar with them. Why? because its
simple
and easy to maintain and modify. Yes, the XML parsing needs to be
moved to
a separate module, but the classes themselves have held up fine. I
will not
allow
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dain
Sundstrom
Sent: Tuesday, June 17, 2003 2:35 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
On Tuesday, June 17, 2003, at 12:36 AM
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dain
Sundstrom
Sent: Tuesday, June 17, 2003 2:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
On Tuesday, June 17, 2003, at 12:58 AM, Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David
Jencks
Sent: Tuesday, June 17, 2003 2:16 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
On Monday, June 16, 2003, at 10:57 PM, Bill
-dev] XSLSubDeployer improvements and jca 1.5 mdb deployment
Not sure I like this idea. Tell me why we need to support 3.2 and 3.0
descriptors in 4.0? I'd much rather a 3.2 component crap out gracefully in
4.0 than have to maintain 3 separate configuration mechanisms.
I do like the idea
An mbean is still an object metamodel. Exposing this as an mbean is a seperate issue.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
I'm not convinced we are, I am unconvinced anything more than mbeans is
necessary. Configuring
- Original Message -
From: Bill Burke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 1:09 AM
Subject: RE: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb deployment
I would rather have a separate migration tool than to actually
We should be looking at jaxb driven by schemas for the metadata parsing before
considering the commons digester framework. I'm looking at jaxb for inclusion
in the 3.2 branch to address some stability issues.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Of David Jencks
Sent: 16 June 2003 05:32
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] XSLSubDeployer improvements and jca 1.5
mdb deployment
I've modified the deployment system to allow for multiple xml
deployment descriptors. XSLSubDeployer can be configured via the
Properties valued
PROTECTED]
Subject: [JBoss-dev] XSLSubDeployer improvements and jca 1.5
mdb deployment
I've modified the deployment system to allow for multiple xml
deployment descriptors. XSLSubDeployer can be configured via the
Properties valued DdNameToKeyMap property to import the specified dds
and store them
.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 15, 2003 9:32 PM
Subject: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb deployment
I've modified
Subject: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
I've modified the deployment system to allow for multiple xml
deployment descriptors. XSLSubDeployer can be configured via the
Properties valued DdNameToKeyMap property to import the specified dds
and store them
-dev] XSLSubDeployer improvements and jca 1.5 mdb deployment
On Monday, June 16, 2003, at 01:53 PM, Scott M Stark wrote:
This is not consistent with the move to extract the metadata parsing
from the current
deployers into filters or interceptors associated with the deployers.
The key
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David
Jencks
Sent: Monday, June 16, 2003 8:49 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
On Monday, June 16, 2003, at 01:53 PM, Scott M
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Scott
M Stark
Sent: Monday, June 16, 2003 11:35 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] XSLSubDeployer improvements and jca 1.5 mdb
deployment
The XSLSubdeployer is acting
I've modified the deployment system to allow for multiple xml
deployment descriptors. XSLSubDeployer can be configured via the
Properties valued DdNameToKeyMap property to import the specified dds
and store them in the DeploymentInfo under the specified key. The
properties lines look like
19 matches
Mail list logo
