Hi,

When you do the port offset, Please change relevant service url in the
location attribute of the wsdl binding for all BPEL process and HumanTask.
Otherwise BPEL process will not able to talk to HumanTask service.

Thanks,
Hasitha.


On Wed, Jul 30, 2014 at 2:12 PM, Jeewani Lakshani [IT/EKO/LOITS] <
jeewa...@lolctech.com> wrote:

>  Hi,
>
> Thank you Hasitha for your prompt response.  We changed our offset to 4
> then it worked.
>
>
>
> Regards,
>
> Jeewani
>
>
>
> *From:* Hasitha Aravinda [mailto:hasi...@wso2.com]
> *Sent:* Wednesday, July 30, 2014 12:46 PM
> *To:* Jeewani Lakshani [IT/EKO/LOITS]
> *Cc:* dev@wso2.org
> *Subject:* Re: [Dev] Remote task is not working in wso2bps-3.2.0
>
>
>
> Hi,
>
> In the error log, I see a Connection refused error. Can you check
> followings. ?
>
> 1) Make sure you have deployed humantask artifacts.
>
> 2) If the humantask is deployed in your system, are you running BPS with a
> portOffset ?
>
>
>
> On Wed, Jul 30, 2014 at 12:33 PM, Jeewani Lakshani [IT/EKO/LOITS] <
> jeewa...@lolctech.com> wrote:
>
>  Hi,
>
> We have tried the sample ClaimApprovalProcess BPEL through wso2bps-3.0.0
> and it worked fine (human task ).
>
>
>
> But when we try it (sample process wso2bps-3.2.0) via wso2bps-3.2.0 it get
> fails at the try it option an error occurred. I have attached herewith the
> error log for your reference.
>
> Are there any limitations in wso2bps-3.2.0 when running such BPEL
> processes?
>
>
>
> No, HumanTask and BPEL written for BPS 3.0.0 is compatible with BPS 3.2.0.
>
> Thanks,
> Hasitha.
>
>
>
>
>
> Thank you.
>
> Regards,
>
> Jeewani
>
> This message (including any attachments) is intended only for the use of
> the individual or entity to which it is addressed and may contain
> information that is non-public, proprietary, privileged, confidential, and
> exempt from disclosure under applicable law or may constitute as attorney
> work product. If you are not the intended recipient, you are hereby
> notified that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and (i) destroy
> this message if a facsimile or (ii) delete this message immediately if this
> is an electronic communication. Thank you.
>
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> --
> Hasitha Aravinda,
> Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile: +94 71 8 210 200
>
> This message (including any attachments) is intended only for the use of
> the individual or entity to which it is addressed and may contain
> information that is non-public, proprietary, privileged, confidential, and
> exempt from disclosure under applicable law or may constitute as attorney
> work product. If you are not the intended recipient, you are hereby
> notified that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and (i) destroy
> this message if a facsimile or (ii) delete this message immediately if this
> is an electronic communication. Thank you.
>



-- 
Hasitha Aravinda,
Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile: +94 71 8 210 200
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to