Hello list.
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. There already was a discussion about this, but it
stopped with no conclusion.
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. Things I really miss
are:
* JSR-303: Beans validation
* JSR-299: Contexts and Dependency Injection
* JSR-330: Dependency Injection for Java
Let me explain why I miss them - some of you may say we have tapestry
equivalents of most of these things.
What would Tapestry win by integrating with these standards?
* JSR-299 / JSR-330:
Supporting these specifications would allow us to make use of EJB3.1
without additional work. This gives transactions as well as JPA2.0
integration for free. Scopes are defined as well, so EJBs could be
tied to the request. I am not sure if all of this is even possible
with tapestry's current architecture.. but the benefits would be huge
and IMHO its worth to think about it.
* JSR-303:
Supporting this spec would allow us to build a tapestry independent
backend. Think about EJBs again - tapestry annotations really should
not go into the backend... in case of remote session beans, tapestry
is not even available to annotate my beans. With JSR-303 I could have
validations that are enforced in the backend as well as in the
frontend... Sometimes the web is just one of the clients!
I understand if you say that its not worth the effort or too hard to
accomplish - but then I need to ask the question how tapestry wants to
stand up against the competition in the future?
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.
In my oppinion, integrating with these standards is more than
important for tapestry to survive. It would become a real alternative
to JSF, playing out its strength: building the frontend, leaving the
backend stuff to the standard: EJB. (Spring integration would benefit
as well, as Spring 3 is completely JSR-330 compatible)
WDYAT?
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
