Hi Mike
Hi Sergey,
On 8 February 2010 17:25, Sergey Beryozkin <[email protected]> wrote:
Having not looked at the way the URI parameters are stored, does the
approach you've suggested come unstuck if the payload represents
non-String, potentially complex objects?
ParameterHandlers can handle complex (query) values, please check
http://cxf.apache.org/docs/jax-rs.html#JAX-RS-DealingwithParameters
Ah... won't this bring us back to the fact that the GWT payload is
difficult to parse into its separate parameters? To use a
ParameterHandler, wouldn't you have to split out the individual
parameters for separate parsing, something which would then require
the code to reach inside GWT's RPC parser and some quite nasty
hackery?
Yeah.. You said using a Map is a possibility, so I mentioned ParameterHandlers,
you can have :
@QueryParam("gwt") Map<String, String>
if needed with ParameterHandlers
cheers, Sergey
I suppose there's a fundamental mismatch between the JAXRS and GWT-RPC
protocol's treatment of request-body parameters. It's almost as if you
need a stream terminator for the GWT request which would be converted
up-front into an model that can be forwarded to JAXRS for processing.
Cheers
Mike
