November 2006 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: @JMX aspect and aop/mc integration

by scott.stark＠jboss.org

"kabir.khan(a)jboss.com" wrote : | I think from your answer that you are saying that we want the aop integration to be deployd as part of the server bootstrap? Meaning that the aspect deployer and the @JMX stuff is available by the time we get to scanning the deploy folder. In which case moving all the required bits into jboss/lib should be fine? Yes, moving this to the bootstrap lib should be fine. It does bring up the issue of javassist users now being coupled to that version, so we will run into the issue of javassit being an implementation detail of the mc, or part of its public api that other deployments should interact with. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984088#3984088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984088

19 years, 5 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: Problems with WAR within EAR

by scott.stark＠jboss.org

Jason created http://jira.jboss.com/jira/browse/JBAS-3837 for Remy to look at this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984085#3984085 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984085

19 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Personalization Options in 2.4?

by thomas.heute＠jboss.com

Wrong forum, I answered you in the user forum already View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984083#3984083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984083

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: @JMX aspect and aop/mc integration

by kabir.khan＠jboss.com

"kabir.khan(a)jboss.com" wrote : Meaning that the aspect deployer and the @JMX stuff is available by the time we get to scanning the deploy folder. Should be "kabir.khan(a)jboss.com" wrote : Meaning that the aspect deployer and the @JMX stuff is available by the time we get to scanning the deployers folder. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984082#3984082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984082

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: @JMX aspect and aop/mc integration

by kabir.khan＠jboss.com

The AspectDeployer is currently deployed under deployers/jboss-aop-jboss5.deployer/META-INF/ and its deployment order relative to the other deployers seems to be arbitrary. I think from your answer that you are saying that we want the aop integration to be deployd as part of the server bootstrap? Meaning that the aspect deployer and the @JMX stuff is available by the time we get to scanning the deploy folder. In which case moving all the required bits into jboss/lib should be fine? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984081#3984081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984081

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Web: ENC References

by scott.stark＠jboss.org

It comes down to not being able to have tomcat use existing pojos. Injection is trivial when you can configure a kernel bean. Injecting stuff into objects created via other means is not. For now we should just make the kernel available from the TomcatDeployer and propagate it to the web components or lookup the WarDeployer bean and access the kernel property. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984079#3984079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984079

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: @JMX aspect and aop/mc integration

by scott.stark＠jboss.org

I believe the aop abstraction needs to be a core part of the bootstrap kernel configuration. I'm not following how the AspectDeployer fits into your question. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984076#3984076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984076

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: VirtualFile metadata

by scott.stark＠jboss.org

I guess I would first ask why we can't leave this in the deployer attachments realm: | VirtualFile vf = ... | ClassFile cf = ... | unit.addAttachment(vf.getPathName(), cf, cf.getClass()); | so that we don't have to be looking in multiple places for the deployment metadata. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984072#3984072 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984072

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: How should deployers obtain a propper CL?

by scott.stark＠jboss.org

The class loader should already be defined for all deployers other than class loading deployers and access via the DeploymentUnit.getClassLoader/DeploymentContext.getClassLoader. A class loading deployer should have already run and built the class loader from the classpath(or overriding metadata). The point of removing the class loader construction out of base functionality of each deployer was to allow for more control over the class loading implementation and integration with deployment lifecycle issues. However, most deployers are still creating child class loaders of the DeploymentUnit/DeploymentContext class loader, or creating the own class loader just using the DeploymentUnit/DeploymentContext classpath. Extracting this aspect is still a work in progress. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984064#3984064 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984064

19 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: What is the Attachment in the deployers projects represe

by scott.stark＠jboss.org

Attachments are metadata associated with a deployment unit. See the http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer for an example. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984059#3984059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984059

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2006