Ok.   The server side does work so the fix is good.

thanks,


Benson Margulies-4 wrote:
> 
> Hmm. The last time I communicated with Dan, he didn't (I thought) have a
> fix to the client side, only the server side.
> 
> 
> On Fri, 2007-12-21 at 12:58 -0800, tcs wrote:
>> So in response to Dan Kulp, the issue with a POJO client talking to a
>> JAXB
>> server is not fixed.
>> 
>> thanks,
>> 
>> 
>> 
>> dkulp wrote:
>> > 
>> > 
>> > I'm deploying a new 2.0.4 snapshot now that SHOULD fix it.  (I'd 
>> > appreciate it if that could be verified)   We'll probably shoot for a 
>> > 2.0.4 release mid January sometime.
>> > 
>> 
>> 
>> 
>> Benson Margulies-4 wrote:
>> > 
>> > If you are really stuck with 1.4, there's not much we can do for you.
>> > You need to really generate a client with wsdl2js or javs2js, and we
>> > can't generate one of those that is 1.4-compatible. 
>> > 
>> > On Fri, 2007-12-21 at 11:00 -0800, tcs wrote:
>> >> I'm still trying to understand if this is an error on my side or if
>> CXF
>> >> is
>> >> not doing the right thing with the Java object fields.
>> >> 
>> >> Any help will be greatly appreciated.
>> >> 
>> >> thanks,
>> > 
>> > 
>> > 
>> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/XML-elements-does-not-belong-to-the-namespace-tp14247019p14463851.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to