[embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-96) Read-only properties should be marked as read-only

Ondrej Žižka (JIRA) jira-events at lists.jboss.org
Fri Mar 13 17:09:24 EDT 2009


    [ https://jira.jboss.org/jira/browse/EMBJOPR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457246#action_12457246 ] 

Ondrej Žižka commented on EMBJOPR-96:
-------------------------------------

The following properties are re-set to original value after being set.
I don't guarantee they are all intended to be read-only.
They are all from class-loading area.

exportAll: expected 'ALL', found 'NON_EMPTY'
cache: expected 'false', found 'true'
blackList: expected 'false', found 'true'
importAll: expected 'false', found 'true'
name: expected 'my.name', found 'eardeployment.ear'
parentFirst: expected 'false', found 'true'
version: expected '10.9.8.7', found '0.0.0'

> Read-only properties should be marked as read-only
> --------------------------------------------------
>
>                 Key: EMBJOPR-96
>                 URL: https://jira.jboss.org/jira/browse/EMBJOPR-96
>             Project: Embedded Jopr
>          Issue Type: Bug
>            Reporter: Ondrej Žižka
>            Assignee: Ondrej Žižka
>             Fix For: 1.2
>
>
> Currently, read-only properties appear the same as editable ones.
> See e.g. any EAR Configuration, property Name.
> If you edit such property, it simply returns to previous value.
> It should be noted somehow that they are readonly,
> and their input should be disabled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       




More information about the embjopr-issues mailing list