<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet">
    <title>gmane.comp.java.restlet</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7042"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7041"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7040"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7039"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7038"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7037"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7036"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7035"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7034"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7033"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7032"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7031"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7030"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7029"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7028"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7027"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7026"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7025"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7024"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.restlet/7023"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7042">
    <title>Newbie questions (just 3!)</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7042</link>
    <description>I am looking into Restlets and am having success, but I do have some initial questions:

Background if you care: My application delivers reports in various representations (flash,html, csv). I use digest authentication. The client does GETs to /report/{reportId}. The representation type is specified by the client, and if a particular report does not support the specified representation it returns a 406.

1. I using the default HTTP connector and it is working fine.  Why move to another one - are there significant performance gains. This will not be a high volume interface.
I expect clients from differing platforms (if that matters).

2. For reports returning CSV, I couldn't find a csv mediatype, so I created my own (new MediaType("text/csv") and return a StringRepresentation. Is this valid /recommended approach?
3. My Flash reports actually might be several flash files. Client can either request links to flash files (MediaType.TEXT_URI_LIST) or a zip of them, for which I return a FileRepresentation of MediaT</description>
    <dc:creator>postmaster&lt; at &gt;tigris.org</dc:creator>
    <dc:date>2008-12-04T21:16:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7041">
    <title>Re: problem with restlet-gwt</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7041</link>
    <description>I very, very seldom use Windows, but Jerome and Thierry do, so I'm sure he's
used the sample there -- I think he updated it most recently.

I think I see what you are asking -- you need to use both Restlet and RPC in
the same application.  I don't have an example of that right at hand; I use
Restlet so I don't have to use RPC at all ... but I do understand and I know
that it can be set up.

If you are running under Eclipse, it is possible for the web.xml to be
overwritten and Eclipse doesn't know about it without you doing an explicit
Refresh on the file -- but you probably tried this already.  Is your web.xml
exactly as it came from the example, or have you modified it in any way?

When we run the gwtshell under eclipse, I saw that it starts a tomcat


Yes, that is how the hosted mode works.

If I start the restlet TestServer component as a standaolne application and


If the standalone uses the same port as hosted mode, you can't run them both
at once.  I think hosted mode defaults to 8888.

I read several</description>
    <dc:creator>Rob Heittman</dc:creator>
    <dc:date>2008-12-04T20:14:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7040">
    <title>Re: problem with restlet-gwt</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7040</link>
    <description>Hi Rob, thanks for your support.
Unfortunatelly the web.xml has not been overwritten.
I controlled it more times and it's ok.
What can be wrong?
Did you try the sample on windows?
It seems like the gwt engine is finding something in the module.
When we perform a gwt-rpc call, we have to add a servlet entry in the module
and the gwt module in this way knows how to route the request.
When we run the gwtshell under eclipse, I saw that it starts a tomcat
instance.
It also deploys the restlet resources there in order they to be found by the
gwt engine?
My question is does the gwt shell behave as a web container and deploy the
resources (in the server folder) within it as we had created a web project
and put the restlet based application 
classes within it?
If I start the restlet TestServer component as a standaolne application and
then run the shell again it complains of an already used address and so the
server side should work well even if I can not see the TestServer's 
sytem.out statements in the console.
I r</description>
    <dc:creator>antoniojg</dc:creator>
    <dc:date>2008-12-04T16:28:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7039">
    <title>Re: problem with restlet-gwt</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7039</link>
    <description>Hi Rob,

if you don't mind, I will cope with this task and tell you when it will 
be achieved.

best regards,
THierry Boileau


------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&amp;dsMessageId=979692

</description>
    <dc:creator>Thierry Boileau</dc:creator>
    <dc:date>2008-12-04T16:20:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7038">
    <title>Re: problem with restlet-gwt</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7038</link>
    <description>


The web.xml inside your project root /tomcat/webapps/ROOT/WEB-INF/web.xml
has probably been overwritten (or never configured).  GWT sometimes will
overwrite this due to some combination of timestamps I've never been able to
figure out.  (If someone knows, and can propose a workaround, I'd love to
hear it).  This needs to have the declaration of the GwtShellServletWrapper
in it (see the one in the example zip).

Moreover has someone succeded in configuring the module to run on a real

Which kind of servlet is it necessary to configure in the deoployment


Yes, just use ServerServlet to power your Restlet server side.  You need not
pass the module information any more, as you'd now be running a JavaScript
compiled version of the client side.  You cannot, to my knowledge, use a
real Tomcat in GWT hosted mode -- I believe there are Google specific
changes in the hosted mode Tomcat bundled with GWT.

