You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Andreas Veithen <an...@gmail.com> on 2010/02/11 11:22:12 UTC
Generating Javadoc from xsd:sequence/xsd:element documentation
Dan,
I read your comment on JAXB issue 172 [1]. Did you ever get feedback
from the guy who said that he had an xjc plugin to generate
getter/setter Javadoc from xsd:sequence/xsd:element
annotations/documentations?
Andreas
[1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=172
Re: Generating Javadoc from xsd:sequence/xsd:element documentation
Posted by Craig Tataryn <cr...@tataryn.net>.
On a side note, I'm not sure if this is of use to anyone else but I
built an XJC plugin that allows you to have generated classes of your
choice extend or implement another class.
So for instance, we have a bunch of top level classes which are
generated by xsds, however they don't extend from a common type and we
don't have control over the schemas. So I tell the plugin that
certain classes should have a super type, and when the class gets
generated it winds up with a fresh implements or extends section
depending on the supertype chosen...
The format of the plugin's config file is:
super.type=generated.type1[, generated.type2, generated.type3,...]
In my case:
eclaims.model.EClaimsRequest=org.hl7.v3.FICRIN600106CA,org.hl7.v3.FICRIN620106CA,org.hl7.v3.FICRIN100206CA,org.hl7.v3.FICRIN600104CA,org.hl7.v3.FICRIN620104CA,org.hl7.v3.FICRIN100204CA
eclaims.model.EClaimsResponse=org.hl7.v3.FICRIN610106CA,org.hl7.v3.FICRIN610104CA,org.hl7.v3.FICRIN630106CA,org.hl7.v3.FICRIN630206CA,org.hl7.v3.FICRIN630104CA,org.hl7.v3.FICRIN630204CA,org.hl7.v3.FICRIN110306CA,org.hl7.v3.FICRIN110304CA
EClaimsRequest/Response are simply an interfaces (without any methods)
that allows us to pass those underlying generated HL7 types around to
our service methods instead of them accepting java.lang.Object. At
runtime, if need be, the type has to be checked if something special
needs to be done with it, but that could probably done smarter.
Craig.
On Thu, Feb 11, 2010 at 12:02 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Thu February 11 2010 5:22:12 am Andreas Veithen wrote:
>> Dan,
>>
>> I read your comment on JAXB issue 172 [1]. Did you ever get feedback
>> from the guy who said that he had an xjc plugin to generate
>> getter/setter Javadoc from xsd:sequence/xsd:element
>> annotations/documentations?
>
> Nope. :-( I'll follow up with another comment. Now that we've pulled
> the xjc plugins out into a subproject (I still need to update the web site),
> it should be easier to get contributions like this.
>
>
> Dan
>
>
>
>>
>> Andreas
>>
>> [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=172
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
--
Craig Tataryn
site: http://www.basementcoders.com/
podcast:http://feeds.feedburner.com/TheBasementCoders
irc: ThaDon on freenode #basementcoders, ##wicket, #papernapkin
twitter: craiger
Re: Generating Javadoc from xsd:sequence/xsd:element documentation
Posted by Daniel Kulp <dk...@apache.org>.
On Thu February 11 2010 5:22:12 am Andreas Veithen wrote:
> Dan,
>
> I read your comment on JAXB issue 172 [1]. Did you ever get feedback
> from the guy who said that he had an xjc plugin to generate
> getter/setter Javadoc from xsd:sequence/xsd:element
> annotations/documentations?
Nope. :-( I'll follow up with another comment. Now that we've pulled
the xjc plugins out into a subproject (I still need to update the web site),
it should be easier to get contributions like this.
Dan
>
> Andreas
>
> [1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=172
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog