Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Fri, 1 Jul 2011 11:00:29 +0000 (UTC)
From: =?utf-8?Q?Martin_Ko=C4=8D=C3=AD_=28JIRA=29?= <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: 
 <407203592.8303.1309518029605.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (MYFACES-3203) improve h:form problems diagnostics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

improve h:form problems diagnostics
-----------------------------------

                 Key: MYFACES-3203
                 URL: https://issues.apache.org/jira/browse/MYFACES-3203
             Project: MyFaces Core
          Issue Type: Sub-task
            Reporter: Martin Ko=C4=8D=C3=AD
            Priority: Minor


Problem 1:=20
In multilevel templating developer losts context easily
and puts a new h:form into exiting one. In this situation myfaces should ou=
tput a warning or throw a exception

Problem 2:
component requiring h:form: some components require h:form to produce reque=
st. Outputs a warning if h:form is missing (this is very common problem, di=
scussed frequently at users mailing list)


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira