s:selectItems + s:convertEntity not pre-selecting

[monkeyden]

Using 2.0.3.CR1 on AS 4.2

I'm using the following snippet of code to render a selectOneListbox:

<h:selectOneListbox value="#{donationManager.editableDonation.donor}" size="1">
     <s:selectItems value="#{donors}" var="donor" label="#{donor.name}" noSelectionLabel="Please select a donor..."/>
     <s:convertEntity/>
     <a4j:support ajaxSingle="true" event="onchange"/>
</h:selectOneListbox>

editableDonation is the selected donation.  donors is an application scoped list of Donors.  Every donation must have a donor.  I also have the entity converter configured in components.xml like so:

<component name="org.jboss.seam.ui.EntityConverter">
    <property name="entityManager">#{em}</property>
</component>

The problem is, it doesn't pre-select the donor and when I submit, it doesn't convert the entity and call the mutator on editableDonation.  One interesting behavior I noticed on the client is that it simply prints the index value for the select tag, when I would expect it to use the value @Id from the entity.

Any suggestions are appreciated.

[emiakoup]

Hello Kyle,
is your #{donors} annotated with @DataModel? Also is #{donationManager.editableDonation.donor} annotated as @DataModelSelection? 

maybe it'll help.

[vladimir.kovalyuk]

Make sure you implemented equals() for your donors

[monkeyden]

Vladimir Kovalyuk wrote on Oct 03, 2008 00:31:


Make sure you implemented equals() for your donors

Yes, I have both equals and hashCode.  I have gotten it to the point where the initial response does match it correctly, and the correct SelectItem is selected, but the setDonor() method always receives null on the post.

[monkeyden]

Incidentally, I dropped a breakpoint in org.jboss.seam.ui.converter.EntityConverter.getAsObject() and it's never called on the submit of the form.  I also have the following code to make an AJAX request:

<a4j:commandLink action="#{donationManager.setEditableDonation(donation)}" reRender="modalPanelContainer"
    oncomplete="#{rich:component('donationEditor')}.show() ">
    #{donation.name}
</a4j:commandLink>

This sets the donation to be edited in the backing bean and reRenders the s:div containing a rich:modalPanel.  Could this be the cause?

[damianharvey.damianharvey.gmail.com]

This is often because the scope of your backing bean is not broad enough - eg. is sent to EVENT. Have you tried changing it to CONVERSATION?

Cheers,

Damian.

[monkeyden]

Damian Harvey wrote on Oct 03, 2008 10:35:


This is often because the scope of your backing bean is not broad enough - eg. is sent to EVENT. Have you tried changing it to CONVERSATION?

Cheers,

Damian.

It's a long running conversation, so there is no way it's going out of scope.  s:convertEntity likely needs the JSF lifecycle to work properly.  An a4j reRender is called on the containing div of this combobox.

[damianharvey.damianharvey.gmail.com]

Sorry to be pedantic, but it's not quite clear from your answer if you have your DonationManager annotated with @Scope(ScopeType.CONVERSATION) ??

Also what does this mean:

One interesting behavior I noticed on the client is that it simply prints the index value for the select tag

Do you mean that the value (label) on the Drop down is the index or do you mean when you look at the HTML source the value of the OPTION is the index?

Cheers,

Damian.

[monkeyden]

Yes, it's annotated as CONVO.  I've used Seam conversations pretty extensively for nearly two years, so this is likely not the issue. 

Yes, the value of the option is the index of the loop.  On second thought however, resolving the selected OPTION to an entity is one of the responsibilities of convertEntity, so this probably functions as designed.

[pmuir]

Remove the ajax stuff, and check if it works ;-)