Seenivasan,
got it.. So the problem was that the addressed query module (http://.../restxq/example) did not exist in your scenario, right?
I've uploaded a new stable snapshot that includes a fix. It will return a header and the error message as second item instead of the error message:
http://files.basex.org/releases/latest/
Looking forward to your feedback, Christian ___________________________
Christian Grün Box 188, Uni KN D-78457 Konstanz www.christian-gruen.de
On Tue, Jul 31, 2012 at 6:07 PM, Seenivasan Gunabalan seenivasan.gunabalan@dedalus.eu wrote:
Hi Christian, Thanks for the link. I will go through it.
to help you, I still need some more concise information..
did you download 7.3 or the latest snapshot?
i downloaded 7.3 and not the snapshot..how did you start the http server?
./basexhttpwhich os are you using?
Ubuntu 11.10 Java-7-openjdk-i386Thanks and Regards, Seenivasan
On 07/31/2012 05:32 PM, Christian Grün wrote:
Hi Seenivasan,
I downloaded a fresh copy of basex and ran the request query that was in my previous email, yet facing the same issue. [...]
to help you, I still need some more concise information..
- did you download 7.3 or the latest snapshot?
- how did you start the http server?
- which os are you using?
Just as a curiosity, it would be very helpful, if you could provide me an link/reference to know more about why
The main reason is the internal transaction architecture [1]: if a reading query sends a writing query to the same database context, this will lead to a deadlock, as the writing query can only be processed if no concurrent reading queries are running.
Just a short answer; hope this helps, Christian