Does it need to be set at all by default? That is, can you have the
URIMappingInterceptor act how you want it to by default when there is a
null value? And then just allow overriding by setting the value on the
message?
- Dan
James Mao wrote:
Hi Dan,
Thanks for pointing this.
I agreed with you that we need to find a place to configure this value
gracefully.
Do you have any suggestions?
Thanks,
James.
[EMAIL PROTECTED] wrote:
HTTP GET Update
* added fixedparameterorder configuration, and set the default value
to false, this means that the given parameters in the request uri
can be random, but the name of value must be given correctly
according to the style/use of the service.
In the JAX-WS case, the name is the value of the name attribute in
WebParam defined in JSR181.
Hi James,
Just looking at this - I'm not sure that FIXED_PARAMETER_ORDER should
be part of the message or the JettyHTTPDestination. If we need this
parameter, it should probably go on the URIMappingInterceptor as that
is the only place really reading it. Second, with the code in
JettyHTTPDestination it will only work with just the Jetty HTTP
transport, not the servlet or possibly the future asyncweb transport.
It would seem to me that it would be better if there was no
fixed_parameter_order value set, you assumed whatever you want the
default to be - instead of trying to explicitly set the default.
Regards,
- Dan
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
