They were in about 5 places include src/webapp/WEB-INF/classes in src and
another 3 or 4 in different target directories.
I think I'll do a mvn clean
Wayne
mraible wrote:
>
> Where were you duplicates? Where they in src/test/resources and
> src/main/resources? If so, that's a bug in 2.0.
>
>
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
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
That can only be answered by looking at your bean definition and
ensuring everything works properly. Maybe write a unit test that just
gets the manager and tests getAll - instead of going through your JSF
bean to do it.
Matt
On 10/5/07, WayneFH <[EMAIL PROTECTED]> wrote:
>
> As to my previous pos
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 selec
As to my previous post showing Hibernate never selects, could this be somehow
the wrong GenericManager for this backing bean? I'm lost. The GetAll works
in the unit testing.
Wayne
mraible wrote:
>
> I would try printing our your results using a simple expression before
> your datatable. Some
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 n
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 t
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
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, Way
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
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 s
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 the
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]
>
>
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 t
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.
Wayn
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 cre
17 matches
Mail list logo
