>From: "JS Portal Support" <[EMAIL PROTECTED]> > > The s in s:form here is the myfaces sandbox, not shale, as you probably > already guessed. >
My guess is that it has to do with command components you are using within the form. The "form" jsfid is the default JSF runtime component where "s:form" is enhanced to work with all the tomahawk bells-and- whistles. I'm not sure how it's related to the maven managed builds. Maybe it's a difference in the tomahawk or myfaces jar since maven will pull the latest snapshot? Gary > -----Original Message----- > From: JS Portal Support [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 31, 2007 3:31 PM > To: [email protected] > Subject: Clay jsfid="form" not working > > Hi, > > I just transitioned my projects over to use Maven. All works quite well and > I'm happy. However, I have a Clay form > allowbody="true"> in which all links end up coming back to the page the form > resides on. When I change to use jsfid="s:form", all works fine. Can this be > due to a missing Maven dependency on the core JSF jar? I used the > maven-myfaces-archetype to generate the project and thought that should > setup the dependencies properly. Or could it be due to the clay config > files? > > Does anyone have a clue what might cause this behaviour? > > Thanks, > Joost > > >
