I'm trying out BaseX and am interested in having the HTTP server serve up static pages which can then access the REST interface to BaseX from the same host and port.
I saw there was a previous discussion about JSONP to hack around the same-origin policy, but I'd like to use XML and other tools I already have, so I'd like to put in a bunch of static files (Javascript, CSS, XSL, PNG, etc) and have the built-in Jetty serve them up conveniently from a single, easily-reached URI route.
I've been through the documentation and the basex-talk list for recent posts and didn't see anything about this.
Thank you, Leigh.
Leigh,
thanks for your email! You might have a look at a small project I recently started, that might suit your needs. It is still really bare-bones + work in progress, but feel free to give it a try: https://github.com/micheee/xquery-webapp-skeleton
Apart from that you might have a look at db:retrieve [1] which will be fine as well to serve some static contents.
Hope this helps Michael
[1] http://docs.basex.org/wiki/Database_Functions#db:retrieve Am 17.11.2011 um 19:14 schrieb Leigh L Klotz Jr:
I'm trying out BaseX and am interested in having the HTTP server serve up static pages which can then access the REST interface to BaseX from the same host and port.
I saw there was a previous discussion about JSONP to hack around the same-origin policy, but I'd like to use XML and other tools I already have, so I'd like to put in a bunch of static files (Javascript, CSS, XSL, PNG, etc) and have the built-in Jetty serve them up conveniently from a single, easily-reached URI route.
I've been through the documentation and the basex-talk list for recent posts and didn't see anything about this.
Thank you, Leigh.
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
Am 17.11.2011 um 19:14 schrieb Leigh L Klotz Jr:
I'm trying out BaseX and am interested in having the HTTP server serve up static pages which can then access the REST interface to BaseX from the same host and port.
I saw there was a previous discussion about JSONP to hack around the same-origin policy, but I'd like to use XML and other tools I already have, so I'd like to put in a bunch of static files (Javascript, CSS, XSL, PNG, etc) and have the built-in Jetty serve them up conveniently from a single, easily-reached URI route.
I've been through the documentation and the basex-talk list for recent posts and didn't see anything about this.
Thank you, Leigh.
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
Dear Leigh,
just a short supplement to Michael's mail: you can have a look at our WAR archive, which can be embedded in a servlet context: this way, you can talk to REST and WebDAV and use Jetty (or Tomcat, etc) for other purposes as well.
Hope this helps, Christian ___________________________
On Thu, Nov 17, 2011 at 7:14 PM, Leigh L Klotz Jr leigh.klotz@xerox.com wrote:
I'm trying out BaseX and am interested in having the HTTP server serve up static pages which can then access the REST interface to BaseX from the same host and port.
I saw there was a previous discussion about JSONP to hack around the same-origin policy, but I'd like to use XML and other tools I already have, so I'd like to put in a bunch of static files (Javascript, CSS, XSL, PNG, etc) and have the built-in Jetty serve them up conveniently from a single, easily-reached URI route.
I've been through the documentation and the basex-talk list for recent posts and didn't see anything about this.
Thank you, Leigh.
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Leigh L Klotz Jr -
Michael Seiferle