We'll add it to the "to do" list to add a walk thru of compilation and
deployment options in some various produ</description>
    <dc:creator>Rob Heittman</dc:creator>
    <dc:date>2008-12-04T15:55:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7037">
    <title>problem with restlet-gwt</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7037</link>
    <description>Hello, I imported the sample restlet-gwt project within eclipse 3.4 but I'm
unable to connect to the restlet resource. When I click on the close button
It complains of the following  error

"unable to find 'ping.gwt.xml' on your classpath; could be a typo, or maybe
you forgot to include a classpath entry for source?"

I get this error both creating a new project with all the dependencies and
importing the already configured one and running the .launch file.
I am using eclipse in windows and I changed the gwt_home setting and the
gwt.....linux settings to point to the right files and path.
I don't understand why it's looking within the module to find the resocuces.
It should use the restlet-gwt jar file and open a http connection.
Can you please suggest me a solution? 
Moreover has someone succeded in configuring the module to run on a real
tomcat instance?
Which kind of servlet is it necessary to configure in the deoployment
descriptor? GwtServletWrapper should not work in web mode so ServerServlet
should be</description>
    <dc:creator>antoniojg</dc:creator>
    <dc:date>2008-12-04T15:31:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7036">
    <title>RE: Important changes to Restlet mailing lists</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7036</link>
    <description>In addition, there is a great MarkMail service that offers a search across all five Restlet mailing lists (Discuss, Code, Wiki, Issues and Commits) at the same time, will slick navigation in message threads:
http://restlet.markmail.org/
 
I've added a link to it on the mailing lists page.
 
Best regards,
Jérôme Louvel
--
Restlet ~ Founder and Lead developer ~  &lt;http://www.restlet.org/&gt; http://www.restlet.org
Noelios Technologies ~ Co-founder ~  &lt;http://www.noelios.com/&gt; http://www.noelios.com

  _____  

De : Jerome Louvel [mailto:jerome.louvel&lt; at &gt;noelios.com] 
Envoyé : mercredi 3 décembre 2008 19:04
À : discuss&lt; at &gt;restlet.tigris.org
Objet : Important changes to Restlet mailing lists


Hi all,
 
A few days ago, Tigris.org completed a major upgrade on their open source hosting platform, where the Restlet project partly lives.
 
As a result, some settings where changed in the mailing lists, potentially affecting some of you. I have just done some adjustments to the configuration that should solve most obvious i</description>
    <dc:creator>Jerome Louvel</dc:creator>
    <dc:date>2008-12-04T15:25:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7035">
    <title>RE: java.lang.AbstractMethodError: org.restlet.util.Engine.fireContextChanged</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7035</link>
    <description>Hi Ian,

The component's context is not longer shared with the connectors. Each one of them can have its own context since 1.1.

This is documented in the Migration guide:
http://wiki.restlet.org/docs_1.1/13-restlet/171-restlet/155-restlet.html 

Let us know if you still can't fix this NPE.

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


-----Message d'origine-----
De : Ian Clarke [mailto:ian.clarke&lt; at &gt;gmail.com] 
Envoye : mardi 2 decembre 2008 17:28
A : discuss&lt; at &gt;restlet.tigris.org
Objet : Re: java.lang.AbstractMethodError: org.restlet.util.Engine.fireContextChanged

Doh!!

Ok, so I've done that, now I'm getting an NPE here, this code worked
fine in 1.0.x:

client.getContext().getParameters().add("converter",
"com.noelios.restlet.http.HttpClientConverter");
client.getContext().getParameters().add("connectionManagerTimeout", "100");

Any ideas?

Ian.

On Mon, Dec 1, 2008 at 1:08 PM, Rhett Sutphin &lt;rhett&lt; at &gt;</description>
    <dc:creator>Jerome Louvel</dc:creator>
    <dc:date>2008-12-04T10:12:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7034">
    <title>Re: Restlet and Java 6</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7034</link>
    <description>hello Jerome,

On Thursday 04 December 2008 05:23:13 am Jerome Louvel wrote:

i'll put something together in the next few days and send it to you 
directly.




cheers;
rsn

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&amp;dsMessageId=979313</description>
    <dc:creator>Raif S. Naffah</dc:creator>
    <dc:date>2008-12-04T07:54:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7033">
    <title>RE: 204 switched to 404 in handleGet</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7033</link>
    <description>That works great.

Thanks for the fast response!

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&amp;dsMessageId=979124

</description>
    <dc:creator>Ryan Niemeyer</dc:creator>
    <dc:date>2008-12-03T21:09:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7032">
    <title>RE: 204 switched to 404 in handleGet</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7032</link>
    <description>Hi Ryan,

