Em Sat, 19 Dec 2009 17:17:15 -0200, Piero Sartini <[email protected]>
escreveu:
Hello list.
Hi!
This mail is inspired from the wishlist thread and the discussion
about persistence, transactions and EJB. Now that JavaEE 6 is out, I
think it is time to think about how tapestry will integrate with this
shiny new stuff.
I think the first question that we need to ask ourselves is which of this
new stuff is worth to spend some time integrating them into Tapestry
and/or Tapestry-IoC.
Current status is that tapestry has its own IoC container which is a
wonderful peace of software.. but it also isolates us from all the
evolution that is going on in the Java world.
Not technically correct. Tapestry is already integrated with Spring. I can
inject a Tapestry service exactly the same way I would inject a
Tapestry-IoC service. Tapestry-IoC already has some hooks to plug objects
built elsewhere.
Things I really miss are:
* JSR-303: Beans validation
This integration has already started, just not released yet. More info
here: http://tapestry.formos.com/nightly/tapestry5/tapestry-beanvalidator/
* JSR-299: Contexts and Dependency Injection
* JSR-330: Dependency Injection for Java
There was a discussion about JSR 330 in the dev mailing list. JSR 330 is
based on Guice. Tapestry-IoC was partly inspired by Guice, so I guess the
integration will not be difficult to implement. No discussion about 299
yet.
I understand if you say that its not worth the effort or too hard to
accomplish -
Everyone is invited to contribute, committers or not.
Let's take a look at Wicket, the main competitior: they already have
it. Struts2 also has a experimental implementation of JSR-299. Seam /
JSF2 is the source of all this.
JSF sucks, by the way. :)
In my oppinion, integrating with these standards is more than
important for tapestry to survive.
A question: how many people/organizations/whatever really care for
standards? How much they care? I don't know the answer.
These JSRs are very, very young, so we can't be really sure whether they
will be adopted. JDO is a JSR and very few people use it.
A standard by itself is as useful as the number of people that use them.
--
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: [email protected]
For additional commands, e-mail: [email protected]
