RE: Shale and MyFaces

[James Salt]

Hi Yee   I am currently using Seam + Facelets to develop web applications (I however have never used Shale-Clay). These are my experiences.   Yes it does lean very heavily on top of Hibernate/EJB3 but this for me is a great asset as it handles the persistence aspect of my web application seamlessly (something that MyFaces-Shale-Clay will not), incorporating if I WISH the more heavy handed aspect of EJB3.  (transactions etc).     As far as view technology goes Seam has developed a very good set of Contexts that expand on those supplied by JSF (primarily the Conversation context), which allows the demarcation of multi page transactions, automatically coping with persistence issues over long running requests (i.e. use hibernate/EJB3 to fetch a Entity/Object and then later in the same request (but not same event) fetch the a related object to Entity/Object without getting a LazyInitialisation error. The conversation context also allows you to seamlessly hold state (not in the session) for the whole of the conversation knowing that once the conversation has ended it will be disposed of gracefully.   Also a new and nice feature is the page flow management via a process language (JPDL) integrating page flow decisions from context variables (i.e. #{reservation.showSolicitorInfo}, and allow actions to be triggered by transitions/outcomes of each page (i.e. transition “success” triggers action #{reservation.finish}, this greatly disassociates the view from the application logic, whilst enhancing your expressiveness.   I am new to Facelets, but my experience so far is very positive (allowing integration of jstl/jsf _expression_ tags in the same page ala JSF 1.2 spec is particularly great), also the templating structure is quite intuitive.   But as you can see I am keen on Seam, so take it as a biased view.   Hope my ramblings help. James Salt From: Yee CN [mailto:[EMAIL PROTECTED] Sent: 16 January 2006 16:28 To: 'MyFaces Discussion' Subject: RE: Shale and MyFaces   Hi Andrew,   Can you please share your experience with SEAM? It is production ready? I heard something like that it is hilariously slow in starting up…   Is there any gotcha? I had a quite look at it a while back, and find it quite interesting, although I was a bit turned off by it heavy lean towards ejb3. I find raw JSF painful to use – and I am seriously considering migrating to one of the combinations you mentioned once I got a chance to do so.   Many thanks in advance Yee   From: Andrew Robinson [mailto:[EMAIL PROTECTED] Sent: Monday, 16 January 2006 11:51 PM To: MyFaces Discussion Subject: Re: Shale and MyFaces   This is not a direct answer, but wanted to also let you know there is a decision between shale and jboss-seam. Both have more robust dialog support than JSF and both implement a higher level of IoC (inversion of control) to be able to "surround" your functionality. Shale has a nice page view controller, and JBoss-Seam has a nice interceptor/factory pattern. It becomes one of those tired debates of which Java frameworks you want to combine on the server. >From the list, I have a feeling most people choose one of the following when selecting frameworks to combine: MyFaces + Facelets + JBoss-Seam MyFaces + Shale + Clay Some people also try the the JSF/Tiles integration, but I found it severly flawed and facelets is incomparably better than Tiles, especially when working with JSF. I cannot speak to Shale-Clay as I have not used it (I am running the first bullet combo). -Andrew On 1/16/06, Miller, John <[EMAIL PROTECTED]> wrote: Can someone explain if there would be any reason to consider Shale if not converting an existing STRUTS application. I/We are currently moving an existing custom web app (not struts) to a standard framework (JSF/MyFaces). I have seen a lot of discussion about using Shale and MyFaces together. So my question is what does Shale give me that a pure MyFaces/JSF impl doesn't? I have downloaded Shale exclusively for the JUnit testing of MyFaces.       NOTICE: This message, including all attachments transmitted with it, is for the use of the addressee only. It may contain proprietary, confidential and/or legally privileged information belonging to Litle & Co. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, you must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message. If you believe you have received this message in error, please delete it and all copies of it from your system and notify the sender immediately by reply e-mail. Thank you.