| Saving Form State to XML and Templates [message #831234] |
Wed, 28 March 2012 12:49  |
 Judith Gull
Messages: 44
Registered: February 2010 |
Member |
|
|
Errors cased by the bugzilla 367850 caused some confusion recently. I'm sorry for the inconvenience. This is an attempt to summarize the topic once again. Please post any further comments regarding this topic in this thread or in the bugzilla ticket directly.
It is possible to store the form state to XML and loading it again. (see doExportXml,doImportXml,getXML, setXML on org.eclipse.scout.rt.client.ui.form.IForm). In the XML the current values of all fields of the form are stored.
This functionality is for example used to create bookmarks by org.eclipse.scout.rt.client.services.common.bookmark.internal.BookmarkUtility.
Previously the fields were identified by the simple class name. It is not allowed to use multiple fields with the same simple name in a form directly. The Scout SDK prevents this and form data creation fails.
However, it is possible to end up with duplicate simple class names when using templates. Consider the following example:
AbstractDateBox.java:
public class AbstractDateBox extends AbstractGroupBox {
public class FromField extends AbstractDateField {}
public class ToField extends AbstractDateField {}
}
ExampleSearchForm.java:
public class ExampleSearchForm extends AbstractSearchForm {
public class MainBox extends AbstractGroupBox {
public class BillingDateBox extends AbstractDateBox {}
public class PaymentDateBox extends AbstractDateBox{}
}
}
FormData import/export still works, because in this case a hierarchical structure using org.eclipse.scout.commons.ClassIdentifier and breadthfirst search is used.
In the XML import/export the fields BillingDateBox.FromField und PaymentDateBox.FromField could not be distinguished. This problem was addressed in ticket 367850.
|
|
|
|
Powered by
FUDForum. Page generated in 0.12579 seconds
] 
Search
Help
Register
Login
Home
