I didn't try wscompile. I used option -uliteral in java2WSDL and deployed to JBoss 4.0.1 again, the problem remains same.
the signature of the service has the following format:
String  method1( arg1, arg2);
I think the type of ArrayOf_xsd_string is generated to reflect return type String by java2WSDL. Maybe this problem could be sovled by wrapping the String  into a class. I really want to reuse the exisitng code.
in the WSDL file the target namespace of ArrayOf_xsd_string is targetNamespace="http://wsdl.phaselc.org". does it prevent Jboss from using java.lang.String? any setting in the mapping file or other descriptor files or configration files could help Jboss to deal with it correctly?
hope to get response again and thanks in advance!
I am having this same problem on Jboss4.0.2RC1, although I also am using the Java2WSDL pacakge as well.
The WSDL for the complex type looks fine regardless of the tool used to generate it (and confirm same problem with ArrayOf_xsd_dateTime).
y_zl, have you found a workaround or solution for this yet?
3. Don't use java2WSDL, use wscompile (included in the Sun JWSDP)