FileUpload extension: multipart/form-data support broken in RC1/RC2

Hi, we noticed a problem with the FileUpload extension when parsing multipart/form-data requests. There is always the following exception (RC2): - org.apache.commons.fileupload.FileUploadException: the request was rejected because no multipart boundary was found at

RE: Re: Issues with WADL extension

Hello Thierry, I just tested it and there is still one thing missing (oversaw that at my tests the other day): In htmlConvert.​xsl the ..research.. namespace still occurs in another line: xsl:variable name=wadl-nshttp://research.sun.com/wadl/2006/10/xsl:variable That has also to be replaced

RE: Re: Issues with WADL extension

Hi Thierry, a further note on the XSLT transformation and the generated HTML: It seems that the output misses some parts if the standard JDK XSLT-TransformerFactory (XSLTC in package com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl) is used. I have attached a WADL and the

RE: Re: Issues with WADL extension

Hi Thierry, ah, thanks for the info. Yeah, now that I look at it, the javadoc is pretty obvious :) cheers, Carsten -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2462112

RE: Re: Issues with WADL extension

Hello Thierry, great, thanks alot. cheers, Carsten -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2461541

Issues with WADL extension

Hi, first of all, congratulations to the RC1 release and thanks for making Restlet such a pleasure to work with! I just migrated from M7 to RC1 and have issues with the WADL features: I get a NPE when making an OPTIONS request to retrieve the WADL. The problem basically seems to be, that

Infinite loop in EncodingReader.addValues()

Hi, I get an infinite loop when calling EncodingReader.addValues() (in RC1): new EncodingReader(gzip,deflate).addValues(new ArrayListEncoding()); Cheers, Carsten -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2460492

RE: Issues with WADL extension

The reason, why the output is empty, when requesting the HTML version of the WADL, seems to be the following: The stylesheet /org/restlet/ext/wadl/htmlConvert.xsl, which converts the generated WADL, uses the WADL namespace http://research.sun.com/wadl/2006/10;. But the generated WADL has the

Potential stackoverflow in Engine c'tor when registerHelper() fails

Hi, I got a stackoverflow exception during instantiation of org.restlet.engine.Engine: (stacktrace from Restlet 2.0M6) ... org.restlet.engine.Engine.(Engine.java:325) org.restlet.engine.Engine.register(Engine.java:246) org.restlet.engine.Engine.register(Engine.java:235)

Bug in MediaType Parameter handling

Hi, when I do the following: --- MediaType mediaType = MediaType.valueOf(application/atom+xml; charset=UTF-8); System.out.println(mediaType.toString()); --- I get this output (with 2.0M6): application/atom+xml; charset=UTF-8; charset=UTF-8 Seems to be a bug in the handling of parameters.

(Servlet context) How to dynamically add Applications to already initialized ServerServlet?

Hi, I use Restlet in a servlet container, using the ServerServlet. In the web.xml I have added the org.restlet.component param and set my specific Component class. When it comes to the applications for this component, I have to be able to dynamically add and remove applications. But once

Thoughts on renamed functions (setEncodeRequest-setEncodingRequest)

Hi, I've just updated from 2.0 M4 to M6 and noticed that quite some methods have been renamed, especially getters and setters of boolean field values. For example in class org.restlet.engine.application.Encoder setEncodeRequest(boolean) has been renamed to setEncodingRequest(boolean) I have to

(fileupload ext) RepresentationContext.getCharacterEncoding()

Hi, I just stumbled upon the RepresentationContext class in the FileUpload extension. There it reads: public String getCharacterEncoding() { if (!this.multipartForm.getEncodings().isEmpty()) { return this.multipartForm.getEncodings().get(0).getName(); }

RE: Re: Resources cannot be found anymore after upgrading from 2.0M5 to 2.0M6

Hello Fabian, which resource is supposed to match the http://localhost:900​0/workspaces/W1 request? From looking at your source code, I guess that you intended this Route to match: wrouter.attach(/{wksp}, WorkspaceResource.class); But that doesn't work because the new default matching mode

Digest-Authentication on the server side (2.0 M4)

Hi, I have problems getting Digest-Authentication to work on the server side. I always get this NPE: - java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:768) at