[jsr-314-open-mirror] [jsr-314-open] New anti-JSF blog entry: http://facemetal.wordpress.com/2010/07/19/jsf/

[Alexander Smirnov]

On 07/21/2010 11:54 AM, Blake Sullivan wrote:
> There is no way to partition the beans to the pieces that consume them.  This causes two problems for large applications:
> 1) The names need to be made longer for uniqueness
> 2) All of the bean information needs to be loaded at startup.  This inefficiency is extremely apparent during development.
Actually, it's not a true. To namespacing beans, you can use
'aggregator' that contains getters for next level objects that can be
created 'on demand'. Netbeans JSF designer does it by creating 'page'
object for each view. With CDI, using the such object is even more
convenient.

About the blog article: don't worry about that. JSF wasn't intended to
solve PHP developer's problems, but to make web interface for corporate
systems cheeper and reduce development time, there its component model
and POJO backend give advantage.

> 
> -- Blake Sullivan
> 
> 
> On Jul 21, 2010, at 7:56 AM, Ed Burns wrote:
> 
>>>>>>> On Wed, 21 Jul 2010 09:31:32 +0200, Martin Marinschek <mmarinschek at apache.org> said:
>>
>> MM> The stuff which is still lacking from JSF, which he partially mentions:
>>
>> MM> - back button support
>> MM> - double click handling
>> MM> - pretty URLs
>>
>> MM> we should definitely address that at some point of time.
>>
>> Thank you so much for your summary.  The double click handling is being
>> covered by Roger as part of [559-SynchronizerToken]. 
>>
>> MM> And: something he mentions I also think is not really good is the
>> MM> "global" managed bean scope. It would be good to have a way to let
>> MM> managed beans live only in a reduced, page (or conversation) visible
>> MM> scope.
>>
>> Doesn't CDI give you this?
>>
>> Ed
>> -- 
>> | edburns at oracle.com | office: +1 407 458 0017
>> | homepage:          | http://ridingthecrest.com/
>> | 18 work days until JSF 2.1 Milestone 2
>