Re: [macker-user] Evaluation questions

[Pablo M. S. <pab...@gm...>]

Thanks Paul. I will try to make it work in my project. First, I will give
you some tips of the project

Im developing an architectural SOA solution   (as a framework) using spring,
hibernate, jsf, sso,... and I have defined some base classes. I want to
check that other projects developed with this solution are using the rules
defined.

My first problem:

I downloaded macker. Im using ant 1.6.5, jdk 1.5. Do you know if I would
have any problem using JDK 1.5 and macker?

To integrate macker in one application, I only have to make the build file
to target "macker"

http://innig.net/macker/guide/ant.html





2008/9/8 Paul Cantrell <can...@po...>

> These are possible:
>
> all classes of type *DaoImpl must extend BaseDao and implement their own
> interface (FooDaoImpl must implement FooDao for example)
> all classes of type *ServiceImpl cant use *POJO classes
> All classes of type *ServiceImpl can use *Dao but not *DaoImpl
>
>
> These are not quite possible:
>
> all methods defined in *Service and *ServiceImpl can only throw
> ServiceException
> all methods defined in *Dao and *DaoImpl can only throw DataBaseException
>
>
> The current version of Macker cannot distinguish between "throws" and
> "uses." So you could write rules of the form "all methods in *Dao and
> *DaoImpl cannot use any subclass of Exception except DataBaseException," but
> that would cover throwing and catching.
>
> You can still probably do what you want. In an interface, "uses" can only
> mean "throws." If you made that rule apply only to the interfaces, it would
> prevent any API methods from throwing exceptions other than
> DataBaseException — and the implementing classes could therefore also only
> throw those exceptions.
>
> Cheers,
>
> Paul
>
>
> On Sep 5, 2008, at 6:02 AM, Pablo Mosquera Saenz wrote:
>
>
> Hi, Im looking for a tool to make that gives me some way to evaluate my
> architecture.
>
> The kind of rules I want to define are:
>
>
>    - all classes of type *DaoImpl must extend BaseDao and implement their
>    own interface (FooDaoImpl must implement FooDao for example)
>    - all classes of type *ServiceImpl cant use *POJO classes
>    - All classes of type *ServiceImpl can use *Dao but not *DaoImpl
>    - all methods defined in *Service and *ServiceImpl can only throw
>    ServiceException
>    - all methods defined in *Dao and *DaoImpl can only throw
>    DataBaseException
>
>
> Can macker do this?
>
> Thanks in advance
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
>
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> Macker-user mailing list
> Mac...@li...
> https://lists.sourceforge.net/lists/listinfo/macker-user
>
> Macker home page: http://innig.net/macker/
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Macker-user mailing list
> Mac...@li...
> https://lists.sourceforge.net/lists/listinfo/macker-user
>
> Macker home page: http://innig.net/macker/
>