Hi We have solved the previous problems. I think we should commit this one too:
MYFACES-3078 performance: allow to disable JSP support and everything will be ready for a release next week after myfaces-test release. regards, Leonardo Uribe 2011/5/9 Leonardo Uribe <lu4...@gmail.com>: > Hi > > 2011/5/9 Martin Koci <martin.kocicak.k...@gmail.com>: >> Hi, >> >> I see one big issue: https://issues.apache.org/jira/browse/MYFACES-3117 >> That may require a change in server state management, so I suggest solve >> it before first 2.1 release > > Just for information the issue title is this: > > MYFACES-3117 Current server state saving implementation prevents > multi-window usage > > In my understanding, the current implementation was made taking into > account the back button. So, if an user navigates from one view to > another one and goes back, the state will be restored. > > @Martin Koci: Could you open a thread on myfaces dev list, so we can > discuss this one properly? This issue is not easy to understand, but > it is very important and deserves a full discussion with myfaces > community. > >> >> Another one is a big performance improvement: >> https://issues.apache.org/jira/browse/MYFACES-3130 that needs >> discussion. >> > > @Martin Koci: Could you open a thread on myfaces dev list, so we can > discuss this one properly too? In theory, it is ok to use iteration > using indices instead call for an iterator for components. In this > case we are supposing an implementation detail about UIComponent, but > I can imagine someone overriding this stuff and using other structure > different to ArrayList. > > I would like to have a list about the tasks we need to do to enhance > myfaces core performance, to take concrete actions and make myfaces > even better. > > regards, > > Leonardo Uribe > >> >> Regards, >> >> Kočičák >> >> Leonardo Uribe píše v Pá 06. 05. 2011 v 11:48 -0500: >>> Hi >>> >>> It could be good to do a release of myfaces core 2.0.5 and 2.1.0-rc in >>> 1 or 2 weeks. >>> >>> The code for myfaces core 2.1.x (actually in trunk) is ready, all >>> features specified by >>> the spec were implemented. So to keep things moving and get some >>> feedback, I think >>> it could be good to do a release, so people can give a try. >>> >>> After that, it could be good to do a release of tomahawk too (1.1.11). >>> Most of the issues >>> planned for this release were already solved, and the only thing left >>> is do a cleanup for >>> sandbox for jsf 2.0. >>> >>> If you have some issues that needs to be included in these releases, >>> it is a good >>> time to say it. >>> >>> best regards, >>> >>> Leonardo Uribe >>> >> >> >> >
