RE: CompressChainlet issue

to: preference.getEncodings().add(new EncodingPref(Encodings.IDENTITY)); Let me know if that solves the issue. Thanks, Jerome -Message d'origine- De : Lars Heuer [mailto:[EMAIL PROTECTED] Envoyé : jeudi 18 mai 2006 16:29 À : Jerome Louvel Objet : CompressChainlet issue Hi Jerome, I discovered

RE: Generics at Restlet

: Jerome Louvel Objet : Re: Generics at Restlet Hi Jerome, [...] One issue I'm having is that the Restlet interface is implemented by many classes (connectors, components, etc.). The changes suggested trigger a cascade of other changes in order to prevent warnings like: Type

RE: Generics at Restlet

Hi Lars, Even if a bunch of classes depend on AbstractRestlet it should work. As long as they are just using the handle(Call call) method they are not forced to cast or something like that. Only if a derived class uses the comfortable handle(Get|Put|..) methods they should use a type.

Restlet 1.0 beta 12 released

Main changes: * Added com.noelios.restlet.build package containing builder classes allowing a compact construction of Restlet applications base of the Fluent design pattern. * Added Tutorial 12 illustrating the used of builders. * Added buffering to Simple server to solve the

Restlet integration

Hi all, I wanted to let you know that a Simple connector (HTTP server) for the Restlet framework was contributed by Lars Heuer (Semagia) and is now part of the latest Restlet release (1.0 beta 12): http://www.restlet.org/docs/nre/com/noelios/restlet/ext/simple/package-summa ry.html First,

TR: [Simpleweb-Support] Restlet integration

in the wait queue for a maximum of 200ms. The javadoc explains the logic in this design. Niall --- Jerome Louvel [EMAIL PROTECTED] wrote: Hi all, I wanted to let you know that a Simple connector (HTTP server) for the Restlet framework was contributed by Lars Heuer (Semagia) and is now part

RE: [Simpleweb-Support] Restlet integration

Hi Niall, Thanks for looking at Restlets and at the code of the Simple connector. 1) I have performed some very quick benchmarks against Jetty 6 (the new NIO implementation). The performance tests using httperf and autobench have shown that Simple performs slightly better under higher load.

RE: RE: Fluent API and StructureBuilder

me from doing so is the fact that RestletContainerBuilder does not have a default constructor. Is that something that could be supported? thanks, -- yuri Jerome Louvel [EMAIL PROTECTED] wrote: Hi all, In beta 12 there is now support for fluent builders. Thanks Yuri and = Lars

RE: Jetty v5 configuration tweaking

I haven't done that personally, but they have a list of system properties here: http://jetty.mortbay.org/jetty/faq?s=250-Configurationt=350System%20Propert ies One of them (POOL_MAX) is apparently letting you change the max thread pool size. Regards, Jerome -Message d'origine- De :

RE: Compiling with JDK1.4

Hi all, Lars's contributions were just integrated to the build process (http://restlet.tigris.org/source/browse/restlet/). There is a new build.properties file that you can use to customize Ant's build.xml file. Just set the backport property to true in order to Retroweave the classes. Thanks,

RE: Proposal for Call

Hi Lars, Just for the record: I am (in contrast to some Restlet delelopers here ;) ) not a big fan of modifiable lists (and collections in general). Understood :-) I know that this is not a classic style for Java APIs. What is the opinion of others on this? IMO it is untypical to return

Restlet 1.0 beta 14 released

Changes: - Adjusted build.properties so that default values work directly. - Refactored the usage of parameter lists by using a new ParameterList (implementing ListParameter) and adding helper methods. - Form now derives from ParameterList. - ConnectorCall.getRequestHeaders() and

RE: Having a difficult time deploying RootContainer on Apache

Title: Having a difficult time deploying RootContainer on Apache Hi Bill, Looking at your web.xml excerpt, there seems to be one error. Instead of this: context-param param-nameorg.restlet.target.init.contextPath/param-name param-value/clientholding/param-value /context-param

RE: More questions about serving html on Tomcat

Title: More questions about "serving" html on Tomcat When using the Servlet embedded mode, the instantiation of your RootContainer will by done via the ServerServlet. So there would be no point in explicitely instantiating a DefaultServer like you propose. Thanks, Jerome De:

