[
https://issues.apache.org/jira/browse/SYNCOPE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529760#comment-13529760
]
Francesco Chicchiriccò commented on SYNCOPE-251:
------------------------------------------------
We can open an issue at [1] for making the SOAP connector project providing two
bundle versions: one with all dependencies inside the JAR (as current) and one
without any dependency inside the JAR. This can be done quite easily.
However, this kind of solution seems quite partial to me: what if we have any
other conflicting dependency with any other bundle?
Isn't possible to use a non-default bus as suggested by Jan above?
About making ConnId OSGi-compatible, it seems to me a complete separate story
to deal with: *all* connector bundles must be OSGi-compatible when Syncope will
become OSGi-compatible.
[1] https://code.google.com/p/connid/issues/list
> Fix Dependency issues with ConnID Bundle deployment
> ----------------------------------------------------
>
> Key: SYNCOPE-251
> URL: https://issues.apache.org/jira/browse/SYNCOPE-251
> Project: Syncope
> Issue Type: Sub-task
> Components: core
> Reporter: Jan Bernhardt
> Assignee: Jan Bernhardt
> Fix For: 1.2.0
>
>
> SOAP ConnID Bundle contains CXF dependencies, which cause Classloading issues
> when migrating Syncope to CXF,
> Currently maven-dependency-plugin:copy is used to generate bundle jars, but
> this plugin does not support to exclude transitive dependencies. Maybe
> another maven plugin (maven-assembly-plugin ?) can be used to exclude CXF
> dependencies from SOAP ConnID Bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
