migration of ALSB2.6 sources to ALSB3.0
Today I started the migration of an ALSB2.6 project to ALSB3.0. Because I had no source tree available, the first thing I did was exporting the sources from a development environment. The result was a sbconfig.jar.
Next step was importing the sbconfig.jar in ALSB3.0. This worked fine, but after testing a business service, I had the next error :
An unexpected error occured accessing information about the WSDL of the service:
com.bea.wli.config.component.NotFoundException: Can not compute effective WSDL for : BusinessService ……
After a Google Search I found a solution on http://orasoa.blogspot.com
The solution is removing the plnk:partnerLinkType tag from the WSDL.
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
