Re: can't access jax-rs resource in gae

2009-10-30 Thread Michael Mogley
Thanks, Jerome. On Thu, Oct 29, 2009 at 1:56 AM, Jerome Louvel jerome.lou...@noelios.comwrote: Hi Michael, In addition, I've also updated our documentation on Restlet edition for GAE in the wiki as it was referring to some outdated materials. For example you can leverage a simpler way to

Restlet + WebObjects (WOLips) + Tomcat

2009-10-30 Thread webpost
I am currently starting a project with WebObjects and Tomcat. One of the major tasks to solve is to provide data with the RESTful architecture. I would like to use Restlet to solve this task. Is it possible to use Restlet in a WebObjects Project (WOLips)? Is there an example to use this

Differences between Servlet and Restlet

2009-10-30 Thread Dan Drillich
Good Day, We have here an internal conversation about the subject. Therefore, what are the benefits of using Web Services and in particular Restlets instead of Servlets? Regards, Dan -- View this message in context:

Re: Xstream naming convension

2009-10-30 Thread Jerome Louvel
Hi there, I agree this would look nicer, but it frequently happens that acronyms are put next to another. In those cases, it seems more readable to systematically use camel case. Instead of HTTPURLConnection, we would use HttpUrlConnection (JDK uses HttpURLConnection which looks inconsistent).

Re: Differences between Servlet and Restlet

2009-10-30 Thread Rob Heittman
Part 1 - Why web services and/or REST? I think the seminal work on this subject is still the Richardson and Ruby book (which also covers Restlet), RESTful Web Services, There's a Manning book coming out about Restlet

Re: Enforcing HTTP accept header

2009-10-30 Thread Jerome Louvel
Hi all, In addition to Ben's excellent reply, I would point that ServerResource subclasses can enforce the media types they accept using annotation parameters, such as: @Put(xml) public void store(Document doc){ ... } More details in the Javadocs or here:

Re: Enforcing HTTP accept header

2009-10-30 Thread Fabian Mandelbaum
I guess the correct syntax would be: @Put(xml) public void store(Document doc) { ... } Same goes for @Get annotation. You can get a list of supported out-of-the-box extensions here

Re: Query Parameters for Directory Restlets and static files (405 error)

2009-10-30 Thread Andrew Moore
Any ideas anyone? Is there another list somewhere I should be posting this? Regards, Andrew Andrew Moore wrote: Hi, I'm still learning REST, HTTP, and Restlets... so this may be a basic question, but here goes... My situation/problem space: We have a javascript heavy client and

Re: Xstream naming convension

2009-10-30 Thread Tim Peierls
And see Item 56 of Effective Java, 2nd edition, where Josh Bloch writes: There is little consensus as to whether acronyms should be uppercase or have only their first letter capitalized. While uppercase may be more common, a strong argument can be made in favor of capitalizing only the first

Re: Xstream naming convension

2009-10-30 Thread legege
But XStream stands for XmlStream. If the library was called XMLStream, I would definitely choose XmlStream; similar to your examples. But this case is different. If we would like to respect the camel case naming convention, XStream would make more sense, doesn't it? Tim Peierls wrote: And

Junit testing of restlet server?

2009-10-30 Thread Ty
Hi, I am setting up a test harness for my restlet server; using junit inside Eclipse. I am using restlet to generate the client side messages and view the responses. It doesn't seem possible to generate bad HTTP headers with the restlet client. Whenever I try to create headers that are part