@XmlRootElement missing

  • Thread starter Thread starter Rock
  • Start date Start date
R

Rock

Hi,

What are the common errors that causes JAXB not to generate @XmlRootElement
tag into Proxy classes from wsdl that is created in .NET environment?

Are Java's and .NET's wsdl excatly same or are wsdl compilers working
differenty?

Any ideas?

Cheers,
 
Hi,

What are the common errors that causes JAXB not to generate @XmlRootElement
tag into Proxy classes from wsdl that is created in .NET environment?

Are Java's and .NET's wsdl excatly same or are wsdl compilers working
differenty?
Click to expand...

WSDL is WSDL, it's a W3C standard. But mappings of it to languages are
not part of that standard, and are defined by implementations. In
particular, there's no reason why standard mappings in Java and .NET
should be the same, or even similar.

So your question really boils down to: "why JAXB does not generate
@XmlRootElement for the WSDL given". Which is a question to a Java
forum or newsgroup, not this one.
 
WSDL is WSDL, it's a W3C standard. But mappings of it to languages are
not part of that standard, and are defined by implementations. In
particular, there's no reason why standard mappings in Java and .NET
should be the same, or even similar.
Click to expand...

Do want to bet? I have noticed hunred times that Companies are making
own extension to standards.
So I would not trust that "good old answer" it's a standard.

So your question really boils down to: "why JAXB does not generate
@XmlRootElement for the WSDL given". Which is a question to a Java
forum or newsgroup, not this one.
Click to expand...

This group has lot's of .NET developers that code software which use
Java Web Services.
That is a good point to ask especially here. This is an error that I
have also noticed.

-- udi
 
Hi,

What are the common errors that causes JAXB not to generate @XmlRootElement
tag into Proxy classes from wsdl that is created in .NET environment?

Are Java's and .NET's wsdl excatly same or are wsdl compilers working
differenty?

Any ideas?

Cheers,
Click to expand...

Actually, when using JAXB compiler xjc, generate wsdl with it and scan
proxy files
for XmlRootElement. Check that the main parameter class has it.

If I remember right I tried to use class that wasn't parent class of
message. I had derived message class from other class.

So, maybe there is actually nothing wrong.

- udi
 
Back
Top