On 1/12/06, Dennis Byrne <[EMAIL PROTECTED]> wrote:
Feedback to the EG alias (mentioned earlier in the thread) would definitely be a good way to bring the idea to the expert group's attention.
In the mean time, I was faced with exactly the same issue in Shale, where I wanted to provide an extra capability if you are running on a J2SE 5 platform. I wanted to let you declare a managed bean with annotations, instead of requiring that they be in a faces-config.xml file -- but configuration-based managed beans should still work (and, indeed, they should override the annotated values if appropriate).
To do this, I had to provide my own variable resolver, and essentially re-implement the standard managed beans factory capabilities, integrating in support for annotated beans that declare themselves. It doesn't yet support the list-entries and map-entries functionality of the standard stuff, but it works pretty nicely for simple beans and properties.
Check out the classes in the shale-tiger.jar file included in a Shale nightly build[1], and the javadocs for them[2].
Craig
[1] http://cvs.apache.org/builds/struts/nightly/struts-shale
[2] http://struts.apache.org/struts-shale/shale-tiger/apidocs/index.html
Perhaps a custom variable resolver could be the solution?
Feedback to the EG alias (mentioned earlier in the thread) would definitely be a good way to bring the idea to the expert group's attention.
In the mean time, I was faced with exactly the same issue in Shale, where I wanted to provide an extra capability if you are running on a J2SE 5 platform. I wanted to let you declare a managed bean with annotations, instead of requiring that they be in a faces-config.xml file -- but configuration-based managed beans should still work (and, indeed, they should override the annotated values if appropriate).
To do this, I had to provide my own variable resolver, and essentially re-implement the standard managed beans factory capabilities, integrating in support for annotated beans that declare themselves. It doesn't yet support the list-entries and map-entries functionality of the standard stuff, but it works pretty nicely for simple beans and properties.
Check out the classes in the shale-tiger.jar file included in a Shale nightly build[1], and the javadocs for them[2].
Craig
[1] http://cvs.apache.org/builds/struts/nightly/struts-shale
[2] http://struts.apache.org/struts-shale/shale-tiger/apidocs/index.html
