You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Ted Roeloffzen <te...@gmail.com> on 2010/11/26 11:03:33 UTC
Marshalling weirdness
Hi All,
At my company we're having a little trouble with the marshalling. Perhaps
you know a solution.
We're trying to connect to a third-party Webservice and we've created the
code ot ouf their WSDL.
We have a few classes, in the same package, with instance variables that
have the same name.
They don 't always have the same type. Sometimes their strings, other times
they are integers or something totally different.
The problem is that the JAXB marshaller keeps track of the variables names,
only not in combination with Classname
That's why we are getting marshalling exceptions.
Does anyone of you recognize this problem and if so, do you have a solution?
thanks a bunch
Greetings,
Ted
Re: Marshalling weirdness
Posted by Benson Margulies <bi...@gmail.com>.
JAXB has a public API. Do you need to do entire SOAP messages or just
individual objects? If the later, JAXB is good enough. There is also
an API to Aegis for this purpose. It all depends on how your
configured CXF.
On Tue, Nov 30, 2010 at 3:49 AM, Ted Roeloffzen
<te...@gmail.com> wrote:
> Apparently i missunderstood my colleague.
> The problem doesn't occur when using CXF to marshall and unmarshall.
> But in our application we are forced to manually marshall and unmarshall the
> xml, and when we do this it fails.
> Is their a way to use the marshaller from cxf to manually marshall and
> unmarshall the XML?
> thnx
>
> 2010/11/26 Ted Roeloffzen <te...@gmail.com>
>
>> yes we are using CXF.
>> The situation looked weird and inplausible to me too.
>> I'll see if i can make a test.
>>
>> 2010/11/26 Benson Margulies <bi...@gmail.com>
>>
>> Are you even using CXF at all?
>>>
>>> The situation you describe does not sound plausible. If you are using
>>> CXF, can you make a test case and post it?
>>>
>>> On Fri, Nov 26, 2010 at 5:03 AM, Ted Roeloffzen
>>> <te...@gmail.com> wrote:
>>> > Hi All,
>>> > At my company we're having a little trouble with the marshalling.
>>> Perhaps
>>> > you know a solution.
>>> > We're trying to connect to a third-party Webservice and we've created
>>> the
>>> > code ot ouf their WSDL.
>>> > We have a few classes, in the same package, with instance variables that
>>> > have the same name.
>>> > They don 't always have the same type. Sometimes their strings, other
>>> times
>>> > they are integers or something totally different.
>>> > The problem is that the JAXB marshaller keeps track of the variables
>>> names,
>>> > only not in combination with Classname
>>> > That's why we are getting marshalling exceptions.
>>> > Does anyone of you recognize this problem and if so, do you have a
>>> solution?
>>> > thanks a bunch
>>> > Greetings,
>>> > Ted
>>> >
>>>
>>
>>
>
Re: Marshalling weirdness
Posted by Ted Roeloffzen <te...@gmail.com>.
Apparently i missunderstood my colleague.
The problem doesn't occur when using CXF to marshall and unmarshall.
But in our application we are forced to manually marshall and unmarshall the
xml, and when we do this it fails.
Is their a way to use the marshaller from cxf to manually marshall and
unmarshall the XML?
thnx
2010/11/26 Ted Roeloffzen <te...@gmail.com>
> yes we are using CXF.
> The situation looked weird and inplausible to me too.
> I'll see if i can make a test.
>
> 2010/11/26 Benson Margulies <bi...@gmail.com>
>
> Are you even using CXF at all?
>>
>> The situation you describe does not sound plausible. If you are using
>> CXF, can you make a test case and post it?
>>
>> On Fri, Nov 26, 2010 at 5:03 AM, Ted Roeloffzen
>> <te...@gmail.com> wrote:
>> > Hi All,
>> > At my company we're having a little trouble with the marshalling.
>> Perhaps
>> > you know a solution.
>> > We're trying to connect to a third-party Webservice and we've created
>> the
>> > code ot ouf their WSDL.
>> > We have a few classes, in the same package, with instance variables that
>> > have the same name.
>> > They don 't always have the same type. Sometimes their strings, other
>> times
>> > they are integers or something totally different.
>> > The problem is that the JAXB marshaller keeps track of the variables
>> names,
>> > only not in combination with Classname
>> > That's why we are getting marshalling exceptions.
>> > Does anyone of you recognize this problem and if so, do you have a
>> solution?
>> > thanks a bunch
>> > Greetings,
>> > Ted
>> >
>>
>
>
Re: Marshalling weirdness
Posted by Ted Roeloffzen <te...@gmail.com>.
yes we are using CXF.
The situation looked weird and inplausible to me too.
I'll see if i can make a test.
2010/11/26 Benson Margulies <bi...@gmail.com>
> Are you even using CXF at all?
>
> The situation you describe does not sound plausible. If you are using
> CXF, can you make a test case and post it?
>
> On Fri, Nov 26, 2010 at 5:03 AM, Ted Roeloffzen
> <te...@gmail.com> wrote:
> > Hi All,
> > At my company we're having a little trouble with the marshalling. Perhaps
> > you know a solution.
> > We're trying to connect to a third-party Webservice and we've created the
> > code ot ouf their WSDL.
> > We have a few classes, in the same package, with instance variables that
> > have the same name.
> > They don 't always have the same type. Sometimes their strings, other
> times
> > they are integers or something totally different.
> > The problem is that the JAXB marshaller keeps track of the variables
> names,
> > only not in combination with Classname
> > That's why we are getting marshalling exceptions.
> > Does anyone of you recognize this problem and if so, do you have a
> solution?
> > thanks a bunch
> > Greetings,
> > Ted
> >
>
Re: Marshalling weirdness
Posted by Benson Margulies <bi...@gmail.com>.
Are you even using CXF at all?
The situation you describe does not sound plausible. If you are using
CXF, can you make a test case and post it?
On Fri, Nov 26, 2010 at 5:03 AM, Ted Roeloffzen
<te...@gmail.com> wrote:
> Hi All,
> At my company we're having a little trouble with the marshalling. Perhaps
> you know a solution.
> We're trying to connect to a third-party Webservice and we've created the
> code ot ouf their WSDL.
> We have a few classes, in the same package, with instance variables that
> have the same name.
> They don 't always have the same type. Sometimes their strings, other times
> they are integers or something totally different.
> The problem is that the JAXB marshaller keeps track of the variables names,
> only not in combination with Classname
> That's why we are getting marshalling exceptions.
> Does anyone of you recognize this problem and if so, do you have a solution?
> thanks a bunch
> Greetings,
> Ted
>