Archive for the 'WSDL' Category

SOA Project Compilation Issue

Recently we came across some compilation issue with SOA composite. Though it’s a small issue, I feel worth sharing as we often forget few basic things during development.

The SOA composite uses DB Adapter for polling the database. Every time we refresh or run through the database wizard and compiles the composite, we are getting compilation error saying ‘variable <<variable name>> of type <<variable type>> is not defined’.

Reason: We will have a WSDL represents the service interface exposed by the DB adapter even when we used the polling option. Whenever we define a variable in BPEL the corresponding XSD (where the elements are defined) will be imported or included into this service WSDL. These import/include statements are getting removed in the WSDL every time we refresh the DB adapter. Re-adding these import/include statements in the WSDL had resolved the issue. This also applies to other kind of service interfaces

We observed the same issue with some of SOA composites after migrating from 10g to 11g.


Namespace Issue

Today, for one of the tasks i need one sample WSDL so that i can create some mock service in SOAP UI. As usual wanted to leverage google search capabilities Smile for the same, instead of coming up with one on my own.

I have taken one of the WSDLs given in to my eclipse. I am surprised to see the errors given by eclipse for the WSDL. I made sure that the WSDL structure, namespace aliases etc. are given correctly.On careful examination of the inline XSD given in the WSDL, found the issue is with the namespace which is given as

Modifying this namespace to resolved the error.

So the moral of the story is that some times blind copy does not give the intended time saving benefits as we expect.



Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 360 other followers

Enter your email address to follow this blog and receive notifications of new posts by email.