You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ron Piterman (JIRA)" <ta...@jakarta.apache.org> on 2005/07/15 17:06:11 UTC

[jira] Created: (TAPESTRY-406) Bean Property does not get updated from component parameter

Bean Property does not get updated from component parameter
-----------------------------------------------------------

         Key: TAPESTRY-406
         URL: http://issues.apache.org/jira/browse/TAPESTRY-406
     Project: Tapestry
        Type: Bug
    Reporter: Ron Piterman
    Priority: Critical
 Attachments: bug.zip

in the bean's <set ... referencing a component parameter causes the following behaiviour:
the first value which is set to the bean property is being use in all instances of the component, as if the bean is shared between instances, without updating its properties.


-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Commented: (TAPESTRY-406) Bean Property does not get updated from component parameter

Posted by "Kent Tong (JIRA)" <ta...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/TAPESTRY-406?page=comments#action_12316042 ] 

Kent Tong commented on TAPESTRY-406:
------------------------------------

The bug seems to be here:

public class BindingBeanInitializer extends AbstractBeanInitializer
{
    public void setBeanProperty(IBeanProvider provider, Object bean)
    {
        if (_binding == null) 
        //BUG: Because there is only one BindingBeanInitializer for a 
        //component type, it should NOT cache the binding because the 
        //binding refers to a specific component.
        {
            IComponent component = provider.getComponent();
            String description = BeanMessages.propertyInitializerName(_propertyName);
            _binding = _bindingSource.createBinding(
                    component,
                    description,
                    _bindingReference,
                    BindingConstants.OGNL_PREFIX,
                    getLocation());
        }
        Class propertyType = PropertyUtils.getPropertyType(bean, _propertyName);
        Object bindingValue = _binding.getObject(propertyType);
        setBeanProperty(bean, bindingValue);
    }
}


> Bean Property does not get updated from component parameter
> -----------------------------------------------------------
>
>          Key: TAPESTRY-406
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-406
>      Project: Tapestry
>         Type: Bug
>     Reporter: Ron Piterman
>     Priority: Critical
>  Attachments: bug.zip
>
> in the bean's <set ... referencing a component parameter causes the following behaiviour:
> the first value which is set to the bean property is being use in all instances of the component, as if the bean is shared between instances, without updating its properties.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Closed: (TAPESTRY-406) Bean Property does not get updated from component parameter

Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-406?page=all ]
     
Howard M. Lewis Ship closed TAPESTRY-406:
-----------------------------------------

    Fix Version: 4.0
     Resolution: Fixed

> Bean Property does not get updated from component parameter
> -----------------------------------------------------------
>
>          Key: TAPESTRY-406
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-406
>      Project: Tapestry
>         Type: Bug
>     Reporter: Ron Piterman
>     Assignee: Howard M. Lewis Ship
>     Priority: Critical
>      Fix For: 4.0
>  Attachments: bug.zip
>
> in the bean's <set ... referencing a component parameter causes the following behaiviour:
> the first value which is set to the bean property is being use in all instances of the component, as if the bean is shared between instances, without updating its properties.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Commented: (TAPESTRY-406) Bean Property does not get updated from component parameter

Posted by "dpr (JIRA)" <ta...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/TAPESTRY-406?page=comments#action_12315936 ] 

dpr commented on TAPESTRY-406:
------------------------------

Looks similar to http://issues.apache.org/jira/browse/TAPESTRY-289

> Bean Property does not get updated from component parameter
> -----------------------------------------------------------
>
>          Key: TAPESTRY-406
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-406
>      Project: Tapestry
>         Type: Bug
>     Reporter: Ron Piterman
>     Priority: Critical
>  Attachments: bug.zip
>
> in the bean's <set ... referencing a component parameter causes the following behaiviour:
> the first value which is set to the bean property is being use in all instances of the component, as if the bean is shared between instances, without updating its properties.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Updated: (TAPESTRY-406) Bean Property does not get updated from component parameter

Posted by "Ron Piterman (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-406?page=all ]

Ron Piterman updated TAPESTRY-406:
----------------------------------

    Attachment: bug.zip

Th eattached file contains an example. The three ValidFields get all the same required state, eventhough they shouldn't

> Bean Property does not get updated from component parameter
> -----------------------------------------------------------
>
>          Key: TAPESTRY-406
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-406
>      Project: Tapestry
>         Type: Bug
>     Reporter: Ron Piterman
>     Priority: Critical
>  Attachments: bug.zip
>
> in the bean's <set ... referencing a component parameter causes the following behaiviour:
> the first value which is set to the bean property is being use in all instances of the component, as if the bean is shared between instances, without updating its properties.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Assigned: (TAPESTRY-406) Bean Property does not get updated from component parameter

Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-406?page=all ]

Howard M. Lewis Ship reassigned TAPESTRY-406:
---------------------------------------------

    Assign To: Howard M. Lewis Ship

> Bean Property does not get updated from component parameter
> -----------------------------------------------------------
>
>          Key: TAPESTRY-406
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-406
>      Project: Tapestry
>         Type: Bug
>     Reporter: Ron Piterman
>     Assignee: Howard M. Lewis Ship
>     Priority: Critical
>  Attachments: bug.zip
>
> in the bean's <set ... referencing a component parameter causes the following behaiviour:
> the first value which is set to the bean property is being use in all instances of the component, as if the bean is shared between instances, without updating its properties.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org