[jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Container Proxy serialization issue

[adrian@jboss.org]

"kabir.khan at jboss.com" wrote : I have largely implemented this locally. Adrian's test still fails since the MetaDataRetrievalToMetaDataBridge is not serializable

That could never be properly serializable. e.g. the bridge
could link to a MetaDataRetrieval that loads data from a database
or it may link to scopes that depend upon the server or cluster you are running in.

What I don't understand is why the objects in the test have a proxy anyway?

Your point creates another issue.
The mechanism of "serialization" should depend upon the use case.

1) The proxy is for server side aspects and should be removed
when given to the client, i.e. we serialize it as the plain class.
Although this use case doesn't make much sense.
2) The proxy is intended for client side use and should contain a MetaData
object that is serializable and contains the client side metadata
(or knows how to link to it on deserialization).
3) The proxy should be replaced with a client side stub that does remote
requests on the server side object.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126659#4126659

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126659