Package com.levigo.jadice.web.client.messaging.data

Class GenericSource

java.lang.Object

com.levigo.jadice.web.shared.model.Source

com.levigo.jadice.web.client.messaging.data.GenericSource

All Implemented Interfaces:

Serializable

public class GenericSource
extends Source

A generic PageSegmentHandle/Source that only lives on the client, specially made for the TypeScript Viewer. In the TS-Viewer you can use pretty much every JSON-structure as a Source. In the GWT-part, we will struggle with untyped Objects. We therefore use these generic classes to transport customer-specific data in a generic params-field as the GWT-Jadice-renderer is only interested in the fields of a handle that come from the abstract class PageSegmentHandle (pageIndex, documentLayer,...). On the Backend-side there is no such thing as a generic Handle/Source. The type tells the Backend to which custom Handle/Source this will be deserialized (the params will be deserialized do a specific Handle/Source-class). This seems to be a proper solution to handle untyped JS together with typed GWT.

See Also:

• Serialized Form

Constructor Summary

Constructors

Constructor	Description
GenericSource()

Method Summary

Modifier and Type	Method	Description
SerializableJavaScriptObject	getParams()
void	setParams(SerializableJavaScriptObject params)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

GenericSource

public GenericSource()

Method Details

getParams

public SerializableJavaScriptObject getParams()

setParams

public void setParams(SerializableJavaScriptObject params)