There's one thing in Facelets that always catches me out and I was just wondering if someone could give me guidance on what I should be doing.
The webapp I'm creating (with Seam) will be created by me but configured by someone else. The configuration needs to be kept in a JSF page as the application itself is made up of several smaller presences. But how do I set variables in JSF so that they are accessible throughout the application? In non Facelets JSF apps, you have the scope tag. But I understand that Facelets works differently so I cannot do this. Just using <c:set> on it's own only makes the variable I create accessible for that small section/composition.
My second problem is with Facelet's pickyness when it comes to source validation. For example, I cannot do:
Instead I have to have the complete code fragments in the ui:fragments (which is not going to happen). Or I can set them in variables and just have something like:
But that leads me back to my first problem. I don't want to have a load of little variables all over the places - I'd like them in one simple page. I then will just need to include this page at the top level, and have the variables filter through down the rest of the pages.
Did all this make sense? And if so - does anyone have any guidance?