I would like to use this thread to discuss issues seen in matching the 
functionality provided by jbossws with that of 'wscompile' tool of Sun's JWSDP.

A reference is the JIRA issue [JBWS-147]
http://jira.jboss.com/jira/browse/JBWS-147

Background:
jbossws will be a tool that will provide ws artifacts just as wsdl, SEI, SE, 
mapping files etc.

Some of my observations about wscompile (with  -f:wsi)
1) Generates Java classes only for the types defined in the  in , that are 
defined as the types used by the message parts. So if the schema defines 10 
complex types and the message parts define 5 types only, wscompile generates 5 
Java classes.  Fair to me!

2)  In the following schema

  | <schema targetNamespace='http://org.jboss.ws/types'
  |   xmlns='http://www.w3.org/2001/XMLSchema'
  |   xmlns:xsi='http://www.w3.org/2000/10/XMLSchema-instance'
  |   xmlns:xsd='http://www.w3.org/2001/XMLSchema'
  |   xmlns:tns='http://org.jboss.ws/types'>
  | 
  |   <xsd:complexType name="Address" >
  |   <xsd:sequence>
  |     <xsd:element name="name"   type="xsd:string"/>
  |     <xsd:element name="street" type="xsd:string"/>
  |     <xsd:element name="city"   type="xsd:string"/>
  |     <xsd:element name="state"  type="xsd:string"/>
  |     <xsd:element name="zip"    type="xsd:decimal"/>
  |   </xsd:sequence>
  |   <xsd:attribute name="country" type="xsd:NMTOKEN" fixed="US"/>
  | </xsd:complexType>
  | 
  | 
  |   <xsd:complexType name="PurchaseOrderType">
  |   <xsd:sequence>
  |       <xsd:group   ref="shipAndBill"/>
  |       <xsd:element name="singleUSAddress" type="Address"/>
  |     <xsd:element ref="comment" minOccurs="0"/>
  |     <xsd:element name="items"  type="tns:Items"/>
  |   </xsd:sequence>
  |   <xsd:attribute name="orderDate" type="xsd:date"/>
  | </xsd:complexType>
  | 
  | <xsd:group name="shipAndBill">
  |   <xsd:sequence>
  |     <xsd:element name="shipTo" type="Address"/>
  |     <xsd:element name="billTo" type="Address"/>
  |   </xsd:sequence>
  | </xsd:group>
  | </schema>
  | 

wscompile throws an error

  | error: modeler error: model error: invalid element: "group"
  | 

So basically it does not support xsd:group.  
Question:  Is this construct important?

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871374#3871374

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871374


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to