6 Replies Latest reply on Mar 5, 2006 10:00 AM by Thomas Diesler

    differences between wscompile and jbossws type name mapping

    Andrew Veliath Newbie

      I'm new to the JBossWS layer, and have run into the following issue with anonymous type name mapping (perhaps it is a result of the new JSR). As an example, try the following wsdl file from Google's APIs (just enough info to show the issue):

      https://adwords.google.com/api/adwords/v3/InfoService?wsdl

      Inside here is the following anonymous type:

       <element name="getOperationsQuotaThisMonth">
       <complexType/>
       </element>
      


      Now, wscompile generates the following type mapping for it:

       <java-xml-type-mapping>
       <java-type>google.GetOperationsQuotaThisMonth</java-type>
       <root-type-qname xmlns:typeNS="https://adwords.google.com/api/adwords/v3">typeNS:getOperationsQuotaThisMonth</root-type-qname>
       <qname-scope>complexType</qname-scope>
       </java-xml-type-mapping>
      


      Note wscompile from jwsdp 2.0 does not generate this as an "anonymous-type-qname" (I am not sure why). However, JBossWS treats this as an anonymous-type-qname when reading the wsdl file and then fails to look up:

      org.jboss.ws.WSException: Cannot obtain java type mapping for:
      {https://adwords.google.com/api/adwords/v3}>getOperationsQuotaThisMonth
      


      because it is stored I think in the org.jboss.ws.metadata.TypesMetaData without the ">" as:

      {https://adwords.google.com/api/adwords/v3}getOperationsQuotaThisMonth
      


      Anyone have any ideas on why these are different? Would it be better to just switch to wstools?

      Andrew