Hi Christian,
On 06/06/2015 02:39 PM, Christian Grün wrote:
Hi Ioan,
Just recently, there has been some discussion on Tomcat and BaseX on the mailing list. I think we managed to successully encounter various of the problems with Tomcats in the latest snapshot [1], so I will be interested in hearing more about your experiences with that version.
Sorry for my english expressing, which unfortunately are not helped me to be well understood!
I carefully watched to all recent discussions on the list, but what is of interest to us is different. I have seen that in these cases it is intended that each application to use a new instance of BaseX. And, on the same Tomcat, to use multiple separate instances of BaseX.
And, in general, I have seen that BaseX is used dedicated for a single application (very suitable for embeded), and used separated instances for other applications. But in our case is exactly the opposite.
We have some experience with web applications on Tomcat, made with JSP / Servlets and relational databases. The structure of the applications installed on web server looks like:
-webapps -app1 -app2 -app3
Each application is developed and deployed separately, as an war archive, having everything it needs inside.
We try to use BaseX in this way to access data directly in XML format. The structure should be something like:
-webapps -basex -bxapp1 -xqrepo1 -bxapp2 -xqrepo2 -bxapp3 -xqrepo3
We managed to make this model functional only if all 3 repositories we have put them together: or directly under BaseX, or in a separate application and setting according to this the path in context-param/restxqpath in web.xml.
But we want it so that each application to contain they repo. How?
It would be possible to set in web.xml, to restxqpath, a list of several repo? Or from somewhere to be told from where to load such a list? Maybe this would be an easier solution. It implies some security problems or other constraints? We looked a bit by sources, but not have identified which part it handles this.
Is welcomed any other idea.
Regarding CACHERESTXQ and .ignore: These features are already available in that snapshot as well (but they will only be officially announced with 8.3). Unless you don't build more complex RESTXQ applications, you won't probably need to care about these features.
Hope this helps, Christian
We tried this last version and, indeed, for what we want does not help us.
Many thanks for your understanding!
Ioan