Hi Bruce,
Thanks for the reporting this new issue. I've entered a formal report:
"NPE during NIO SelectableChannel.register"
http://restlet.tigris.org/issues/show_bug.cgi?id=603
As it looks like a JVM bug, it would be very useful if you could indicate
your OS, JVM version on the report.
Best
Hello Paolo,
at first sight, we agreed with your proposition for a new constructor.
However, the context of a Component is quite uncommon since it handles
the client and server dispatchers of a component, and since such context
is instantiated with the component's helper. We think that introdu
Awesome. I learn somethin' new every day! :-)
On Mon, Sep 29, 2008 at 2:59 AM, Jerome Louvel <[EMAIL PROTECTED]>wrote:
> Hi Rob,
>
> I'd just like to point out that there are now shortcut Resource#getQuery()
> and getMatrix() methods that internally calls
> getRequest().getResourceRef().getQue
Hi Roman,
when I have a look at the source code of the StringRepresentation class,
I notice that the length is computed on via the "getBytes" method which
should calcute the correct length.
I have a few questions: as I think that this code
("Response.ok().entity(result).build();") is certainl
Hi Jerome,
My environment is as follows:
OS: Windows XP Pro SP2
JVM:
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
Regards,
Jerome Louvel wrote:
Hi Bruce,
Thanks for the reporting this new issue. I've entered a formal rep
Hi Thierry
To my knowledge my example uses only Restlet classes, i.e.
javax.ws.rs.core.Response
I think the problem could be in
org.restlet.ext.jaxrs.internal.provider.StringProvider.getSize(...). It
returns the number of characters, but the docs of
javax.ws.rs.ext.MessageBodyWriter.getSize
Good day.
I've been following the "first resource" example as I teach myself
restlet 1.1 programming, in the context of using the simple standalone
server:
http://www.restlet.org/documentation/1.1/firstSteps
However, doing so in the 1.1-RC2 release leads to what I assume are
new deprecat
To avoid the warning: change the example code:
// Attach the sample application.
component.getDefaultHost().attach(
new FirstStepsApplication(component.getContext()));
To
// Attach the sample application.
component.getDefaultHost().attach(
Answering my own question, I *think* the log message means one should
do this when setting up the standalone server:
restletComponent = new Component();
restletComponent.getServers().add(Protocol.HTTP, 8182);
Context context =
restletComponent
.getContext().createChildContext();
Our emails crossed in the mail...
Got it. Thank you.
Mark
On Sep 29, 2008, at 12:13 PM, Rob Heittman wrote:
To avoid the warning: change the example code:
// Attach the sample application.
component.getDefaultHost().attach(
new FirstStepsApplication(component.ge
Hi All,
I have a small problem which may be big (:)) internally.
Actually, I am load testing a Restlet application which takes some request
parameters as input, makes a LDAP query and returns data as an XML in response.
So, what happening in this load test is "Spiky behavior" of CPU.
CPU utili
11 matches
Mail list logo
