Hi Mahesh, Following documentation[1] has the explanation for setting endpoint references through EPR files by modifying them in registry.
However as I understood in your case you are sending those endpoint references through the request and epr count may vary. AFAIK this is not possible since in-order to create the BPEL you need to archive the wsdl as a BPEL content to generate the relevant variables(request, response, role, partnerLink). So if you could identify all the endpoints that are going to be exist then, you can load all the relevant wsdls correspondent to those services and then set the endpoint references through registry resources. Whenever there is change on the EPR you can update them easily in the registry without modifying the BPEL artifact. @Hasitha: please update if I have miss anything. https://docs.wso2.com/display/BPS320/Endpoint+References Thank you & Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Wed, Sep 3, 2014 at 1:10 PM, Mahesh Chinthaka <[email protected]> wrote: > Hi, > > Is there a way to set dynamic endpoints in a bpel. Normally what we do is > set end points in wsdl file , then create archive and deploy. > > What I need to do is, send some endpoints as input parameters along with > request message, then the bpel will call the service with those endpoints. > Same service will be called (TenantMgtAdminService). > > And one more thing, number of endpoints will also vary. > > Seeking for help to figure out a way to do this.. > > > Thanks in advance, > > -- > Mahesh Chinthaka > Software Engineer , WSO2. > > Phone : (+94) 71 63 63 083 > Email : [email protected] > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
