Hi! very interesting thread. I use T5 since 1 year aprox, and it's
true that T-IOC was the first "wall" I had, now I understand it and I
like it a lot (my system does NOT use spring, all with t-ioc). I don't
know which is the solution, because there is documentation about
t-ioc, but maybe more documentation? or maybe a demo-project that uses
basic t-ioc. I think is easier seeing something working, than reading
t-ioc documentation and start from scratch.

Another point.. I think it's impossible to use T5 without t-ioc, is
this right? If it's possible, it would be a good idea uploading
another demo-project without t-ioc.

What else? js.. prototype-based, I know it's possible to have
prototype+jquery together, but I can see lot of people heading jquery,
so I have a long-term plan.. make a tapestry.js based on jquery, if I
do it obviously I'll share it.
But "the solution" for this would be a tapestry.js agnostic, so people
can "inject" their favourite framework. So, maybe it could be shipped
with a default prototype injection, but anyone could write a mootols
injection, jquery injection, etc etc

Last, it would be good more components (ui components).

I think I have no more suggestions

On Wed, Dec 23, 2009 at 5:08 PM, Thiago H. de Paula Figueiredo
<thiag...@gmail.com> wrote:
> Em Wed, 23 Dec 2009 17:37:24 -0200, Piero Sartini <li...@pierosartini.de>
> escreveu:
>
>> For me, authentication is an important part of a web framework and
>> should provide some standard way to do so.
>
> Wicket itself doesn't. Nor does JSF. (all this as far as I know and I google
> it)
>
> There is a third-party package for Wicket:
> http://wicketstuff.org/confluence/display/STUFFWIKI/Wicket-Security.
>
> For Tapestry, there's ChenilleKit Access:
> http://www.chenillekit.org/chenillekit-access/
>
>> Great! Really looking forward to this.
>
> Me too. :)
>
>> JDO on the other
>> hand does - it was designed from the ground up to support different
>> types of persistence engines.
>
> I never paid attention to JDO. Wouldn't be the case case as JPA regarding
> use of low-level APIs?
>
> Regarding JDO, its implementations need for class enhancement after
> compilation is something very annoying. Am I right?
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
> instructor
> Owner, software architect and developer, 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to