Java Class not generated by jax-ws Weblogic 10.3 if empty xs:enumeration

Question

Hi everyone!
I discovered tricky problem. I've defined
     <xs:simpleType name="MyType">
          <xs:restriction base="cm:ValidStringType">
               <xs:enumeration value="TRG"/>
               <xs:enumeration value="TRM"/>
               <xs:enumeration value="TMP"/>
               <xs:enumeration value="TMV"/>
               <xs:enumeration value="SFL"/>
               <xs:enumeration value="PRQ"/>
               <xs:enumeration value=""/>               
          </xs:restriction>
     </xs:simpleType>
in some.xsd where
<xs:simpleType name="ValidStringType">
<xs:restriction base="xs:token">
<xs:pattern value="([A-Z\p{S}\p{P}\d\s]){0,255}"/>
</xs:restriction>
</xs:simpleType>
Problem is MyType.java is not generated now at all.
But if I remove last entry <xs:enumeration value=""/> when the class gets generated.
We are migrating from Weblogic 9.2 Java 1.5_11 and jaxrpc into
Weblogic 10.3 jdk 1.6_14 and jaxwc-2.0.jar.
Is that a bug in weblogic.wsee.tools.anttasks.WsdlcTask? I use it to generate source code files.
Or jax-ws 2.0 has some limitations that <xs:enumeration value=""/> is not supported?
So any ideas how to fix my situation?
Here is the part of my build.xml
<taskdef name="wsdlc" classname="weblogic.wsee.tools.anttasks.WsdlcTask" classpath="${wl103.dir}/server/lib/weblogic.jar"/>     
          <wsdlc verbose="on"
               srcWsdl="${basedir}/../definitions/wsdls/mywsdl.wsdl"
          destJwsDir="${comp_wsdl.dir}"
          destImplDir="${generated.sources.dir}"
               type="JAXWS">
               <binding dir="${basedir}" includes="${binding.files}"/>               
     </wsdlc>
Note all paths are correct.
Thanks a lot
Igor
Edited by: user461997 on Jun 19, 2009 1:54 PM

Answer 1

That's a problem.
Other classes just complain that MyType class was not found.
MyType.java file simply was not generated by wsdlc ( classname="weblogic.wsee.tools.anttasks.WsdlcTask ).
There is no direct messages giving clue why MyType.java file was not generated.
Is any verbose, diagnostic to turn on etc. tricks to get more generation process info?
Are anywhere good articles reviling in-depth the process of generating java source code files by WsdlcTask and using javax.jws_2.0.jar
in my case?
For me it's an emergency. So if anybody can give some ideas?
Is that a bug in weblogic.wsee.tools.anttasks.WsdlcTask which does not like empty xs:enumeration value="" ? I use it to generate source code files.
Or jax-ws 2.0 has some limitations that <xs:enumeration value=""/> is not supported?
Thanks a lot
Igor
Edited by: user461997 on Jun 22, 2009 7:10 AM