javax.xml api versionshttps://www.eclipse.org/forums/index.php/mv/msg/4035/11976/#msg_11976
of which are different from the budle version, so automatic association
won't work. In cases where other bundles use versions on their import
package headers, such as org.xml.sax;version="2.0.2", they won't resolve.
I think the versions are as follows (used this to fix my issues):

Also, you're suggesting this on just 'exports' right? And, it's your own=
plugin that does the import-package with version constraints? Or, ... a=
re you saying we should use import-package in the rest of the xerces "fa=
mily" (which, I'd see as a bit more "risky" to change at this point).

Also, you're suggesting this on just 'exports' right? And, it's your own=
plugin that does the import-package with version constraints? Or, ... a=
re you saying we should use import-package in the rest of the xerces "fa=
mily" (which, I'd see as a bit more "risky" to change at this point).

Thanks!]]>David Williams2008-04-15T16:26:13-00:00Re: javax.xml api versionshttps://www.eclipse.org/forums/index.php/mv/msg/4035/12086/#msg_12086
Yes, I'm just suggesting this for exports. In most cases, the api version
is the same as the bundle version, but in this case there are a few
versions, and that's what caused the problem. It wasn't my own plugin that
had the constraint, it was a plugin from Knopflerfish. Since our product is
Equinox based, I try to use the Orbit plugins wherever possible, but in this
case (axis2), Knopflerfish had what I needed, and I want it to work with the
parser bundle from Orbit.

As for the imports, yes, it would be nice if the Require-Bundle's were
changed to Import-Package, but in this case, it would likely, as you pointed
out, cause problems somewhere.

Also, you're suggesting this on just 'exports' right? And, it's your own
plugin that does the import-package with version constraints? Or, ... are
you saying we should use import-package in the rest of the xerces "family"
(which, I'd see as a bit more "risky" to change at this point).

Thanks!]]>Paul Gardiner2008-04-16T16:30:58-00:00Re: javax.xml api versionshttps://www.eclipse.org/forums/index.php/mv/msg/4035/563417/#msg_563417
Yes, I'm just suggesting this for exports. In most cases, the api version
is the same as the bundle version, but in this case there are a few
versions, and that's what caused the problem. It wasn't my own plugin that
had the constraint, it was a plugin from Knopflerfish. Since our product is
Equinox based, I try to use the Orbit plugins wherever possible, but in this
case (axis2), Knopflerfish had what I needed, and I want it to work with the
parser bundle from Orbit.

As for the imports, yes, it would be nice if the Require-Bundle's were
changed to Import-Package, but in this case, it would likely, as you pointed
out, cause problems somewhere.

Also, you're suggesting this on just 'exports' right? And, it's your own
plugin that does the import-package with version constraints? Or, ... are
you saying we should use import-package in the rest of the xerces "family"
(which, I'd see as a bit more "risky" to change at this point).

Also, you're suggesting this on just 'exports' right? And, it's your own
plugin that does the import-package with version constraints? Or, ... are
you saying we should use import-package in the rest of the xerces "family"
(which, I'd see as a bit more "risky" to change at this point).

Also, you're suggesting this on just 'exports' right? And, it's your own
plugin that does the import-package with version constraints? Or, ... are
you saying we should use import-package in the rest of the xerces "family"
(which, I'd see as a bit more "risky" to change at this point).