[jboss-jira] [JBoss JIRA] Assigned: (JBSEAM-280) Integrate the page context with Seam Remoting

[Shane Bryzak (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-280?page=all ]

Shane Bryzak reassigned JBSEAM-280:
-----------------------------------

    Assignee: Shane Bryzak

> Integrate the page context with Seam Remoting
> ---------------------------------------------
>
>                 Key: JBSEAM-280
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-280
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Remoting
>            Reporter: Shane Bryzak
>         Assigned To: Shane Bryzak
>             Fix For: 1.1
>
>   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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira