I think I understand what you saying, but the one thing I am not seeing as
explicit are the Domain and VirtualHost mbeans. So when your talking
about the "mbean representing that deployment", I am thinking of this
structure:
<Domain>
<VirtualHost>
...
<Deployment>
<ejb/>
</Deployment>
</VirtualHost>
</Domain>
There has to be a default Domain and a default VirtualHost that correspond
to the current deployment context of a global domain and all server
interfaces
with default ports(be they anonymous or service specific defaults).
Its this notion that I'm looking for to move from the vague to a concrete
representation in the new deployment scheme.
----- Original Message -----
From: "David Jencks" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, November 30, 2001 10:11 PM
Subject: Re: [JBoss-dev] JBoss Deployer
> On 2001.12.01 00:24:43 -0500 Scott M Stark wrote:
> > A good side effect of this dependency should be that one can disable JSR
> > monitoring for a deployment if a dependency on the JSR mbeans is not
> > specified. The JSR77 stuff is by definition very J2EE specific
>
> OK, I didn't know that.
>
> and we
> > know
> > this is not what the base framework is about.
> >
> > With regard to virtual hosts, are you saying I need a JSR77 mbean config
> > to enable scoping? This should not be if you are.
>
> not any more;-)
>
> I would suggest having
> > a Domain mbean that contains one or more VirtualHost mbeans and the
> > J2EEServer model implementation would be associated with a VirtualHost
> > mbean.
>
> Hey, here's an even more half baked idea...
>
> I was playing around with combining deployment descriptors using xslt
> earlier this week (ejb-jar and jbosscmp) and its really pretty easy. We
> could process all the deployment descriptors into a service.xml file,
where
> each e.g. ejb-jar gets put into the config of an mbean representing that
> deployment -- in fact that bean would be the deployer for its contents.
> The config for the mbean could be generated automatically or specified
> explicitly if you wanted to specify scope, whether jsr77 is enabled, etc.
>
> Thanks
> david jencks
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
