1 2 Previous Next 16 Replies Latest reply on Jun 2, 2009 2:03 PM by luxspes Go to original post
      • 15. Re: Web Beans vs. .NET vs. RoR
        pmuir

        Read the code (look at changes in injection design, upfront resolution and verification of injection points, reflection caching (by default), delegation of reflection to container (optional), delegation of service discovery to container.

        • 16. Re: Web Beans vs. .NET vs. RoR

          Pete Muir wrote on Jun 02, 2009 13:31:



          But for these specific feature requests, custom contexts are possible in Seam3,



          Great!



          a programatic navigation API for JSF isn't planned (maybe for JSF 2.1)



          Already knew it... did not suprise me given JSF development history...




          , but we could look at doing this as a Seam extension. File a RFE in JIRA.


          Now this would be great... not only because it would make debugging easier (I hate those un-debuggable, un-loggable, .xml files) but because that means it would make it possible to write our own navigation managers based on the programmatic API (and read navigation configuration from new datasources, like for example a database or a webservice, as requested from some of my customers).


          1 2 Previous Next