The 2nd problem happens when from the list page of any entity that has a
OneToOne relationship defined, the "Add" button is clicked or any record is
selected for editing.  The stack trace is below:

This is likely from the following "todo"s....what do I need to change here? 
I could really use some examples on how to implement OneToOne, OneToMany,
etc. end to end using JSF and JPA.

    <!-- todo: change this to read the identifier field from the other pojo
-->
    <h:selectOneMenu value="#{rateForm.rate.admissionCategory}"
id="admissionCategory" required="false" styleClass="select">
        <f:selectItems value="#{rateForm.rate.admissionCategory}"/>
    </h:selectOneMenu>
    <!-- todo: change this to read the identifier field from the other pojo
-->
    <h:selectOneMenu value="#{rateForm.rate.discountCategory}"
id="discountCategory" required="false" styleClass="select">
        <f:selectItems value="#{rateForm.rate.discountCategory}"/>
    </h:selectOneMenu>
    <!-- todo: change this to read the identifier field from the other pojo
-->
    <h:selectOneMenu value="#{rateForm.rate.availability}" id="availability"
required="false" styleClass="select">
        <f:selectItems value="#{rateForm.rate.availability}"/>
    </h:selectOneMenu>

-- 
View this message in context: 
http://www.nabble.com/Need-help-with-basic-relationship---JPA-%2B-MySQL-%2B-JSF-tf4708504s2369.html#a13522744
Sent from the AppFuse - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to