Hello all, sorry for being pedantic but I'm really stuck with this. I've tried to pass the post body through the session mechanism to the called function. It works but it's not a viable solution since I have to change the annotations removing the %rest:POST("{$postbody}") annotation because otherwise I get the BASX0003 error before entering the function. But the called function needs to remain a "lower level" REST entrypoint so it definitely needs to keep the rest annotations as they are. Moreover there is no possibility of stating that the postbody may possibly be empty, is it? Could anyone please let me know if I'm going a wrong way with architectural design? Thanks a lot. Marco.
On 01/13/2014 11:48 AM, Marco Lettere wrote:
Hi all, I'm currently using a pattern where I POST to a rather generic restxq function that performs some pre-validation on the POST body. At that point, according to information I get from the request (path, headers) I call a subsequent more specific function through the <forward/> construct. It works nicely up to the access to the POST content which appears to be consumed defintely by the first function. Actually I get the following error at the called function:
[BASX0003] Input could not be converted: "POST.xml" (Line 1): No input found.
I don't see in the docs any way I can get <forward/> to pass ahead the post body and I thought it should be natural ... what am I missing?
Regards, Marco Lettere.
P.S. I'm using basex 7.7. _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk