Perhaps if that was supported by JAXB|Castor whatever... but then the config for that component now depends on XML too.
I don't know very much about the details of schema or namespace usage... only what I have picked up from scanning through various docs. Any other insight would be helpful. --jason Hiram Chirino wrote: > > Would using a seperate namespace in the XML snipplet help with > defining a schema?? > > Regards, > Hiram > >> From: Jason Dillon <[EMAIL PROTECTED]> >> To: [EMAIL PROTECTED] >> Subject: [JBoss-dev] XML snippet, JAXB|Castor & Schemas (oh my) >> Date: Fri, 08 Mar 2002 21:22:43 -0800 >> >> I looked into Castor a little bit more today... specificially trying to >> see if there was and documented way to treat a block of xml as a type. >> It does not appear to be the case... which does not really surprise me. >> I started looking for other such JAXB|Castor-like things, but I >> stopped, thinking that most tools will do the same. >> >> I suppose we could implement something like Ant, to use reflection to >> create a model from XML... but perhaps there is an easier way? I think >> there is, not with out issues, but a better way to handle this. >> >> Embedding an XML snippet is really easy, but makes it rather impossible >> to define a schema for the service.xml files (perhaps there is some >> schema directive for this, I don't know... so I am going on what I do >> know). I sugest that a better aproache would be to configure the >> snippet from a URL. >> >> I personally would like to find a way to keep the snippet, but I think >> that we may be better off using someone else's xml->object generator and >> providing a schema to validate the xml against. >> >> The obvious draw back to this is, well, more files. Though not a huge >> number of files. For .sar usage, the resource:// protocol can be used >> to pull out a config from the containing file. Target components would >> then take that url and unmarshal there configuraion model from it (and >> then invoke the proper configure method with that model, so xml is not >> required to configure) or they can simply parse it and get an Element. >> >> It seems like this is the simplest way to get to non-xml specific >> configuration by using thirdparty tools. >> >> The downside is more files... which sucks, but I think that we can >> probably make that a mute point with the adition of an easy to use >> configuration manager service. Which would basically hide all of the >> details of files behind a simple web interface, thus allowing ease of >> configuration, by simulating xml snippets in a webpage, but underneith >> managing some files. That I will leave for future descussion... as the >> usage of NetBoot becomes more common place for large distributions of >> JBoss nodes something like this will really blow peoples minds... >> >> --jason >> >> >> _______________________________________________ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > _________________________________________________________________ > Send and receive Hotmail on your mobile device: http://mobile.msn.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
