Hello, I hope you enjoyed your holidays, I've tried to simplify the XML schema removing types, groups and elements that are not necessary. Thanks in advance,
Werner Guttmann wrote: > > Sure, plenty of ideas, but in the meantime myself (and others) have been > taking holiday (it's summer time after all), etc. > > In addition, as already mentioned a few times, the complexity of your > XML schema is simply to high to showcase the problem at hand. If you > want us to assist you (in our spare time, that is), please take some (of > your) time and break the XML schema down to something minimal, and > remove everything else. > > Otherwise, please do consider taking up professional services where any > of us (committers) will be able to assist you in our professional (day) > time. > > Regards > Werner > > Paco Sanchez wrote: >> No ideas ?? >> >> >> Paco Sanchez wrote: >>> Someone have tested this and get the same error? >>> Thanks. >>> >>> >>> Paco Sanchez wrote: >>>> Sorry Werner, there are one error in xml sample. The value for element >>>> <peticion> was wrong. The correct value is "FirmaServidor". If you see >>>> the schema definition <mensajeSalida/respuesta/Respuesta> you can see >>>> that is a choice from several groupid's (resultadoValidarFirma, >>>> resultadoFirmaServidor,resultadoFirmaServidorCoSign, ...). The only one >>>> that is unmarshalling OK is 'resultadoValidarFirma'. With the others, I >>>> allways get the error I described in the first post. >>>> If you drill down >>>> <mensajeSalida/respuesta/Respuesta/resultadoFirmaServidor> you find >>>> that >>>> through the group reference 'resultadoGeneral' you get the element >>>> 'estado' and the element 'descripcion'. >>>> >>>> Any ideas? >>>> Thanks in advance, >>>> >>>> >>>> >>>> Werner Guttmann wrote: >>>>> Just looking at some XML schema artifacts, it looks like <descripcion> >>>>> cannot be of type text in this context of the sample message. >>>>> >>>>> Drilling down from <mensajeSalida/respuesta/Respuesta> in your case, >>>>> you'll find that through the group reference to the group definition >>>>> >>>>> resultadoValidarFirma >>>>> >>>>> there#s a 'descripcion' element, but not of type 'xs:string'. I hope >>>>> this helps. >>>>> >>>>> Regards >>>>> Werner >>>>> >>>>> >>>>> Paco Sanchez wrote: >>>>>> Hi , >>>>>> I've generated the java classes from one xsd using the ant task. I've >>>>>> I >>>>>> use >>>>>> the castor-anttask 1.2 with a binding file. When I try to unmarshall >>>>>> some >>>>>> xml I get the error >>>>>> >>>>>> "Illegal Text data found as child of: descripcion value "Proceso >>>>>> terminado correctamente" >>>>>> >>>>>> I've attached the xsd, the binding file and one xml sample file. >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> http://www.nabble.com/file/p18524517/ws.xsd ws.xsd >>>>>> http://www.nabble.com/file/p18524517/binding-firma.xml >>>>>> binding-firma.xml >>>>>> http://www.nabble.com/file/p18524517/MensajeSalidaEjemplo.xml >>>>>> MensajeSalidaEjemplo.xml >>>>>> >>>>>> >>>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>>> >>>>> >>>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > http://www.nabble.com/file/p19408723/ws.xsd ws.xsd -- View this message in context: http://www.nabble.com/Illegal-Text-data-found-as-child-of%3A-tp18524517p19408723.html Sent from the Castor - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
