To give you a bit more details, just in case you manage to see a bit
more what's happening on your side, the patch that was put in the trunk
today (r6407) was clearly due to the fact I had omitted a very important
line: the one that passes the parameters to the factory:
if (result ==
Hi Bruno-
So, I got Jetty working as the connector, and yes, it does seem to
work fine with our previously discussed HTTPS configuration. So that
can hold us for now, but we do eventually want to use the Simple
connector.
Incidentally, based on recent postings to the simpleframework support
list
Hello Matthieu,
I've just fixed the GWT edition, there was a bug avoiding to correctly handle
arrays.
Could you try tomorrow with the future snapshot
(http://www.restlet.org/downloads/)?
Best regards,
Thierry Boileau
--
http://restlet.tigr
Hello Xavier,
I've just tried with the jse edition and the gwt edition. It just works. Could
you precise your context?
Best regards,
Thierry Boileau
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2465133
Hi Jerome-
I did try a number of variations:
// My original code:
ClientResource res = new ClientResource(Method.POST, uri);
Representation entity = res.post(null);
// with an empty Representation:
ClientResource res = new ClientResource(Method.POST, uri);
Representation entity = res.post(new Em
I'll try Jetty to see if it works, although I'd prefer in the long
term to use Simple. the only thing is that this is a bit more
burdensome to try for our environment, because we have an OSGi-based
stack, and I have to rebuild any new extension with a new manifest
entry to make it a bundle fragmen
Hello Rob,
thanks for your report, I've entered an issue for that:
http://restlet.tigris.org/issues/show_bug.cgi?id=1068
Best regards,
Thierry Boileau
> Hi all,
>
> I haven't explored it in sufficient detail yet to have a patch, but
> request.getCookies() is returning only the first cookie sen
Hi David,
The connector does work for some requests. Actually, it passes quite a bunch
of unit tests :)
However, it is possible that the null entity generates a side-effect. We'll
investigate.
BTW, we have just fixed in SVN trunk and issue that would cause requests to
be pipelined all the time.
Hi all,
I haven't explored it in sufficient detail yet to have a patch, but
request.getCookies() is returning only the first cookie sent by the browser,
I think since some of the engine refactoring in early March may have to do
with it? I think it was OK before then.
A quick step thru seems to i
Hi David,
David Fogel wrote:
> Hi Bruno, Jerome-
>
> Thanks for taking a look at this! I've just updated to the latest in
> trunk (SVN revision 6407).
>
> Unfortunately, the fix doesn't seem to be working- in fact now what
> I'm seeing is that the connection is never made from the client, but
>
ok, perfect !
thanks again.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2464996
Hi Bruno, Jerome-
Thanks for taking a look at this! I've just updated to the latest in
trunk (SVN revision 6407).
Unfortunately, the fix doesn't seem to be working- in fact now what
I'm seeing is that the connection is never made from the client, but
now my server starts using both CPU cores (up
Hi all,
Bruno's patch has just been applied to SVN trunk.
Best regards,
Jerome
-Message d'origine-
De : Bruno Harbulot [mailto:bruno.harbu...@manchester.ac.uk]
Envoyé : jeudi 25 mars 2010 15:32
À : discuss@restlet.tigris.org
Objet : Re: HTTPS / SSL not working after updating to trunk
Hi,
I've put a patch for this in
http://restlet.tigris.org/issues/show_bug.cgi?id=977
I've tried it locally with the Simple, Jetty and Grizzly connectors (and
the test cases pass).
This patch also removes the explicit use of DefaultSslContextFactory in
the test case, to assume we're testing t
Hi,
well, maybe in one month. However, you can get the current snapshot of the 1.1
branch (refreshed each day) from this page:
http://www.restlet.org/downloads/1.1/
Best regards,
Thierry Boileau
--
http://restlet.tigris.org/ds/viewMessage.do?
On Thu, Mar 25, 2010 at 12:35 PM, Jerome Louvel
wrote:
> Hi guys,
>
> Sorry for being late to the discussion.
>
> The dependency on the Servlet API is an issue indeed, but I think you should
> be able to achieve what you want by injecting the Restlet request/response
> and then from that retrievin
Hi again...
by the way the JAX-RS module has already a dependency on the servlet
API
(http://restlet.tigris.org/source/browse/*checkout*/restlet/trunk/modules/org.restlet.ext.jaxrs/pom.xml?revision=5522&content-type=text%2Fplain)
-Fabio
On Thu, Mar 25, 2010 at 12:35 PM, Jerome Louvel
wrote:
>
Hi,
Thank you for fixing this.
Do you plan to release a new package soon ?
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2464949
Hi Nirav,
The JAAS extension integrates with Restlet for the authentication aspects
thanks to the JaasVerifier class. For the authorization aspect, you can use
the static JaasUtils#createSubject(ClientInfo) method to retrieve a JAAS
Subject from your authenticated request.
The org.restlet.
Hi there,
Were you able to solve this issue? If not, please provide a reproducible
test project and enter a defect report.
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.org
Noelios Technologies ~ http://www.noelios.com
-Message d'origine-
De
FYI, thread continued here:
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2454223
-Message d'origine-
De : javaxmlsoapdev [mailto:vika...@yahoo.com]
Envoyé : mercredi 3 mars 2010 02:30
À : discuss@restlet.tigris.org
Objet : Spring not working with Restlet
I have
Hi Bruno,
After recent changes, the latest "accept.properties" file in SVN trunk has
this:
#Internet explorer
agentName: msie
acceptOld:
acceptNew:
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
I guess with this you won't need to customize it.
Hi Sopasakis,
Looking at the code, this shouldn't happen normally. Could you enter a bug
report with the precise version/environment and stack trace? Then, we'll
need to find a way to reproduce it :)
http://restlet.tigris.org/issues/enter_bug.cgi
If this is blocking you, I suggest using another c
Hi guys,
Sorry for being late to the discussion.
The dependency on the Servlet API is an issue indeed, but I think you should
be able to achieve what you want by injecting the Restlet request/response
and then from that retrieving the Servlet request/response.
org.restlet.ext.servlet.internal.S
Reading the documentation as always helps:
Switching the internal type for Jetty to BlockingChannelConnector (type=2)
improves the performance dramatically:
Results: troughput in megabytes per second (MB/sec)
Internal/Default Jetty
Hi Mickey,
You are hit by the Same Origin Policy (SOP) restrictions.
http://en.wikipedia.org/wiki/Same_origin_policy
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.org
Noelios Technologies ~ http://www.noelios.com
-Message d'origine-
De : Mic
Hi Fabian,
The "Via" HTTP header is now properly parsed into an
org.restlet.data.RecipientInfo class accessible with the Message#recipientsInfo
list property since 2.0 RC1. This should help :)
See the updated mapping page:
http://wiki.restlet.org/docs_2.0/13-restlet/27-restlet/324-restlet/130-r
Hi Valdis,
It’s taking a while, but I’m getting to your issue J
I have just fixed all the ‘object’ converters to properly handle local
serialization/deserialization. I’ve tested it successfully using the attached
class. It should work with your annotated resources now. Please let me know
Hi,
Sorry, that's probably due to a patch I submitted a few weeks ago and
that was put in the trunk a couple of days ago.
The aim was to consolidate the SSL settings to have them in one place,
but it seems that there was a line missing unfortunately.
Here is a patch:
diff --git
a/modules/org.
Hi Felix,
Ive looked again at this issue and dont see why it occurs. The close()
method should be invoked by the HTTP server connector already, sometimes
after the write().
Otherwise, in the ByteUtils class we only close the inputstream when copying
it to an outputstream
Hi Tal,
Thanks for providing this test class. This wasn't the intended behavior and
this is now fixed in SVN trunk. The change was done in
UniformResource#doCatch() method, which can be overridden as a workaround if
necessary.
Best regards,
Jerome Louvel
--
Restlet ~ Founder and Technical Lead ~
Hello,
thanks for your reports. Such special characters were not taken correctly into
account. The fix is available in the svn repository.
Best regards,
Thierry Boileau
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=
32 matches
Mail list logo