You are viewing a plain text version of this content. The canonical link for it is here.
Posted to savan-dev@ws.apache.org by "William Walsh (JIRA)" <ji...@apache.org> on 2010/06/28 17:32:50 UTC
[jira] Commented: (AXIS2-3642) jibx libs coming in Axis2 distrib
are renamed while still reffering in their manifests to old names
[ https://issues.apache.org/jira/browse/AXIS2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883187#action_12883187 ]
William Walsh commented on AXIS2-3642:
--------------------------------------
This issue also exists in Axis2 1.5.1 where the jibx manifests refer as the following fragments show:
jibx-run-1.2.1.jar
Class-Path: xpp3.jar stax-api.jar wstx-asl.jar
jibx-bind-1.2.1.jar
Class-Path: bcel.jar jibx-run.jar xpp3.jar stax-api.jar wstx-asl.jar
The fix for this should be:
1. Remove the jars that Axis2 doesn't ship: xpp3.jar and stax-api.jar
2. Rename the jars in the Class-Path lists to match the naming that Axis2 uses.
Without these changes deployment errors occur on systems (e.g. NetWeaver) that strictly check the manifests.
I assume Axis2 made the decisions it did to ship/not ship the related jars and deviate from the jibx packaging since the javax.xml.stream classes are provided in geronimo-stax-api_1.0_spec-1.0.1.jar and xpp3.jar functionality is provided by smack-3.0.4.jar. (Note that some environments provide their own implementations, for instance, of javax.xml.stream (e.g. WebSphere JDK, Weblogic).)
Having said all that; I'd advocate removing the Class-Path entries altogether because: 1) Unless you decide to put Class-Path entries in all the jars for consistency, having it only a couple of jars is inconsistent overall; and 2) Since some users have to repackage for local requirement (e.g. we package axis2 in our ear files in its own subdirectory) the Class-Path entries would have to be changed locally anyway.
> jibx libs coming in Axis2 distrib are renamed while still reffering in their manifests to old names
> ---------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3642
> URL: https://issues.apache.org/jira/browse/AXIS2-3642
> Project: Axis2
> Issue Type: Bug
> Components: databinding
> Affects Versions: 1.3
> Reporter: Michael B
> Assignee: Dennis Sosnoski
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Funny thing I found: i can not use jibx-bind-1.1.5.jar coming in full Axis2 distrib to postprocess my compiled databinding DTOs.
> The cause is that jibx-bind-1.1.5.jar needs some classes from jibx-run.jar which is named in Axis2 distrib as jibx-run-1.1.5.jar. But unfortunately ibx-bind-1.1.5.jar still has its META-INF/MANIFEST.MF containing the line:
> Class-Path: bcel.jar jibx-run.jar xpp3.jar stax-api.jar wstx-asl.jar
> That is - reffering to jibx-run.jar, not jibx-run-1.1.5.jar which is present in the Axsis2 disctrib.
> Of cause this is not a major issue, but i think that it would be better to fix it either by renaming jars back (i.e. stripping version) or modifying their manifest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org