What's the best practice for error handling in an intermediate restlet? I am
building a web service and I assume throwing an exception will terminate the
forward chaining, is that correct?
How is information passed back to the client? If set set say status in the
client and then throw an exceptio
On 9/20/06, Jerome Louvel <[EMAIL PROTECTED]> wrote:
[...]
Not all applications require this level of transactionality/atomicity. In
those cases, directly using PUT to create a resource is just fine as putting
the same representation multiple times as no visible side effect.
I.e., that directne
On 9/19/06, Vincent <[EMAIL PROTECTED]> wrote:
[...]
> You keep bringing this RPC vs. REST thing up. That's a false
> dichotomy and I think it's just confusing things for you.
It's not a false dichotomy at all. From Fielding's dissertation:
"[Roy's] just this guy, you know." :-)
6.5.2 HTTP
On 9/22/06, Jerome Louvel <[EMAIL PROTECTED]> wrote:
[...]
For example, what happens
if I try to set a Location: header in a redirect response vs. setting it
in a "normal", non-redirect response?
The proposition I made (and the current implementation) forbids the
*addition* of *standard* HTTP h
Hi Mikkel,
Indeed, as the default JDK's behavior is to support keep-alive, I decided to
respect this instead of changing a JVM-wide setting.
You can always disable it by using the standard JDK mechanism, setting the
"http.keepAlive" system property to false.
Best regards,
Jerome
> -Messa
Hi Piyush,
> So as my http basic setup continues to befuddle me I decided to use a
> login form instead.
If you could find time to send sample code or steps to reproduce your issue,
that could help me debug this and eventually fix any issue in the code.
> So I wrote an Authentication filter t
Quick question:
I can see in the changes log that http.keepalive is no longer set to false. Does
this mean that keep-alive is supported in the HttpClient since this class uses
HttpUrlConnection???
- Mikkel
Hi,
So as my http basic setup continues to befuddle me I decided to use a
login form instead.
So I wrote an Authentication filter that basically looks for a session
id if it isn't found or the associated session is stale it redirects
to a login resource which is basically "/login".
That resour
[...]
>> If we need to attract some servlet developers later-on maybe it is
>> wise to have a method like getParameter() this will help in
>> transition from servlets to restlets.
... and you can use a WrapperCall if you want additional methods. You
can implement shortcuts etc. in your Wrapper
Hi John,
[...]
> I'm okay with the attributes being shared between the application and
> the framework. Just need to document it really well (in
> particular how
> to handle clashes/errors) and have some good examples. The example
> that you have is a good start but it doesn't deal with the
Hi Piyush,
> I couldn't find any such method in b18 is it in b19?
Actually, the method you are looking for is probably
myCall.getResourceRef().getQueryAsForm().getFirstValue("key1")
which returns the (first) parameter value as a string instead of an instance
of Parameter. Check org.r
11 matches
Mail list logo
