project status
transmeta01
that of the 24 tests run, 24 are in ERROR, not failure. The cobertura
plugin also produce a nice
Focus on getting all the tests to pass. Don't worry about the guice
integration. I will give you a hand after the service and DAO are
complete (all tests pass) .
It has been over 2 weeks and the project is already behind schedule
and getting late even more.
The many-to-many mapping have been mapped yet. Some entity are not
coded yet. Focus on completing those first.
Have you met with difficulties? Is there anything I can do to help
make the project progress faster?
Regards
Richard
transmeta01
Cristian Olaru
I made a push with some changes. This should fix the cobertura run.
Hi Cristian, if you run "mvn clean cobertura:cobertura", you will see
that of the 24 tests run, 24 are in ERROR, not failure. The cobertura
plugin also produce a nice
Focus on getting all the tests to pass. Don't worry about the guice
integration. I will give you a hand after the service and DAO are
complete (all tests pass) .
It has been over 2 weeks and the project is already behind schedule
and getting late even more.
The many-to-many mapping have been mapped yet. Some entity are not
coded yet. Focus on completing those first.
I will focus on this.
Have you met with difficulties? Is there anything I can do to help
make the project progress faster?
I think I need some feedback from you regarding the services/dao/entities I implement. If there is a need for them from the presentation. that's why I tried to implement the REST calls.
Regards...
Regards
Richard
--
Cristian Olaru
weblog: http://olaru.blogspot.com
mobile: 0743163039
Richard Mutezintare
Richard
sent from android 2.2
On Feb 3, 2011 2:56 AM, "Cristian Olaru" <col...@gmail.com> wrote:
>
> Hi Richard.
>
> I made a push with some changes. This should fix the cobertura run.
>
> On Thu, Feb 3, 2011 at 4:09 AM, transmeta01 <trans...@gmail.com> wrote:
>>
>> Hi Cristian, if you run "mvn clean cobertura:cobertura", you will see
>> that of the 24 tests run, 24 are in ERROR, not failure. The cobertura
>> plugin also produce a nice
>>
> You made some changes in classic\src\test\resources\META-INF\persistence.xml file. That's why te tests are failed. Now should work with the last push.
<property name="hibernate.archive.autodetection" value="class, hbm"/> should allow you to remove all the xml configuration telling hibernate which classes are persistence entities.
>
>>
>> Focus on getting all the tests to pass. Don't worry about the guice
>> integration. I will give you a hand after the service and DAO are
>> complete (all tests pass) .
>>
> I think that also is important to have a end to end view of the system. For me is fine. I will continue with the services/dao implementation/testing.
>
The system's architecture is simple. The system start with the RESTful front end controller (extract request params, un-marshall data, pre-validate and calls the services), which uses the services (authorization, apply business logic, call DAO) , which use the DAO (CRUD)...DOA returns, Service returns, front end marshalls pojo in to message-body of response, set proper header if need...end of lifecycle.
The client knows only URI and maintains it`s own state. The service side knows only about URI too.
There is also the infrastructure(cross concern) stuff such as DI, logging, monitoring...But do not worry about those for now. Every service and every DAO should be able to be tested independently of all other stuff, with mock objects if necessary.