From: <ale...@jb...> - 2005-12-17 02:27:27
|
This is not a deployment problem. The BPEL document contains an error. Take a look at /process/partnerLinks/partnerLink[2]: <partnerLinks> | <partnerLink name="client" partnerLinkType="client:myEcho" myRole="myEchoProvider"/> | <partnerLink name="myEcho" partnerRole="myEcho_Role" myRole="myEcho_Role" partnerLinkType="ns1:myEcho_PL"/> | </partnerLinks> It defines a bidirectional relationship between the process and an external service. Now follow the partner link type reference to {http://localhost:8081/axis/myEcho.jws}myEcho_PL: <plnk:partnerLinkType name="myEcho_PL"> | <plnk:role name="myEcho_Role"> | <plnk:portType name="impl:myEcho"/> | </plnk:role> | </plnk:partnerLinkType> It declares an unidirectional relationship, since it contains only one role subelement. This makes sense because your process does not receive through the myEcho partner link. In this situation, the partner link has no reason to assign a role to the BPEL service. Therefore, you should drop the myRole attribute. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913222#3913222 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913222 |