[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601183#action_12601183
]
Sebastian Voigt commented on TUSCANY-2343:
------------------------------------------
In addition to Georges post:
We have tested the latest build (incl. the osgi-installer), and we were able to
start our junit-test which starts the sca-domain and tests some method-calls).
We have to include our jaxb-fix (that is describe
https://issues.apache.org/jira/browse/TUSCANY-2346), but it is running now (it
wasnt with the older osgi-bundles (5).
But we have problems to integrate the tuscany-bundles into our pdebuild. The
build is done with an ant-script which runs the pde-build. We have installed
the tuscany-bundles
into an extension-location for the eclipse that is used for the pde-build. We
have problems with the tuscany-bundles, because there are a lot of
"Unsatisfied import package"-messages. The installer bundle doesn't help
because it doesn't create the needed 3rd-party bundles while building.
Also the installer-bundle would not help for deploying our product, because it
contains the classpath to the local maven repository and not every customer
would install maven and
will build tuscany (par example). Therefore the solution with the installer is
for our case not acceptable. We need for every 3rd-party an osgi-bundle, for
our technologies we have create them,
but now the dependencies for tuscany are missing.
At the moment we are discussing to create all bundles that are needed by
tuscany (see the above post from George), but therefore we would know if the
tuscany-developer will
provide these bundles (in the future).
If we have to build all dependencies ourself it would be interesting how often
the tuscany-developer will use newer versions of the 3rdparty-technologies,
because we have to update them in this case every time.
Also it would be interesting if your team can add version-numbers for all
imports: that would help implementing all 3rd-party bundles.
> OSGi bundle design leads to class loading issues
> ------------------------------------------------
>
> Key: TUSCANY-2343
> URL: https://issues.apache.org/jira/browse/TUSCANY-2343
> Project: Tuscany
> Issue Type: Bug
> Reporter: Georg Schmidt
> Attachments: Libary Versions.xls
>
>
> Currently the design of the OSGi bundles leads to class loading exceptions.
> There seem to be several reasons for this behavior:
> * reexporting of all libraries without version numbers
> * imports without version numbers
> Please use distinct bundles for 3rd party libraries. That would lead to
> easier reusage of your bundles in a larger OSGi project.
> The current status leads to undefined system behaviour due to the OSGi class
> loading concept.
> Please tell if you see a way, how we could support you by achieving this
> goal. (If a solution is interesting for you) We are willing to contribute
> because its a critical project issue for us.
> The problems occur with the current snapshot release. Sorry, I do not know
> which version to take.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
