Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <1981500134.1217235361112.JavaMail.jira@brutus>
Date: Mon, 28 Jul 2008 01:56:01 -0700 (PDT)
From: "James Strachan (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-632) hack the XSD generator (patching
 JAXB's mvn plugin) so that the javadoc is included in the generated XSD as
 documentation
In-Reply-To: <2079584732.1214299740276.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44583#action_44583 ] 

James Strachan commented on CAMEL-632:
--------------------------------------

Yeah - I think we need to hack the RI code to fix this. We can submit a patch to them (they've been responsive in the past - I've submitted a number of patches in the past, particularly in the Java -> XSD generation part).

In a short term we could have our own custom build of the RI for XSD generation (which we did for quite a while - as I'd fixed a load of issues with the Java -> XSD generation).

So I'd say, lets 

* patch the RI code to fix this
* submit a patch to the RI
* we use our own build of the RI for XSD generation only - until the RI contains our patch

> hack the XSD generator (patching JAXB's mvn plugin) so that the javadoc is included in the generated XSD as documentation
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-632
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-632
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: James Strachan
>            Assignee: Jonas Lim
>             Fix For: 1.5.0
>
>
> In tools like Eclipse/IDEA there is smart completion when editing the XML with the XSD; however there's no documentation for elements/attributes.
> We should extract the JavaDoc from the Java code and include it into the generated XSD. There's an existing issue here...
> https://jaxb.dev.java.net/issues/show_bug.cgi?id=369
> as part of this we need to improve the javadoc too :)

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