RE: Passing Servlet Context Parameters to Restlet?

Hi Evan, I just started investigating Restlet a few days ago, and I'm quite intrigued. It looks like it would be a perfect fit for a project I'm working on, which uses Tomcat as the servlet container. Cool! The only issue I'm running in to is that my application needs access to

Re: Javascript Client Connector

FYI, I've entered an issue to keep track of this feature request: http://restlet.tigris.org/issues/show_bug.cgi?id=129 -- Jerome Louvel http://www.restlet.org

RE: Restlet AsyncWeb?

Hi John, FYI, a new HTTP server connector based on AsyncWeb was introduced in beta 15. This integration effort was done by Lars Heuer: thanks Lars :) Let us know if it works well for you. We also discussed the development of a pure Mina-based HTTP connector that would let us fully leverage the

RE: HostRouter

Hi Jim, The problem is that the regexp is case sensitive. My host name (as returned by InetAddress.getLocalHost().getHostName()) is uppercase and the browser apparently lowercases the host before making a request. I have no idea why anyone would use uppercase host names. Its a company

RE: JSR and updated road map

Hi Lars, I hope that the development is not stalled because of the JSR approval process. My intent, as indicated in the road map, is to continue the development normally, at least until the JSR is approved. Beyond that point, I need to have a look at the JCP rules so see when the expert

RE: [OT] A kind of standard XML format for e-mails

Hi Lars, There is indeed a hole here. The Internet Mail Consortium (IMC), started some work on a Next Generation of email as well as an XML message format, but nothing concrete came out so far and the groups are inactive. Paul Prescod did an interesting proposal for a RESTful email system but

RE: How to obtain the mime type on a PUT

Dave, Just do this: call.getInput().getMediaType().equals(MediaTypes.APPLICATION_XML); Thanks, Jerome -Message d'origine- De : Dave Pawson [mailto:[EMAIL PROTECTED] Envoyé : vendredi 28 juillet 2006 12:34 À : discuss@restlet.tigris.org Objet : How to obtain the mime type on a

RE: sample CRUD app?

I'll come back to you next Monday. For now here is a a good start: http://www.restlet.org/faq#15 Thx, Jerome -Message d'origine- De : Winters, Chris [mailto:[EMAIL PROTECTED] Envoyé : vendredi 28 juillet 2006 17:03 À : discuss@restlet.tigris.org Objet : sample CRUD app? I'm

RE: How to obtain the mime type on a PUT

On 28/07/06, Jerome Louvel [EMAIL PROTECTED] wrote: Dave, Just do this: call.getInput().getMediaType().equals(MediaTypes.APPLICATION_XML); I found it (eventually) then realised that application/xml is in fact *two* calls, to main and the other one. it seems 'wrong' when

Re: Relative vs absolute context path in embedded mode

Hi Bill, Hope all is peaceful in Restlet Valley! Peaceful but very busy :-) A colleague and I were discussing the single contextPath of the ServerServlet when running in embedded mode. For instance we wanted to be able to run both of these urls and get to the same Restlet container:

RE: Some API related questions

Hi Piyush, 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: Resources and Representations

Hi Piyush, I find that the Resource and its representations is a central part of the dissertation but the tutorial somehow doesn't bring that to the fore. Would you agree on that? I do :-) and there is a plan to fill this hole: http://restlet.tigris.org/issues/show_bug.cgi?id=118 The

RE: Some API related questions

Hi Piyush, [..] Now we are talking taste here but I think Java packages aren't a very good example because some of them are there since jdk 1.0 and can't be refactored without breaking thousands of apps ..I am pretty sure that the Sun Java API gurus don't sleep easy at night :) Good

RE: error running b18 on Simple

