Okay, I ran it under a debugger. But since it's down in the GenericManager
that it's not returning data, I can't follow that code through the debugger.
I think logging is the best option.

Wayne


WayneFH wrote:
> 
> How can I run jetty:run with a debugger? What is s.o.p?
> I'll looking into how to setup hibernate logging.
> Sincerely,
> Wayne
> 
> mraible wrote:
>> 
>> Of course, using a debugger might be much easier.
>> 
>> http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Plugin+inside+Eclipse
>> 
>> On 10/4/07, Matt Raible <[EMAIL PROTECTED]> wrote:
>>> Did you add S.o.p to your getter method to make sure it's getting
>>> called?
>>>
>>> Matt
>>>
>>> On 10/4/07, WayneFH <[EMAIL PROTECTED]> wrote:
>>> >
>>> > Could it have anything to do with a hibernate relationship?
>>> > caseitem has a foreign key to prescriberitem table.
>>> > But in the database they're all there.  And in the junit
>>> > tests they work fine creating each and inserting in the
>>> > table and reading back. I inserted System.out.println
>>> > all over to make sure.
>>> >
>>> > Wayne
>>> >
>>> > WayneFH wrote:
>>> > >
>>> > > Yes, definately. I have mysql-front looking at the mysql database.
>>> > > The items are there. Is there any logging for hibernate or spring to
>>> check
>>> > > if it's doing anything or getting any errors? No errors come to the
>>> > > console
>>> > > where I run jetty:run.
>>> > > Sincerely,
>>> > > Wayne
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > mraible wrote:
>>> > >>
>>> > >> Are you sure there's data in your database? You might want to query
>>> it
>>> > >> while your app is running and make sure data is in there.
>>> > >>
>>> > >> Matt
>>> > >>
>>> > >> On 10/4/07, WayneFH <[EMAIL PROTECTED]> wrote:
>>> > >>>
>>> > >>> I also printed out ${backingBean.caseItemManager} to make sure it
>>> was
>>> > >>> set.
>>> > >>> And it shows [EMAIL PROTECTED]
>>> > >>>
>>> > >>> So the caseItemManager has been set by Spring and the data is in
>>> the
>>> > >>> database.
>>> > >>>
>>> > >>> I'm at a loss why doesn't the backingBean.caseItems produce
>>> anything.
>>> > >>> Argh!
>>> > >>>
>>> > >>> Please give me some idea. Here's the code for my backingBean
>>> > >>> (CaseItemList
>>> > >>> actually).
>>> > >>>
>>> > >>>
>>> > >>> package com.fhsc.flac.web.action;
>>> > >>>
>>> > >>> import java.io.Serializable;
>>> > >>> import java.util.List;
>>> > >>>
>>> > >>> import org.appfuse.service.GenericManager;
>>> > >>> import org.appfuse.webapp.action.BasePage;
>>> > >>>
>>> > >>>
>>> > >>> public class CaseItemList extends BasePage implements Serializable
>>> {
>>> > >>>     /**
>>> > >>>          *
>>> > >>>          */
>>> > >>>         private static final long serialVersionUID =
>>> > >>> 2480218430411808484L;
>>> > >>>         private GenericManager caseItemManager;
>>> > >>>
>>> > >>>     public void setCaseItemManager(GenericManager manager) {
>>> > >>>         this.caseItemManager = manager;
>>> > >>>     }
>>> > >>>
>>> > >>>     public GenericManager getCaseItemManager() {
>>> > >>>         return caseItemManager;
>>> > >>>     }
>>> > >>>
>>> > >>>     public CaseItemList() {
>>> > >>>         setSortColumn("caseId"); // sets the default sort column
>>> > >>>     }
>>> > >>>
>>> > >>>     public List getCaseItems() {
>>> > >>>         return sort(caseItemManager.getAll());
>>> > >>>     }
>>> > >>> }
>>> > >>>
>>> > >>>
>>> > >>> WayneFH wrote:
>>> > >>> >
>>> > >>> > Thanks. I tried that and it only printed an empty [].
>>> > >>> > In the junit CaseItemListTest class, I did a
>>> > >>> > System.out.println(backingBean.getCaseItems()). That, prints out
>>> the 3
>>> > >>> > items (2 from dbunit plus the one it inserts). Why would it be
>>> empty?
>>> > >>> >
>>> > >>> > It works in the junit tests, just fine. I'm stumped.
>>> > >>> > Wayne
>>> > >>> >
>>> > >>> >
>>> > >>> > 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#a13050294
>>> > >>> 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#a13050385
>>> > 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
>>>
>> 
>> 
>> -- 
>> 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#a13050900
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