Hi,
I tried using BPEL 2 and it didn't work out.
The only one accepted was
|
| <copy>
|
| <from>
|
| <literal>
|
| <wsa:EndpointReference>
|
| <wsa:Address>THE_URI_FROM_THE_SERVICE_IN_THE_WSDL</wsa:Address>
| <wsa:ServiceName PortName="myPort">THE_SERVICENAME_FROM_THE_WSDL</wsa:ServiceName>
|
| </wsa:EndpointReference>
|
| </literal>
|
| </from>
| <to partnerLink="myPL">
| </copy>
|
|
Ideally, the partnerLink should be OK. I saw the implementation of EndpointReference in endpointref package and no additional info is required.
The assignment goes fine but the invoke fails and the reason is that no port implements the required port type. Moreover it look like the process tries to build a new partnerlink loking the wsdl files in the URI catalog.
Hope anyone has a solution. Bye
ZazzaZ
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101754#4101754
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101754
Are you trying to access a different Bean than what you have called the method on? ie. your s:button called BeanA and you want to access properties of BeanB.
If so, then assuming BeanB has been outjected into the Conversation scope, you just need to inject BeanB into your BeanA. eg in BeanA.java :@In
| BeanB beanB;
or if you'd rather call it inline:if(getConversation()!= null)
| { //Aqui me cargo la conversacion si es que existe
| System.out.println("conversation ID " .concat(getConversation().getId()));
| //access to managed bean in Conversation
| BeanB beanB = (BeanB)Component.getInstance("beanB");
| }
|
Cheers,
Damian.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101750#4101750
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101750