Thank you for your feedback, Chun-Yian Liew!
Thank you for your support, Philip Barlow!
Now I know that I'm not getting crazy... ;)
Well,
I harcoded my properties too and I will back this question in a near future.
For now, I'm running the Manager facade tests and it's all Ok!
So I will be gl
Hmmm, that would mean starting to change one of the appfuse core test
classes.
I think I will set the test values hardcoded for now.
But your workaround will definitely be very usefull for me in the future in
case this problem remains in future appfuse releases.
Thanks for the tip!!
Philip Barl
I had this problem before and i got around it by using commons beanutils
instead of springs implementation, you also have to switch "source" and
"destination" parameters in the copyproperties method as commons takes
them in the opposite way.
Don't know if there are any advantages to using springs
Correction, the sentence
"The keys of those two entries are "null" and "class" both having a
PropertyDescriptor as value."
should have been
"The keys of those two entries are "empty" and "class" both having a
PropertyDescriptor as value."
in my previous post.
Chun-Yian Liew wrote:
>
> cele
celeraman+, have you managed to get the properties based population working?
I am currently running into a similar kind of a problem with the appfuse
tutorial PersonDaoTest example.
I am also trying to populate the Person object with the populate method of
the BaseDaoTestCase class.
At first I re
On 4/24/07, celeraman+ <[EMAIL PROTECTED]> wrote:
mraible wrote:
>
> Did you translate your log file before posting? According to it, the
> resource bundle is using "name" and your class is using "nome".
>
> The last thing I can think of is to debug your test and step through
> the populate m
mraible wrote:
>
> Did you translate your log file before posting? According to it, the
> resource bundle is using "name" and your class is using "nome".
>
> The last thing I can think of is to debug your test and step through
> the populate method to see what's going wrong.
>
>
Yes, I was
I've corrected this in the Hibernate, iBATIS and JPA tutorials.
In this example, if you put a {{PersonDaoTest.properties}} file in
_src/test/resources/org/appfuse/tutorial/dao_, this file's properties
will be available via an "rb" variable.
Thanks for your help!
Matt
On 4/23/07, celeraman+ <
celeraman+ wrote:
>
> You are just right! If I put my .properties file into
> src/test/resources/my/package/name, so
> the NullPointerException from populate Method goes away.
>
Just for take some notes...
Here a quote from Using Hibernate tutorial:
> Simply create a PersonDaoTest.properti
Did you translate your log file before posting? According to it, the
resource bundle is using "name" and your class is using "nome".
The last thing I can think of is to debug your test and step through
the populate method to see what's going wrong.
Matt
On 4/23/07, celeraman+ <[EMAIL PROTECTED
mraible wrote:
>
> If you change DepartamentDaoTest.properties to use "name" instead of
> "nome", does it populate the name property?
>
I'm sorry, Matt, for this misspelling because I'm translating my class from
portuguese to english before I post here.
The portuguese word 'nome' means 'name'
If you change DepartamentDaoTest.properties to use "name" instead of
"nome", does it populate the name property?
Matt
On 4/23/07, celeraman+ <[EMAIL PROTECTED]> wrote:
FIY, I got some progress...
1. The bean definition in src/main/webapp/WEB-INF/aplicationContext.xml file
for DepartmentDao
w
FIY, I got some progress...
1. The bean definition in src/main/webapp/WEB-INF/aplicationContext.xml file
for DepartmentDao
was wrong as following:
Note *DepartmentDao* where must be *departmentDao*.
2. my test case properties files was including the id property. The
Hiberna
Thank you for your reply, Matt!
I have tried a solution for that NullPointerException
without any success. Because I'm feeling completelly idiot,
I decided to post again. I'm so sorry for
this newbie question again.
I add some code to my test case method and I see a 100% sure
that the populate
It's propably case sensitive - I'd try:
name=MyValueForNameAttribute
Matt
On 4/19/07, celeraman+ <[EMAIL PROTECTED]> wrote:
Thanks a million, Matt!
You are just right! If I put my .properties file into
src/test/resources/my/package/name, so
the NullPointerException from populate Method goes
Thanks a million, Matt!
You are just right! If I put my .properties file into
src/test/resources/my/package/name, so
the NullPointerException from populate Method goes away.
The bad news is that the NullPointerException goes to dao.save() method.
I know that the NullPointerException was execut
If you put your DepartamentoDaoTest.properties file in
src/test/resources/org/appfuse/tutorial/dao, it should work. Maven
expects your .java files to be in src/test/java and all other files to
be in src/test/resources. If you'd like to put them alongside the
.java files, you'll need to change you
I'm trying to do a test case based on Person Hibernate Tutorial. The news is
that I want to do this using a .properties file, like the same tutorial for
AppFuse 1.x. I'm using a AppFuse 2.0M4.
However, I got a NullPointerException on the code that will populate the
object.
I couldn't see what is
18 matches
Mail list logo
