Where were you duplicates? Where they in src/test/resources and
src/main/resources? If so, that's a bug in 2.0.

Matt

On 10/5/07, WayneFH <[EMAIL PROTECTED]> wrote:
>
> You're a GENIUS!!
> That fixed it. For some reason I had other versions of hibernate.cfg.xml in
> deployment directories.
>
> Why doesn't maven update them when I run mvn jetty:run?  Actually I have had
> this same issue with log4j.xml and a couple other things.
>
> Maybe I need to do a "mvn clean".
>
> Wayne
>
>
> mraible wrote:
> >
> > On 10/5/07, WayneFH <[EMAIL PROTECTED]> wrote:
> >>
> >> Matt,
> >>
> >> Please help. I turned on DEBUG logging for Hibernate and added a logging
> >> message to backingBean.getCaseItems() right before calling
> >> caseItemManager.getAll().
> >>
> >> As you see, Hibernate only opens the session and closes it without
> >> selecting
> >> on the database.
> >> What can possible cause Hibernate to never even try to "select" the rows?
> >
> > I don't know - maybe your class isn't mapped to your table properly.
> > If it works in your tests, I'm stumped. Maybe you have duplicate
> > hibernate.cfg.xml files and the test reads one while the production
> > version reads the other. Do you get the same behavior if you deploy to
> > Tomcat (mvn -Dcargo.wait=true)?
> >
> >>
> >> NOTE: I get a warning on startup of jetty saying there is not transaction
> >> manager configured. Can that be related?
> >
> > No, this is Jetty warning you that you don't have a JTA Transaction
> > manager configured.
> >
> > Matt
> >
> >>
> >> What's the deal?
> >> Wayne
> >>
> >> DEBUG [btpool0-1] CaseItemList.getCaseItems(38) | Called getCaseItems.
> >> DEBUG [btpool0-1] SessionImpl.<init>(220) | opened session at timestamp:
> >> 4880806619398144
> >> DEBUG [btpool0-1] JDBCTransaction.begin(54) | begin
> >> DEBUG [btpool0-1] ConnectionManager.openConnection(421) | opening JDBC
> >> connection
> >> DEBUG [btpool0-1] JDBCTransaction.begin(59) | current autocommit status:
> >> true
> >> DEBUG [btpool0-1] JDBCTransaction.begin(62) | disabling autocommit
> >> DEBUG [btpool0-1] JDBCTransaction.commit(103) | commit
> >> DEBUG [btpool0-1] JDBCTransaction.toggleAutoCommit(193) | re-enabling
> >> autocommit
> >> DEBUG [btpool0-1] JDBCTransaction.commit(116) | committed JDBC Connection
> >> DEBUG [btpool0-1] ConnectionManager.afterTransaction(302) | transaction
> >> completed on session with on_close connection release mode; be sure to
> >> close
> >> the session to release JDBC resources!
> >> DEBUG [btpool0-1] ConnectionManager.closeConnection(441) | releasing JDBC
> >> connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets:
> >> 0,
> >> globally: 0)]
> >> DEBUG [btpool0-1] ConnectionManager.afterTransaction(302) | transaction
> >> completed on session with on_close connection release mode; be sure to
> >> close
> >> the session to release JDBC resources!
> >>
> >>
> >> mraible wrote:
> >> >
> >> > I would try printing our your results using a simple expression before
> >> > your datatable. Something like ${backingBean.caseItems}. If that
> >> > doesn't print out anything, there's probably something wrong with your
> >> > backing bean.
> >> >
> >> > Matt
> >> >
> >> > On 10/4/07, WayneFH <[EMAIL PROTECTED]> wrote:
> >> >>
> >> >>
> >> >> Please help, I created caseitem.xhtml just like persons.xhtml in
> >> AppFuse
> >> >> but
> >> >> it doesn't display any rows.
> >> >>
> >> >> I already created the POJO CaseItem, already setup Hibernate, already
> >> >> configured Spring and already wrote successful junit CaseItemListTest
> >> >> that
> >> >> passes the test and creates the rows.
> >> >>
> >> >> Also, dbunit is setup to load 2 rows into the caseitem table and I
> >> >> verified
> >> >> they are there.
> >> >>
> >> >> Still, caseitem.xhtml only displays the columns names but not the
> >> data.
> >> >>
> >> >> I'm a newbie to JSF and xhtml. Please provide some tips on how to
> >> debug
> >> >> this. I could do it easily in JSP. But I don't see where I can insert
> >> any
> >> >> log messages or get any clues to see why the xhtml isn't generating
> >> the
> >> >> data. I've gone over it with a fine tooth come to make sure I replaced
> >> >> "person" with "caseItem" etc. whereever appropriate. I'm lost.
> >> >>
> >> >> Sincerely,
> >> >> Wayne
> >> >> --
> >> >> View this message in context:
> >> >>
> >> http://www.nabble.com/Help-with-JSF-xhtml-List-tf4571775s2369.html#a13049705
> >> >> Sent from the AppFuse - User mailing list archive at Nabble.com.
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > http://raibledesigns.com
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> > For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Help-with-JSF-xhtml-List-tf4571775s2369.html#a13063403
> >> Sent from the AppFuse - User mailing list archive at Nabble.com.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > http://raibledesigns.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> --
> View this message in context: 
> http://www.nabble.com/Help-with-JSF-xhtml-List-tf4571775s2369.html#a13063665
> Sent from the AppFuse - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
http://raibledesigns.com

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

Reply via email to