Hi Guillaume,
I'm not entirely clear why WS-Addressing is required for this scenario
to work. Is it because the components don't publish their interfaces
(WSDL) on the JBI bus? Or perhaps because the BPEL service engine
doesn't explicitly expose its (internal) endpoints as external SOAP/HTTP
endpoints?
Would the scenario work without WS-A if all components were directly on
the JBI bus?
I'd be interested to know what are the missing links to make this
scenario work without WS-Addressing and without hard-wiring components
together using Spring. Not that I'm against using WS-A, but I'm
interested in interoperability with components that do not support WS-A,
such as simple REST clients and services, or POJOs deployed directly on
the JBI bus.
regards,
alex
Guillaume Nodet wrote:
You will need to create correlations some way for the bpel engine to
be able
to correlate the request you sent to the response from the worklist
service.
Then you would need a simple component that you would put between the
bpel
process and the http BC to add the ws-addressing soap headers. You
need to
specify a replyTo that will be understand by both the
worklist-webservice.
See
http://servicemix.goopen.org/site/servicemix-http.html#WS-Addressing to
understand how the servicemix-http handle wsa headers.
I guess this could be simplified, but servicemix-http does not support
wsa
when acting as a client yet. I will raise a JIRA for that.
Cheers,
Guillaume Nodet
On 6/15/06, oho <[EMAIL PROTECTED]> wrote:
My problem ist inverse:
* BPEL-Process is sending a request to worklist-webservice.
Worklist-webservice will answer to the request by sending another http
request to BPEL-Process
Activities:
* the BPEL-Process is calling worklist-webservice (is not a
BPEL-Process)
* then the worklist-webservice is waiting (perhaps one week) for answer
from user
* now, worklist-webservice has answer from user and must calling back to
the BPEL-Process. But worklist-webservice hasn't the addressing
informations
for request to BPEL-Process
Snippet from BPEL-Process:
<invoke name="Invoke_Worklist" partnerLink="Worklist"
portType="wl:CreateTaskService" operation="createTask"
inputVariable="Invoke_Worklist_createTask_InputVariable"/>
<receive name="Receive_Worklist" partnerLink="Worklist"
portType="wl:CreateTaskCallback" operation="createTaskCallback"
variable="Receive_Worklist_createTaskCallback_InputVariable"
createInstance="no"/>
Greetings
Oliver
--
View this message in context:
http://www.nabble.com/WS-Addressing-from-pxe-over-JBI-t1785537.html#a4877950
Sent from the ServiceMix - User forum at Nabble.com.
