[
https://jira.jboss.org/browse/SEAMREMOTING-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Bryzak moved JBSEAM-151 to SEAMREMOTING-11:
-------------------------------------------------
Project: Seam Remoting (was: Seam)
Key: SEAMREMOTING-11 (was: JBSEAM-151)
Affects Version/s: (was: 1.0 beta 2)
Component/s: (was: Remoting)
> Create debug page for remoting framework
> ----------------------------------------
>
> Key: SEAMREMOTING-11
> URL: https://jira.jboss.org/browse/SEAMREMOTING-11
> Project: Seam Remoting
> Issue Type: Task
> Reporter: Shane Bryzak
> Assignee: Shane Bryzak
> Priority: Minor
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The remoting framework should provide a debug page that allows a user to
> conveniently make remoting calls to test their components. It should be
> accessible via a url such as /<app>/seam/remoting/debug/<componentName>. The
> page should list all of the remotable methods of the component, and provide
> an easy way of invoking each method and viewing its result. It should also
> allow additional context parameters (such as conversation ID) to be set for
> an invocation. For methods that accept complex types, collections or maps as
> parameters there should be an easy way for the user to specify these values.
> The availability of the debug page should be controlled via a "debug"
> parameter in the remoting servlet configuration in web.xml, and be turned off
> by default. This would allow the application to be deployed in a production
> environment without the debug pages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
