You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Lukasz Jazgar (JIRA)" <ji...@apache.org> on 2009/05/21 14:45:45 UTC
[jira] Created: (TAP5-715) Coercion from primitive types to wrapper
classes?
Coercion from primitive types to wrapper classes?
-------------------------------------------------
Key: TAP5-715
URL: https://issues.apache.org/jira/browse/TAP5-715
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-ioc
Affects Versions: 5.1.0.5
Reporter: Lukasz Jazgar
Priority: Minor
I checked 2 cases:
typeCoercer.explain(boolean.class, Boolean.class)
returns
Object --> String, String --> Boolean
typeCoercer.explain(int.class, Integer.class)
returns
Number --> Long, Long --> Integer
Strange.
Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-715) Coercion from primitive types to wrapper
classes?
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-715:
--------------------------------------
Issue Type: Bug (was: Improvement)
> Coercion from primitive types to wrapper classes?
> -------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-715) TypeCoercer.explain incorrectly reports
the plan to coerce from primitive types to wrapper types
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-715:
--------------------------------------
Summary: TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types (was: Coercion from primitive types to wrapper classes?)
> TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types
> ------------------------------------------------------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.2.0
>
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-715) TypeCoercer.explain incorrectly reports
the plan to coerce from primitive types to wrapper types
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-715:
--------------------------------------
Summary: TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types (was: Coercion from primitive types to wrapper classes?)
> TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types
> ------------------------------------------------------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.2.0
>
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-715) Coercion from primitive types to wrapper
classes?
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-715:
--------------------------------------
Issue Type: Bug (was: Improvement)
> Coercion from primitive types to wrapper classes?
> -------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-715) Coercion from primitive types to
wrapper classes?
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-715:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> Coercion from primitive types to wrapper classes?
> -------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-715) Coercion from primitive types to
wrapper classes?
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-715:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> Coercion from primitive types to wrapper classes?
> -------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-715) TypeCoercer.explain incorrectly reports
the plan to coerce from primitive types to wrapper types
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-715.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types
> ------------------------------------------------------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.2.0
>
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-715) TypeCoercer.explain incorrectly reports
the plan to coerce from primitive types to wrapper types
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-715.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.0
> TypeCoercer.explain incorrectly reports the plan to coerce from primitive types to wrapper types
> ------------------------------------------------------------------------------------------------
>
> Key: TAP5-715
> URL: https://issues.apache.org/jira/browse/TAP5-715
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.2.0
>
>
> I checked 2 cases:
> typeCoercer.explain(boolean.class, Boolean.class)
> returns
> Object --> String, String --> Boolean
> typeCoercer.explain(int.class, Integer.class)
> returns
> Number --> Long, Long --> Integer
> Strange.
> Shouldn't TypeCoercer cast directly to wrapper classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.