[Carbon-dev] R: R: R: R: R: R: WSO2 component to deploy a simple servlet?
ruwan at wso2.com
Fri Mar 19 04:06:17 PDT 2010
Supun Kamburugamuva wrote:
> In Case of GET and if there is no content type Synapse NHTTP transport
> handles it in a different way. In this case Nhttp transport doesn't
> call the builder and creates an empty SOAP envelope and set it to the
> message context. So this works with the Nhttp transport.
Hhhmmm... where is that logic Supun?? I am sorry I don't see such a
logic on the nhttp transport. at least on trunk. Nhttp transport
delegates the actual processing to the
Am I missing something?
> On Fri, Mar 19, 2010 at 2:54 PM, Sanjiva Weerawarana <sanjiva at wso2.com> wrote:
>> On Fri, Mar 19, 2010 at 2:43 PM, Supun Kamburugamuva <supun at wso2.com> wrote:
>>> Yes there is the problem with the default builder as well. Ideally we
>>> should be able to configure this in the axis2.xml's messageBuilders
>>> configuration. How about having a defaultBuilder configuration
>>> attribute for the message builders in the axis2.xml? We can put this
>>> to the messageFormatters as well.
>> +1 but that needs to go to dev at axis.
>>> Regarding the Roberto's problem, there was a real issue with the GET
>>> requests and message relay. We've fixed this in the 3.0.0 release.
>> Yes but it still won't work for him because his GET has no media type. So we
>> need a default builder option before it'll work right?
>> Sanjiva Weerawarana, Ph.D.
>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
>> email: sanjiva at wso2.com; phone: +1 408 754 7388 x51726; cell: +94 77 787
>> blog: http://sanjiva.weerawarana.org/
>> Lean . Enterprise . Middleware
>> Carbon-dev mailing list
>> Carbon-dev at wso2.org
> Carbon-dev mailing list
> Carbon-dev at wso2.org
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
phone: +1 408 754 7388 ext 51789
email: ruwan at wso2.com; cell: +94 77 341 3097
Lean . Enterprise . Middleware
More information about the Carbon-dev