Hello Jeremy and other woden devs, and thanks for being so concerned about my problem ! I think that Woden is already very useful and well tough despite the XMLSchema issue.
IMHO it's worst to rely on a specific XML Schema technology than on a particular XML representation/parsing system (DOM, SAX,...). Because as soon as a generic-xml parsing technology has been defined you can always provide access-points in the API for people to plug their own domain-specific parsers (like JaxMeXS for XML-Schemas for example). And this way you will automatically be able to handle non-XML extension type systems. XML Schema seems like a good API to me, but it's clearly limited and I didn't see any recent activity on the project page... But I also tend to think that a lot of people are currently using the extensibility capabilities of XML Schema (which the ws-commons xmlschema API fails to handle) and will use the extensibility elements of WSDL 2.0 (already handled by Woden)... I need to use both :-) If you are able to give me access to a getSchemaElement() method, I'll have first to check if it's possible to inject the DOM element object into an other XML-Schema parser (like JaxMeXS). If you choose to fix XmlSchema, it would be a great idea to temporarily add the getSchemaElement() method until XmlSchema is fixed :-) I'm sure I will be able to retrieve the needed information from within the DOM Element on way or another. It will always be better than the current situation where I have no way whatsoever to access this information. -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Jeremy Hughes Envoyé : jeudi 6 juillet 2006 15:40 À : [email protected] Objet : Re: TR: how to retrieve element information from XmlSchemaElement Hi Pierre, On 7/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi jeremy, > > I didn't get any answer for the commons-dev mailing list. But from what I > have seen in the API doc of XMLSchema, you're totally right: there is no way > to access attributes that aren't in the schema namespace. > > But I just can't throw away woden for that, good please don't - Woden is in incubation so is very much under development, both from a code and community point of view, so we value your input. > so I guess the only solution is to provide me with the raw XML-Schema type > declaration referenced frow within the WSDL declaration. This way I could > inject this xml segment in an other XML Schema parser. Do you mean you'd like the DOM Element object. ie. add public Element getSchemaElement(); method to the org.apache.woden.schema.Schema interface. The difficulty is we've tried to steer clear of relying on any one particular XML parsing technology - DOM vs SAX vs StAX. The irony now is we've hardcoded to XmlSchema as our schema API and that isn't up to what you need. Perhaps you don't mind whether you have a DOM Element object or something from the SAX or StAX world - but in any of these cases we would be introducing a dependency in the Woden API on one parsing technology. What I would prefer to do is fix XmlSchema. > > Is it possible ? Perhaps we could add the getSchemaElement() method to help out Pierre until we fix XmlSchema ... what do the other woden-devs think? Cheers, Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
