Re: [JBoss-dev] WL Deployer, II

[Scott M S. <Sco...@jb...>]

This is not going to work as many users already have stated they
create deployment units that contain all app server DDs and even
proprietary descriptors for their own use.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Andreas Schaefer" <an...@jb...>
To: <jbo...@li...>
Sent: Wednesday, May 15, 2002 3:13 PM
Subject: [JBoss-dev] WL Deployer, II


> Hi Geeks
>
> Based on an email of Dain I think the easiest
> way to start is to use the Deployer's accept()
> method and add additional test in the current
> deployers there that only JBoss "compliant"
> are deployed.
> Now the Foe-Deployer can check it if not
> "compliant" and then try to convert it to a
> JBoss "compliant" deployment which is then
> resent to the Main Deployer for another try.
>
> This wouldn't require a new Main Deployer
> or add any dependencies into the existing
> deployers.
>
> Any objects to add this tests to the existing
> deployers ?
> Most likely I will test for JAR if "jboss.xml"
> is available, in WAR that either "jboss-web.xml"
> is available or no other DD is there except
> "web.xml", for EARs I don't know.
>
> xxxxxxxxxxxxxxxxx
> Andreas Schaefer
> Senior Consultant
> JBoss Group, LLC
> xxxxxxxxxxxxxxxxx
>
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Jboss-development mailing list
> Jbo...@li...
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>