-
1. Re: Advised classes after serialization
kabirkhan Aug 12, 2005 10:59 AM (in response to timfox)I must confess I am a bit shaky on this point, but serialization of advised classes is not a "supported feature" ATM.
If you were to precompile the classes, making sure the versions in both JVMs are binary compatible, you could probably serialize the classes across. However, with the current weaving you need to access the AspectManager, which contains all the advice bindings etc. and this is configured and initialized local to the jvm, so you would need a jboss-aop.xml on the client.
I am working on reweaving of AOP for AOP 2.0, and have run into some issues there regarding serialization, but need to talk to Bill about that when he's back from holiday. -
2. Re: Advised classes after serialization
timfox Aug 13, 2005 4:45 AM (in response to timfox)Thanks Kab.
So it seems serialization of advised classes is probably not the right choice for us for now.
Another thought would be to load the aop config from the server at client startup and then use that to initialise the aop engine on the client. That would prevent us having to maintain a jboss-aop.xml on the client.
Is it possible to programmatically start aop explicitly with a supplied config., rather than one having to be available in the META-INF directory or on the file system?
Or perhaps this is a dumb idea?
wdyt? -
3. Re: Advised classes after serialization
kabirkhan Aug 14, 2005 7:00 AM (in response to timfox)Whether or not it will work in this case I can't guarantee, but we do support dynamically adding/removing aop.xml files at runtime. The entry point would be
org.jboss.aop.AspectXmlLoader.deployXml()
Let me know how you get on