Re: Commons Logging

Hi Adam, We already had a discussion on this topic. See http://thread.gmane.org/gmane.comp.java.restlet/905/focus=937 Cheers Piyush On 5/24/07, Adam Taft [EMAIL PROTECTED] wrote: Yes, I've read all that. Those links are well known. But please carefully read from the link you provided...

Re: StackOverflowError

Perhaps this helps? http://63.246.22.60/browse/CONF-7573 On 3/8/07, Jonathan Hall [EMAIL PROTECTED] wrote: Hi, Just before I start to debug. Has anyone load tested an application yet? I'm getting StackOverflowError on 1.0rc5: Happens after about 1k requests on 1.6. SEVERE: Unhandled

Re: Tutorial, cleanup

HI Dave, I had the same issues .. it was cumbersome to always locate the java process and kill it. I have a shutdown restlet ... where it can be told in secs when to shutdown .. in my soln. it isn't a guarded restlet but I think it should be Ideally JMX would be the solution for stopping

Java SE 6

Hi, Do we move now? Supposed to be faster and hey i like that Mozilla rhino comes bundled! I don't see any migration efforts. I might be wrong on that though. Cheers Piyush

Applications

Hello, I have been thinking of what to expect from restlet applications. Here are two requirements that I can come up with that would be really great ... 1) A common application context for sharing between applications. 2) Hierarchical applications. In order to be able to selectively overrride

Re: Restlet 1.0 beta 21 released

hi Jerome, shouldn't that be b21 in the download link?

Re: name conflicts

I use netbeans too and it behaves just like eclipse it proposes potential imports and you import one. Till now I haven't had this problem of direct conflict with java(x).* packages. Dave are you referring to a sun.* package? Could you please give a specific example? Checkstyle can check for

Re: patch for issues reported by findbugs for org.restlet

Hi Jerome, I messed up the parameter equals method here is the fix and the hash codes etc... You can review them. I used new templates that you provided and still the formatting is an issue while generating patches .. Cheers Piyush findbugs_build2.patch Description: Binary data

Re: New snapshot of beta 21

Hi Jerome, Maybe it is important to warn the fact that the DateUtils formats are lists now instead of arrays ? the only public api that I changed.. And the fact that trying to modify system set dates will yield unsupportedoperationexception Cheers Piyush P.S: I am trying to compile latest

findbugs and checkstyle

Hi Jerome, It seems like you are already implementing the suggestions.. Encodings.java etc. cool :) But I think checkstyle should be preferred for revelations like using final while declaring constants etc. What do you think? Cheers Piyush P.S: I saw that in PipeStream you did

Re: Wiki - How to develop with Eclipse and contribute

Hi Jerome, The tutorial misses on how to enable/use the provided build.xml file within eclipse. Cheers Piyush

Re: Wiki - How to develop with Eclipse and contribute

I thought so ..

Re: Wiki - How to develop with Eclipse and contribute

I was going to provide a patch for some findbugs warnings but there seems to be some very drastic changes on the way .. I will wait ...

Re: monitoring an application

I think we need to put in a little more thought about lifecycles first ... the states that i would love to have is created (The application was created/initialized properly but never started) started (The application has been asked to run) running (The application is successfully running maybe

Re: Wiki - How to develop with Eclipse and contribute

Thanks Jerome.

Re: using log4j

Yeah! and that was a comment written in 2002 (If I can deduce that correctly) .. that is some very specific planning.. divide and conquer monthly :) But eh! august is long gone.. I would love to know what were the other 5 and what happened to them?

Re: using log4j

Hi Sean, I think you nailed it. That is exactly what I was hinting at (or atleast that was the undercurrent) if teams want to use X framework for something they are welcome to do it and frankly they will do it. But as a specification you don't always have the leisure to accommodate all. And

Re: Restlets and JMX

Hi Jerome, What about lifecycles? It is nice to be able to document lifecycle of a restlet and container etc... Then we can expose status through the MBeans ... and ways (operations) to transit from one state to another. Looks like a comprehensive list and I don't see why we can't have a

Running a simple example

Hi Jerome, I wanted to update my code. Before that in order to comprehend things I started implementing some simple use cases. The following code doesn't work as intended I always get a 404 public class Playground { public static void main(String[] args) throws Exception {

Re: Running a simple example

