You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2010/09/19 14:17:31 UTC
I didn't know you could do this to a classpath, as it were
OK, well, I'm doing archeology into the problems that erupt when
trying to use the CXF client side from inside an OpenOffice UNO
extension.
Well, so far ...
A call to the JAX-WS service class results in the search for the SPI
file. Good news: the JAX-WS code successfully reads the file and comes
up with org.apache.cxf.jaxws.spi.ProviderImpl as the name of the
class.
This is when things get wierd. It fails to find that class.
I haven't looked as closely as I might as to whether the Sun code in
the JRE is using exactly the same class loader each time.
Re: I didn't know you could do this to a classpath, as it were
Posted by Benson Margulies <bi...@gmail.com>.
Oh, boy, THAT is really a bad idea. Off for a JIRA.
On Sun, Sep 19, 2010 at 8:20 AM, Benson Margulies <bi...@gmail.com> wrote:
> OK, well, now I have something interesting to report.
>
> Thread.currentThread().getContextClassLoader() returns null. Now go to
> see if changing that helps anything.
>
> On Sun, Sep 19, 2010 at 8:17 AM, Benson Margulies <bi...@gmail.com> wrote:
>> OK, well, I'm doing archeology into the problems that erupt when
>> trying to use the CXF client side from inside an OpenOffice UNO
>> extension.
>>
>> Well, so far ...
>>
>> A call to the JAX-WS service class results in the search for the SPI
>> file. Good news: the JAX-WS code successfully reads the file and comes
>> up with org.apache.cxf.jaxws.spi.ProviderImpl as the name of the
>> class.
>>
>> This is when things get wierd. It fails to find that class.
>>
>> I haven't looked as closely as I might as to whether the Sun code in
>> the JRE is using exactly the same class loader each time.
>>
>
Re: I didn't know you could do this to a classpath, as it were
Posted by Benson Margulies <bi...@gmail.com>.
OK, well, now I have something interesting to report.
Thread.currentThread().getContextClassLoader() returns null. Now go to
see if changing that helps anything.
On Sun, Sep 19, 2010 at 8:17 AM, Benson Margulies <bi...@gmail.com> wrote:
> OK, well, I'm doing archeology into the problems that erupt when
> trying to use the CXF client side from inside an OpenOffice UNO
> extension.
>
> Well, so far ...
>
> A call to the JAX-WS service class results in the search for the SPI
> file. Good news: the JAX-WS code successfully reads the file and comes
> up with org.apache.cxf.jaxws.spi.ProviderImpl as the name of the
> class.
>
> This is when things get wierd. It fails to find that class.
>
> I haven't looked as closely as I might as to whether the Sun code in
> the JRE is using exactly the same class loader each time.
>