Craig McClanahan schrieb: > On 1/16/06, *Werner Punz* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > > [snip] > > Well from the small project I have done, you basically can take all your > JSF knowledge with you, Seam is an extension which simplifies many > things in JSF. > > > Yep ... like Shale, Seam is a layer of additional functionality built on > top of JSF, not a separate framework that just happens to coexist with it. > > For instance you do not define any backing beans in xml > anymore, just a class which you then annotation as session bean etc... > > > If you like that idea, but for some reason don't want to buy in to the > whole Seam stack, Shale can do this now as well (in nightly builds) when > you add the shale-tiger.jar library to your project. See the overall > description of the Shale Tiger extensions[1], and the javadocs for > annotated managed beans[2] for more info. > > The hardest part of seam is to get the project structure and deployment > in place the rest is "seamless" > > Hi thanks for pointing it out, I was aware of them (and love them) but forgot to mention your work, it is better to have this posted by the author anyway.
Anyway, I checked out the extensions, and personally think they are heavens sent, but in my opinion there is huge room for more. What I really love about Seam and what is missing in the extensions is an easy dialog mechanism. Currently you have to define your own dialog flow in a file. Seam does it rather basic, and easy to understand with a @begin and @end annotation marking the dialog flow borders, everything in between is not interesting configurationwise. Is there anything similar planned for Shale? Also one room for improval might be an annotation or implicit navigation handler which directs with an implicit return "nextPage"; onto a nextPage.jsp/jsf if it can be located within a search path, unless it is overridden by the config file. That would reduce the number of navigational entries tremendously.
