I have a seperate faces-config.xml file for a seperate context for example faces-subcontext.xml
However it seams the from-view-id and to-view-id are not context relative and I have to put /subcontext/view.jsp everytime. I would think since it was in the faces-subcontext.xml that it would assume /subcontext/ as a base in the from-view-id and to-view-id. Seems like it makes for a lot of extra work making sure the subcontext is in every view path. Shawn -----Original Message----- From: [EMAIL PROTECTED] To: MyFaces Discussion; [EMAIL PROTECTED] Sent: 1/16/2006 5:51 PM Subject: Re: Shale and MyFaces On 1/16/06, Simon Kitching < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: On Mon, 2006-01-16 at 20:56 +0100, Werner Punz wrote: > Well seam basically is JSF interwoven with EJB3, the thing is, basically > every session bean becomes automatically a backend bean, so you program > the entire backend code all three tiers in EJB3. If you do not like that > stay away. A developer at my most recent client had done an evaluation of Seam, and rejected it due to this point. According to him, presentation logic ends up in EJB stateless session beans. This isn't necessarily bad for small projects; J2EE has always been massively overcomplicated for projects of the size of a few weeks development. However proper separation of presentation and business logic is critical for larger projects. That's an interesting line of reasoning (although, as Andrew points out, you're not *required* to use EJB3 for the backing beans). Wouldn't that same line of reasoning reject the use of pure POJO backing beans, because it puts presention logic in Java classes? I would expect that the JSF backing beans you write for Seam would be similar in content to the JSF backing beans you write wthout it ... the event handlers would delegate to your real business logic anyway, and the fact that the JSF backing bean might itself be an EJB3 bean is an implementation detail for the folks writing the view tier portion of the application. Craig **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ****************************************************************************
