On 26/01/15 14:02, MayBee wrote:
Sergey Beryozkin wrote
The prefix name does not affect the namespace binding at all.
WADLGenerator will only use 'prefixN' if it auto-generates the grammar.
However you can control that by having a package-level info where a
preferred XMLSchema namespace prefix is set. WADLGenerator also has a
'namespacePrefix' property. This is all may needed only if you prefer to
customize the auto generation process, no need to do it if you link to
the external schemas
Sry for the last mail... I wanted to just preview ;)
I thought about the prefix referencing xsd types from any representation
into the grammars. Therefore I have not understood the generated prefixes.
Thus as I got you right, the prefixes in the representation@element
declarations are non-sense and do not refer to any grammar?
They do. It just does not make a difference that the inlined schema may
have different prefix names, because generally speaking the prefix names
are just aliases which bind a given name to a given namespace
Sergey
Kind Regards,
Malte
--
View this message in context:
http://cxf.547215.n5.nabble.com/included-xsd-s-are-not-resolved-for-wadl-generation-tp5753451p5753543.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