This sounds like a bug to me. I have made the following change in SVN branch 1.1 and trunk:

                if ((getResponse().getStatus() == null)
                        || (getResponse().getStatus().isSuccess() &amp;&amp; !Status.SUCCESS_NO_CONTENT
                                .equals(getResponse().getStatus()))) {
                    getResponse().setStatus(Status.CLIENT_ERROR_NOT_FOUND);
                } else {
                    // Keep the current status as the developer might prefer a
                    // special status like 'method not authorized'.
                }

Let me know if it works fine.

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


-----Message d'origine-----
De : Ryan Niemeyer [mailto:ryan.niemeyer&lt; at &gt;gmail.com] 
Envoye : mercredi 3 decembre 2008 17:31
A : discuss&lt; at &gt;restlet.tigris.org
Objet : RE: 204 switched to 404 in handleGet

A better solution than overriding handleGet is </description>
    <dc:creator>Jerome Louvel</dc:creator>
    <dc:date>2008-12-03T19:20:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7031">
    <title>RE: Tutorial Missing Info</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7031</link>
    <description>Hi Simon,

Thanks for reporting this. It is now fixed online!

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


-----Message d'origine-----
De : Simon Earnshaw [mailto:simon.earnshaw&lt; at &gt;forestry.gov.uk] 
Envoye : mercredi 3 decembre 2008 18:11
A : discuss&lt; at &gt;restlet.tigris.org
Objet : Tutorial Missing Info

At this point in the tutorial:

http://www.restlet.org/documentation/1.0/firstResource#part07

where it says:

"This client application must be run as a standalone Java application using a couple of JARs:

    * org.restlet.jar
    * com.noelios.restlet.jar
    * com.noelios.restlet.ext.httpclient.jar
    * org.apache.commons.httpclient.jar"

it has missed out some jars that seem to be crucial in getting the server to work properly - nameley:

org.apache.commons.logging.jar
org.apache.commons.codec.jar

- just thought the docs should be updated to show that you need to include these jars too.

Cheers
Simon

</description>
    <dc:creator>Jerome Louvel</dc:creator>
    <dc:date>2008-12-03T18:47:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7030">
    <title>RE: Restlet and Java 6</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7030</link>
    <description>Hi Raif,

Thanks for the updates. I'm glad you found a solution!

The conclusion, there is an integration issue between Tomcat 6.0, JDK 6 and Restlet 1.1... We need to have a look as it might be a
common scenario.

Do you have some reproducible code (ideally a WAR with source would be perfect) that could help us debug this?

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com


-----Message d'origine-----
De : Raif S. Naffah [mailto:tigris&lt; at &gt;naffah-raif.name] 
Envoye : mercredi 3 decembre 2008 10:33
A : discuss&lt; at &gt;restlet.tigris.org
Objet : Re: Restlet and Java 6

hello again,

On Wednesday 03 December 2008 06:46:39 pm Raif S. Naffah wrote:

