Well, the thing is that in a large app you are going to need to split your pages.xml up anyway (which is why seam 1.1 lets you put stuff in myViewId.page.xml files as an alternative to META-INF/pages.xml). But then you get back to the same kind of thing that sucked with Java (code and metadata in two files). So, i wondered if the solution that worked well for Java could also work here. I mean ... the view template is _already_ XML, so why not stick some more XML in there...
It kinda goes back more to the oldschool style of JSP app where everything was driven by the page definition than the action-style web framework. Remember that JSF is naturally page-oriented, not action-oriented. Anyway, its just an idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986742#3986742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986742 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
