Thanks Amila, thanks Robert. I found the problem, it isn´t a bug.
I used XStream for transform schema domain objects to ResponseDocument.
XStream generates the xml representation:
content
content
content
and response looks like this:
...
content
content
content
On 10/16/07, robert lazarski <[EMAIL PROTECTED]> wrote:
>
> What version of axis2 are you using? If not using 1.3, try upgrading
> to that if possible. This seems like an old bug.
if error is there with axis2 1.3 please try with a nighly build.
If you are using axis2 1.3, try pasting your code
What version of axis2 are you using? If not using 1.3, try upgrading
to that if possible. This seems like an old bug.
If you are using axis2 1.3, try pasting your code and wsdl and maybe
someone can help.
Robert
On 10/16/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
> Hi.
> I´m usin
Hi.
I´m using XMLBeans data binding. I receive the response Document and I do
Foo f = response.getFooResponse().getReturn();
Foo has an attribute named foo and
f.getFoo() returns null, but f.toString() return a string which contains the
correct xml (with foo attribute fixed).
¿Why f.getFoo() re
