[Design of the JBoss EJB Container] - Re: NPE in HomeHandleImplIIOP
by adrian@jboss.org
You can't make the stubClass non-transient. That breaks serialization
compatibility with older versions.
In fact, it shouldn't work, there is a readObject method.
The stubClass is re-initialized in that method.
My guess is that the read/writeObject() methods are not getting invoked
because according to the spec they should be private instead of public.
They are private for the HandleImplIIOP.
This is probably a confusion between readObject and readExternal
in the original development?
ReadObject
anonymous wrote :
| For serializable objects, the readObject method allows a class to control the deserialization of its own fields. Here is its signature:
|
| private void readObject(ObjectInputStream stream)
| throws IOException, ClassNotFoundException;
|
ReadExternal
anonymous wrote :
| Objects implementing java.io.Externalizable must implement the readExternal method to restore the entire state of the object. It must coordinate with its superclasses to restore their state. All of the methods of ObjectInput are available to restore the object's primitive typed fields and object fields.
|
| public void readExternal(ObjectInput stream)
| throws IOException;
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090924#4090924
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090924
18 years, 2 months
[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme
by alesj
"scott.stark(a)jboss.org" wrote :
| We are missing the setup of the Fields proxy. The fields creation in AbstractManagedObjectFactory needs to be using the org.jboss.managed.plugins.advice.WrapperAdvice.wrapFields utility to allow an advice to update the metadata instance on the setValue call.
|
"scott.stark(a)jboss.org" wrote : Really, aop usage is not needed.
This means removing WrapperAdvice usage?
"scott.stark(a)jboss.org" wrote : Where we copy the client side value to the server side property, the Fields impl can handle the writethrough, and the runtime property dispatch be done in the ManagementViewImpl.
I saw we already have WritethroughManagedPropertyImpl, but I think it overrides the wrong method - instead of overridding setField it should override setValue.
Fixing this is exactly what we need + adding runtime dispatch into MVI. And like you said, with no AOP.
On the other hand, keeping the WrapperAdvice, does give you a lot of flexibility. I guess its intention should be clarified.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090892#4090892
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090892
18 years, 2 months