Hello Alex,
Of course i have specified in bpel-application.xml the location of my URL to
the wsdl-document of my service.
But in the server.log file there is some thing curios:
anonymous wrote : 2007-01-03 22:53:20,708 DEBUG
[org.jboss.ws.server.ServiceEndpoint] WSDL request, using host:
OK, I get it now. What happens if you set alwaysModifySOAPAddress to false?
That should preserve the original address in the WSDL document, provided it is
a valid URL.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3997998#3997998
Reply to the post :
Hi Alex,
of course: This was the raison why the soap:address element where alway
overritten and the HTTP Request arrived to the monitoring component without
SOAP Message inside.
SOLUTION:
I was Using Jbossws 1.0.4 and i have perform the following setting:
In
Hi Bertrand,
Does the monitoring component at http://localhost.8081/creditprocess/schufa
have a WSDL document? You should include the location of that WSDL document in
your service catalog in bpel-application.xml.
The soap:address element in the WSDL document should, in turn, specify the
Hello Alex,
first thanks for your reply and i'll like to give some background informations
hier to let you understand what i'm trying to do.
I wan jbpm invoke an already running service under:
http://localhost:8080/axis/services/schufaServiceB?wsdl. But this service is
not to access directly
I'll like to bring some precision once again.
I have tried some test scenario.
When i specify the service wsdl location:
http://localhost.8081/creditprocess/schufa at the first time monitoring
component receive a request. Hier some output:
| Starting daemon thread...ok.
| - Listening
I'm using jbpm-3.1.1 jbpm.bpel.1.beta1, jboss AS 4.0.4.GA, and java 1.5
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3993932#3993932
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3993932
Hi Bertrand,
If I understand correctly, jBPM is sending an HTTP request to a partner
service, but the SOAP envelope being transmitted is not what the service
expects. In this case, I'd like to take a look at the outgoing SOAP message and
the partner WSDL document for determining the possible
