| Re: [cdi-dev] CDI profiles (was RE: About parsing beans.xml files in Lite) |
I think it is best to keep things technically focused and assume good intent. I have to be honest in that I do not see anything more than people with different opinions trying in good faith to reach consensus.
For example, trying to maintain a reasonable notion of backwards compatibility while enabling newer approaches is a reasonable and good faith approach. I think that is possible utilizing the proposed profiles solution (and yes, of course profiles are a compromise solution but perhaps also a pragmatic one to solve a class of problems).
_______________________________________________
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
On 1/27/21 10:14 AM, Edward Moore wrote:
On Wednesday, 27 January 2021, 14:20:51 GMT, Graeme Rocher <graeme.rocher@xxxxxxxxx> wrote:
> I don't think naming names helps in this scenario, the overall tone of the various threads is very much people attacking other approaches rather than providing any actual useful insight or suggestions to move the conversation forward.
Nah, people are just passionate about their point of view. I don't see much hostility tbh.
> You want to know why Spring won and is by far the most dominant framework in the Java ecosystem and CDI is still a footnote in comparison?
Their unique approach to marketing?
> Because the Spring team is immensely adaptable to evolving technologies and not held back by design-by-committee processes that are openly hostile to progress.
Nah, the design-by-committee thing in Java EE has not been there for a decade or more. It's all open source and open processes these days. That's why we are having this discussion here now ;)
> In fact Spring Boot was an evolution of Spring whereby they made a conscious decision not to support Spring XML which was at the time the main way to configure Spring.
Java EE started to use annotations in Java EE 5, which was long before Spring started to use them. In fact, I remember Spring still preaching the advantages of XML then (separating code and config, making Spring code independent of Spring since everything Spring was in the XML config).
Then when annotations became a big success in Java EE, Spring followed after some years.
And that's okay. Java EE and Spring have inspired each other throughout their lifetimes, and this synergy made them both better frameworks.
> Today Spring Boot is the main way and they will probably drop support for XML all together, ie the community and the technology evolved to new and better ways to do things.
CDI never had a full XML config. It was discussed during the CDI 1.0 days, and there was a prototype, but eventually it was dropped. Modern Java EE specs like security and JSON don't have any XML config at all.
_______________________________________________ cdi-dev mailing list cdi-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev