It's definitley happening. It didn't render an action attribute. All I did was <af:form id="myform> and it rendered <form id="myform">.
The reason I was using af:form is because I was trying to use af:subform for something... Frank Russo Senior Developer FX Alliance, LLC -----Original Message----- From: Adam Winer [mailto:[EMAIL PROTECTED] Sent: Thursday, March 30, 2006 12:00 PM To: [email protected] Subject: Re: af:form doesn't render an action attribute af:form definitely always renders an "action". The action has nothing to do with the submit button (if it did, how would you deal with having two buttons?). It's just about posting back to the original page. You can use h:commandButton, h:form, etc.: ADF doesn't at all require that you only use ADF components. So you can certainly use h:form for now, but I'm really interested in how you managed to get af:form to not render an "action". Could you double-check that that's really happening? -- Adam Winer On 3/30/06, Frank Russo <[EMAIL PROTECTED]> wrote: > I have the following tag in my page: > > <af:form id="searchForm"> > > which gets rendered as: > > <form id="searchForm"> > > When I use the standard version of the component: > > <h:form id="searchForm"> > > it renders as: > > <form id="searchForm" action="myapp/search.jsf"> > > which is based, I assume on the button of the submit button I'm using > on the page, which is: > > <h:commandButton id="searchUsers" value="Search" > action="#{searchBean.searchUsers}"/> > > Shouldn't the af:form render the html form tag with an action? If not, > on submit, the page seems to be confused on where to go. > > Am I supposed to be using an adf version of the commandButton? If so, > I thought that the adf components were supposed work with standard > components, as well as other third party components, like tomahawk. > > Thanks... > > Frank Russo > Senior Developer > FX Alliance, LLC > > > >
