containers, just like AWT does with desktop windows. Both frameworks share the same component-based architecture: in AWT we have a Windows instance which represents the physical windows containing GUI components switch off versioning for a given page, we can call its method setVersioned(false). 47 8.2.3. Pluggable serialization Starting from version 1.5 it is possible to choose which implementation of Java serialization for inter- component communication which brings to our components a desktop-like event-driven architecture. Then, we have introduced a new entity called initializer which can be used to configure resources

containers, just like AWT does with desktop windows. Both frameworks share the same component-based architecture: in AWT we have a Windows instance which represents the physical windows containing GUI components switch off versioning for a given page, we can call its method setVersioned(false). 46 8.2.3. Pluggable serialization Starting from version 1.5 it is possible to choose which implementation of Java serialization for inter- component communication which brings to our components a desktop-like event-driven architecture. Then, we have introduced a new entity called initializer which can be used to configure resources

containers, just like AWT does with desktop windows. Both frameworks share the same component-based architecture: in AWT we have a Windows instance which represents the physical windows containing GUI components switch off versioning for a given page, we can call its method setVersioned(false). 46 8.2.3. Pluggable serialization Starting from version 1.5 it is possible to choose which implementation of Java serialization for inter- component communication which brings to our components a desktop-like event-driven architecture. Then, we have introduced a new entity called initializer which can be used to configure resources

containers, just like AWT does with desktop windows. Both frameworks share the same component-based architecture: in AWT we have a Windows instance which represents the physical windows containing GUI components switch off versioning for a given page, we can call its method setVersioned(false). 45 8.2.3. Pluggable serialization Starting from version 1.5 it is possible to choose which implementation of Java serialization for inter- component communication which brings to our components a desktop-like event-driven architecture. Then, we have introduced a new entity called initializer which can be used to configure resources

containers, just like AWT does with desktop windows. Both frameworks share the same component-based architecture: in AWT we have a Windows instance which represents the physical windows containing GUI components