Re: [Lift] re: How do I get the stacktrace when EntityManager fails to be instantiated

2010-01-02 Thread James Black
Thank you for the response.

The problem was that I was not printing out the stack trace, just the
exception message.

On Wed, Dec 30, 2009 at 10:05 AM, Derek Chen-Becker
dchenbec...@gmail.comwrote:

 Are you using ScalaJPA? It shouldn't be absorbing any exceptions. Perhaps
 you have the log4j threshold at INFO instead of DEBUG?

 Derek


 On Tue, Dec 22, 2009 at 8:54 PM, James Black planiturth...@gmail.comwrote:

 I am having a problem with one entity trying to use @OneToMany, and I
 would like to see what the actual error is, but that seems to be
 getting absorbed.

 For more on my actual problem you can look at this:


 http://stackoverflow.com/questions/1947627/entitymanager-fails-to-instantiate-using-jpa-hibernate-when-i-add-a-onetomany-ann

 This is my values within persistence.xml:

 property name=hibernate.dialect
 value=org.hibernate.dialect.DerbyDialect/
 property name=hibernate.connection.driver_class
 value=org.apache.derby.jdbc.EmbeddedDriver/
 property name=hibernate.connection.url
 value=jdbc:derby:lift_example;create=true/
 property name=hibernate.max_fetch_depth value=3/
 property name=hibernate.show_sql value=true /
 property name=hibernate.hbm2ddl.auto value=create-drop /
 
 property name=hibernate.format_sql value=true/

 All I get when I have deleted the database, and then do 'mvn clean
 compile install' at the end of my unit test is:
 13853 [main] INFO org.hibernate.cfg.SettingsFactory - Deleted entity
 synthetic identifier rollback: disabled
 13853 [main] INFO org.hibernate.cfg.SettingsFactory - Default entity-
 mode: pojo
 13853 [main] INFO org.hibernate.cfg.SettingsFactory - Named query
 checking : enabled
 13858 [main] INFO org.hibernate.impl.SessionFactoryImpl - building
 session factory
 [PersistenceUnit: jpaweb] Unable to build EntityManagerFactory


 I would like to see the exception that leads to it not being able to
 build the EntityManagerFactory.

 --

 You received this message because you are subscribed to the Google Groups
 Lift group.
 To post to this group, send email to lift...@googlegroups.com.
 To unsubscribe from this group, send email to
 liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/liftweb?hl=en.



  --
 You received this message because you are subscribed to the Google Groups
 Lift group.
 To post to this group, send email to lift...@googlegroups.com.
 To unsubscribe from this group, send email to
 liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/liftweb?hl=en.


--

You received this message because you are subscribed to the Google Groups 
Lift group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.




Re: [Lift] re: How do I get the stacktrace when EntityManager fails to be instantiated

2009-12-30 Thread Derek Chen-Becker
Are you using ScalaJPA? It shouldn't be absorbing any exceptions. Perhaps
you have the log4j threshold at INFO instead of DEBUG?

Derek

On Tue, Dec 22, 2009 at 8:54 PM, James Black planiturth...@gmail.comwrote:

 I am having a problem with one entity trying to use @OneToMany, and I
 would like to see what the actual error is, but that seems to be
 getting absorbed.

 For more on my actual problem you can look at this:


 http://stackoverflow.com/questions/1947627/entitymanager-fails-to-instantiate-using-jpa-hibernate-when-i-add-a-onetomany-ann

 This is my values within persistence.xml:

 property name=hibernate.dialect
 value=org.hibernate.dialect.DerbyDialect/
 property name=hibernate.connection.driver_class
 value=org.apache.derby.jdbc.EmbeddedDriver/
 property name=hibernate.connection.url
 value=jdbc:derby:lift_example;create=true/
 property name=hibernate.max_fetch_depth value=3/
 property name=hibernate.show_sql value=true /
 property name=hibernate.hbm2ddl.auto value=create-drop /
 
 property name=hibernate.format_sql value=true/

 All I get when I have deleted the database, and then do 'mvn clean
 compile install' at the end of my unit test is:
 13853 [main] INFO org.hibernate.cfg.SettingsFactory - Deleted entity
 synthetic identifier rollback: disabled
 13853 [main] INFO org.hibernate.cfg.SettingsFactory - Default entity-
 mode: pojo
 13853 [main] INFO org.hibernate.cfg.SettingsFactory - Named query
 checking : enabled
 13858 [main] INFO org.hibernate.impl.SessionFactoryImpl - building
 session factory
 [PersistenceUnit: jpaweb] Unable to build EntityManagerFactory


 I would like to see the exception that leads to it not being able to
 build the EntityManagerFactory.

 --

 You received this message because you are subscribed to the Google Groups
 Lift group.
 To post to this group, send email to lift...@googlegroups.com.
 To unsubscribe from this group, send email to
 liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/liftweb?hl=en.




--

You received this message because you are subscribed to the Google Groups 
Lift group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en.