LocalTransportSender is defined in the axis2.xml we ship with Carbon. To use it, you need to set the target EPR to something like;
local://services/ServerAdmin and do the service invocation in the regular way. That's it! Azeez On Wed, Nov 18, 2009 at 6:16 AM, Milinda Pathirage <[email protected]> wrote: > +1. > > If we have BPEL feature installed in WSAS can we use this local transport > to call the WSAS services from BPEL processes. Do we have to do any changes > to enable that or Axis2 automatically figure out the transport when the > calling service which is deployed in same Axis2 engine? > > Thanks > Milinda > > On Wed, Nov 18, 2009 at 11:36 AM, Afkham Azeez <[email protected]> wrote: > >> Hi Folks, >> IMO, when the FE & BE reside on the same JVM, it is better yo use the >> local transport instead of the OSGi Web service impl object. This way, we do >> not have to make major code changes. Also, the security mechanisms built in >> for securing the BE services will also work. >> >> I have been working with the local transport a bit, and there seem to be >> no major issues with it. >> >> Thoughts welcome. >> >> -- >> -- >> Afkham Azeez >> [email protected] >> WSO2 Inc. http://wso2.com >> Blog: http://afkham.org >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Milinda Pathirage > Product Manager, Business Process Server - WSO2 Inc > Blog: http://blog.mpathirage.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- -- Afkham Azeez [email protected] WSO2 Inc. http://wso2.com Blog: http://afkham.org
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
