Hello, Does anyone know if it's possible to setup the code generation in a way that will not generate the types folder for simple types -
For example, the following partial xsd (from oasis): ... ... <xsd:schema targetNamespace="http://com.xyz.schema/oasis/codelist" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ccts="http://com.xyz.schema/oasis" xmlns:clm66411="http://com.xyz.schema/oasis/codelist/unitcode" <xsd:simpleType name="UnitCodeContentType"> <xsd:restriction base="xsd:token"> <xsd:enumeration value="04"> <xsd:annotation> <xsd:documentation> <ccts:CodeName>small spray</ccts:CodeName> <ccts:CodeDescription></ccts:CodeDescription> ... ... And using a castorbuilder.properties mapping file (partial shown) with: org.exolab.castor.builder.nspackages=http://com.xyz.schema/oasis/codelis t=com.xyz.schema.oasis.codelist Instead of generating the UnitCodeContentType.java file into com.xyz.schema.oasis.codelist, it generates into com.xyz.schema.oasis.codelist.types. I'm using the same xsd files with Oracle wsa tool to generate web-services, and it is unable to find the generated java file since it's not in the correct package - it's looking for them in com.xyz.schema.oasis.codelist as specified by the namespace. I need some way to prevent the types folder from being created, but can't see how unless I modify the xsd not to use simple types. Thanks for your help, Roger IMPORTANT NOTICE Email from OOCL is confidential and may be legally privileged. If it is not intended for you, please delete it immediately unread. The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in doing so. Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email. Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email

