Thanks for answering! Indeed https://issues.apache.org/jira/browse/TUSCANY-2343 covers the same problem (problem 1), We added comments to give you more information and we will provide more feedback after we tested The new osgi-bundles you mentioned. Also we opened a second Jira-issue to describe the second problem that covers the problems with jaxb-contexts within tuscany. It can be discussed under https://issues.apache.org/jira/browse/TUSCANY-2346
Regards, Sebastian Voigt > -----Original Message----- > From: Rajini Sivaram [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 28, 2008 10:45 AM > To: [email protected] > Subject: Re: Jaxb & Tuscany Problems > > On 5/27/08, Sebastian Voigt <[EMAIL PROTECTED]> wrote: > > > > In our application we use Jaxb for reading and storing of configurations. > > This application is distributed and uses Tuscany for the remote > > communication. > > The first problem that we have is that we load a configuration file with > > jaxb and then we send this java object (the configuration) over a Tuscany > > remote API. > > > > For this workflow there exits two problems for us at the moment: > > 1) The more common problem at first. In our application the configuration > > is created > > with our jaxb-classes and sometimes (not always) Tuscany finds another jaxb > > -classes (classes within jaxb). > > The problem is in this case that the serialization isn't working. Tuscany > > compares the classes (e.g. elements/ > > annotations classes) and it can't find them because they were loaded by a > > different classloaders. > > In some cases it uses in both the same jaxb-implementation, then the > > serialization works fine. One main problem > > is that the current Tuscany bundles only have "short" manifest -files. The > > imports and so on don't have version restrictions included. >
