Bug 867381
Summary: | Seam2.3 seam-gen generated action shows "The form component needs to have a UIForm in its ancestry. ..." message | ||
---|---|---|---|
Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Marek Schmidt <maschmid> |
Component: | Seam | Assignee: | Marek Novotny <mnovotny> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Marek Schmidt <maschmid> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.1.0 | CC: | myarboro, snagarwa |
Target Milestone: | --- | ||
Target Release: | 2.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: | http://java.net/jira/browse/JAVASERVERFACES-1922 | ||
Whiteboard: | Seam2.3 | ||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
On submitting a JSF request, a JSF warning message is displayed. As a workaround for this issue, use PRODUCTION value for javax.faces.PROJECT_STAGE in web.xml as follows:
<context-param>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Production</param-value>
</context-param>
As a result, the JSF request is submitted successfully.
|
Story Points: | --- |
Clone Of: | 832115 | Environment: | |
Last Closed: | 2013-07-22 13:25:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marek Schmidt
2012-10-17 12:00:21 UTC
I doubt that this issue is a clone of https://bugzilla.redhat.com/show_bug.cgi?id=832115 as I can see that change in sources. I will try to reproduce it. I forget on issue in JSF itself - http://java.net/jira/browse/JAVASERVERFACES-1922 No way how to get rid of this Warning, we don't want to use PRODUCTION level for seam-gen application from the start. <context-param> <param-name>javax.faces.PROJECT_STAGE</param-name> <param-value>Production</param-value> </context-param> Known issue for WFK 2.1. Fix requires JSF update. Referring to the Doc Text: The result of the workaround for this bug is also a warning message? Doc Text updated. This JSF issue was fixed in JSF 2.2.0-m01. So it won't be fixed for Seam with JSF 2.1 and EAP 6. |