You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org> on 2005/02/13 17:12:11 UTC
[jira] Created: (BEEHIVE-291) netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
--------------------------------------------------------------------------------------------------------
Key: BEEHIVE-291
URL: http://issues.apache.org/jira/browse/BEEHIVE-291
Project: Beehive
Type: Bug
Components: NetUI
Versions: V1Beta
Reporter: Eddie O'Neil
Currently, the pageFlow and sharedFlow implicit objects are data bindable from a browser with:
{pageFlow.foo} or {sharedFlow.foo}
This can lead to manipulation of values exposed from the pageFlow / sharedFlow to JSPs in ways that weren't intended. While this can be used to expose properties on a JPF as if the JPF itself was a form bean, it's often the case that a JPF needs to expose read-only data to a JSP that isn't web-writable.
The netui-config file and the expression language need to support *preventing* this type of expression-based update by allowing an app developer to constrain the list of writable implict objects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-291) netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-291?page=all ]
Eddie O'Neil updated BEEHIVE-291:
---------------------------------
type: Improvement (was: Bug)
Version: V1
Fix Version: TBD
(was: V1)
Pushing this out to a future release; this is really an enhancement to the current feature set as opposed to a bug.
Will get to it if possible...
> netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
> --------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-291
> URL: http://issues.apache.org/jira/browse/BEEHIVE-291
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1, V1Beta
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Fix For: TBD
>
> Currently, the pageFlow and sharedFlow implicit objects are data bindable from a browser with:
> {pageFlow.foo} or {sharedFlow.foo}
> This can lead to manipulation of values exposed from the pageFlow / sharedFlow to JSPs in ways that weren't intended. While this can be used to expose properties on a JPF as if the JPF itself was a form bean, it's often the case that a JPF needs to expose read-only data to a JSP that isn't web-writable.
> The netui-config file and the expression language need to support *preventing* this type of expression-based update by allowing an app developer to constrain the list of writable implict objects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-291) netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-291?page=history ]
Eddie O'Neil updated BEEHIVE-291:
---------------------------------
Fix Version: V1
> netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
> --------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-291
> URL: http://issues.apache.org/jira/browse/BEEHIVE-291
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Fix For: V1
>
> Currently, the pageFlow and sharedFlow implicit objects are data bindable from a browser with:
> {pageFlow.foo} or {sharedFlow.foo}
> This can lead to manipulation of values exposed from the pageFlow / sharedFlow to JSPs in ways that weren't intended. While this can be used to expose properties on a JPF as if the JPF itself was a form bean, it's often the case that a JPF needs to expose read-only data to a JSP that isn't web-writable.
> The netui-config file and the expression language need to support *preventing* this type of expression-based update by allowing an app developer to constrain the list of writable implict objects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-291) netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-291?page=history ]
Eddie O'Neil reassigned BEEHIVE-291:
------------------------------------
Assign To: Eddie O'Neil
> netui-config needs to be able to configure the writability of the pageFlow / sharedFlow binding contexts
> --------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-291
> URL: http://issues.apache.org/jira/browse/BEEHIVE-291
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
>
> Currently, the pageFlow and sharedFlow implicit objects are data bindable from a browser with:
> {pageFlow.foo} or {sharedFlow.foo}
> This can lead to manipulation of values exposed from the pageFlow / sharedFlow to JSPs in ways that weren't intended. While this can be used to expose properties on a JPF as if the JPF itself was a form bean, it's often the case that a JPF needs to expose read-only data to a JSP that isn't web-writable.
> The netui-config file and the expression language need to support *preventing* this type of expression-based update by allowing an app developer to constrain the list of writable implict objects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira