[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601171#action_12601171
]
Daniel Stucky commented on TUSCANY-2343:
----------------------------------------
Hi Rajini,
this week I've been testing the new Tuscany bundles with the installer bundle.
In eclipse our bundles compile and the tests run sucessfully.
There are is a minor issue concerning the InstallerBundleActivator. All Tuscany
bundles (including the installer) and all 3rd party jars are located in the
same directory. In the installer's classpath all entries are absolute paths to
the maven repository. On machines without the repository, the jars are not
found. As I unsterstand there should be some code in the
InstallerBundleActivator that checks this and tries to find the jars relative
to the installer., but this does not work. I guess the boolean logic at line
169 is not correct:
...
if (!jar.isAbsolute()&&!jar.exists()) {
jar = new File(tuscanyInstallDir, jar.getName());
}
...
Another problem is that we are trying to build our application automatically
using ant and eclipse pdebuild. So far we did not get it running. An error
occurs in the first bundle that makes use of Tuscany classes. If we exclude
those bundles from the build everything works fine. There are lots of warnings
regarding "Unsatisfied import package".
Has anyone experience using pdebuild and tuscany ?
Bye,
Daniel
> 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.
