RE: Adding standard headers

2006-10-30 Thread Jerome Louvel
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: SPI Factory + OSGi

2006-10-30 Thread Jerome Louvel
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 possibl

RE: SPI Factory + OSGi

2006-10-30 Thread Jerome Louvel
Hi Kobe, Thanks for the detailed email. Note that the generated JARs are also Eclipse plugins which should/could be compatible with other OSGi environments. What OSGi environment are you actually using? I understand the problems related to using the current thread's classloader for any dynamic c

RE: Adding standard headers

2006-10-30 Thread Jerome Louvel
Hi Mikkel, I went ahead and implemented the proposed workaround. Now the AWS authorization header is computed with an "application/x-www-form-urlencoded" content-type header value when: - no content found - method is not PUT - Java version starts with "1.4" or "1.5" As I haven't tested it dir