axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barry L Rogoff (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-3371) It would be VERY useful if WSDL2Java generated also Javadoc from schema and WSDL documentation elements
Date Tue, 08 Dec 2009 18:09:18 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787608#action_12787608
] 

Barry L Rogoff commented on AXIS2-3371:
---------------------------------------

> I still think this is rather an improvement than a bug...

The software fails to handle <documentation> tags correctly. If that doesn't qualify
as a bug in your lexicon, what does? Perhaps you're unaware of the fact that most software
development groups consider "improvements" to be "wish list" items such as additional features
and prioritize them as such. In other words, if you want this issue to have even the remotest
chance of being addressed before the sun becomes a red dwarf, I strongly urge you to promote
it to a bug.

> It would be VERY useful if WSDL2Java generated also Javadoc from schema and WSDL documentation
elements
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3371
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3371
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 1.3
>            Reporter: Mauro Molinari
>         Attachments: Create Cell Javadoc.png, Create Cell WSDL.png
>
>
> It would be EXTREMELY useful if WSDL2Java could take <xsd:annotation><xsd:documentation>...</xsd:documentation></xsd:documentation>
elements content relative to elements, types and enumeration in the schema, as well as <wsdl:documentation>...</wsdl:documentation>
elements content relative to services and operations, to generate Javadocs for skeleton, stubs
and ADBBeans.
> My raw proposed mapping is:
> - <wsdl:documentation> before <wsdl:types> => skeleton/stub class Javadoc
> - <xsd:annotation><xsd:documentation> for a defined root element/complex
type in the schema => ADBBean class Javadoc
> - <xsd:annotation><xsd:documentation> for a defined element of a complex
type in the schema => ADBBean method Javadoc and @param entries for skeleton/stub methods
> - <wsdl:documentation> for an operation => method Javadoc for skeleton/stub
methods
> - <xsd:annotation><xsd:documentation> for a defined enumeration value of
an extension of a type in the schema => properties Javadoc for the different instances
of the generated typesafe enum

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message