Hi Seth,
thanks for that, I'll give it a try. I can regression test the original
OTRS plugin, which should give some degree of confidence regarding
compatibility.
Cheers ... J
On Thu, Feb 6, 2014 at 9:18 PM, Seth Leger <s...@opennms.org> wrote:
> Hi Jonathan,
>
> You should:
>
> - Add the wsdl4j maven artifact that you want, along with the version that
> you want, to the top-level pom.xml (in the root directory of the OpenNMS
> source tree) in the <dependencyManagement> section. This will tell all
> projects to use the same version of the artifact.
> - Add <exclusion> tags to all Apache Axis dependencies to prevent the old
> wsdl4j from being pulled in as a transitive dependency of Axis.
> - In each pom.xml where you add an exclusion, manually add your desired
> wsdl4j artifact as a separate dependency *without a version*. It will pick
> up the version from the <dependencyManagement> section of the top-level
> pom.xml.
>
> This will force all projects that rely on Apache Axis to use the new
> wsdl4j artifact which is (hopefully) still backwards-compatible with Apache
> Axis.
>
> Seth Leger
> The OpenNMS Group
>
>
>
> On 2/6/14, 3:32 PM, Jonathan Sartin wrote:
>
> Hi All,
>
> I'm using Apache CXF for the OTRS 3.1 integration. It depends on a later
> version of a library that is a dependency of a framework we already use
> (Axis).
>
> Axis(used by the previous OTRS and remedy integrations) bundle the
> dependency with a different name, so we end up with both dependencies on
> the classpath (wsdl4j 1.5.1 - through the renamed axis verison and wsdl4j
> 1.6.3 through cxf).
>
> I'd like to exclude 1.5.1 (the axis version) and keep 1.6.3. What's the
> best way of managing that? I see some "dependencies" projects. Is that the
> right approach? Unfortunately, I can't just eliminate one of the frameworks
> as the WSDL styles are different (rpc/encoded for the older webservices vs
> document literal for the newer) and each framework only supports one.
>
> Cheers ... J
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the
> Whitepaper.http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Please read the OpenNMS Mailing List
> FAQ:http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of this
> page:https://lists.sourceforge.net/lists/listinfo/opennms-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