Hi Jerome, I added this line host.getAllowedNames().add(localhost); and now my url localhost:8182/something works but 127.0.0.1:8182/something doesn't work Using getDefaultHost() and then attaching the target works fine in both the cases. And when I do VirtualHost

Re: Shutting down

Hi Jerome, I totally agree that restlets shouldn't be able to stop containers... I thought may be there is already a way to administratively stop a container that I am not aware of. I guess JMX interface would be the best way to do that. Till then I will have to work out something :) That

Re: Beta 19 and fluent builders

Hi Sean, Honestly I didn't like the fluent builder because (apart from aesthetically unpleasing upRouter() and a little hack of owner().start()) a) problem with multiline statements (including compromised readability). And to fit it all on a single line would mean unecessary tinkering with

Re: Breaking Call into Request and Response (Was: Allow Header)

Been thinking over the weekend on this issue. I rather like the call interface. It is a unified and well encapsulated entity. How about keeping the Restlets handle(Call) as is and let it extract the request and response objects as and when it requires? Call.getRequest() Call.getResponse()

New releases and API changes

Hi Jerome, I have been thinking about how we could manage API changes and the related pain better. I think the best way would be to start using the @deprecated and setting a removal deadline by naming a future release. Here is a good synopsis of the annotation (picked up from a cached Google

Re: Allow Header

My immediate concern is a Call object with an ever increasing interface. As of last count (b18) it stands at 30+ methods.

Re: Breaking Call into Request and Response (Was: Allow Header)

Hi Jerome, +1 As usual I will keep the final word till I have already used the refactorings... Bugger I have to change all that code again.. did I just ask for all those changes... what extent we go for apparent improvements :) Do you have a deadline in mind for the b19? I think many are

Re: handling posted forms

Hi Jerome, So here are my findings... 1. I had erroneously used id instead of name for form input elements that is why things didn't turn up as expected. 2. A form with enctype=multipart/form-data isn't parsed properly. Attached restlet shows it. Everything works fine if you remove the

handling posted forms

Hi, So as my http basic setup continues to befuddle me I decided to use a login form instead. So I wrote an Authentication filter that basically looks for a session id if it isn't found or the associated session is stale it redirects to a login resource which is basically /login. That

Re: b19 - Call converters

Sorry I was way too quick for myself ... There is a method Parameter get(int) and it throws IOException. On 9/21/06, Piyush Purang [EMAIL PROTECTED] wrote: Hi Jerome, There is a programmatic way to get this: Call.getResourceRef().getQueryAsForm().get(key1) I couldn't find any such method

b18 factory methods

Hi Jerome, I am trying to migrate my work to b18. Eventhough I have to unlearn a lot, it is much nicer to work with the API. I have a suggestion to make about some o.r.data classes. For Protocol you provide the method - create, that acts as a factory method. It would be very convenient to have

Re: API design review

I agree with the very first comment to the message posted on theserverside.com. But I also agree Chris's comment - Make all classes, except those intended to be subclasses, as final. Which ones? This is trickier. You might want to let the API stabilize a bit and see what people actually do

Re: Some API related questions

Thanks Jerome for lending an ear. How can I best get to what you have already done? Should I wait for the next b-release or a nightly release (that would be cool)? I will need to change my classes now :) I will comment on/pursue these issues after I have used what's been done. Cheers Piyush

Re: Resources and Representations

Perhaps a WIKI on restlet.org with a general/open examples section would be great so that examples could be uploaded and discussions can be had on the uploaded examples.. I would then upload my solution to configuring components using an XML file (JAXB and handler classes). Chris could upload

Re: Some API related questions

Hi Jerome, 1) Why does org.restlet.data have so many classes? Couldn't they be divided into sub packages? See also remark 3. There is a simple reason which is that the REST style defines three and only three architectural elements: - Data Elements org.restlet.data - Connectors

Re: representations + caching (ETags, etc.)

Hi Chris, I am working on some ideas with restlets .. could you share your code or is that closed-source? Cheers Piyush On 8/8/06, Jerome Louvel [EMAIL PROTECTED] wrote: Hi Chris, Your approach sounds very good to me, unless your client is a Web browser. In this case, you might have trouble

internal redirects

Hi, Before I creat an issue in the issues DB I wanted to discuss it here... I want to internally redirect all /a/ calls to /a/b so I use the RedirectRestlet like RedirectRestlet redirect = new RedirectRestlet(myContainer, /a/b, RedirectRestlet.MODE_INTERNAL); host.getScorers().add(/a/,