Hi Jorge, On Mon, Feb 7, 2011 at 12:00 AM, Jorge Infante Osorio <[email protected]> wrote: > Hi Anjana. I glad to hear that you are fine. > For example, I don´t alter the order of the parameter, I just modified or re > save one of them and the order change.
Yeah you're correct, that is definitely a bug in the UI, I've created an issue here [1], and will be resolved soon. [1] https://wso2.org/jira/browse/CARBON-8613 Thanks and Regards, Anjana. > > This a query in a DS: > > <query id="query1" useConfig="CDAE"> > <sql>SELECT * FROM datos.id WHERE id = ?</sql> > <result element="ids" rowName="id"> > <element name="fecha_emision" column="fecha_emision" > xsdType="xs:date" /> > <element name="fecha_renovacion" column="fecha_renovacion" > xsdType="xs:date" /> > <element name="letra" column="letra" xsdType="xs:string" /> > <element name="serie" column="serie" xsdType="xs:string" /> > <element name="descripcion_objecion" column="descripcion_objecion" > xsdType="xs:string" /> > <element name="fecha_objecion" column="fecha_objecion" > xsdType="xs:date" /> > <element name="objecion" column="objecion" xsdType="xs:string" /> > </result> > <param name="id" paramType="SCALAR" sqlType="STRING" type="IN" > ordinal="1" /> > </query> > > And this is part of the XSD generated in the WSDL: > > <xs:complexType name="ids"> > <xs:sequence> > <xs:element maxOccurs="unbounded" minOccurs="0" > name="id" nillable="true" type="ns1:id" /> > </xs:sequence> > </xs:complexType> > > <xs:element name="ids" type="ns1:ids" /> > <xs:complexType name="id"> > <xs:sequence> > <xs:element name="fecha_emision" nillable="true" > type="xs:date" /> > <xs:element name="fecha_renovacion" nillable="true" > type="xs:date" /> > <xs:element name="letra" nillable="true" > type="xs:string" /> > <xs:element name="serie" nillable="true" > type="xs:string" /> > <xs:element name="descripcion_objecion" nillable="true" > type="xs:string" /> > <xs:element name="fecha_objecion" nillable="true" > type="xs:date" /> > <xs:element name="objecion" nillable="true" > type="xs:string" /> > </xs:sequence> > </xs:complexType> > > As you can see the order is fine. > > Now in the UI I make some change in the fecha_emision output element, and > then discard the change and save it again, so the DS is the same. But: > > <query id="obtenerDatosId" useConfig="CDAE"> > <sql>SELECT * FROM datos.id WHERE id = ?</sql> > <result element="ids" rowName="id"> > <element name="fecha_renovacion" column="fecha_renovacion" > xsdType="xs:date" /> > <element name="letra" column="letra" xsdType="xs:string" /> > <element name="serie" column="serie" xsdType="xs:string" /> > <element name="descripcion_objecion" column="descripcion_objecion" > xsdType="xs:string" /> > <element name="fecha_objecion" column="fecha_objecion" > xsdType="xs:date" /> > <element name="objecion" column="objecion" xsdType="xs:string" /> > <element name="fecha_emision" column="fecha_emision" > xsdType="xs:date" /> > </result> > <param name="id" paramType="SCALAR" sqlType="STRING" type="IN" > ordinal="1" /> > </query> > > As you can seenow , the output element fecha_emision go to the bottom and > this imply that the XSD in WSDL change as this: > > <xs:complexType name="ids"> > <xs:sequence> > <xs:element maxOccurs="unbounded" minOccurs="0" > name="id" nillable="true" type="ns1:id" /> > </xs:sequence> > </xs:complexType> > > <xs:element name="ids" type="ns1:ids" /> > <xs:complexType name="id"> > <xs:sequence> > <xs:element name="fecha_renovacion" nillable="true" > type="xs:date" /> > <xs:element name="letra" nillable="true" > type="xs:string" /> > <xs:element name="serie" nillable="true" > type="xs:string" /> > <xs:element name="descripcion_objecion" nillable="true" > type="xs:string" /> > <xs:element name="fecha_objecion" nillable="true" > type="xs:date" /> > <xs:element name="objecion" nillable="true" > type="xs:string" /> > <xs:element name="fecha_emision" nillable="true" > type="xs:date" /> > </xs:sequence> > </xs:complexType> > > If I have a client consuming this service, I need to modify it to avoid an > error of this type: > AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement > > The solution for me now is in the DS code move the fecha_emision element to > the right place. > A better solution will be that the position don´t change or have in the UI > the way to change the position again. > > Jorge. > > > -----Mensaje original----- > De: [email protected] [mailto:[email protected]] En > nombre de Anjana Fernando > Enviado el: domingo, 06 de febrero de 2011 7:43 > Para: [email protected] > Asunto: Re: [Carbon-dev] Session on DS wizard usability > > Hi Jorge, > > On Fri, Feb 4, 2011 at 11:54 PM, Jorge Infante Osorio <[email protected]> > wrote: >> Hi folks. >> >> Another usability recommendation for DS: >> >> In the output mapping configuration into the wizard: the order of >> element depend of the order they are put, when some modification occur >> in any of this elements, this order are alter, so change the wsdl of >> DS, if I put the DS behind a proxy service with a WSDL predefined this >> is a big problem with client side error due to a modification of DS. >> The solution is alter the order by code, because in the UI don´t exist > this option. > > I do not get the idea of alter the order by code, can you elaborate more on > that please. Because, fundamentally, if you change the order of the > parameters, or add a new parameter to an operation call, the WSDL must > change, and the client must be changed according to that. > > Cheers, > Anjana. > >> >> Jorge. >> >> De: [email protected] [mailto:[email protected]] >> En nombre de Afkham Azeez Enviado el: viernes, 04 de febrero de 2011 >> 10:09 >> Para: carbon-dev >> Asunto: [Carbon-dev] Session on DS wizard usability >> >> I'd like to have this session early next week with Anjana et. al, and >> it will also be good for the tooling folks to be there. I want to do >> this while it is fresh on my mind. >> >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; >> http://wso2.com, Member; Apache Software Foundation; >> http://www.apache.org/ >> email: [email protected] cell: +94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> Lean . Enterprise . Middleware >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > Anjana Fernando > Software Engineer > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Anjana Fernando Software Engineer WSO2, Inc.; http://wso2.com lean.enterprise.middleware _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
