Hi Kit,
Resource instances are created on a per-request base. When you attach a
Resource class to a Router, you indirectly attach a Finder instance that
will automatically instantiate your Resource class when a request comes in.
There are probably ways to achieve what you need though. Could
Hello anthony,
you're right, this mechanism has changed. As for the Server and Client
connectors, the available authentication helpers are now automatically
discovered via the meta information available in the classpath (every
file META-INF/services/com.noelios.restlet.AuthenticationHelper
Hello Helen,
what kind of client connector are you using? These parameters apply only
with the JDK client, that is to say the net connector.
best regards,
Thierry Boileau
Hello there,
I'm new to restlet and I'm using restlet 1.0 now.
I'm trying to do a client request through the
Hi Kevin,
Paul has entered a bug report with the thread dump:
Hanging on ServerSocket.accept()
http://restlet.tigris.org/issues/show_bug.cgi?id=528
I have no clue for now, any help is welcome.
Best regards,
Jerome
_
De : Kevin Conaway [mailto:[EMAIL PROTECTED]
Envoyé : jeudi
Why are there so many threads blocked on:
Thread-14 prio=6 tid=0x2eb16800 nid=0x11c4 waiting on condition
[0x30c2f000..0x30c2fd94]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for 0x2a9d7808 (a
Jerome Louvel contact at noelios.com writes:
Hi Kit,
Resource instances are created on a per-request base. When you attach a
Resource class to a Router, you indirectly attach a Finder instance that
will automatically instantiate your Resource class when a request comes in.
There are
Hi Thierry,
I followed the sample client code from document Restlet 1.0 - First resource,
and the following are the jar files in my classpath when I run the client code,
so I think I'm using apache commons http client connector.
include name=org.restlet.jar /
Hi,
If you think of the Resource class in a Model-View-Controller pattern,
you can think of the Resource the class that will implement the
Controller (getRepresentation, acceptRepresentation, storeRepresentation
-- probably a completely different terminology than your 'controller')
which
Hi Kit,
In addition to Bruno's comment, if your backend processing is short, you
should have a look at the Java concurrency APIs such as:
- java.util.concurrent.Future
- java.util.concurrent.ExecutorService
In recent Restlet 1.1 builds, the org.restlet.Context class even gives you
access to a
http://philipp.wagner.name/mozilla-xforms/ works in FF3, except for the
Mac.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bruno Harbulot
Sent: Tuesday, July 08, 2008 4:41 PM
To: discuss@restlet.tigris.org
Subject: Re: XForm integration with the RestLet framework
Yes... That's precisely my problem ;-) Many of our users have Macs too.
Funnily enough, the more and more we demonstrate our system (which is
still a work in progress), the more people like this idea of having the
web-service and the web-interface be the same. Although this
web-interface was
Take a look at Ubiquity XForms. It won't solve your problem today, but
it looks like it's headed that way, and if you're presently (as we are)
developing your REST layer and testing it with the Mozilla XForms XPI
and then passing off the presentation layer to multiple other
technologies to
Hi,
I've just updated the JAX-RS extension to API version 0.9. Here the most
important API changes, that are incompatible to the JAX-RS 0.8
* renamed @ProducedMime to @Produces
* renamed @ConsumedMime to @Consumes
* renamed MessageBodyWorkers to Providers (provides also access to
Thanks guys. This is what I was looking for.
Correct, my controller is not the same as a MVC controller. It is an async
process controller...and not my choice of name. ;)
Thanks again.
Kit
On 7/11/08 9:52 AM, in article [EMAIL PROTECTED],
Jerome Louvel [EMAIL PROTECTED] wrote:
Hi Kit,
14 matches
Mail list logo
