What is the problem that .NET/Python clients run
into ?
If you don't want to modify your schema, use an external
customization file ( similar to
http://forums.java.net/jive/thread.jspa?threadID=22576&tstart=15 ).
jaxb:javadoc was added because sometimes it may not be possible
and/or desirable to modify the schema (e.g. industry standard schema).
In such cases, you can still use an external customization file and generate
javadoc using the JAXB customization.
annotation/documentation is not disallowed by the spec.
Sekhar
Ingo Siebert wrote:
> Thank you Sekhar.
>
> But i don't want to added elements of the JAXB namespace, because my
> web serivce is called by .NET and Python.
>
> Why has the property jaxb:javadoc been created, if an
> annotation/documentation element is already available?
> I think annotation/documentation should be supported as well.
> This should be changed, what do you think?
>
> Cheers,
>
> Ingo
>
>
> Sekhar Vajjhala schrieb:
>
>> This is already supported.
>>
>> Use the JAXB customization <jxb:javadoc>.
>> <jxb:javadoc> has been present since JAXB 1.0 and is mandated by
>> the JAXB spec.
>>
>> <xsd:complexType name="TransferableDataObject">
>> <xsd:annotation> <xsd:appinfo>
>> <jxb:class>
>> <jxb:javadoc> JAVADOC ONE </jxb:javadoc>
>> </jxb:class>
>> </xsd:appinfo></xsd:annotation>
>>
>> <xsd:sequence>
>> <xsd:element minOccurs="1" maxOccurs="1" nillable="true"
>> name="objectType" type="xsd:string" >
>> <xsd:annotation> <xsd:appinfo>
>> <jxb:property>
>> <jxb:javadoc> JAVADOC TWO </jxb:javadoc>
>> </jxb:property>
>> </xsd:appinfo> </xsd:annotation>
>> </xsd:element>
>> </xsd:sequence>
>> </xsd:complexType>
>>
>> </xsd:schema>
>>
>> JAVADOC TWO will be generated for both getter/setter.
>>
>> Sekhar
>>
>> Ingo Siebert wrote:
>>
>>> Hi,
>>>
>>> i wrote a WSDL and some XSDs for my web service.
>>>
>>>
>>> WsImport generates the classes and all beans for me, but i'm missing
>>> JavaDoc comments.
>>>
>>> That's a snippet of my XSD:
>>>
>>> <xsd:complexType name="TransferableDataObject">
>>> <xsd:annotation>
>>> <xsd:documentation>JAVADOC ONE</xsd:documentation>
>>> </xsd:annotation>
>>>
>>> <xsd:sequence>
>>> <xsd:element minOccurs="1" maxOccurs="1" nillable="true"
>>> name="objectType" type="xsd:string" >
>>> <xsd:annotation>
>>> <xsd:documentation>JAVADOC TWO</xsd:documentation>
>>> </xsd:annotation>
>>> </xsd:element>
>>> ...
>>>
>>>
>>>
>>> If i look at the generated classes, only "JAVADOC ONE" is included
>>> as JavaDoc comment, but "JAVADOC TWO" is missing.
>>>
>>> I think the comment "JAVADOC TWO" should appear at the getter and
>>> setter of the property.
>>> What do you think?
>>>
>>> Cheers,
>>>
>>> Ingo
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
>>> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
>> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>