Hiya,
I don't believe that XMLBeans has custom types, but I know that JAXB
does as well. You can use an aegis custom type with any other binding
though. XFire should be able to just see that there is a Type registered
for that class and use that custom type instead of an XMLBeans or JAXB Type.
- Dan
Frank Sweeney wrote:
Hi Dan,
Will any other type of binding solve the problem ... maybe xmlbeans ?
Regards
Frank
Dan Diephouse wrote:
Hi Frank,
Unfortunately this is a limitation with JAXB it seems, but I really
need to investigate further. The easy way around this is to create a
global schema <element> and not a <complexType> in your schema.
- Dan
Frank Sweeney wrote:
Hi there,
I have made a client stub generation (with binding = jaxb) of a
webservice also created with xfire. It automatically generates a
class of the imported complex type as seen below.
My question is that it seems to create the class with types of
JAXBElement<String> rather than that of type string, is there
anyway that I can get it generate a imported class with the java
types instead. As it makes using the class more difficult
Type long seems to be handled properly, it is strings and dates that
are set to these types
Regards
Frank
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
