On 21/08/12 21:42, Mark D wrote:
Thanks, Sergey.
Do you mean this one?
https://issues.apache.org/jira/browse/CXF-4290
I noticed your comment at the end. I'm not familiar with the internals of
CXF but it looks like this is an issue in the main CXF libraries, i.e., not
specifically DOSGi and that the problem is only highlighted in particular
cases, like OSGi's classloaders.
I guess the class is attempting to create a proxy web client with the given
interface and that isn't visible on it's class path. Was the fix passing in
a classloader as a parameter?
The actual fix at the moment is to pass a composite loader in a retry
attempt. This can be optimized and the loader can be passed as a
parameter to the factory, but I was not yet 100% sure the simple
composite loader we came up with was good enough to be used on the
'main' path - a bit more testing is needed...
I'm also curious as to why it works for the single-bundle dist and not the
multi-bundle (the one I am using!). Surely it's just the CXF bundle?
I've really no idea - I guess in the single bundle case the class
visibility is much higher
Is there an open issue for the multi-bundle problem? I couldn't find one.
https://issues.apache.org/jira/browse/DOSGI-18
Cheers, Sergey
Thanks for the help.
--
View this message in context:
http://cxf.547215.n5.nabble.com/DOSGI-RS-client-issue-JAXRSClientFactoryBean-class-visibility-maybe-causing-a-connect-exception-tp5712885p5712924.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
