Zazzaz,
After an examination of the stack trace you posted, the error occurs inside the
SAAJ implementation (JBossWS) not in jBPM BPEL code. I'd like to determine why
JBossWS malfunctions when the sopaAction attribute is not present. Which JBoss
AS version are you using?
View the original
I found it out!
It was a bad web service building. I looks like when jbpm-bpel acts as a client
(invoke situation) it is sensible to service implementation.
I found out that my service was missing the soapAction attribute in the
binding. The odd thing was that a test client worked out with
Ok,
thanks for answering but I have already set my URIs in the catalog.
I saw it from advanced example ATM.
I'm thinking that this error is related to wrong manipulation of messages and
messages parts in the BPEL. This way when the service calling occurs the SOAP
message is in a wrong state.
Hi
I think that your problem is that you have to add the URL of the service that
you invoke in the bpel-application.xml file. For example, I use 2 services in
my bpel process and my bpel-application.xml is like this:
?xml version=1.0 encoding=UTF-8?
| bpelApplication name=procesoLocalizacion