Hi Chris, Thanks for reporting this regression. It's fixed it in SVN. Make sure you fully refresh your local copy. Best regards, Jerome -Message d'origine- De : Chris Winters [mailto:[EMAIL PROTECTED] Envoyé : jeudi 10 août 2006 00:24 À : discuss@restlet.tigris.org Objet :

RE: Some API related questions

what's been done. Cheers Piyush On 8/9/06, Jerome Louvel [EMAIL PROTECTED] wrote: Hi Piyush, [..] Now we are talking taste here but I think Java packages aren't a very good example because some of them are there since jdk 1.0 and can't be refactored

RE: error running b18 on Simple

Chris, [...] Another thing I noticed is that using a base filename in the DirectoryHandler no longer works. My older code had: DirectoryHandler staticFiles = new DirectoryHandler( this, webUri, index ); which didn't pull up the 'index.html' page on a directory

RE: (E)Tag: for resource or representation?

Hi Chris, [...] My reading of the HTTP/1.1 spec [...] says that an ETag (Entity Tag) is attached to a representation rather than a resource. [...] ...which says to me that I should generate the tag based on the content of a representation. Does this sound right? Absolutely, that's why

RE: managing URIs?

Chris, It *is* valuable information, and I don't think we can anticipate every situation where people will need it. Creating a protocol-generic API is useful, but IMO you still need to give people access to what's going on behind the scenes. Even if it's a little messy :-)

RE: b17, tomcat and spring

Hi Marcel, Thanks for the details about your issue. There is a plan to write an integration guide for Tomcat as we are getting many related questions. I'll have a look at your case and get back to you tomorrow. Best regards, Jerome -Message d'origine- De : Marcel Schepers

RE: Restlet wiki (was: Resources and Representations)

, Jerome Louvel [EMAIL PROTECTED] wrote: Ok, I've entered an issue to keep track of this request: http://restlet.tigris.org/issues/show_bug.cgi?id=150 Best regards, Jerome -Message d'origine- De : Chris Winters [mailto:[EMAIL PROTECTED] Envoyé : jeudi 10 août

RE: b17, tomcat and spring

: Re: b17, tomcat and spring Hi Jerome, That would be great. As a counter favor, I'll help you with the Tomcat/Spring integration guide. Have a nice day, Marcel Jerome Louvel wrote: Hi Marcel, Thanks for the details about your issue. There is a plan to write

RE: updated sample app: POST new resources

Thanks for the update, I've added a note and a link to your sample application at: http://www.restlet.org/faq#15 Best regards, Jerome -Message d'origine- De : Chris Winters [mailto:[EMAIL PROTECTED] Envoyé : lundi 14 août 2006 22:10 À : discuss@restlet.tigris.org Objet : updated

Fisheye service available!

Hi all, I'm pleased to announce you that our SVN repository is currently being indexed by FishEye. It is a great product that adds powerful search, change log (with RSS feeds) and code browsing features. Cenqua, its editor, is providing us with a free hosting service at:

RE: b17, tomcat and spring

finding the problem. I have a working restlet container, RestTarget in my case. I am only attaching a router to it or am I not? The specified URI (http://localhost:8080/rest/helloworld) should produce the 'hello world' string. Greetings, Marcel Jerome Louvel wrote: Hi Marcel

API design review

changes from SVN: http://www.restlet.org/downloads/current.zip Best regards, Jerome Louvel -- Noelios Consulting http://www.noelios.com

RE: API design review

my inline comments. On 8/16/06, Jerome Louvel [EMAIL PROTECTED] wrote: Following the recent questions and suggestions from Piyush Purang, I've started reviewing and refactoring the API to make it more inline with the current best practices. I'm basing my work on the following guide

RE: svn build error with Jetty6

Just fixed, it was due to Jetty 6.0 RC1 upgrade. Thanks for reporting this, Jerome -Message d'origine- De : Chris Winters [mailto:[EMAIL PROTECTED] Envoyé : jeudi 17 août 2006 15:37 À : discuss@restlet.tigris.org Objet : svn build error with Jetty6 FYI, building the project

RE: API design review

Agreed, let's wait more before make a decision on final classes. I want to review the pointers that you sent before making my mind on this, also we will need some time to play with the numerous API changes in beta 18 (to be released tomorrow). However, it seems better to be more conservative for

Restlet 1.0 beta 18 released

Finally, the new release is out! With the numerous fixes, API simplifications and enhancements done, I hope that we are reaching a new level of maturity. Some new concepts were introduced like the notion of Restlet context which abstracts a Restlet from its environment (connectors, logging

RE: Restlet 1.0 beta 18 released

: Restlet 1.0 beta 18 released Jerome Louvel wrote: ... - Following the advices of API design gurus Eamonn McManus and Joshua Bloch), I've refactored the whole API in several ways: - Set most of the member variables to private instead of protected for better encapsulation

RE: b17, tomcat and spring

, see updated roadmap here: http://www.restlet.org/roadmap Best regards, Jerome -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Peter Murray Envoyé : mercredi 30 août 2006 23:19 À : discuss@restlet.tigris.org Objet : Re: b17, tomcat and spring Jerome Louvel

RE: FileRepresentation buffers large files

Hi Mikkel, As Lars pointed out, the HttpUrlConnection was improved on this front in JDK 5: 1) Fixed Streaming mode when content length is known 2) Chunked Streaming mode when content length is not known The current HTTP client connector even has a parameter called chunkLength that can be set,

RE: What happened to ConnectorCall???

Just a minor correction: getInputAsForm() only works with input Web forms sent with POST/PUT. To get the query parameters as a Form instance, use this instead: Form form = call.getResourceRef().getQueryAsForm(); Best regards, Jerome -Message d'origine- De : Lars Heuer

RE: Basic Authentication and ServerServlet

Hi Evan, I've set the debug-vars flag to true by default. Does anyone know if there are any unwanted side effects? Best regards, Jerome -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Evan DiBiase Envoyé : jeudi 7 septembre 2006 16:19 À :

RE: Restlet mention in Dion Hinchcliffe blog

Hi Chris, Thanks for finding this post, this is cool! I've just published a related note: http://blog.noelios.com/2006/09/12/restlet-blog-coverage/ Best regards, Jerome -Message d'origine- De : Chris Winters [mailto:[EMAIL PROTECTED] Envoyé : lundi 11 septembre 2006 03:05 À :

RE: Restlet mention in Dion Hinchcliffe blog

@restlet.tigris.org Objet : Re: Restlet mention in Dion Hinchcliffe blog Jerome Louvel wrote: Thanks for finding this post, this is cool! I've just published a related note: http://blog.noelios.com/2006/09/12/restlet-blog-coverage/ Sure thing! BTW, I updated the sample app a week or so ago

RE: b17, tomcat and spring

2006 18:38 À : discuss@restlet.tigris.org Objet : Re: b17, tomcat and spring Jerome Louvel contact at noelios.com writes: In beta 18, I've only been able to partially support the Restlet Application concept. Two core classes where added org.restlet.Context (accessible form Call.getContext

RE: What happened to ConnectorCall???

FYI, I've just completed the support for call converters, for both client and server HTTP calls. A new FAQ entry is also available at http://restlet.tigris.org/faq#05. Note that the FAQ on the main web site was also updated to mention Lars's workaround: http://www.restlet.org/faq#05. You can

RE: Basic Authentication and ServerServlet

FYI, I've fixed this bug and updated the related report: http://restlet.tigris.org/issues/show_bug.cgi?id=161 Best regards, Jerome -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Evan DiBiase Envoyé : vendredi 8 septembre 2006 01:01 À :

RE: b19 - Call converters

Hi Lars, The call converters give you access to all the raw HTTP headers. If you need the value of some of them (probably in the case of non-standard HTTP headers?) in your Restlets, then you need to *push* them to the uniform Call instance. This is what the sample converter code demonstrates.

RE: b19 - Call converters

Hi again :) The getWrappedCall() method has been changed to protected in order to provide a stricter encapsulation. It's like preventing some client code to manually access to the members of an object without going through the proper method. However, I don't want to sound too dogmatic: if

RE: b18 factory methods

Hi Piyush, Excellent remark. I fully agree and have started renaming existing create methods and adding new ones to CharacterSet, Encoding, Manguage, MediaType and Status. The big advantage of using this static valueOf method instead of a constructor is that an existing constant can be returned

RE: Re: How to compromise when designing a RESTful API?

Hi Vincent, You are indeed asking a good question, not because you are reaching any limit of the REST/HTTP style but because you have a case where there is no simplistic separation between REST and RPC styles. At the most abstract level, REST doesn't force the use of any protocol (though HTTP

RE: b19 - Call converters

/com/noelios/restlet/example/misc/HeadersTest.java ?rev=947view=markup Let me know if you still have concerns. Best regards, Jerome -Message d'origine- De : Jerome Louvel [mailto:[EMAIL PROTECTED] Envoyé : vendredi 15 septembre 2006 19:51 À : discuss@restlet.tigris.org Objet : RE: b19

RE: b19 - Call converters

, this should be properly documented in the Javadocs. Would that address your concern? Best regards, Jerome -Message d'origine- De : Lars Heuer [mailto:[EMAIL PROTECTED] Envoyé : mercredi 20 septembre 2006 13:35 À : Jerome Louvel Objet : Re: b19 - Call converters Hi Jerome, Sorry

RE: b19 - Call converters

Hi Piyush, I think org.restlet.http.request.headers is the best choice. It may seem lengthy but adheres the pattern of namespaces and properties very well. As we already use this org.restlet.* convention for the parameter names of the ServerServlet extension, I'm inclined to follow you.

RE: b19 - Call converters

septembre 2006 16:17 À : Jerome Louvel Objet : Re: b19 - Call converters Hi Jerome, Just a short note that I really like the solution. I aligned my implementation to it. It is very flexible and does not force the user to depend on a particular Restlet engine. Thanks for the work :) Best

RE: b19 - Call converters

Could we somehow do the same with parameters of the query string? /a/b/c?key1=value1key2=value2 org.restlet.reference.params.key1 org.restlet.reference.params.key2 There is a programmatic way to get this: Call.getResourceRef().getQueryAsForm().get(key1) Was

RE: b19 - Call converters

Hi John, [...] I'm okay with the attributes being shared between the application and the framework. Just need to document it really well (in particular how to handle clashes/errors) and have some good examples. The example that you have is a good start but it doesn't deal with the

RE: b19 - Call converters

/06, Jerome Louvel [EMAIL PROTECTED] wrote: [...] For example, what happens if I try to set a Location: header in a redirect response vs. setting it in a normal, non-redirect response? The proposition I made (and the current implementation) forbids the *addition* of *standard

RE: Best practice, error handling

Hi Sean, Have a look at the StatusFilter, it catches any unhandled exception (thrown inside a handle(Call) method) and sets the call's status to INTERNAL_ERROR (500 in HTTP) in this case. You can override it to customize the status page displayed. If you want a different status when an

RE: handling posted forms

Hi Piyush, [...] 2. A form with enctype=multipart/form-data isn't parsed properly. Attached restlet shows it. Everything works fine if you remove the enctype. Ah, I see! There is an existing issue for this. I've updated it with your test code and comments:

RE: Surprising interaction between Call status and output

Hi Sean, I've fixed the issue in SVN. Thanks for the feed-back! Best regards, Jerome -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Sean Landis Envoyé : vendredi 29 septembre 2006 20:40 À : discuss@restlet.tigris.org Objet : Surprising interaction between

RE: Method

:[EMAIL PROTECTED] Envoyé : lundi 2 octobre 2006 09:42 À : Jerome Louvel Objet : Re: Method Hi Jerome, In the current state, the description (from Metadata super class) and the uri property could be customized for the same method. Okay, I overlooked that. :/ Therefore

RE: Method

Hi Lars, I think Method should not be derived from Metadata because it doen't adds a value IMO. To avoid confusion if the Method can be compared by identity or not, we should convert Method (back?) to an Enum. Enums can always be compared by identity, so it limits confusion if Method

RE: Method

No problem Lars, I've been through this line of thought several times myself when I wanted to leverage the enums by mixing them with classes :-) Best regards, Jerome -Message d'origine- De : Lars Heuer [mailto:[EMAIL PROTECTED] Envoyé : mardi 3 octobre 2006 18:43 À : Jerome Louvel

RE: Allow Header

Hi Lars, Only non-standard headers can be added via the special attribute. The Allow header is supported at the API level by the Call.getClient().getAccepted*() methods. Best regards, Jerome -Message d'origine- De : Lars Heuer [mailto:[EMAIL PROTECTED] Envoyé : jeudi 5 octobre

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

Piyush, :) I'll be working full-time on beta 19 tomorrow, hopefully making good progress and maybe having a testable snapshot. If coding and testing go fine, I'll release on Monday or more likely on Friday next week. Best regards, Jerome -Message d'origine- De : Piyush Purang

RE: Status of b20 w/ pieces necessary for Spring Framework integration

Hi Peter, Good progress is made on beta 19. Release scheduled for next week. Best regards, Jerome -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Peter Murray Envoyé : vendredi 6 octobre 2006 14:32 À : discuss@restlet.tigris.org Objet : Status of b20 w/

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

Hi Lars, Thanks for the testing, I appreciate! Best regards, Jerome -Message d'origine- De : Lars Heuer [mailto:[EMAIL PROTECTED] Envoyé : samedi 7 octobre 2006 15:50 À : Jerome Louvel Objet : Re: Breaking Call into Request and Response (Was: Allow Header) Hi Jerome

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

Hi Piyush, I went through the same path before converting myself to the new API included in SVN: handle(Call call) == handle(Request request, Response response) The advantage of using Call as a holder of Request and Response is that you indeed encapsulate more information, having a

RE: Beta 19 and fluent builders

Hi Sean, I am concerned about abandoning the fluent style of configuration as I found this a tremendous advantage and selling point of the architecture. It is a very good thing to be able to examine one Java file and see the entire application layout before you. It is also nice to

RE: Beta 19 and fluent builders

Like methods, we don't know in advance the list of all protocols. Someone could decide to write a connector for some custom or new protocol and we should still allow it. However, we could restrict the protocol name to not include spaces for example (bad for XSD lists) and restrict the allowed

RE: Shutting down

Hi Piyush, By design, a Restlet doesn't have full access to its container. It may not even have a parent container in some cases. Also, in case a single container manages multiple applications, it wouldn't be a good idea to allow Restlets in one application to shutdown the container. In case

Powered by Restlet

Hi all, Sometimes ago, Lars suggested that I provide an affiliation button to put on web sites using Restlets. I thought it was a good idea and created thisbutton: This is also documented on the new Wiki. There is also a table that you can edit tolink your product or web site:

RE: b19 Wrapper (was: Re: b19 - Resource)

Hi Lars, So, we need the wrapper classes for the Restlet / Noelios engine? If they are needed for the latter, why don't we remove them from org.restlet and put them into the noelios.impl package? I indeed have a need for those wrappers in the NRE and I thought it would also benefit to

RE: Restlets and JMX

Hi, IMO, a JMX interface is primarily useful for an administrator who wants to monitor/manage a Resltet container, its connectors, its virtual hosts and of course its applications. Here is my candidate list: - ContainerMBean - ClientMBean | ServerMBean - ClientRouterMBean | ServerRouterMBean

RE: Restlets and JMX

Hi Sean, I think any component or restlet that has useful telemetry and/or knobs is a candidate for exposure as an MBean. The two above make sense to me. Agreed. Logging control is a candidate. Actually, in beta 19, the call logging (writing a file similar to an HTTP log) will be

RE: Restlets and JMX

Hi Pyiush, What about lifecycles? It is nice to be able to document lifecycle of a restlet and container etc... This would be centralized on RestletMBean because the Restlet class has the start(), stop(), isStarted() and isStopped() methods. Then we can expose status through the MBeans

RE: Running a simple example

Hi Pyiush, Your virtual host doesn't allow any domain names. That's why it fails. Use VirtualHost.getAllowedNames(); You can also use container.getDefaultHost().attach() directly if you prefer, it is setup to accept all requests. Best regards, Jerome -Message d'origine- De :

RE: New snapshot of beta 19

a lot of the changes you have made with b19 and i'm eager to incorporate them. If the release won't be for a few more days that would be good to know too, thanks! Kabe On 10/18/06, Jerome Louvel [EMAIL PROTECTED] wrote: FYI, I've just updated the snapshot to fix

RE: Restlets and JMX

Hi Pyiush, Stopping the container should stop all the connectors are they are conceptually also contained in the container. Could you let me know which connector doesn't respect the stop command? Best regards, Jerome -Message d'origine- De : Piyush Purang [mailto:[EMAIL PROTECTED]

RE: starting, stopping and starting a container throws an exception

Hi again, Thanks an interesting issue :-) After investigation, the Container does close the connectors as intended. This is actually done by the Component super class. In the Jetty 6 case, it does invoke the stop() method on the Jetty server, which apparently invokes the close() / stop() methods

Re: client POSTing

() throws IOException are implemented? And if so which? If so this should be documented... Or perhaps I am thinking of this wrong. Henry Home page: http://bblfish.net/ Sun Blog: http://blogs.sun.com/bblfish/ Foaf name: http://bblfish.net/people/henry/card#me -- Jerome Louvel http

RE: Response corruption using ServerServlet

Hi Sean, First behavior looks like a regression/bug. I will look at the rest tomorrow. Meanwhile, if you could have a look at ServerServlet code and propose a patch that would be useful. Best regards, Jerome -Message d'origine- De : news [mailto:[EMAIL PROTECTED] De la part de Sean

RE: Adding standard headers

to this email too). I'll release a new snapshot of beta 20 later today. Best regards, Jerome -Message d'origine- De : Jerome Louvel [mailto:[EMAIL PROTECTED] Envoyé : jeudi 26 octobre 2006 19:50 À : discuss@restlet.tigris.org Objet : RE: Adding standard headers Hi Mikkel

RE: Adding standard headers

Hi Mikkel, As you said, the problem lies in a JDK bug (details at: http://www.restlet.org/faq#18). One workaround is to use JDK 6 beta 2 if possible. Otherwise, I don't know how to workaround the bug. Setting the content type to may solve the issue? Could you try? Otherwise, we always have the

RE: Filter questions

Hi Vincent, You encountered the bug with filter that was just fixed in the latest snapshot. Please try it. Also, I'll modify the default StatusFilter to also catch Throwable and think about a way to let you plug a custom StatusFilter. Best regards, Jerome -Message d'origine- De :

RE: Filter questions

snapshot available too. Best regards, Jerome -Message d'origine- De : Jerome Louvel [mailto:[EMAIL PROTECTED] Envoyé : samedi 28 octobre 2006 12:14 À : discuss@restlet.tigris.org Objet : RE: Filter questions Hi Vincent, You encountered the bug with filter that was just fixed

RE: Adding standard headers

FYI, I've submitted a bug report to Sun asking for a backport to JDK 1.5 of the fix to this bug. I'll keep you updated. Thanks, Jerome -Message d'origine- De : Jerome Louvel Envoyé : samedi 28 octobre 2006 12:09 À : discuss@restlet.tigris.org Objet : RE: Adding standard headers

Extensions reorganization

Hi all, Recently, Lars Heuer suggested (http://restlet.tigris.org/issues/show_bug.cgi?id=151) that there would be room for a Restlet-Utils library, that would solely be based on the Restlet API. After thinking about it, it makes a lot of sense. For example, the FreeMarker extension should

RE: Adding standard headers

against Amazon S3, could you let me know if it works? http://www.restlet.org/downloads/current.zip Best regards, Jerome Louvel -Message d'origine- De : Jerome Louvel Envoyé : samedi 28 octobre 2006 12:09 À : discuss@restlet.tigris.org Objet : RE: Adding standard headers Hi

RE: SPI Factory + OSGi

Kabe, The SPI pattern is the standard mechanism used in all standard Java libraries like JDBC, JNDI, NIO, etc. The Restlet API was designed with the application developer as the main user. It does has the ability to create embedded containers, but it does try to hide as much complexity as

RE: Adding standard headers

FYI, Sun has replied positively to the idea of backporting the fix to this bug in JDK 5. It should be available soon! Let's keep our fingers crossed while waiting for JDK 1.5.0_10 :-) Best regards, Jerome -Message d'origine- De : Jerome Louvel [mailto:[EMAIL PROTECTED] Envoyé

Re: starting, stopping and starting a container throws an exception

Hi Piyush, The issue was actually coming from Restlet's code which was recreating the connector instead of reusing the instance. Fix to be checked in SVN. Best regards, Jerome Piyush Purang a écrit : thanks for looking into it .. now we wait for the folks at mortbay On 10/23/06, Jerome

RE: Filter questions

); return filter; } }; application.getStatusService().setEnabled(true); container.getDefaultHost().attach(, application); try { container.start(); } catch(Exception e){ e.printStackTrace(); } } } Jerome Louvel contact at noelios.com

  1   2   3   4   5   6   7   8   9   10   >