Spring and JSF integration-frustration
November 12, 2008 – 8:31 pmI have not posted in quite some time but I ran into a small problem today that I hadn't seen in many spring/JSF integration documents. Our current thick application is heavily dependent upon spring to wire together our views/controllers/and web services. Originally, there were naming conflicts between beans. A naming scheme was devised similar to java package naming where "."s are used in combination with the name (i.e. mycontext.geographicmap.mapattribute). Recently I began working with JSF and knew that "." has a different meaning when used in JSF El processing. For example, #{mapcontext.attributes} is going to call the attributes property. However, I thought my DelegatingVariableResolver would be smart enough to know that to spring those "." don't mean the same as in JSF. However, since JSF is calling the DelegatingVariableResolver, that expression is already parsed before it gets to the spring classes. Long story short, if you're integration JSF and Spring, make sure your spring ...
