Hi,
Agree with Lukasz on separating the two layers.
Also, if your DAO class (or any other class you want to test) needs a
full J2EE container (which I suspect it might), then I don't think it
will run properly under JUnit. I ran into problems trying to test my
persistence code with JUnit
Usually you would separate this two layers of your application - you
would have a service layer and a DAO layer. The service classes
contains the logic accessible for the client and DAO takes care only
of the data access. In this case you can write nice unit tests for
your DAO and you don't need
Hi Lukasz,
Thanks for the reply. About my test logic (which I'm starting to
believe that it's wrong) is this:
I want to test my Hibernate DAO (let's call it UserDAO) which extends
GWT's RemoteService, so my project looks like this:
- GWT
- com.gwt.client
- interface userDAO
Can you post your actual test logic? I don't understand why do you
need to go through the GWT servlets to do some unit testing of your
DAO. It would be better to test the DAO logic separately.
On 8 Okt., 04:33, VrmpX vrm...@gmail.com wrote:
Hello,
I'm currently using GWT 2.0.4 with Hibernate3,
Hello,
I'm currently using GWT 2.0.4 with Hibernate3, on Eclipse Helios, to
create a simple web application. So far, I'm able to reach the
database and do some RPC's to the server perfectly without any
problem.
The problem arises whenever I try to test out my server classes (the
data access
