Forgive me if this has already been brought up, but what about URIs > 255 chars ? I recall being on a PHP project three of four years ago and we were passing serialized objects around until we started losing data with a few HTTP proxies. Should this be a concern in 2006? What does the servlet spec say about URI size limits?
As much as I love JSF, there are occasions when I just wish I could map a java method to the URI itself ( Struts style ). I feel this way a lot now that my day job has shifted from complex CRUD screen to reports that need to be book marked. Dennis Byrne >-----Original Message----- >From: Mario Ivankovits [mailto:[EMAIL PROTECTED] >Sent: Thursday, April 6, 2006 01:52 AM >To: 'MyFaces Development' >Subject: Re: RESTful JSF > >Hi! >> Why do we need a component to take values out of the request and >> apply them to a managed bean? JSF managed-beans can do this >> right now without putting anything in the component tree. >> >As the example shows, it allows us to attach converter and validators. >Not every property of a managed bean is a string or other primitive type. >And not every converter can be looked up from the faces-config. >At last using validators we can secure what CAN be set to the managed >property. > >I think it makes no difference if the data were entered by the user or >comes in through get-requests. > >It might look like overhead using the view for this, but it'll give us >the same flexibility as we have normally. >And it detaches the url parameter from the managed-bean. So you can >refactor your beans withouth breaking the url. > >Ciao, >Mario > >
