Thanks Supun for the info. BTW, I got to know that this kind of a configuration is practical. And we can skip hidden services from message-relay by engaging the relay module and setting the <includeHiddenService> param (Admin service are by default skipped by the relay module).
Charitha, I was able to get the ESB working properly with above mentioned solution. So, how shall I proceed with this issue? Regards, AmilaM. On Tue, Jul 24, 2012 at 8:20 PM, Supun Kamburugamuva <[email protected]>wrote: > On Tue, Jul 24, 2012 at 10:17 AM, Amila Maha Arachchi <[email protected]> > wrote: > > Hi, > > > > This is regarding the issue https://wso2.org/jira/browse/CARBON-13674 . > > > > When message-relay builder is configured in ESB, all the service > invocations > > are going through this builder. Special thing to note is all the > > content-types are set to go through relay builder. > > > > <messageBuilder contentType="application/xml" > > > class="org.wso2.carbon.relay.BinaryRelayBuilder"/> > > <messageBuilder contentType="application/x-www-form-urlencoded" > > > class="org.wso2.carbon.relay.BinaryRelayBuilder"/> > > <messageBuilder contentType="multipart/form-data" > > > class="org.wso2.carbon.relay.BinaryRelayBuilder"/> > > <messageBuilder contentType="multipart/related" > > class="org.wso2.carbon.relay.BinaryRelayBuilder"/> > > <messageBuilder contentType="application/soap+xml" > > class="org.wso2.carbon.relay.BinaryRelayBuilder"/> > > <messageBuilder contentType="text/plain" > > class="org.wso2.carbon.relay.BinaryRelayBuilder"/> > > <messageBuilder contentType="text/xml" > > class="org.wso2.carbon.relay.BinaryRelayBuilder"/> > > > > This gives all sorts of exceptions (due to namespace mismatches. You can > see > > them in the jira). To get rid of this, we have to engage the "relay > module". > > It by default filters out admin service calls. If we want to filter out > > non-admin but hidden services, we need to edit its policy to > > includeHiddenServices=true. > > > > Question1) Is the above configuration a valid scenario (setting all the > > content types to go through the relay builder). My understanding is, it > is > > not. > > Question2) If so, how can we fix this? > > This can be fixed if we can configure MessageBuilders per Endpoint > (i.e. URL). As I remember the basics required for this has being > implemented in the Transport core and this functionality is already > available for Nhttp transport. > > Thanks, > Supun.. > > > > > Regards, > > AmilaM. > > > > -- > > Amila Maharachchi > > Technical Lead > > Member, Management Committee - Cloud & Platform TG > > WSO2, Inc.; http://wso2.com > > > > Blog: http://maharachchi.blogspot.com > > Mobile: +94719371446 > > > > > > > > _______________________________________________ > > Dev mailing list > > [email protected] > > http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > > -- > Supun Kamburugamuva > Member, Apache Software Foundation; http://www.apache.org > E-mail: [email protected]; Mobile: +94 77 431 3585 > Blog: http://supunk.blogspot.com > -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud & Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
