You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Dimitar Simeonov (JIRA)" <em...@incubator.apache.org> on 2012/07/18 19:05:34 UTC
[jira] [Created] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Dimitar Simeonov created EMPIREDB-150:
-----------------------------------------
Summary: <sample:formInputRow> component failed to parse/resolve the "for" attribute
Key: EMPIREDB-150
URL: https://issues.apache.org/jira/browse/EMPIREDB-150
Project: Empire-DB
Issue Type: Bug
Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
Reporter: Dimitar Simeonov
The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also <a href="https://issues.apache.org/bugzilla/show_bug.cgi?id=50147">Tomcat issue</a>.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Posted by "Rainer Döbele (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele closed EMPIREDB-150.
----------------------------------
Resolution: Fixed
Patch supplied by Dimitar Simenonov applied and verified.
> <sample:formInputRow> component failed to parse/resolve the "for" attribute
> ----------------------------------------------------------------------------
>
> Key: EMPIREDB-150
> URL: https://issues.apache.org/jira/browse/EMPIREDB-150
> Project: Empire-DB
> Issue Type: Bug
> Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
> Reporter: Dimitar Simeonov
> Assignee: Rainer Döbele
> Labels: patch
> Attachments: patch.txt
>
>
> The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also issue link.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere reopened EMPIREDB-150:
--------------------------------------------
> <sample:formInputRow> component failed to parse/resolve the "for" attribute
> ----------------------------------------------------------------------------
>
> Key: EMPIREDB-150
> URL: https://issues.apache.org/jira/browse/EMPIREDB-150
> Project: Empire-DB
> Issue Type: Bug
> Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
> Reporter: Dimitar Simeonov
> Assignee: Rainer Döbele
> Labels: patch
> Fix For: empire-db-2.3.1
>
> Attachments: patch.txt
>
>
> The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also issue link.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Posted by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere resolved EMPIREDB-150.
--------------------------------------------
Resolution: Fixed
Fix Version/s: empire-db-2.3.1
> <sample:formInputRow> component failed to parse/resolve the "for" attribute
> ----------------------------------------------------------------------------
>
> Key: EMPIREDB-150
> URL: https://issues.apache.org/jira/browse/EMPIREDB-150
> Project: Empire-DB
> Issue Type: Bug
> Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
> Reporter: Dimitar Simeonov
> Assignee: Rainer Döbele
> Labels: patch
> Fix For: empire-db-2.3.1
>
> Attachments: patch.txt
>
>
> The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also issue link.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Posted by "Rainer Döbele (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele reassigned EMPIREDB-150:
--------------------------------------
Assignee: Rainer Döbele
> <sample:formInputRow> component failed to parse/resolve the "for" attribute
> ----------------------------------------------------------------------------
>
> Key: EMPIREDB-150
> URL: https://issues.apache.org/jira/browse/EMPIREDB-150
> Project: Empire-DB
> Issue Type: Bug
> Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
> Reporter: Dimitar Simeonov
> Assignee: Rainer Döbele
> Labels: patch
> Attachments: patch.txt
>
>
> The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also issue link.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Posted by "Rainer Döbele (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420287#comment-13420287 ]
Rainer Döbele commented on EMPIREDB-150:
----------------------------------------
Hello Dimitar,
thak you very much for your patch, that was very helpful indeed.
Although our solution worked in our environment - your solution is a lot smarter and fulfils the standard.
Good work.
Regards
Rainer
> <sample:formInputRow> component failed to parse/resolve the "for" attribute
> ----------------------------------------------------------------------------
>
> Key: EMPIREDB-150
> URL: https://issues.apache.org/jira/browse/EMPIREDB-150
> Project: Empire-DB
> Issue Type: Bug
> Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
> Reporter: Dimitar Simeonov
> Assignee: Rainer Döbele
> Labels: patch
> Attachments: patch.txt
>
>
> The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also issue link.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Posted by "Dimitar Simeonov (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimitar Simeonov updated EMPIREDB-150:
--------------------------------------
Attachment: patch.txt
A patch to fix the tomcat issue.
> <sample:formInputRow> component failed to parse/resolve the "for" attribute
> ----------------------------------------------------------------------------
>
> Key: EMPIREDB-150
> URL: https://issues.apache.org/jira/browse/EMPIREDB-150
> Project: Empire-DB
> Issue Type: Bug
> Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
> Reporter: Dimitar Simeonov
> Labels: patch
> Attachments: patch.txt
>
>
> The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also <a href="https://issues.apache.org/bugzilla/show_bug.cgi?id=50147">Tomcat issue</a>.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (EMPIREDB-150) component
failed to parse/resolve the "for" attribute
Posted by "Dimitar Simeonov (JIRA)" <em...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/EMPIREDB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimitar Simeonov updated EMPIREDB-150:
--------------------------------------
Description: The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also issue link. (was: The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also <a href="https://issues.apache.org/bugzilla/show_bug.cgi?id=50147">Tomcat issue</a>.)
> <sample:formInputRow> component failed to parse/resolve the "for" attribute
> ----------------------------------------------------------------------------
>
> Key: EMPIREDB-150
> URL: https://issues.apache.org/jira/browse/EMPIREDB-150
> Project: Empire-DB
> Issue Type: Bug
> Environment: JDK6, JSF 2.1.7, Tomcat 7.0.27
> Reporter: Dimitar Simeonov
> Labels: patch
> Attachments: patch.txt
>
>
> The EL implementation in Tomcat 7 has been changed, as from 7.0.4 it disallows Java keyword literals as EL properties. See also issue link.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira