geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-4407) Dupldate attribute entries exist in the config.xml while changing the value between zero-length string and no-zero-length string
Date Sat, 29 Nov 2008 21:48:46 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor resolved GERONIMO-4407.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2
                   2.1.4
         Assignee: Jarek Gawor

Committed fixes for this problem to trunk (revision 721726) and branches/2.1 (revision 721729).
The better solution for this problem would be to rewrite the code to use one map for attributes
(instead of 3) and one map for references (instead of 2). 


> Dupldate attribute entries exist in the config.xml while changing the value between zero-length
string and no-zero-length string
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4407
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4407
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 2.1.3, 2.2
>         Environment: Windows XP
> JDK 1.5.0
>            Reporter: Ivan
>            Assignee: Jarek Gawor
>             Fix For: 2.1.4, 2.2
>
>
> While an attribute's initial value is no-zero length  value, then we set  its value with
zero-length value in the portlet, then we could find the in the config.xml file, there are
 duplicate attribute entries.
> Like 
>             .......
>             <attribute name="LoginTimeout">0</attribute>
>             <attribute name="ShutdownDatabase">shutdown2</attribute>
>             <attribute name="ShutdownDatabase"/>
>             ......
> It seems that it is caused we use two Map (attributes, clearAttributes ) to keep the
attribute values, while we setting the attribute, no code checks that the attribute should
only exist in one map. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message