Hi Cristina,
Why you have to use @XmlSeeAlso?
I don't have a workaround solution, but if it's possible, you can send
me the test case.
If you must use the annotation, then currently you have to choose JAXWS RI.
Regards,
James
Hi James,
Thanks for your reply.
I tried using the latest 2.1-incubator-snapshot version of cxf-bundle and it
seems like it's still using the JAXWS2.0 and JAXB2.0. If the upgrade of
versions will be done in the 2.1 final release, can you suggest any
workaround that I could do for now?
Thanks,
Cristina Malonzo
James Mao wrote:
If I remember correctly, @XmlSeeAlso is defined in the JAXWS2.1
(JAXB2.1) spec, right? currently we only support JAXWS2.0 (JAXB2.0)
And we will support JAXWS2.1 in the 2.1 final release
Cheers,
James
Hi all,
I just want to know if latest snapshot uses vesion 2.1 of both jaxb and
jaxws.
Here goes my problem. I had created a web service using code-first
approach.
Some of my model beans have the annotation @XmlSeeAlso. I used java2wsdl
goal to generate the wsdl file. Now, a client does wsdl2java to get the
sources for the services. I noticed that the generated java code doesn't
contain the annotation @XmlSeeAlso. I'm not sure exactly what happened
here
but this is what i think (just a hunch =^D). During the java2wsdl goal,
cxf
didn't recognize the @XmlSeeAlso annotation. So the resulting wsdl file
doesn't include the necessary elements/values/attributes so that when a
wsdl2java goal is invoked on the said wsdl file, no @XmlSeeAlso
annotation
is written.
I've used version 2.1-incubator-SNAPSHOT of cxf-bundle already and
nothing
has changed with the generated sources. I read in this forum that the
upgrade of versions is already being taken into consideration.
If you could suggest a workaround for this, that would be so much
appreciated. =^D
Thanks in advance,
Cristina Malonzo
