]
Shane Bryzak resolved JBSEAM-280.
---------------------------------
Resolution: Out of Date
Integrate the page context with Seam Remoting
---------------------------------------------
Key: JBSEAM-280
URL:
https://jira.jboss.org/browse/JBSEAM-280
Project: Seam
Issue Type: Feature Request
Components: Remoting
Reporter: Shane Bryzak
Assignee: Shane Bryzak
Fix For: The future
Original Estimate: 2 days
Remaining Estimate: 2 days
Support the propogation of Seam's Page Context between remoting requests.
Functional Requirements:
* The page context should be stored client-side in the global js variable
Seam.pageContext.
* The page context should be included in any Seam Remoting requests in the packet header,
i.e.:
<page-context><variable name="foo"><ref
id="0"/></variable>...</page-context>
* The page context should be returned by all remoting requests and replace the local
copy
* The client web page should be able to manipulate the page context, changing values,
adding new values, etc via Seam.pageContext, e.g. Seam.pageContext.foo = bar;
Non functional requirements:
* Add a server-side convenience method to convert an object to serialized XML
* Add a client-side convenience method to deserialize XML into an object
* Create a <pageContext/> JSF tag that will embed a <script> block into the
web page that initializes the page context when the page is first loaded
* Modify the client-side remoting framework to support the dynamic discovery of object
types. Use the __type field (or something similar) to identify the object type. This
will mean that type stubs will not need to be explicitly imported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: