Hi Hannes,
It looks like a bug but after looking at the code I don't see what we are doing
wrong as we have no control on encoding for Object serialization.
Anyway, I've entered a bug report:
Encoding issue with ObjectRepresentation
http://restlet.tigris.org/issues/show_bug.cgi?id=525
If you
Hi Stephan,
I think you will have time to upgrade to JAX-RS 0.9. See my upcoming replies
for roadmap updates.
Best regards,
Jerome
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : lundi 30 juin 2008 15:25
À : discuss@restlet.tigris.org
Objet : JAX-RS
Hi Mark,
Thanks for investigating this issue. Things are not clear for me either
because what you changed in getHostPort() should already be done by the
parseHost() method called.
Could you try to debug this a bit more and see what is wrong with the
current logic? We need to take into account
Hi Jerome,
Jerome Louvel wrote:
It looks like a bug but after looking at the code I don't see what we
are doing wrong as we have no control on encoding for Object
serialization.
Anyway, I've entered a bug report:
great, thanks!
If you could attach a reproducible test case (client+server
Hi Stephan,
We have updated our roadmap for 1.1. The target for 1.1 final is now 2008
Q3.
We also introduced a new 1.1 M5 release as many features slipped in since
1.1 M4 and doing a direct jump to 1.1 RC didn't seem like a good idea.
Best regards,
Jerome
-Message d'origine-
De :
Hi Hendy,
Thanks for sharing this new technique. It looks better to me as well and
more inline with the existing logic. I've updated the related RFE and will
do the refactoring for 1.1 M5.
Support for OSGI plugin framework
http://restlet.tigris.org/issues/show_bug.cgi?id=83
Best regards,
Hi Patrick and Tim,
Thanks for the feed-back. I fully agree with all your comments and made the
following changes to SVN trunk:
- Replaced the Context#getThread(Runnable) method with a more flexible
getExecutorService() method.
- Clarified Javadocs for static getCurrent() methods.
Tim,
Hi Aron,
The ability to configure a Component using an XML document is already
available in standalone mode. Therefore you can use it with the Simple
connector.
However, the current mechanism isn't dynamic, you would have to recreated
the Component instance each time you modify the XML config
Hi Bruce,
There is an existing bug report covering this exception:
File transfer exception on Linux
http://restlet.tigris.org/issues/show_bug.cgi?id=502
It would help if you could attach a simple reproducible test case and maybe
dig into Grizzly extension code if you are more adventurous!
Hi Paul,
This is new to me. What do you mean by launching 1/10 times? Do you stop and
restart the application? Do you do this using Component#start() and stop()
methods and differently? It is important to cleanly shutdown your server
connector in order to quickly release the open sockets.
Did
Hi Evgeny,
We already have a free source code repository at Tigris, so why not use it
directly instead of maintain something in parallel?
If you have some intensive checkin/update work to do, I could even give you SVN
commit access to the Restlet Spring extension.
Other contributors can use
Hi Jerome,
I think you will have time to upgrade to JAX-RS 0.9.
yes. I hope, I will have the time for it, but I think, it should work.
See my upcoming replies for roadmap updates.
thanks for the update.
best regards
Stephan
All,
I am considering using Restlet to code up a simulator of an external
website and would appreciate some comments / help. The problem is that
the external URLs are ugly and not RESTian at all, see the examples
below. Does this preclude me from using Restlet in the first place as
I I've read
Hi Marcus,
I propose to implement a Restlet subclass which parses the URI, instead
of using the Router.
Or you create a sub class of Router, which modifies the URI, before you
give it to the Routes for scoring.
best regards
Stephan
Marcus Edwards schrieb:
All,
I am considering using
I will submit a bug report. thanks
From: Jerome Louvel [EMAIL PROTECTED]
Reply-To: discuss@restlet.tigris.org
Date: Fri, 4 Jul 2008 10:50:31 +0200
To: discuss@restlet.tigris.org
Subject: RE: More on port 80 - VirtualHost.resourcePort property
Hi Mark,
Thanks for investigating this issue.
Hi Marcus,
I send you a sample Router class that mix two logics of routing :
- the first one is classically based on the URIs (i.e.
/internal/kb.portal is not the same than /internal/blabla)
- the second one is based on the query parameters values (you can extend
it to the body)
At the
Hello Marc-Elian,
Salut Thierry,
component.getClients().add(Protocol.HTTP); // mandatory
Got it, that's the line I was missing.
Thanks.
BR,
Meb
Next time the server blocks, send a thread dump to the list. I'd like to
see what's hanging.
Cheers,
Kevin
On Thu, Jul 3, 2008 at 2:38 PM, Paul J. Lucas [EMAIL PROTECTED] wrote:
When launching my application, perhaps 1/10 times, the underlying web
server gets stuck in ServerSocket.accept().
Hi,
are there some new about the Restlet book Restlet: Official Developer's
Guide to RESTful Web Applications in Java, that could I put in the
section Related Work of my thesis?
best regards
Stephan
Hi
I have an XForm built on the OPS XForms processor. Rather than use the OPS
pipelines for connecting my XForms to datasources I would like to use the
Restlet Framework to connect my XForm fields to datasources like MySQL, a Web
Service, XML databases like eXist, etc.
I would like to get XML
20 matches
Mail list logo