Error selecting object - SEAM 1.2.1GA

[james_hays]

I'm using SEAM 1.2.1GA and have all of a sudden run into random errors selecting objects out of a drop down list. It doesn't have all the time and seems very random.

I've attempted to enhance the equals() method and the hashcode, but nothing seems to matter in that regard. When I debug the EntityConverter, the key associated with the object is incorrect. You can see this from the error message as well.

ERROR [EntityConverter] Cannot load entity (com.ball.lcgm.entity.User with id org.jboss.seam.ui.NoSelectionConverter.noSelectionValue) from persistence context

I mainly see this when my dropdown list is populated from an ajax call, but I've also seen this error when selecting from a selectManyCheckbox:

<h:selectManyCheckbox value="#{manageOwners.ownersToRemove}" layout="pageDirection">
 <s:selectItems value="#{profileRecord.owners}" var="user" label="#{user.fullName}"/>
 <s:convertEntity/>
</h:selectManyCheckbox>
<h:commandButton action="#{manageOwners.removeOwners}" value="Remove Owners"/>

The error quoted above is directly from the specified code. As you can see, there is no mention of noSelectionValue.

Any help would be appreciated. I've read before to upgrade to the latest in CVS, but that is not an option at the moment. We do have a JBoss support agreement and if needed, I can escalate it there.

Thanks,

James

[pmuir]

If you can create an example with reproduction steps, then please create a jira issue and attach it so we can take a look at it.

[james_hays]

I can't duplicate it on a regular basis, thats the troubling part. It seems completely random. How difficult would it be to jar up the EntityConverter used in the latest seam builds and pull it in as a separate tag like we did when we used ec:convertEntity?

[pmuir]

I rewrote the whole entity converter between 1.2 and 2.0 - ant its quitedeeply integrated into Seam core as well. You should be able to pull out the relevant classes though to build your own version - you'll need classes from org.jboss.seam.ui.converter and org.jboss.seam.framework.

[james_hays]

I'm assuming from the previous postings that you've seen this issue before?

[pmuir]

I can't remember, 1.2.1 was a while ago now ;) But I've not seen it in 2.0 for sure.

When I asked for a JIRA issue I missed you were on 1.2.1 - if you can move to 2.0.0 or 2.0.1 then that would be a good first step.

Part of the reason I did a complete rewrite was because of problems like this, and also the error reporting was bad...

[james_hays]

We currently have multiple applications deployed under JBoss 4.0 with differing deployment requirements. We have been unable to move to 4.2 for this reason. Hopefully after the new year, we can move toward this, but in the mean time, I'm stuck in the land of legacy.