[Design of POJO Server] - Re: Ordering of nested deployments
by scott.stark@jboss.org
You understanding is correct. The problem as I see it is that this is really more of a component lifecycle issue rather than a deployer issue. In our old deployment framework deployment and component lifecycle were tightly coupled. Now the deployers are just translating metadata into kernel beans, and the kernel lifecycle/dependency should be triggering things like commiting the PCs before the deployment components are fully started. The associated java.security.Policy object also needs to be refreshed after this.
The best way would be to hook in a JaccSetup pojo would be a bean apon which the "container" beans dependend. Maybe this is best done via injection of the bean representing the security domain. I think its just going to take a fair amount of refactoring to properly leverage the mc where approriate.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977395#3977395
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977395
19 years, 6 months
[Design of AOP on JBoss (Aspects/JBoss)] - JBoss AOP and Mobile Agents -- Will it work????
by zarafield
I am a newbie to AOP and have a little experience with mobile agents. I have Aglets working with AspectJ, but would like to be able to use dynamic AOP - I am not sure if it is going to be possible!!!!
Initially I am trying Voyager and the standalone version of AOP. As you are required to set the classloader to one that is jboss specific, this affects the running of Voyager. as per the warnings and errors below.
Also, if a migrating POJO moves to a new location with it's annotated aspect, would it need to have the aop classloader running on the new location in order for the annotated aspects to work?
Finally, when running an annotated aspect you need to specify the directory where the annotated class would be i.e.
java -Djava.system.class.loader=org.jboss.aop.standalone.SystemClassLoader -Djboss.aop.class.path=c:\jbossaop2\jboss-aop_1.5.1.GA\docs\aspect-framework\examples\annotated-aspects\ Driver
This is also causing a problem....
Any suggestions appreciated!!!
-------------------------------------------------------------------------------------
Voyager also has the following resourceloading api
http://www.ifi.unizh.ch/ddis/staff/vorburg/doc/api/Orbpro/com/objectspace...
-------------------------------------------------------------------------------------
[warn] Could not find class com.ms.security.PolicyEngine that com.objectspace.vo
yager.loader.MSVoyagerClassLoader references. It may not be in your classpath a
nd you may not be getting field and constructor weaving for this class.
javassist.NotFoundException: com.ms.security.SecurityClassLoader
at javassist.ClassPool.get(ClassPool.java:416)
at javassist.CtClassType.getSuperclass(CtClassType.java:602)
at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(Fi
eldAccessTransformer.java:80)
.......
[error] failed to transform: com.objectspace.voyager.loader.MSVoyagerClassLoader
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977387#3977387
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977387
19 years, 6 months
[Design of POJO Server] - Re: Ordering of nested deployments
by bill.burke@jboss.com
"scott.stark(a)jboss.org" wrote : Currently all deployments are added to a list in breadth first order. Previously I had a plugin that would return a directed graph of the contexts in a given top level deployment which allowed this to be configurable. This or some other metadata to control this for backward compatibility seems needed.
|
This ordering needs to be nailed down. Why? Please take a look at the server/ module under
org.jboss.deployment.JaccInitializationDeployer and JaccCommitDeployer.
Unless I am misunderstanding JACC, the parent PC cannot commit until all child PCs are linked. So, the implementation of these deployers is dependent on the ordering of deployment units. My implementation depends on Bredth-first, as initialisation creates and links the PC while commit just commits. I'll have to switch where the link happens based on whether it is depth/bredth.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977374#3977374
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977374
19 years, 6 months