Semantic age is coming!

Since last year, spring has been very popular. As a container that can be configured in a technical environment, spring's support for components in the poor container environment is still very good or won a lot of praise. As a result, many people are clamoring that spring will become the mainstream of j2ee development, and lightweight will be the trend of the future. In the eyes of many people, spring plays the role of the savior of j2ee. I said this is impossible. ejb is incomparable to spring in terms of technical completeness, but more importantly, ejb provides a set of standard enterprise-level development semantics, that is, enterprise software development semantic. Some people want to talk about it again. You just like to create a concept. Why have I never heard of any enterprise software development semantic. Well, let me not talk about semantics and reuse it first. For example, let me say: That's it. So you must be confused? There is a lack of necessary semantic environments. "This" is a common and reusable word that cannot be understood. In this sentence, the "this" I used cannot be used in your ideas very well, so I want to provide enough semantic context. For example, I said: Today I am very tired and want to go to bed. It is easy to infer the context.
Components, as the smallest part of software physics, have a great conceptual similarity with the words we use to speak, representing a certain degree of software semantics. Therefore, the key to reusing it is not to look at the intrusion or anything else, but to determine whether it is easy to build a reusable semantic environment. For example, if I say "", many people will not understand it, I need to cite the moral scriptures to make a good explanation. the reusability of this word is very poor because there is no standard understanding of semantics. On the contrary, "Apple" is quite understandable because its semantics is relatively general. Spring's success lies in its good support for various components, but it is far from shaking the foundation of j2ee, because it does not have a unified and accepted enterprise-level development semantics, and ejb has such transactions, we can use spring to easily describe transactions, but it is a poor semantic description. ejb uses Required, RequiredNew, and other words to describe transactions in a unified rich semantics, the most important thing is that this is standard.
Spring gives us freedom. ejb gives us a unified and consistent model for enterprise development. We can use spring to construct our system, but it is not a standard enterprise-level development semantics, but a custom semantics. Of course, I am not saying that our semantics is not good, but sun's definition is good. However, with the spread of the gospel of mda, core semantic definitions are truly competitive. One day later, j2ee application compatibility will be identified using semantic compatibility. What should we do? Let's take a look at jsr250, look at ibm j2ee mof, and look at cwm. The power of semantics is coming soon.
Spring wants to truly continue to affect mainstream j2ee development. Let's look at your semantics. Otherwise, being hacked is an unavoidable fate (becoming a semantic plug-in implement), and semantic age is coming, what should we do?