[Stratos-dev] Registry responds with incorrect content types
Supun Kamburugamuva
supun at wso2.com
Sun Nov 14 03:59:33 PST 2010
On Sun, Nov 14, 2010 at 4:47 PM, Sanjiva Weerawarana <sanjiva at wso2.com>wrote:
> On Sun, Nov 14, 2010 at 4:39 PM, Sumedha Rubasinghe <sumedha at wso2.com>wrote:
>>
>> To run in the case of no builder for a given content type?
>>
>
> Yes.
>
>
>> Is so, I do not see how Sameera's original problem is solved by that.
>>
>
> Basic problem was that if a message comes with an unknown content type then
> Axis2 defaults to building it with the SOAP builder. That fails of course.
>
> What the load balancer scenario needs is the binary builder/fomatter to be
> the default for all media types. In that case we'd not have known that there
> was a weird media type involved because of the load balancer .. we'd have
> known when we saw a broken image icon in the browser!
>
> For the ESB to be a generic load balancer (when we build the WSO2 Load
> Balancer product) we need to have it work on any media type ..
>
>
Sorry to bring this up late. But from the code it seems axis2 already
supports this concept.
If we specify a message formatter as
<builder content-type=".*" class="org.wso2.carbon.relay.builder"/>
This should match to any incoming content type. Heven't tested it though.
Thanks,
Supun..
> Sanjiva.
> --
> 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
> 6880 | +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>
> _______________________________________________
> Stratos-dev mailing list
> Stratos-dev at wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>
>
--
Supun Kamburugamuva
Technical Lead
WSO2 Inc.; http://wso2.org
E-mail: supun at wso2.com; Mobile: +94 77 431 3585
Blog: http://supunk.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://wso2.org/pipermail/stratos-dev/attachments/20101114/ed571534/attachment.htm>
More information about the Stratos-dev
mailing list