Yay. I got it works !
I forgot to mapped the beans entity on my hibernate configuration

<hibernate-configuration>
    <session-factory>
        <property
name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property>
        <property
name="hibernate.connection.url">jdbc:mysql://localhost:3306/tapestryboard</property>
        <property
name="hibernate.dialect">org.hibernate.dialect.MySQLDialect</property>
        <property name="hibernate.connection.username">root</property>
        <property name="hibernate.connection.password"></property>
        <property name="hbm2ddl.auto">update</property>
        <property name="hibernate.show_sql">true</property>
        <property name="hibernate.format_sql">true</property>

        <mapping class="org.makeasoup.hibernateboard.beans.Address"/>

    </session-factory>
</hibernate-configuration>

Thnx guys ^^,

On Sat, Feb 26, 2011 at 11:29 PM, dwi ardi irawan
<penyihirke...@gmail.com>wrote:

> here is my source code ....
> so it doesn't show an error like it did previously
> but I have to you mvn jetty:run instead of using jetty launcher.
>
> but now, it show : "There is no data to display"
>
> could anyone help me?
>
>
> On Sat, Feb 26, 2011 at 11:17 PM, dwi ardi irawan <penyihirke...@gmail.com
> > wrote:
>
>> Yes, I've checked it. And it doesn't corrupt at all.
>> I think the problem is in the jetty launcher, cos when use mvn jetty:run,
>> it doesn't show any error
>> Strange ....
>>
>> but now there is another problem, now, the page is show:
>> "There is no data to display."
>>
>> my table has only 1 row.
>>
>>
>>
>> On Sat, Feb 26, 2011 at 10:07 PM, Thiago H. de Paula Figueiredo <
>> thiag...@gmail.com> wrote:
>>
>>> On Sat, 26 Feb 2011 09:52:40 -0300, dwi ardi irawan <
>>> penyihirke...@gmail.com> wrote:
>>>
>>>  As of Hibernate 3.6, JDK 1.4 support has been dropped and the Hibernate
>>>> Annotations have been merged back into Core.
>>>> Then why should I need hibernate annotations on my pom.xml ??
>>>>
>>>
>>> You shouldn't. Have you checked if the Hibernate JAR was correctly
>>> downloaded and if you have two different Hibernate versions in the
>>> classpath? A corrupted or truncated JAR can cause strange problems.
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
>>> and instructor
>>> Owner, Ars Machina Tecnologia da Informação Ltda.
>>> http://www.arsmachina.com.br
>>>
>>
>>
>>
>> --
>> http://dwiardiirawan.com
>> "cos everyone could be extraordinary...lighten up !"
>>
>>
>
>
> --
> http://dwiardiirawan.com
> "cos everyone could be extraordinary...lighten up !"
>
>


-- 
http://dwiardiirawan.com
"cos everyone could be extraordinary...lighten up !"

Reply via email to