You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bval.apache.org by "Carlos Vara (JIRA)" <ji...@apache.org> on 2010/04/06 04:12:28 UTC
[jira] Created: (BVAL-17) PathImpl keeps a null-named first node on
unindexed property paths
PathImpl keeps a null-named first node on unindexed property paths
------------------------------------------------------------------
Key: BVAL-17
URL: https://issues.apache.org/jira/browse/BVAL-17
Project: BeanValidation
Issue Type: Bug
Components: jsr303
Affects Versions: 0.1-incubating
Reporter: Carlos Vara
Attachments: PathImpl.patch
PathImpl keeps a null-named first node on unindexed property paths, so the TCK tests detect the paths as invalid (the toString() produces the same output, but your PathImpl has an extra uneeded node there).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BVAL-17) PathImpl keeps a null-named first node on
unindexed property paths
Posted by "Carlos Vara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BVAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Vara updated BVAL-17:
----------------------------
Attachment: PathImpl.patch
Fix attached, with it applied, 27 more tests in the TCK pass :-)
> PathImpl keeps a null-named first node on unindexed property paths
> ------------------------------------------------------------------
>
> Key: BVAL-17
> URL: https://issues.apache.org/jira/browse/BVAL-17
> Project: BeanValidation
> Issue Type: Bug
> Components: jsr303
> Affects Versions: 0.1-incubating
> Reporter: Carlos Vara
> Attachments: PathImpl.patch
>
>
> PathImpl keeps a null-named first node on unindexed property paths, so the TCK tests detect the paths as invalid (the toString() produces the same output, but your PathImpl has an extra uneeded node there).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (BVAL-17) PathImpl keeps a null-named first node
on unindexed property paths
Posted by "Roman Stumm (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BVAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Stumm reassigned BVAL-17:
-------------------------------
Assignee: Roman Stumm
> PathImpl keeps a null-named first node on unindexed property paths
> ------------------------------------------------------------------
>
> Key: BVAL-17
> URL: https://issues.apache.org/jira/browse/BVAL-17
> Project: BeanValidation
> Issue Type: Bug
> Components: jsr303
> Affects Versions: 0.1-incubating
> Reporter: Carlos Vara
> Assignee: Roman Stumm
> Attachments: PathImpl.patch
>
>
> PathImpl keeps a null-named first node on unindexed property paths, so the TCK tests detect the paths as invalid (the toString() produces the same output, but your PathImpl has an extra uneeded node there).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BVAL-17) PathImpl keeps a null-named first node on
unindexed property paths
Posted by "Roman Stumm (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BVAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Stumm updated BVAL-17:
----------------------------
Fix Version/s: 0.1-incubating
> PathImpl keeps a null-named first node on unindexed property paths
> ------------------------------------------------------------------
>
> Key: BVAL-17
> URL: https://issues.apache.org/jira/browse/BVAL-17
> Project: BeanValidation
> Issue Type: Bug
> Components: jsr303
> Affects Versions: 0.1-incubating
> Reporter: Carlos Vara
> Assignee: Roman Stumm
> Fix For: 0.1-incubating
>
> Attachments: PathImpl.patch
>
>
> PathImpl keeps a null-named first node on unindexed property paths, so the TCK tests detect the paths as invalid (the toString() produces the same output, but your PathImpl has an extra uneeded node there).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (BVAL-17) PathImpl keeps a null-named first
node on unindexed property paths
Posted by "Roman Stumm (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BVAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on BVAL-17 started by Roman Stumm.
> PathImpl keeps a null-named first node on unindexed property paths
> ------------------------------------------------------------------
>
> Key: BVAL-17
> URL: https://issues.apache.org/jira/browse/BVAL-17
> Project: BeanValidation
> Issue Type: Bug
> Components: jsr303
> Affects Versions: 0.1-incubating
> Reporter: Carlos Vara
> Assignee: Roman Stumm
> Attachments: PathImpl.patch
>
>
> PathImpl keeps a null-named first node on unindexed property paths, so the TCK tests detect the paths as invalid (the toString() produces the same output, but your PathImpl has an extra uneeded node there).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BVAL-17) PathImpl keeps a null-named first node
on unindexed property paths
Posted by "Roman Stumm (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BVAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Stumm resolved BVAL-17.
-----------------------------
Resolution: Fixed
I merged and committed your patch, thanks again!
> PathImpl keeps a null-named first node on unindexed property paths
> ------------------------------------------------------------------
>
> Key: BVAL-17
> URL: https://issues.apache.org/jira/browse/BVAL-17
> Project: BeanValidation
> Issue Type: Bug
> Components: jsr303
> Affects Versions: 0.1-incubating
> Reporter: Carlos Vara
> Assignee: Roman Stumm
> Attachments: PathImpl.patch
>
>
> PathImpl keeps a null-named first node on unindexed property paths, so the TCK tests detect the paths as invalid (the toString() produces the same output, but your PathImpl has an extra uneeded node there).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.