Generating full path to @Element annotation

[4everalone]

See bulldog2011/nano#2

[bulldog2011]

Hi 4everalone:

Thx for your contribution!

I am thinking about adding some conditional logic in the template:
if dom element is imported, then use fully qualified @element annoation.

Will update the source and build a patch release tomorrow.

Thx!
-William

[bulldog2011]

Hi 4everalone:

I have updated the source on master and done basic test, please have a check.

Thx!
-William

[4everalone]

Thank you!

[bulldog2011]

Now both mxjc and mwsc zip packages have been re-built, you can download and have a try.

[4everalone]

I've tried. The problem still exist but in other kind of nature. My wsdl contains a complex type called "Element", as a result generated class "Element" conflicts with @element annotation :)
You may say that your project will not support such situtation, but this is a real problem which require to be fixed. I know you trying to write a nice code, but seems choosen name for annotation was a bad idea.
so there is tree way to resolve this:

1. Generate full path to annotation.
2. Continue fixing name conflicts.
3. Rename annotation.

As for me i'm choosing the first, because of not enough time.

I think you did a great job, please don't stop.

[bulldog2011]

Hi 4everalone:

Thanks for your suggestion!

I also found that the chosen name for annotations was ill-considered, depends on how many users have similar issue, I may rename the annotations in nano in next release, for example, add 'Nano' prefix to all annoations.

There is another option to resolve your issue, you can customize the class name generated by JAXB(on which mxjc built) using custom binding, see details here:
http://stackoverflow.com/questions/4793637/jaxb-how-to-change-xjc-generated-classes-names-when-attr-type-is-specified-in-x

Thx for your good feedback!
-William