On 8 September 2014 11:39, Vijayaratha Vijayasingam <[email protected]> wrote:
> > > On 8 September 2014 11:32, Uvindra Dias Jayasinha <[email protected]> > wrote: > >> Yes it does forward it, that is what I am trying to avoid in this case >> and invoke the service deployed in ELB instead. >> >> Is this the right behavior? where it forwards, if endpoint is wrong? > > The way the new ELB has been configured it is always working as a proxy to try and forward all requests to the downstream processes that it is fronting regardless whether the call is for a service deployed in ELB itself. On the other hand if the endpoint is wrong obviously the call will fail. > Had a chat with Azeez and he suggested to use a normal Axis2 service >> instead of a Synapse proxy to achieve this functionality. That way the >> built in service dispatch functionality of Axis2 can be utilized. >> >> +1 > > >> On 8 September 2014 11:24, Vijayaratha Vijayasingam <[email protected]> >> wrote: >> >>> >>> >>> On 8 September 2014 07:49, Uvindra Dias Jayasinha <[email protected]> >>> wrote: >>> >>>> Hi All, >>>> >>>> Im trying to invoke a a Synapse proxy service that will be running in >>>> an instance of ELB 2.1.1 via an Axis2 handler that will be also deployed in >>>> the ELB. >>>> >>>> >>>> If you directly send a request to the proxy deployed @ ELB, Does ELB >>> forwards that request to other nodes? >>> >>> >>> Out of the box ELB 2.1.1 is configured to forward all incoming requests >>>> to the downstream worker/manager nodes that it is fronting. But in my >>>> scenario when it comes to requests that are directed toward the particular >>>> proxy service deployed in ELB, I want to invoke this service via the Axis2 >>>> handler and prevent that call from being forwarded any further(to any other >>>> service or the worker/manager nodes). >>>> >>>> Based on what I have found it seems that the call to the proxy needs to >>>> be captured by the Dispatch phase of the In-Sequence. This is the exact >>>> functionality that I require since this will prevent that call from being >>>> processed any further. But enabling the same handlers that are available in >>>> ESB in the dispatch phase of the ELB doesn't have any effect. >>>> >>>> I am able to invoke my custom handler but I'm not sure how to call the >>>> Synapse proxy from within the handler and make Axis2 stop processing the >>>> request any further. Any ideas on how this can be achieved? Thanks. >>>> >>>> -- >>>> Regards, >>>> Uvindra >>>> >>>> Mobile: 777733962 >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> -Ratha >>> >> >> >> >> -- >> Regards, >> Uvindra >> >> Mobile: 777733962 >> > > > > -- > -Ratha > -- Regards, Uvindra Mobile: 777733962
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
