> a standard is not useful because it is a standard but because it provides us
> with an advantage. From a business point of view being a standard provider
> is a good reason to sell things to enterprise customer. Enterprise love
> standards not because they are innovative but because they are stable and
> you are able to switch to a different vendor (at least the sales brochure is
> telling you this).
You are right - that is why I mentioned the benefits of integrating
with these standards.
Of course, we could invent solutions on top of tapestry-ioc that would
be as good or better..
but then, why re-invent the wheel?
What I miss most in tapestry are remote services, transactions and
support for JPA.
The question is if we will bake all this ourselfe or integrate with EJB3?
There is a Spring integration.. but well - I don't see the point in
using another abstraction.
> The strategy behind 299, 303 and 330 is in my opinion to describe features
> in a standard in order to attract enterprise customers. Red Hat influences
> 303 (Hibernate Validation 4 is the reference implementation) and 299 (former
> Web Beans, the DI part of JBoss Seam, now Weld project), Spring Source
> attacks from the other side by standardizing their stuff in JSR 330. Google
> worked with Red Hat first and then moved over to support JSR 330.
To be honest, it does not matter what is the strategy behind this.
Fact is that both of these JSRs are part of JavaEE 6.
They are available in many application servers, and they are easily
embedded in pure servlet containers.
> I only agree that it would be nice to support JSR 303 (Validation
> framework). This is not becauce it is standardized. I believe that it is
> totally nonsense to standardize a couple of validations. The reason is that
> JPA and Hibernate uses those validations and as a matter of fact 95 % (my
> guess) of all persistence layers are written with those technologies.
So you say its totally nonsense to standardize these annotations, but
then you want it because
software is standardized on them? Oh well...
I totally agree that standards are not the solution for everything and
innovation needs to break out at times.
But.. standards are useful and important if you want to take advantage
of things you can't offer yourself.
Hey.. after all we talk about Java. And one argument for a Java Web
framework is integration with the rest of the huge Java ecosystem,
isn't it?
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
