Leszek Gawron wrote:
I agree that the syntax really sucks - but the old way was really very confusing. Now I also agree that upgrading by hand is a nightmare. So I would suggest that we simply write an upgrading stylesheet that scans an xml file for ${cocoon.session.SOMETHING} where SOMETHING is not a method on the session object and replaces this with the proper syntax. Shouldn't be too difficult to do this (we can also use a java class instead of xslt - I don't care).
Still there is one thing in trunk I do not like which breaks jxtg compatibility. It is the removal of wrappers around request, session etc. Because of that all users will be forced to change from ${cocoon.session.user.id} to ${cocoon.session.getAttribute('user').id}. Took me 2 hours to upgrade the smallest project I have to cocoon trunk. It will take at least few days to convert a project with 200+ templates. I'm already scared of bugs that it will introduce.
The fact that new syntax sucks is the least of the problems.
But the other valid point remains: the syntax. Now, what about:
${cocoon.session.attributes.user.id} ?Carsten
-- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
