Hi
I'm relatively new to axis2 so I hope this question sounds sensible. I'm
using xmlbeans as a data binding for building axis2 services. I import
various (standard) schemas into the wsdl for describing the service
interface and some of these are also used by other developers on our
project who are also developing axis2 services. So, we want to generate
xmlbeans for these schemas directly and share these, i.e. by referencing
a single jar, instead of using each generating our own versions of the
same classes.
It seems the way to do this is with the external-mapping (-em) option
of wsdl2code. From the documentation my understanding is that to use
this you write a mapping file that maps every schema type (element,
type, attribute and group) to its generated java interface (<qname
namespace="ns" prefix="p1">localName</qname> <value>type</value> )
The problem is first, that the schema I'm importing is quite big (gml
for anyone familiar with it) so i don't really want to write out a long
mapping file by hand. Secondly, it's not always obvious what the
mapping is because the gml uses underscores sometimes in element names
(e.g. _Geometry) which are purged in the generation making a
semi-automated process cumbersome. Finally, it just doesn't really seem
sensible to write a mapping file by hand to describe a mapping that
another xmlbeans build generated.
I'm assuming this must be a common problem, so does anyone have any
experience using the externalMapping parameter (I'm wanting to build
with maven just to complicate matters), or know of a better solution? or
failing that, a way to generate the mapping file automatically, or at
least obtain a description of the mapping automatically while building
the beans that can be transformed later when building the service.
Cheers Alistair
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
