Jochen,
Why is not contentLengthOptional handled in XmlRpcServlet.init(ServletConfig
pConfig) just like enabledForExtensions? It this really by design?
I think that init should handle contentLengthOptional (and possibly other
params) and this way one would not have to subclass XmlRpcServlet just like
one does not have to subclass to enable extensions.
However, I still need to subclass the XmlRpcServlet anyhow because I need to
set AuthenticationHandler and RequestProcessorFactoryFactory. It would be
useful if one could set AuthenticationHandler and
RequestProcessorFactoryFactory on the XmlRpcServlet for it to use in
newXmlRpcHandlerMapping (or newPropertyHandlerMapping). It then invokes
AbstractReflectiveHandlerMapping.setAuthenticationHandler()
and/or
AbstractReflectiveHandlerMapping.setRequestProcessorFactoryFactory
if the respective instance variable is set.
My first idea was simply to override XmlRpcServlet myself, but I believe
that this could be useful to others as well.
Regards,
Jimisola
Jochen Wiedmann wrote:
>
> Jimisola Laursen wrote:
>
>> and as I you can see I've enabled extensions. Does this mean that the
>> XmlRpcServlet will use "optional content length" out-of-the-box if the
>> XmlRpcServer and client supports HTTP 1.1?
>
> I believe, that "contentLengthOptional" is another property, which you
> need to enable in your servlet. Typically this should be done in the
> servlets "init" method. In other words, you possibly need a subclass.
>
>
> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/How-to-setup-and-configure-a-Servlet-solution-programmatically-tf2300489.html#a6405617
Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
