Hi Ole, maybe you have encountered similar problems and can help: I ran upon some problems with wscompile when using complex types:
I import the schema-file using: | xmlns:orderTypes="urn-my-namespace/types" | .... | | <types> | <xs:schema elementFormDefault="qualified" targetNamespace="urn-my-namespace/types"> | <xs:import namespace="urn-my-namespace/types" | schemaLocation="http://localhost:8080/order/types/order.xsd"/> | </xs:schema> | </types> | and then construct a message using: | <message name="OrderRequest"> | <part name="request" element="orderTypes:order" /> | </message> | | <portType name="SignupPort"> | <operation name="signup" > | <input message="tns:OrderRequest" /> | <output message="tns:OrderResponse" /> | </operation> | </portType> | The wscompile works, but if generates a signup with an empty signature: | public interface SignupPort extends java.rmi.Remote { | public javax.xml.soap.SOAPElement signup() throws | java.rmi.RemoteException; | } | At least, I would have assumed a SOAPElement in the signature - at least, that's what is generated for a simple type like xs:string (but only if I use a type in the part, not an element...) Maybe you have a quick idea, what's going wrong here?! Thx for the help!! Cheers stf View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910072#3910072 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910072 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
