| [Texo] make _eclass optional when using query in PUT [message #906743] |
Sun, 02 September 2012 08:07  |
Eclipse User |
|
|
|
Does it make sense to default the _eclass param to "request|QueryType" in a query using PUT?
Currently, I would do the query as follows:
{
"_eclass": "request|QueryType",
"namedQuery": "myQueries.getObjectList"
}
Maybe, texo could handle the following, too:
{
"namedQuery": "myQueries.getObjectList"
}
|
|
|
| Re: [Texo] make _eclass optional when using query in PUT [message #906994 is a reply to message #906743] |
Mon, 03 September 2012 01:23  |
| Eclipse User |
|
|
|
Hi Erdal,
Yes it probably does, can you enter a bugzilla for this one to?
gr. Martin
On 09/02/2012 02:07 PM, Erdal Karaca wrote:
> Does it make sense to default the _eclass param to "request|QueryType" in a query using PUT?
> Currently, I would do the query as follows:
>
> {
> "_eclass": "request|QueryType",
> "namedQuery": "myQueries.getObjectList"
> }
>
> Maybe, texo could handle the following, too:
>
> {
> "namedQuery": "myQueries.getObjectList"
> }
>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxx - mtaal@xxxxxxxx
Web: www.springsite.com - www.elver.org
|
|
|
Powered by
FUDForum. Page generated in 0.05882 seconds
Home