Now, the compiler takes care of elements with anonymous complex types, but
ignores elements referring to public complex types which probably makes sense
but what does not make sense is that when generating the types only in this
latter case it omits the @XmlRootElement.
It is probably not quit
Are you sure you are using Log4J for CXF logging? (aka: followed instructions
at: http://cxf.apache.org/docs/debugging-and-logging.html to turn on log4j)
The formatting of that log looks more like the default j.u.l logging in which
case you would need to configure a logging.properties file for
On Wed February 24 2010 5:42:31 am Sergey Beryozkin wrote:
> Now, the compiler takes care of elements with anonymous complex types, but
> ignores elements referring to public complex types which probably makes
> sense but what does not make sense is that when generating the types only
> in this lat
Since you are mucking in code, if you create a binding customization file that
has a jaxb:globalBindings element with generateElementClass="true" attribute,
it will generate a class for the element. It's kind of an ugly class though
and possibly not really usable.
Dan
On Tue February 23 201
Hi Dan
This is useful, I may play with it later on, and the hint to do with causing anonymous types be created is something we can advise
to code-first users...I needed classes created from element for wadl:representation/@element values be resolved easier but I also
ended up creating a map of
On Tue February 23 2010 11:50:18 am Matt wrote:
> We are using WSDLToJava to build a web service. We have a simple type that
> is restricted to an enumeration. In the xml we define the order of the
> enumeration values. After the WSDLToJava the enumeration values are
> alphabetized in the .java
