INFO: .NET Web services invocation integration considerations with Java, Php and others
Summary
This article describes a fundamental consideration whenever a client implemented in Java, Php or another different from .NET, invokes a web service in .NET (mainly those exposed by BizAgi).
Applies To
BizAgi Xpress 9.1.x versions.
.NET Web service invocation with a Java, Php,. client
Consideration 1
Whenever you wish to use a Java, Php or other technology client in order to consume a BizAgi (.NET) web service, its referenced url must be complemented with the "?wsdl" termination.
For example:
If BizAgi's web service is exposed and browser-located as:
http://localhost/BizAgi_project/webservices/entitymanagersoa.asmx
Then, a Java or Php client should reference:
http://localhost/BizAgi_project/webservices/entitymanagersoa.asmx?wsdl
Consideration 2
While using complex type requests and/or responses, you may need to check your web services definition structure, so serialization of these elements is possible.
This means double checking if your complex type requires any given namespace for its definition.
Otherwise your elements may not take the desired values as XML if these scenarios happen:
1. Some of your elements require a namespace and you have not defined this in your XLST files.
2. You have defined 2 totally different namespaces (one is not contained in the other) for elements which one contains the other.
We recommend you ensure having knowledgement about the target web service's specification, or you can contact someone who does.
Java, Php, implemented web service invocation from a BizAgi project
Consideration 1
Whenever you wish to use a Java, Php,. web service from your BizAgi project, you may have to consider if your web service implementation's definition has mapped its access so its invocation has the ?wsdl or .wsdl termination.
We recommend you ensure having knowledgement about the target web service's specification, or you can contact someone who does.
Consideration 2
While using complex type requests and/or responses, you may need to check your web services definition structure, so serialization of these elements is possible.
This means double checking if your complex type requires any given namespace for its definition.
Otherwise your elements may not take the desired values as XML if these scenarios happen:
1. Some of your elements require a namespace and you have not defined this in your XLST files.
2. You have defined 2 totally different namespaces (one is not contained in the other) for elements which one contains the other.
Again, we recommend you ensure having knowledgement about the target web service's specification, or you can contact someone who does.
Keywords
Java, Php, Web services.
