[richfaces-issues] [JBoss JIRA] (RF-12608) pickList without collectionType results in failure to lazily load

[Ken H (JIRA)]

    [ https://issues.jboss.org/browse/RF-12608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740658#comment-12740658 ] 

Ken H commented on RF-12608:
----------------------------

Juraj,

I have updated the test and made a pull request for the changes. There are two tests in the index page, Alpha and Beta. To run a test, change the select items and click save. The only difference between the two is that Beta has collectionType defined.

You should see the following:

With 4.2.3.Final and 4.3.0.M2: 
* Changing Alpha and saving results in an exception
* Changing Beta and saving works without issue

With 4.2.0.Final
* Changing Alpha and saving works without issue
* Changing Beta does not work correctly (Note: This was unexpected, I am unsure why collectionType does not work in 4.2 but it is unrelated to this issue)

I will update the description with the full stack trace.
                
> pickList without collectionType results in failure to lazily load
> -----------------------------------------------------------------
>
>                 Key: RF-12608
>                 URL: https://issues.jboss.org/browse/RF-12608
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.2.3.Final, 4.3.0.M2
>            Reporter: Ken H
>            Assignee: Juraj Húska
>              Labels: regression, waiting_on_user
>
> Changes to the selectManyHelper class in 4.2.3+ causes a lazy loading exception in hibernate when the backing collection is persistent and is not eagerly loaded.
> The problem seems to be that fetching the collection in SelectManyHelper.getConvertedValue bypasses the PersistentSet getter that would normally issue the lazy load request.
> Defining the collectionType (e.g. java.util.ArrayList) bypasses this issue.
> Ideally this method would detect Hibernate proxy collections and handle them appropriately. However, I realize that may cause a dependency so perhaps it would be enough to document this option and situation in the component reference.

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