Geert, > The Xopus configuration does allow turning off validation (though an initial validation is still executed so it seems), but it won't do > without an XML Schema. Luckily it is easy to generate a temporary one using xquery.. ;-)
Xopus used to allow disabling validation on load, but now that configuration option only exists for backward compatibility. Xopus will always require an XML Schema and a valid XML document. We have made the choice to never ask our users to make an invalid document valid and we use the XML Schema and the valid XML structure of the document to guide the user while editing. Xopus offers most of its benefits in a environment with strictly enforced structure rules. Best regards, Laurens van den Oever Xopus BV 2009/9/10 Geert Josten <geert.jos...@daidalos.nl> > Laurens, all, > > > Thanks for your interest in our product. We are currently > > building an integration with MarkLogic for one of our own > > customers. In that case we use the Java API to connect to > > MarkLogic from a different server. A proof of concept > > implementation can be much simpler than that as Geert already > > pointed out. I have asked one of our developers to quickly > > build the small mockup Geert was referring to. > > > > The WebDAV API is only suitable for a load/save roundtrip > > optionally with locking. In addition you'll need a user > > interface for content management (create/delete documents, > > search for documents to edit, etc). > > Typically we use WebDAV when Xopus is integrated into a CMS > > which offers such user interface. In this case you either > > will have to develop that workflow or purchase a product > > which integrates both (like RSuite). For what kind of > > workflow are you planning to use Xopus? > > The last question is meant for Jakob, but people might be interested in my > use case as well. I was looking for a small XML editor that can be used > within a browser to manipulate XML documents within MarkLogic Server > databases directly. Some while ago Eric Palmitesta came up with a > scaffolding tool, that was basically a HTML form generated out of XML that > allowed some basic editing. But a real XML editor, especially as light > weight as Xopus, would be much nicer. > > Though Xopus can be fully configured for real editing, my use case is more > in the line of a development tool that allows debugging and fixing small > issues in XML documents within the databases directly. For similar reasons I > had developed a database browser earlier as well, which looks a lot similar > to the way you can browse SVN repositories through HTTP (in the simplest > way). It was easy enough to drop Xopus in a MarkLogic Appserver, and create > a SaveToXQY example. Making the Xopus 'island' dynamic was a bit harder, but > that hadn't really much to do with Xopus itself. It looks like I have things > working more or less now. > > Since this database browser was running on an HTTP Appserver the most > logical choice was to use HTTP to access documents from Xopus, using only a > few small helper xqueries. Accessing through WEBDAV is equally complex > though, but would require an additional Appserver; WEBDAVTools instead of > HTTPTools object of Xopus and slightly different JavaScript logic. > > Now, one of my problems was that I don't have an XML Schema for all my > documents. I know, bad practice, but I tend to be too lazy to add a > namespace to config files and such. Let alone creating XML Schemas for them. > The Xopus configuration does allow turning off validation (though an initial > validation is still executed so it seems), but it won't do without an XML > Schema. Luckily it is easy to generate a temporary one using xquery.. ;-) > > Kind regards, > Geert > > > Drs. G.P.H. Josten > Consultant > > > http://www.daidalos.nl/ > Daidalos BV > Source of Innovation > Hoekeindsehof 1-4 > 2665 JZ Bleiswijk > Tel.: +31 (0) 10 850 1200 > Fax: +31 (0) 10 850 1199 > http://www.daidalos.nl/ > KvK 27164984 > De informatie - verzonden in of met dit emailbericht - is afkomstig van > Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit > bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan > dit bericht kunnen geen rechten worden ontleend. > > > > _______________________________________________ > General mailing list > General@developer.marklogic.com > http://xqzone.com/mailman/listinfo/general >
_______________________________________________ General mailing list General@developer.marklogic.com http://xqzone.com/mailman/listinfo/general
