RE: error running b18 on Simple

2006-08-10 Thread Jerome Louvel

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 : error running b18 on Simple
 
 On grabbing b18 from svn and compiling, my sample app dies 
 immediately 
 on any request with: 
 
 Aug 9, 2006 6:16:54 PM 
 com.noelios.restlet.connector.AbstractHttpServer 
 handle 
 WARNING: Error while handling an HTTP server call: 
 Aug 9, 2006 6:16:54 PM 
 com.noelios.restlet.connector.AbstractHttpServer 
 handle 
 INFO: Error while handling an HTTP server call 
 java.lang.NullPointerException 
 at 
 org.restlet.connector.AbstractServer.handle(AbstractServer.java:66) 
 at 
 com.noelios.restlet.connector.AbstractHttpServer.handle(Abstra
 ctHttpServer.java:86) 
 at 
 com.noelios.restlet.connector.AbstractHttpServer.handle(Abstra
 ctHttpServer.java:67) 
 at 
 com.noelios.restlet.ext.simple.SimpleServer.handle(SimpleServe
 r.java:134) 
 at simple.http.Dispatcher.run(Unknown Source) 
 at simple.util.process.Daemon.execute(Unknown Source) 
 at simple.util.process.Daemon.run(Unknown Source) 
 
 It looks like the 'target' property of AbstractServer isn't 
 being assigned. 
 
 Chris 
 
 -- 
 Chris Winters ([EMAIL PROTECTED]) 
 Lead Software Developer 
 Vocollect Healthcare Systems 
 
 CONFIDENTIAL, PRIVILEGED COMMUNICATION: This e-mail is private and 
 intended for the addressee(s) only. It may contain privileged and/or 
 confidential information. If you have received it in error 
 you are  not 
 authorized to disseminate it in any manner; please delete it and any 
 copies and reply to the sender that it was misdirected. 
 
 
 


Re: error running b18 on Simple

2006-08-10 Thread Chris Winters

Chris Winters wrote:

Jerome Louvel wrote:

Thanks for reporting this regression. It's fixed it in SVN. Make sure you
fully refresh your local copy.


Wow, lots of updates! And more API breaks :-) I'll plow through those 
and let you know how it goes.


BTW, thanks for keeping up the relatively detailed notes the changelog. 
I know it's a PITA to do but much appreciated.


Okay, that didn't take too long. Mostly just the MediaType/s collapsing 
(which is nice). 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 request. 
Changing it to:


DirectoryHandler staticFiles =
new DirectoryHandler( this, webUri, index.html );

worked fine. Do you think it's a good idea to have a set of possible 
files, similar to the Apache directive?


I'll post a link to the silly sample app in a few minutes. Thanks for 
the updates!


Chris

--
Chris Winters ([EMAIL PROTECTED])
Lead Software Developer
Vocollect Healthcare Systems

CONFIDENTIAL, PRIVILEGED COMMUNICATION: This e-mail is private and 
intended for the addressee(s) only. It may contain privileged and/or 
confidential information. If you have received it in error you are  not 
authorized to disseminate it in any manner; please delete it and any 
copies and reply to the sender that it was misdirected.




RE: error running b18 on Simple

2006-08-10 Thread Jerome Louvel

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 request. 
 Changing it to: 
 
  DirectoryHandler staticFiles = 
  new DirectoryHandler( this, webUri, index.html ); 
 
 worked fine. Do you think it's a good idea to have a set of possible 
 files, similar to the Apache directive? 

The issue is coming from the new negotiationEnabled flag which is turned
off by default now. 
Just do directory.setNegotiationEnabled(true); to enable it. When exposing
static files that were generated like Javadocs, there is no need for content
negotiation based on file extensions. First, that slows things down a bit
and then it creates side-effects with inner class names like Router.Mode
because Mode is not a recognized extension, etc.

As for having multiple index base names I'm not sure yet because that
complexifies things for now. If you really need this you can always setup
additional DirectoryHandlers for a specific trees of files.

 I'll post a link to the silly sample app in a few minutes. Thanks for 
 the updates! 

I'm looking forward to playing with it :-)

Best regards,
Jerome