Restoring OSB 12.2.1 Maven Functionality by Robert Patrick
April 4, 2017 Leave a comment
It seems that testing of the Oracle Service Bus (OSB) Maven functionality in the new 12.2.1 release failed to catch a few issues that make the OSB Maven plugin unusable out of the box. Oracle is aware of the issue and working to create a patch for this. In the meantime, users can work around the problem with a few simple changes. This blog documents those changes.
Fixing the com.oracle.servicebus:client POM
The first change we need to make is to edit the com.oracle.servicebus:client POM. This POM can be found at ${ORACLE_HOME}/osb/plugins/maven/com/oracle/servicebus/client/12.2.1/client-12.2.1.pom. Open this file in a text editor and make the following changes.
- Delete the <dependency> stanza for the com.oracle.weblogic:wlthint3client. This artifact does not exist. Fortunately, it is is not needed since the weblogic-server-pom dependency provides all of the connectivity to WebLogic Server that is required.
- In the weblogic-server-pom dependency, change the <version> element’s value from “LATEST” to “[12.2.1,12.2.2)” (without the double quotes).
- In the com-bea-core-xml-xmlbeans dependency, change the <artifactId> element’s value from “com-bea-core-xml-xmlbeans” to “com.bea.core.xml.xmlbeans” (without the double quotes).
- In the com-bea-core-xml-xmlbeans dependency, change the <version> element’s value from “LATEST” to “[12.2.1,12.2.2)” (without the double quotes).
After making these changes, the relevant section of the file should look like the one shown here. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog
Twitter
LinkedIn
Facebook
Wiki
Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress
