aspose file tools*
The moose likes Web Services and the fly likes schemaLocation Problem (Netbeans and Remote BPEL-Services) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "schemaLocation Problem (Netbeans and Remote BPEL-Services)" Watch "schemaLocation Problem (Netbeans and Remote BPEL-Services)" New topic
Author

schemaLocation Problem (Netbeans and Remote BPEL-Services)

Heinrich He
Greenhorn

Joined: Feb 26, 2008
Posts: 1
I there,

did anyone ever deploy and test BPEL Services running on a remote Glassfish installation?

Coding and deploying seems to be working. But I think i forgot a configration option. Because the schmeLocations in the automatic generated xml File are wrong.

the deplayed wsdl files are always pointing to:
http://mySillyServername.localdomain:18181/....CompositeAppAddr../
instead of a correct ip address/dns-name:
http://10.3.3.33:18181/....

Where do i config the remote wsdl services or casa port bindings? Is there a hidden Netbeans Config File?

If I deploy only the .xsd and .wsdl files on my local domain and test the BPEL-Composite-App with the SOAP-UI (Eclipse-Plugin), the CompositeApp is working (remotely!!). But Netbeans still wont test it because of SOAP Port Binding errors..
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: schemaLocation Problem (Netbeans and Remote BPEL-Services)