How about making this step in MainDeployer/SubDeployer mutually recursive?
so SubDeployer calls MainDeployer to unpdack/deploy sub packages if it
wants, or if it is war deployer, doesn't call. I haven't looked, but it
might work.
david jencks
On 2002.04.11 12:49:53 -0400 Vesco Claudio wrote:
> Hi!
>
> Also I haven't looked yet the patch, but I have a proposal to the
> deployment
> system... I think we have problems with blind deploy of
> jar/ear/sar/war/...
> This problem is already met with war which are not unpacked because there
> is
> need a particular deployment by the web container.
>
> I think that we can add to org.jboss.deployment.SubDeployer interface a
> metod, canSubdeploy for example, which is invoked by MainDeployer before
> invoking unpackSubPackages. This metod return true if the sub-deployer
> delegate to MainDeployer to deploy the subpackages, with this we can
> remove
> the test di.shortName.endsWith(".war") at begin of unpackSubPackages.
>
> I think that when we deploy a ear, we need to control which modules
> deploy.
> For example, I can have this ear:
>
> /
> jboss-ejb.jar
> weblogic-ejb.jar
>
> I know that I can remove (in every mode :-) ) the weblogic part, but I
> can
> configure the ear with
>
> <application>
> <module><ejb>jboss-ejb.jar<ejb></module>
> </application>
>
> and I have only the jboss ejbs deployed.
>
> I return in an old mailing list thread, if I remember well, but I think
> that
> a jboss-application.xml is a better solution to the current sort system
> to
> resolve the dependencies between sar-war-ejb.
>
> In this mode we can configure a jboss-application.xml with
>
> <jboss-application>
> <module><sar>jboss-service1.sar</sar></module>
> <module><ejb>jboss-ejb.jar</ejb></module>
> <module><sar>jboss-service2.sar</sar></module>
> ...
> </jboss-application>
>
> My bad English have hit another time?
>
> Claudio
>
> > -----Original Message-----
> > From: David Jencks [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, April 11, 2002 2:38 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-dev] Exploded archive deployment
> >
> > OK. I haven't looked yet but am a little worried about a couple of
> > things,
> > although maybe I misinterpreted your comments-
> >
> > 1. indefinitely nested deployments are useful and used. I don't see any
> > reason to restrict the depth. The spec requires jar in rar in ear.
> >
> > 2. As I recall deploymentInfo had the info on what to watch. Is this
> > otherwise inaccessible to the deployment scanner?
> >
> > Anyway, thanks for the work. I will look it over and add at least the
> > parts I like;-). I'm glad to have someone testing and expanding some
> of
> > this stuff.
> >
> > david jencks
> >
> > On 2002.04.11 02:05:44 -0400 Larry Sanderson wrote:
> > > I just submitted a bunch of patches to allow archives
> (sar,rar,jar,war
> > > and ear) to be deployed in their exploded form. Could someone with
> CVS
> > > write permissions look them over?
> > >
> > >
> > http://sourceforge.net/tracker/index.php?func=detail&aid=542341&group_id=2
> > 2866&atid=376687
> > >
> > > Thanks
> > >
> > > _________________________________________________________
> > > View thread online:
> > http://main.jboss.org/thread.jsp?forum=66&thread=12665
> > >
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > >
> > >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
