You can use deferred binding on a factory class, so only the factory will need default constructors, and its methods can use whatever constructors, and take whatever parameters, you want.
On Oct 6, 2:43 am, Madhu <[EMAIL PROTECTED]> wrote: > Hi, I have a scenario where I have many screens (each is a panel) > with many UI Components, gwt-ext ones expecially. Depending on a > certain URL parameter, I will have to initialize one of these screens. > I wanted to implement deferred binding but am running into > multiple "type <Class> was not serializable and has no concrete > serializable subtypes" issues > I have a class DetailPanel which is abstract and initializes > certain framework UI components. All my screens are inheriting and > implementing various UI gwt-ext components (grids, combos etc.) Of > course, many of these components are "Not Serializable" and may not > have implemented a "Default Constructor". I am assured that all > classes I am writing implement Serializabe and provide a default > constructor. I am not sure of the 3rd party ones. > Will I still be able to implement deferred binding in this case. > I have all the other configurations correct viz. <define-property, > <extend-property, <replace-with, <when-type-is, <when-property-is etc. > > Thanks, > Sampath. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
