| Design Question about IServiceHandler [message #933700] |
Fri, 05 October 2012 08:56  |
Eclipse User |
|
|
|
I am currently implementing my first org.eclipse.rwt.service.IServiceHandler. I wonder why IServiceHandler#service() takes no HttpServlerRequest/Response arguments, instead one have to call the static RWT.getRequest() and RWT.getResponse(). To me it smells bad, who prevent me to call these static methods anywhere else in my code, and what is the effect? Its also hard to test the IServiceHandler implementation.
Wouldn't IServiceHandler#service(HttpServletRequest,HttpServletResponse) fit better here? Hopefully RAP 2.0 can fix this.
[Updated on: Fri, 05 October 2012 10:55] by Moderator Report message to a moderator |
|
|
| Re: Design Question about IServiceHandler [message #936624 is a reply to message #933700] |
Mon, 08 October 2012 06:51  |
| Eclipse User |
|
|
|
Hi Christian,
could you please open an enhancement request with your suggestion?
Thanks,
Ivan
On 10/5/2012 11:56 AM, Christian Schwarz wrote:
> I am currently implementing my first
> org.eclipse.rwt.service.IServiceHandler. I wonder why
> IServiceHandler#service() takes no HttpServlerRequest/Response
> arguments. Instead one have to call the static RWT.getRequest() and
> RWT.getResponse(). To me it smells bad, who prevent me to call these
> static methods anywhere else in my code, and what is the effect?
> Wouldn't
> IServiceHandler#service(HttpServletRequest,HttpServletResponse) fit
> better here? Hopefully RAP 2.0 can fix this.
--
Ivan Furnadjiev
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03376 seconds
] 
Search
Help
Register
Login
Home
