Yes, please don't make us use AspectJ to develop in tapestry.  I don't
care if you want to use AspectJ behind the scenes to implement Tapestry,
but please don't make us have to weave aspects into our classes to get
stuff done.  Also, we need to figure out how to allow HiveMind to support
aspects the way Spring does.  I don't think it's going to be difficult.  I
just haven't had the time to sit down and code it up.

> http://howardlewisship.com/blog/2006/04/gambling-on-aspectj.html
>
> It's a gamble for sure.
>
> Pls reassure me that my 9 team members will never have to look at,
> learn, or understand anything about AspectJ to use T5. Ie. it will be
> am implementation detail of T5 and not a "feature". Also, that any
> mention of AspectJ will relegated to an "appendix" in the
> documentation for T5 that 99.9999% of Tapestry 5 users can ignore.
>
> Geoff
>
> --
> The Spindle guy. http://spindle.sf.net
> Blog:                  http://jroller.com/page/glongman
> Other interests:  http://www.squidoo.com/spaceelevator/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


James Carman, President
Carman Consulting, Inc.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to