You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Alberto Lepe <al...@gmail.com> on 2005/03/10 00:30:57 UTC
Multiple Visit Classes
The proyect that we are starting will be develop by 4 teams
(Tapestry/EJB). Each team will be incharge of a module. At the end, we
are going join all the modules. The problem is that each team needs to
modify the Visit class. I read that one of the advantages of tapestry
is that you don't have that kind of problems. The only solution I see
is create subclasses within the Visit class, so each team modify their
own class. The .application don't let me duplicate the property name:
"....tapestry.visit-class". I also thought in manage all modules as
independient applications, but that won't work for us. Is there any
other solution?
A. Lepe
www.alepe.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Multiple Visit Classes
Posted by Howard Lewis Ship <hl...@gmail.com>.
When I don't have specific help for 3.0 I can tease you with 3.1.
3.1 supports any number of application state objects (similar to visit
and global in 3.0). Perfect for your needs. Just keep that in mind.
I prefer Richard Hensley's approach, of having a wrapper class around
the individual team-specific objects.
On Wed, 9 Mar 2005 15:30:57 -0800, Alberto Lepe <al...@gmail.com> wrote:
> The proyect that we are starting will be develop by 4 teams
> (Tapestry/EJB). Each team will be incharge of a module. At the end, we
> are going join all the modules. The problem is that each team needs to
> modify the Visit class. I read that one of the advantages of tapestry
> is that you don't have that kind of problems. The only solution I see
> is create subclasses within the Visit class, so each team modify their
> own class. The .application don't let me duplicate the property name:
> "....tapestry.visit-class". I also thought in manage all modules as
> independient applications, but that won't work for us. Is there any
> other solution?
>
> A. Lepe
> www.alepe.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org