From: Sebastian B. <sb...@jb...> - 2004-08-05 13:29:36
|
On Thursday 05 August 2004 20:00, Wolfgang Meier wrote: > Hi Sebastian, > > Great. I really would like to see these features as part of eXist. > > > > Alas the code of Castor is ugly too ... however I used Castor > > > successfully in 2 projects. > > > > I would prefer to have own implementations. Possible generated > > (using one of the Java-to-XML bindings you mention below. > > It would certainly be nice to have a good schema representation api > in eXist, as we will probably need it in other places too. I don't > know enough about castor's api, but I see you already have some > additional classes in parts/ which duplicate the castor classes? Those classes in o.e.schema.parts are not quite standard as they are used for the schema generator (which uses an intermediate language a bit different from XML Schema). They also lack the ability to be created from XML instance data. And of course they don't represent XML Schema fully. I think it would be best to run a XML-to-Java binder over the schema for XML Schema (http://www.w3.org/TR/xmlschema-1/#normative-schemaSchema), that way we can be fairly certain not to forget the fine points. > > Concerning the qnames: where can I find javax.xml.namespaces.QName? eXist-1.0/lib/optional/axis-jaxrpc-1.1.jar ;-) > Maybe we can have org.exist.dom.QName subclass that class, so you > won't need to convert it all the time. That's a dangerous endeavor. Looks simple at first glance, but the parameters (localpart and namespace) of the constructor are reversed. We would need to be very careful. And it will touch almost every file in xquery.* and many more. But you are right, it might be a good time to do this. Sebastian > > Wolfgang |