[ https://issues.apache.org/jira/browse/CAY-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856880#action_12856880
]
Andrus Adamchik commented on CAY-1420:
--------------------------------------
> So we can use a generic HttpRemoteService to serve hessian requests.
Ok, maybe not... We still need a way to obtain current request, so using Hessian-specific
code is the easiest way to go about it:
HttpServletRequest request = (HttpServletRequest) ServiceContext.getContextRequest();
But will still be removing Hessian lifecycle methods.
> Migrate ROP server-side components to DI-based stack
> ----------------------------------------------------
>
> Key: CAY-1420
> URL: https://issues.apache.org/jira/browse/CAY-1420
> Project: Cayenne
> Issue Type: Task
> Components: Core Library
> Affects Versions: 3.0.1
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
> Fix For: 3.0.1
>
>
> Change the bootstrap procedure of the ROP server-side components to use CayenneServerRuntime,
maybe with an addition of a special ROP server module. We may actually implement this as a
new servlet, with parameters being the same as the ones used by CayenneFilter ("configuration-location",
"extra-modules"), and using servlet name as a default configuration name. HessianServlet should
be deprecated (see WebApplicationContextFilter for how it was done).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|