At the beginning I worried the incompatibility issue since developers won't declare transient. It will cause failure when trying to serialize it. After the second thought, it won't work actually without seializable -- it just doesn't dump error messages (but skip it).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ready since 6/10
---
If you want a composer to be serializable, declare java.io.Serializable and transient for all variables to be wired. For example,
public class Composer5 extends GenericForwardComposer implements java.io.Serializable {
private transient Textbox firstName;
private transient Textbox lastName;
private transient Label fullName;
/** onChange event from firstName component
*/
public void onChange$firstName(Event event) {
fullName.setValue(firstName.getValue()+" "+lastName.getValue());
}
/** onChange event from lastName component
*/
public void onChange$lastName(Event event) {
fullName.setValue(firstName.getValue()+" "+lastName.getValue());
}
}
Tom,
Why not serialize an composer by default?
Looks like, if I want my application to be clustered in ZK it should be made alterations over it.
Agree, I made it as default.
At the beginning I worried the incompatibility issue since developers won't declare transient. It will cause failure when trying to serialize it. After the second thought, it won't work actually without seializable -- it just doesn't dump error messages (but skip it).