You are viewing a plain text version of this content. The canonical link for it is here.
Posted to graffito-dev@incubator.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/04/20 14:12:15 UTC

[jira] Created: (GRFT-131) ResidualProperties Converter uses wrong AtomicType Converter on update

ResidualProperties Converter uses wrong AtomicType Converter on update
----------------------------------------------------------------------

                 Key: GRFT-131
                 URL: https://issues.apache.org/jira/browse/GRFT-131
             Project: Graffito
          Issue Type: Bug
          Components: JCR-Mapping
    Affects Versions: 1.0-a1-dev
            Reporter: Felix Meschberger
             Fix For: 1.0-a1-dev


When writing back data, the ResidualPropertiesCollectionConverterImpl.internalSetProperties method looks at the type of the Java object
to find the atomic type converter instead of getting the converter according to the collection descriptor.

This may lead to NullPointerExceptions in case the concrete type is an extension (or implementation) of the declared type.

I am currently working on a patch to attache to this bug.

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


[jira] Assigned: (GRFT-131) ResidualProperties Converter uses wrong AtomicType Converter on update

Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GRFT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christophe Lombart reassigned GRFT-131:
---------------------------------------

    Assignee: Christophe Lombart

> ResidualProperties Converter uses wrong AtomicType Converter on update
> ----------------------------------------------------------------------
>
>                 Key: GRFT-131
>                 URL: https://issues.apache.org/jira/browse/GRFT-131
>             Project: Graffito
>          Issue Type: Bug
>          Components: JCR-Mapping
>    Affects Versions: 1.0-a1-dev
>            Reporter: Felix Meschberger
>         Assigned To: Christophe Lombart
>             Fix For: 1.0-a1-dev
>
>         Attachments: GRFT-131.diff
>
>
> When writing back data, the ResidualPropertiesCollectionConverterImpl.internalSetProperties method looks at the type of the Java object
> to find the atomic type converter instead of getting the converter according to the collection descriptor.
> This may lead to NullPointerExceptions in case the concrete type is an extension (or implementation) of the declared type.
> I am currently working on a patch to attache to this bug.

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


[jira] Updated: (GRFT-131) ResidualProperties Converter uses wrong AtomicType Converter on update

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GRFT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated GRFT-131:
-----------------------------------

    Attachment: GRFT-131.diff

And here is the patch.

Note that the ResidualProperties converter will now throw a PersistenceException on read or write if no atomic type converter can be found for the element class name.

> ResidualProperties Converter uses wrong AtomicType Converter on update
> ----------------------------------------------------------------------
>
>                 Key: GRFT-131
>                 URL: https://issues.apache.org/jira/browse/GRFT-131
>             Project: Graffito
>          Issue Type: Bug
>          Components: JCR-Mapping
>    Affects Versions: 1.0-a1-dev
>            Reporter: Felix Meschberger
>             Fix For: 1.0-a1-dev
>
>         Attachments: GRFT-131.diff
>
>
> When writing back data, the ResidualPropertiesCollectionConverterImpl.internalSetProperties method looks at the type of the Java object
> to find the atomic type converter instead of getting the converter according to the collection descriptor.
> This may lead to NullPointerExceptions in case the concrete type is an extension (or implementation) of the declared type.
> I am currently working on a patch to attache to this bug.

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