search

javaee / ejb-spec

See javax.ejb project for API. Contains legacy issues only.
https://github.com/javaee/javax.ejb
6 stars 1 forks source link

Update project lead in JIRA #120

Open glassfishrobot opened 10 years ago

glassfishrobot commented 10 years ago

As Marina is not involved with EJB spec anymore the project lead field of the ejb-spec JIRA project has to be updated ASAP.

Affected Versions

[3.3]

glassfishrobot commented 10 years ago

Reported by mkarg

glassfishrobot commented 10 years ago

reza_rahman said: The most productive and advisable approach in this case is to contact the java.net administrator. That being said, I will follow up with the respective resource manager personally. In the meanwhile the Oracle Java EE team will continue to respond to any valid issues within reason until a new revision of EJB is spun up (if such a revision is actually warranted).

glassfishrobot commented 10 years ago

mkarg said: Meanwhile you'd might be kind enough to post the name of the new EJB spec lead here, as it is just fair to let the community know whom Oracle decided to lead this absolutely essential project?

glassfishrobot commented 10 years ago

reza_rahman said: I think it is fairly apparent that we are currently in the process of planning the next set of technologies for Java EE. If it is determined that EJB requires a further revision I am sure a spec lead will be assigned once a JSR is actually launched. This will happen in a proper and transparent fashion as always via the JCP. The best way to keep abreast of this is via subscribing to the Aquarium blog (https://blogs.oracle.com/theaquarium/). It is important to understand however that the community by and large has not expressed much interest in further significant revisions to EJB beyond more CDI alignment of EJB style services (likely to happen in specs other than EJB) and further pruning of EJB features.

glassfishrobot commented 10 years ago

mkarg said: I think you mix up teams up here. The Aquarium is about a product (GlassFish) provided by Oracle. I am talking about a standards specification (EJB) which is provided by a standardization organization (JCP) in which other companies have a say, too and in which I am a member. So if I understand your comments correctly then Oracle is not interested in further leading the EJB expert group and wants other people to chime in and define EJB 3.3? I mean, just because Oracle does not see a future of EJB does not mean that other JCP members share this vision.

glassfishrobot commented 10 years ago

reza_rahman said: Firstly, GlassFish is the Java EE reference implementation and not a commercial product. That means The Aquarium is as much about Java EE as it is about GlassFish. Indeed it is likely the best way to stay up-to-date with Java EE for this reason.

Please read the thread carefully - what I said is that we are in the middle of determining what work is warranted for EJB/Java EE based on community feedback we have made significant efforts to try to gather. The feedback definitely does not indicate a strong desire for significant further work in EJB, if any work at all. If you have a different opinion it would be useful to know the precise technical details of that opinion is. Keep in mind you would be in a rather tiny minority so what you have to say would have to be pretty compelling.

If/when a JSR is launched and a spec lead is present, an EG will be formed. Anyone including you (provided you are deemed qualified to join the EG) can work with the spec lead from that reasonable starting point to determine what is actually done and how it is done.

Do keep in mind other key JCP partners with credible technical and resource capabilities are usually also consulted at various stages even before any key JSR is launched so a JSR filing carries far more weight than you perhaps realize. It is unlikely their opinion would differ significantly from the large numbers of developers that have already given us clear feedback.

glassfishrobot commented 10 years ago

mkarg said: Reza, be assured as a JCP member I know all that. No need to tell me.

BTW, Oracle might like to overhaul the web site so the official statements published there will align with your comments. Firstly, the official GlassFish web site at https://glassfish.java.net/ literally says: "Oracle GlassFish Server - The commercial, supported version of GlassFish". I know that Oracle announced to stop commcercial support, but the web site still says "commcerial". Second, the official subtitle of the Aquarium blog at https://blogs.oracle.com/theaquarium/ literally says: "The Aquarium - News from the GlassFish Community". I know that also spec topics are covered there from time to time, but the web site still says "GlassFish Community" but not "Java EE Team". Hence both pages support my previous statement at least currently.

Side note about the separation: As a JSR 339 EG member and former Jersey contributor I like the JAX-RS team's way of separating spec and product. Jersey is a product and has a product page and announcement space dealing with the product (but not with JAX-RS). JAX-RS is a specification developed by an expert group at the JCP which tries to find concencus among all participants, not simply an abstracted description of the Jersey product's way to work. It has its own annoncement space independent of the RI. The fact that Jersey is also the RI is visible, but recognized as a side effect, not as the main purpose of the product. People and vendors can see that Oracle understands that a specification is a common effort and Jersey follows the rules defined by spec – and not vice versa. So anyone interested in JAX-RS can get the latest news without even having to get in any contact with Jersey in particular or Oracle in common. I see EJB in the same way, hence you now better understand my division into EJB and GlassFish.

glassfishrobot commented 10 years ago

reza_rahman said: The link to commercial GlassFish only exists to point to continued support for GlassFish 3, not GlassFish 4 moving forward. As you have noted, we have made it amply clear what the current goals of GlassFish are. As to the description of The Aquarium - it is 100% accurate. It is news about GlassFish and GlassFish is principally the reference implementation of Java EE and not a commercial product. Hence, the primary theme of the blog is Java EE implicitly. This is distinctly different from Jersey, etc as Jersey is in fact a supported commercial product via WebLogic as well as a reference implementation and will focus on far more than simply JAX-RS.

As to the EJB issues you are referring to it should be discussed in it's own existing thread, not in this context where it is confusing for others. As it is this thread has veered too far off topic.

glassfishrobot commented 10 years ago

mkarg said: Ok let's sum up to get it stopped:

Okay for me. Things can be expressed so concise and short, I wonder what all the discussion was about.

glassfishrobot commented 10 years ago

reza_rahman said: If there is some value to summation, here is mine:

I also don't really get what the point and motivation of this entry was when a simple email or forum question would have sufficed as a first step.

glassfishrobot commented 10 years ago

mkarg said: To answer your last question: If you meant my last comment with "entry", then the motivation was to check whether I understood correctly the result of our earlier discussion above. If you meant this JIRA ticket with "entry", then the motivation is found in the original description: To update the JIRA system, which still says Marina is the spec lead.

glassfishrobot commented 10 years ago

reza_rahman said: I meant this entire JIRA issue was probably best handled elsewhere via the mechanisms mentioned.

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA EJB_SPEC-120