[forge-issues] [JBoss JIRA] (FORGE-1002) Faces scaffold should treat properties lacking suitable converters differently

Vineet Reynolds (JIRA) jira-events at lists.jboss.org
Sat Jul 20 02:12:26 EDT 2013


     [ https://issues.jboss.org/browse/FORGE-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vineet Reynolds updated FORGE-1002:
-----------------------------------

    Description: 
This is from the [Sakila-H2 model|https://github.com/maxandersen/sakila-h2].

The {{Staff}} JPA entity generated using the Forge Hibernate Tools plugin, contains a {{byte[]}} property in the form of a {{picture}}. The property is rendered as a {{h:inputText}} widget in the create/edit screens and as a {{h:outputText}} widget in the view screen. This results in errors like the following being reported during operations in such screens: {{Conversion Error setting value '' for 'null Converter'.}}

Since a default converter cannot be applied, mostly due to the possibility of changing semantics of such properties across applications, it would be better to 

* either omit such properties for functional scaffolds,
* or generate converters for every such type.
* or use more appropriate widgets (like a file upload widget) that can operate on such data types.

Also see the TicketMonster model, where a {{long[][]}} property is present in the {{SectionAllocation}} entity.

  was:
This is from the [Sakila-H2 model|https://github.com/maxandersen/sakila-h2].

The {{Staff}} JPA entity generated using the Forge Hibernate Tools plugin, contains a {{byte[]}} property in the form of a {{picture}}. The property is rendered as a {{h:inputText}} widget in the create/edit screens and as a {{h:outputText}} widget in the view screen. This results in errors like the following being reported during operations in such screens: {{Conversion Error setting value '' for 'null Converter'.}}

Since a default converter cannot be applied, mostly due to the possibility of changing semantics of such properties across applications, it would be better to 

* either omit such properties for functional scaffolds,
* or generate converters for every such type.

Also see the TicketMonster model, where a {{long[][]}} property is present in the {{SectionAllocation}} entity.


    
> Faces scaffold should treat properties lacking suitable converters differently
> ------------------------------------------------------------------------------
>
>                 Key: FORGE-1002
>                 URL: https://issues.jboss.org/browse/FORGE-1002
>             Project: Forge
>          Issue Type: Feature Request
>          Components: Scaffold
>    Affects Versions: 1.3.2.Final
>            Reporter: Vineet Reynolds
>
> This is from the [Sakila-H2 model|https://github.com/maxandersen/sakila-h2].
> The {{Staff}} JPA entity generated using the Forge Hibernate Tools plugin, contains a {{byte[]}} property in the form of a {{picture}}. The property is rendered as a {{h:inputText}} widget in the create/edit screens and as a {{h:outputText}} widget in the view screen. This results in errors like the following being reported during operations in such screens: {{Conversion Error setting value '' for 'null Converter'.}}
> Since a default converter cannot be applied, mostly due to the possibility of changing semantics of such properties across applications, it would be better to 
> * either omit such properties for functional scaffolds,
> * or generate converters for every such type.
> * or use more appropriate widgets (like a file upload widget) that can operate on such data types.
> Also see the TicketMonster model, where a {{long[][]}} property is present in the {{SectionAllocation}} entity.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the forge-issues mailing list