the above did not work.  the input stream returned (as it was before) an 
EOF --last call that is not returning the correct (read expected) 
characters is a sun.nio.cs.StreamDecoder.read([char,int,int) although the 
(Restlet) Entity.getSize() and .getAvailableSize() both return</description>
    <dc:creator>Jerome Louvel</dc:creator>
    <dc:date>2008-12-03T18:23:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7029">
    <title>Important changes to Restlet mailing lists</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7029</link>
    <description>Hi all,
 
A few days ago, Tigris.org completed a major upgrade on their open source hosting platform, where the Restlet project partly lives.
 
As a result, some settings where changed in the mailing lists, potentially affecting some of you. I have just done some adjustments
to the configuration that should solve most obvious issues such as moderation of some subscribers not registered with Tigris. Please
report any remaining issue that you encounter.
 
The good news is that they have added new features such as online posting without being subscribed. This could be useful for
newcomers or people rarely posting.
 
Finally, I have fully rewritten the mailing lists page with the greatest options to get you connected to the Restlet community
(Tigris, Nabble, GMane):
http://www.restlet.org/community/lists
 
Best regards,
Jérôme Louvel
--
Restlet ~ Founder and Lead developer ~  &lt;http://www.restlet.org/&gt; http://www.restlet.org
Noelios Technologies ~ Co-founder ~  &lt;http://www.noelios.com/&gt; http://www.noelios.com

</description>
    <dc:creator>Jerome Louvel</dc:creator>
    <dc:date>2008-12-03T18:04:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7028">
    <title>Tutorial Missing Info</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7028</link>
    <description>At this point in the tutorial:

http://www.restlet.org/documentation/1.0/firstResource#part07

where it says:

"This client application must be run as a standalone Java application using a couple of JARs:

    * org.restlet.jar
    * com.noelios.restlet.jar
    * com.noelios.restlet.ext.httpclient.jar
    * org.apache.commons.httpclient.jar"

it has missed out some jars that seem to be crucial in getting the server to work properly - nameley:

org.apache.commons.logging.jar
org.apache.commons.codec.jar

- just thought the docs should be updated to show that you need to include these jars too.

Cheers
Simon

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&amp;dsMessageId=978983

</description>
    <dc:creator>Simon Earnshaw</dc:creator>
    <dc:date>2008-12-03T17:11:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7027">
    <title>Re: another missing method due to using http client connector</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7027</link>
    <description>Hello Thilo,

it seems you are mixing the httpclient extension of Restlet 1.1 and the 
api of Restlet 1.0...
Could you check that you get the right java archives?



Best regards,
Thierry Boileau
--
Restlet ~ Core developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&amp;dsMessageId=978964

</description>
    <dc:creator>Thierry Boileau</dc:creator>
    <dc:date>2008-12-03T16:47:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7026">
    <title>RE: 204 switched to 404 in handleGet</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7026</link>
    <description>A better solution than overriding handleGet is probably returning Representation.createEmpty() instead of null for 204 responses.

That works fine, though it does seem like null should be an appropriate response too.

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&amp;dsMessageId=978955

</description>
    <dc:creator>Ryan Niemeyer</dc:creator>
    <dc:date>2008-12-03T16:30:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7025">
    <title>another missing method due to using http client connector</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7025</link>
    <description>Hello together,
currently I´m "fighting" with restlet to connect our database resources via
url to the web. I want to run the service in the  tomcat container. Without
tomcat I can use the apache httpclient to connect to a url. In tomcat the
same code does not work anymore. I don´t know what dependencies are not
fullfilled. If I use the httpclient directly everything works fine but it´s
not as elegant in comparison to the http client in restlet api. The code is
quite simple:

...getRepresentation(...)

Client client = new Client(Protocol.HTTP);
Response response = client.get(url);
in comparison to
    HttpClient httpClient = new HttpClient();
    GetMethod getMetadataRequest = new GetMethod(url);
        try {
            httpClient.executeMethod(getMetadataRequest);
            BufferedReader in = new BufferedReader(new InputStreamReader(
                    getMetadataRequest.getResponseBodyAsStream()));
        } catch (HttpException e)
            e.printStackTrace();
        } catch (IOException e) {</description>
    <dc:creator>Thilo Wehrmann</dc:creator>
    <dc:date>2008-12-03T15:45:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7024">
    <title>another missing method</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7024</link>
    <description>Hello together,
currently I´m "fighting" with restlet to connect our database resources
via url to the web. I want to run the service in the  tomcat container.
Without tomcat I can use the apache httpclient to connect to a url. In
tomcat the same code does not work anymore. I don´t know what
dependencies are not fullfilled. If I use the httpclient directly
everything works fine but it´s not as elegant in comparison to the http
client in restlet api. The code is quite simple:

...getRepresentation(...)

Client client = new Client(Protocol.HTTP);
Response response = client.get(url);
in comparison to
    HttpClient httpClient = new HttpClient();
    GetMethod getMetadataRequest = new GetMethod(url);
        try {
            httpClient.executeMethod(getMetadataRequest);
            BufferedReader in = new BufferedReader(new InputStreamReader(
                    getMetadataRequest.getResponseBodyAsStream()));
        } catch (HttpException e)
            e.printStackTrace();
        } catch (IOException e) {</description>
    <dc:creator>Thilo Wehrmann</dc:creator>
    <dc:date>2008-12-03T15:42:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7023">
    <title>204 switched to 404 in handleGet</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7023</link>
    <description>On line 501 in version 1.1.1 of org.restlet.resource.Resource.handleGet(), there's logic that sets the response status to 404 if the representation is null and the response status is 200-299.  That logic doesn't seem to account for status 204, which by definition should not contain a message body.

In my resource, I was overriding represent(Variant) and in certain situations setting the response status to 204 and returning a null response, however the base class flipped that to a 404 on me.

I can obviously work around this by overriding handleGet() (any other suggestions?), but ideally line 501 in handleGet would be changed to account for 204/null being an acceptable GET response.

Code snippet in question...

            if (selectedRepresentation == null) {
                if ((getResponse().getStatus() == null)
                        || getResponse().getStatus().isSuccess()) {
                    getResponse().setStatus(Status.CLIENT_ERROR_NOT_FOUND);
                } else {
                    // Keep</description>
    <dc:creator>Ryan Niemeyer</dc:creator>
    <dc:date>2008-12-02T20:22:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.restlet/7022">
    <title>Envoyez vos cartes de voeux personnalisees a bas prix</title>
    <link>http://permalink.gmane.org/gmane.comp.java.restlet/7022</link>
    <description/>
    <dc:creator>cartes de voeux</dc:creator>
    <dc:date>2008-12-03T06:59:24</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.java.restlet">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.java.restlet</link>
  </textinput>
</rdf:RDF>
