[jboss-dev] Deployment chains

[Ales Justin]

Adrian, how much work you have left with the deployers?
Just asking, since I'm about to do CR2 release tomorrow.

Should I wait - for some stuff you still wanna include in the CR2,
or I can go ahead?
I'll at least wait for the reply to this email. ;-)
(not that hard, since deployers are the last in MC release chain :-)

Adrian Brock wrote:
> On Mon, 2008-10-06 at 17:08 +0200, Adrian Brock wrote:
>> A sample output is attached (this is for the console-mgr.sar)
> 
> The sample out on the earlier post shows that
> org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer
> is putting the AspectManager attachment in the wrong "bucket".
> 
> Implementation details should go in the transient attachments.
> Which is the default if you use addAttachment().
> 
> The managed objects are intended to hold attachments that
> come from xml so we can differentiate what we create and
> what the user specified.
> 
> e.g. You'll also see that for the console-mgr.sar
> the ClassLoadingMetaData is also in the transient attachments.
> That is because it was created from the <loader-repository/>
> xml of the -service.xml.
> If it had come from META-INF/jboss-classloading.xml
> it would be in the managed objects.