Re: [bdbxml] Developing a local (Swing) front-end
"Mark R. Diggory" <mdiggory-Mahy8Y1M33PaZwrp7/[email protected]>
| Newsgroups | gmane.comp.db.dbxml.general |
|---|---|
| Message-ID | <[email protected]> |
I see this discussion and come back to the opinion that this is what the XMLDB api is really tuned to (http://xmldb-org.sourceforge.net). Basically, providing an API in Java for which drivers (analogous to JDBC) can be developed. There are already examples of Drivers that use XMLRPC for communication available if you review the eXist and Xindice codebases. Ultimately both support embedded and remote db instances. XMLDB in exist is delivered using standard XML-RPC and Servlet API's, so theres no reinvention there and it represents a good example for more native tooling. Theres no reason the same sort of remote server interface couldn't be delivered using C/C++ or whatever. This is elegant in that the XMLDB api already has hooks for extensions such as XQueryServices, XPath services which are considered Core functionality, and any driver can implement extended services on their db, for instance eXist provides an UserManagement service thats built into its implementation. I've been working on two little projects at the moment: 1.) A very generic XMLDB browser/manager for Eclipse/Java based somewhat on the Attrezzo Per Xindice (http://attrezzo.sourceforge.net/)which is an XMLDB based Eclipse Perspective that is dependent on Xindice. 2.) an XMLDB client to interact with embedded bdbxml instances for the above manager. I have very very limited time for both these projects at the moment and havn't yet released any of my development. IMHO BDBXML really needs an XMLDB API Client/Service implementation (even if its a separate project external to BDBXML). There are communities of OpenSource tools (Apache XML, Apache Cocoon, Spring etc) that are using XMLDB as means to provide Generic Sources of XML data to webapplications. Implement even just an embedded XMLDB client using the BDBXML java api and BDBXML becomes very attractive in those markets. -Mark Tom McCubbin wrote: > FIRST, I (and the 'others') are totally unconnected to Sleepycat, or any > official anything in regard to DBXML. > > That said, there was recently an issue w/ this very topic brought up ~1 > month ago. We decided to put together > a client/server layer that would extend DBXML for this purpose. A thin > layer to issue XPath, XQuery stuff, > etc. > > I am currently putting together the server side of things in C++, while > others will be making the java > client package. For iter #1, it will be embedded in SOAP transactions, > and details above and beyond > are still congealing. > > So, it this is for work, don't wait for us. If this is production, > don't wait for us. If you want to join us in our > mad adventure, i'm sure you'd be welcome. However, it'd be great if i > wasn't the only c++ guy, as > i haven't a clue re: the nitty gritty details of win32, or the > development platform, as my work is predominantly > focused on solaris/sparc, and now growing slowly more onto linux x86. > > That being sad, I have used dev-cpp/gcc on the win platform, and it > makes us unix people feel much more at > ease. I imagine most use the MS VisualXXX stuff though, and i am > clueless. It is so easy, i just don't get it:) > > -tom > > Breno Costa wrote: > >> Hi, >> >> I was developing a Web-based interface for acessing BDB XML >> containers, but now I need to switch to a swing-based desktop app. >> >> I'm just worried on network access of the containers, as BDB XML is >> embedded and has no servers. Network shares are an obvious solution >> but I dont think it's the best. >> >> Has anyone ever been in this same situation? >> >> thanks, >> >> -- Breno >> >> >> ------------------------------------------ >> To remove yourself from this list, send an >> email to [email protected] >> >> > > > > ------------------------------------------ > To remove yourself from this list, send an > email to [email protected] > ------------------------------------------ To remove yourself from this list, send an email to [email protected]