You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by no...@comments.apache.org on 2014/10/23 14:47:59 UTC

Jerzy Sorokowski commented on http://tapestry.apache.org/using-tapestry-with-hibernate.html

Hello,
    Jerzy Sorokowski has commented on http://tapestry.apache.org/using-tapestry-with-hibernate.html. 
    You can find the comment here:
    http://tapestry.apache.org/using-tapestry-with-hibernate.html#comment_3167
    Please note that if the comment contains a hyperlink, it must be approved
    before it is shown on the site.

    Below is the reply that was posted:
    ~~~~
    It should be mentioned, that package for classes mapped to hibernate should have name "com.example.tutorial.entities" (i.e. the last part must be "entities") to provide appropriate mapping. Otherwise, the hibernate.cfg.xml should contain the following mapping: <mapping class="com.example.tutorial.[your-own-name].Address"/>
In the previous chapter the statement:
"Unlike the use of the pages sub-package (for page component classes), this is not enforced by Tapestry; it's just a convention (but as we'll see shortly, a handy one)." is a little bit confusing.
    ~~~~

    With regards,
    The Apache Tapestry Project.

    You are receiving this email because you have subscribed to changes for the tapestry site.
    To stop receiving these emails, unsubscribe from the mailing list that is providing these notifications.
	    

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org