Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EJBCLIENT-403 Replace Enterprise JavaBeans|EJB references in java doc… #538

Merged
merged 1 commit into from
Jun 6, 2022

Conversation

RanabirChakraborty
Copy link
Contributor

@chengfang
Copy link
Contributor

The exact replacement should depend on the context in which the term ejb is used.

When the existing term "EJB" means the terminology for the technology (EJB technology), replace it with "Enterprise Beans" ( a proper noun)

When it is used in the form of "this EJB", "an EJB", "one EJB", it refers to a bean , an enterprise bean, so replace it with "this | an | one enterprise bean".

When it refers to such beans in its plural form: "ejbs", "EJBs", "some EJBs", "these EJBs", replace it with "enterprise beans".

@RanabirChakraborty
Copy link
Contributor Author

Hello, @chengfang I also thought about the same but the thing is as per the official eclipse foundation site there is only Jakarta Enterprise Beans.

Even inside the project details there is a line
Jakarta Enterprise Beans is an architecture for the development and deployment of component-based business applications.
even though Jakarta Enterprise Beans is a plural form but they have used is instead of are that's why I have used Enterprise Beans instead of Enterprise Bean in places.

@chengfang
Copy link
Contributor

what you cited is when using this term as a technology platform, so I would read this term as singular opaque block, even though it ends with beans.

But in many other cases, as I commented earlier, the term is used to refer to concrete object, or objects, where it doesn't feel right to me to replace into the full legal name.

@RanabirChakraborty
Copy link
Contributor Author

@chengfang thanks for the review, I have tried to change as you recommended. If you can review once will be great :)

@chengfang chengfang merged commit b4b6ffa into wildfly:4.0 Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants