Re: [vote] Make status code attribute of seriailzers expandable
Reinhard Poetz wrote: I propose making the status code attribute of serializers expandable. This makes it easier to provide REST style services with Cocoon that make use of the different meanings of status codes. +1 Jeroen
Re: [vote] Make status code attribute of seriailzers expandable
Reinhard Poetz wrote: I propose making the status code attribute of serializers expandable. This makes it easier to provide REST style services with Cocoon that make use of the different meanings of status codes. +1. Should have actually been there right from the start! Sylvain -- Sylvain Wallez - http://bluxte.net
RE: [vote] Make status code attribute of seriailzers expandable
Reinhard Poetz wrote: I propose making the status code attribute of serializers expandable. This makes it easier to provide REST style services with Cocoon that make use of the different meanings of status codes. +1. Should have actually been there right from the start! big +1 because I have needed it quite some times before! Sylvain -- Sylvain Wallez - http://bluxte.net
Re: [vote] Make status code attribute of seriailzers expandable
On 3/28/07, Reinhard Poetz [EMAIL PROTECTED] wrote: snip/ I propose making the status code attribute of serializers expandable. This makes it easier to provide REST style services with Cocoon that make use of the different meanings of status codes. Could you explain what you mean by expandable a little? -- Peter Hunsberger
Re: [vote] Make status code attribute of seriailzers expandable
Peter Hunsberger wrote:
On 3/28/07, Reinhard Poetz [EMAIL PROTECTED] wrote:
snip/
I propose making the status code attribute of serializers expandable.
This makes
it easier to provide REST style services with Cocoon that make use of the
different meanings of status codes.
Could you explain what you mean by expandable a little?
Can't do it any better than Jochen at the provided JIRA link:
---
map:serialize type=html status-code={sc}/
does not return the resolved variable sc as HTTP status code but simply returns
200 OK as HTTP code. Some applications may want to store the status code in a
variable and pass this varibale to the serialzer, expecting it to expand it
(Cocoon-Lenya is an example).
Suggested enhancement patch to expand variables on the serializer is attached.
---
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: [vote] Make status code attribute of seriailzers expandable
Reinhard Poetz wrote:
I propose making the status code attribute of serializers expandable.
This makes it easier to provide REST style services with Cocoon that
make use of the different meanings of status codes.
+1
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: [vote] Make status code attribute of seriailzers expandable
Reinhard Poetz schrieb: Reinhard Poetz wrote: I propose making the status code attribute of serializers expandable. This makes it easier to provide REST style services with Cocoon that make use of the different meanings of status codes. +1 +1
Re: [vote] Make status code attribute of seriailzers expandable
On 3/28/07, Reinhard Poetz [EMAIL PROTECTED] wrote:
Peter Hunsberger wrote:
On 3/28/07, Reinhard Poetz [EMAIL PROTECTED] wrote:
snip/
I propose making the status code attribute of serializers expandable.
This makes
it easier to provide REST style services with Cocoon that make use of the
different meanings of status codes.
Could you explain what you mean by expandable a little?
Can't do it any better than Jochen at the provided JIRA link:
---
map:serialize type=html status-code={sc}/
does not return the resolved variable sc as HTTP status code but simply returns
200 OK as HTTP code. Some applications may want to store the status code in a
variable and pass this varibale to the serialzer, expecting it to expand it
(Cocoon-Lenya is an example).
Suggested enhancement patch to expand variables on the serializer is attached.
Ah, got ya, you mean, return the proper status code or some such thing...
+1
--
Peter Hunsberger
Re: [vote] Make status code attribute of seriailzers expandable
Reinhard Poetz napisał(a): Reinhard Poetz wrote: Vadim Gritsenko wrote: Reinhard Poetz wrote: Is there a specific reason why this patch (http://issues.apache.org/jira/browse/COCOON-1354) has never been applied? Technically, other than rewriting the last chunk of the patch, it looks Ok. From procedure POV, I don't recall a VOTE on that. Previous decision on what can be expandable in the sitemap was VOTEd upon. I will start a vote on this then. Any opinions in the meantime? I don't see reason why not, even if not needed often. Vadim My usecase is that I want to provide REST-style webservices with Cocoon and knowing which status code to set is part of the business logic. - o - I propose making the status code attribute of serializers expandable. This makes it easier to provide REST style services with Cocoon that make use of the different meanings of status codes. +1 -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/
Re: [vote] Make status code attribute of seriailzers expandable
Reinhard Poetz escribió: I propose making the status code attribute of serializers expandable. This makes it easier to provide REST style services with Cocoon that make use of the different meanings of status codes. +1 Best Regards, Antonio Gallardo.
