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 issue is
to support transformation of multiple versions of the various descriptors into metadata
used by the current deployer. 

Converting the XSLSubDeployer into a filter for the different transformations that 
need to
be supported is also something that make more sense than leaving this as a deployer. We
also need the ability for multiple deployers to operation on a given deployment if we
do not already.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

----- 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 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 <dd-name>=KEY.
> 
> I've also added the new DeploymentInfoURIResolverFactory which can 
> resolve uris to documents in the current deployment info or documents 
> in other DeploymentInfo mbeans.  URIs are of the form 
> jboss-di://<deployment-info-name>#<key>#<xpath expression>.  The 
> deployment-info-name and xpath-expression are optional.  The 
> DeploymentInfoDocumentURIResolver is now obsolete.  I've discovered 
> that use of two # characters in a URI is ungrammatical so the first 
> will be changed to ! shortly.
> 
> I've simplified the ejb container mbeans to remove common code to the 
> Container class and allow deployment of MDBs with arbitrary interfaces 
> per the ejb 2.1 spec.  However, only jms MessageListener MDBs can be 
> deployed at the moment.  Deployment proceeds by constructing and 
> deploying an ActivationSpec xmbean instance from the ejb 2.0 mdb dd.
> 
> Finally, I've modified message delivery to always use the jmsra jca 1.5 
> adapter and correspondingly removed the asf classes.
> 
> thanks
> david jencks
> 
> /**********************************
> * David Jencks
> * Partner
> * Core Developers Network
> * http://www.coredevelopers.net
> **********************************/



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to