Hi Dan,
My question basically is when the server start up, how can we let the
URIMappingInterceptor know which value user provided for
FIXED_PARAMETER_ORDER if we don't provide a configuration?
This value is a user configuration, if FIXED_PARAMETER_ORDER set to
true, means user want have fixed parameter order, in this case the
parameter name is just a placeholder, we will not check the parameter
name, and the parameter values are given in order.
If user doesn't set the value or set to false(DEFAULT value), that means
that the order of parameters given can be random, and we will check the
parameter names, the name is the value of the name attribute in WebParam
defined in JSR181.
So, by default, the following two uris are same:
http://localhost/SoapContext/SoapPort/greetUs?you=Dan&me=James
http://localhost/SoapContext/SoapPort/greetUs?me=James&you=Dan
or
http://localhost/SoapContext/SoapPort/greetUs/me/James/you/Dan
http://localhost/SoapContext/SoapPort/greetUs/you/Dan/me/James
So, what i mean is that we provide a configuration for user to decide
which server mode they want to use.
I can remove the configuration if user feel that this configuration is
unnecessary, the server should always work on the random parameter
order, and should always check the parameter name.
According to this, i have not figure out where to place this
configuration instead of the JettyHTTPDestination, maybe you already
have a good idea.
I guess we can talk this tomorrow morning, right?
Cheers,
James.
Dan Diephouse 写道:
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
