Just start with a security domain name as an attribute of every component
and we can go from there.
----- Original Message -----
From: "David Jencks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 20, 2001 10:52 PM
Subject: Re: [JBoss-dev] Thoughts on deployers
> Thanks for the info. I agree with you about the confusion...
>
> Do you think if I get the stuff I outlined working we can add the security
> aspects after that?
>
> Thanks
> david jencks
>
>
> On 2001.09.21 01:25:58 -0400 Scott M Stark wrote:
> > I think part of the confusion on AutoDeployer vs UniversalDeployer is
> > that
> > the AutoDeployer is a limited UniversalDeployer today. It accepts ears,
> > jars, wars,
> > and rars and delgates to specific deployers, so let's isolate dependency
> > management
> > to the UniversalDeployer and leave simplify the role of the AutoDeployer
> > to
> > detecting
> > changes and notifying the UniversalDeployer.
> >
> > More below.
> >
> > > So what I'd like to do first is make the universal deployer and
> > unpacking
> > > service, and hook everything else up to it, removing the existing
> > unpacking
> > > services from RARDeployer and J2eeDeployer (which maybe we should call
> > > EARDeployer).
> > >
> > The EARDeployer needs to also be updated to know about the RARs that
> > were deployed as part of the EAR. In general we need to overhaul the
> > deployment
> > objects as they were originally only designed for unsecure ejbs. Now as
> > of
> > J2EE 1.3 life is a much more complicated mixture of jars, wars, rars +
> > security.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
