On Mon, 13 Jun 2011 22:01:44 -0300, jqzone <jqz...@gmail.com> wrote:
I want to do this too,but I don't konw how to do it.
I would do this:
* Create a separate project and Tapestry-IoC module class just with the
service interfaces (I'll call core-api)
* Create a separate project and Tapestry-IoC module class with the local
implementation of the services interfaces (core-impl).
* Create a separate project and Tapestry-IoC module class with the remote
implementation of the service interfaces, using the REST API (core-rest).
* Create a webapp using the core-api JAR plus one of the implementation
JARs (core-impl or core-rest).
You can merge the webapp with core-api instead of having them in different
projects if you want. It wouldn't really change the architecture. The
trick here is to have service interfaces separated from their
implementations.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
