Better, Faster and Smarter development: UDDI

Learnings from Gora (amitagl27@gmail.com)

I was creating a WSDL in my project to generate contract first webservices.

When I imported the WSDL in cordys, it gave me empty namespaces just after the attributes, i.e. it looked something like this :



<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<CreateForeclosureProcess xmlns="http://schemas.bas.com/ext/IntakeProcessServices/">
<CaseId xmlns="">PARAMETER</CaseId>
</CreateForeclosureProcess>
</SOAP:Body>
</SOAP:Envelope>



<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
<Body>
<CreateForeclosureProcess xmlns="http://schemas.bas.com/ext/IntakeProcessServices/">
<CaseId xmlns="">[string]</CaseId>
</CreateForeclosureProcess>
</Body>
</Envelope>

I did two things to remove these namespaces.

1. To remove from Cordys : Instead to having a direct element in my Request schema, I created a reference to another element.

Old :

<xsd:element name="CreateForeclosureProcess">
<xsd:complexType>
<xsd:sequence>
<xsd:element type="xsd:string" name="CaseId" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>

Modified :

<xsd:element name="CreateForeclosureProcess">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="tns:CaseId" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:element type="xsd:string" name="CaseId" />

2. Even after doing this, the Wizdler plugin was still showing the empty namespace, then a little research on web gave me following link :

http://docs.intersystems.com/ens20082/csp/docbook/DocBook.UI.Page.cls?KEY=GSOP_service_fine_tuning

which suggested to add

elementFormDefault='qualified'
to my schema tag as an attribute.

Example :
<xsd:schema targetNamespace="http://www.darkhorseboa.org/ThirdPartyUtilities/" elementFormDefault="qualified">

This post describes how to implement interceptor for all external service calls done through UDDI Connector.

Why Interceptor ?

End Point not static : You might change the end point for every UDDI call based on some logic. This is a general scenario where in you need to change the end point of all the services for every deployment. This can be achieved by changing every web service's end point by going to external services configuration but this is a tedious task as one needs to do it after every deployment and also to all the web services in the solution. One might think about the effort of changing 10 interfaces having 10 web services in each interface.
Defaulting few tags : A Scenario where for every UDDI call there are many tags which are to be defaulted and this should not be taken at process level (BPM level) as it(defaulting) has to be implemented whenever a UDDI service to be called.
Tweaking the request : A possible scenario of encrypting/decrypting some or all of the request tags.
Tweaking the response : A possible scenario of encrypting/decrypting some or all of the response tags.
Audit Log : Auditing every UDDI call.

There might be many more scenarios which might need the concept of Interceptor to be implemented.

How ?

We need to write a class which extends Customizer class of UDDIConn.jar. This Customizer class is an abstract class, hence a class which extends this class has to implement all the abstract methods among which OnRequest and OnResponse are also the methods.
A Sample scenario in which request and response is logged is shown below,

package better.faster.smarter.development.uddi.interceptor;

import com.eibus.applicationconnector.uddi.AuthenticationDetails;

import com.eibus.applicationconnector.uddi.Customizer;

import com.eibus.applicationconnector.uddi.IHTTPObject;

import com.eibus.applicationconnector.uddi.InterceptorException;

import com.eibus.applicationconnector.uddi.UserInfo;

import com.eibus.util.logger.CordysLogger;

import com.eibus.util.logger.Severity;

import com.eibus.xml.nom.Node;

public class CustomInterceptor extends Customizer {

private static CordysLogger logger = CordysLogger.getCordysLogger(CustomInterceptor.class);@Override

public void initialize(int arg0) {