Java EE

Vote for a new name for Java EE - 'Jakarta EE' or 'Enterprise Profile' - before 23 Feb 2018

If you have visited planet Java in recent times, you'll know that "Enterprise Java", the Java Enterprise Edition, Java EE, is "moving" from Oracle to the Eclipse Foundation. (I'd have far preferred Apache Foundation, but so be it.)

The options for names of the top-level specification projects have been whittled down to:

  • 'Jakarta EE', where Jakarta of course is a "sub-family" of Java-related open source projects within the Apache Foundation.
  • 'Enterprise Profile'

You can vote here til 23 Feb 2018.

I think Enterprise Profile is not a bad name, but the trouble with it is that it is too vague and does not have any clear reference to or link to Java technology. Another popular suggestion I quite liked, Open EE, did not get up.

I have voted for Jakarta EE, which will likely have the acronym JEE (which ironically was a common mistake often-used instead of Java EE). I like the fact that it has a direct historical association with Java, even if that association is only clear to existing Java users, and I like the fact that it is affiliated with the Apache Foundation. (Also, perhaps more trivially, if new projects must use a new namespace, jakarta.xyz is easier than writing enterprise.xyz every time.)

Many recruiters (at least in Australia) still ask for "J2EE developers" about 10 years too late, and seem to get upset when you correct them and explain what Java EE is/was, perhaps because it might yet again reveal they in fact have no idea at all about the technology the are seeking placements for, and they are just lazily trying to tick off a box with J2EE on it, rather than knowing stuff. The mind boggles over how they'll handle this new major technology name change.

Some background leading up to these final 2 candidates

The short version of the long story is that after a gazillion suggestions - none of which were allowed to include the word Java because of Oracle silliness - only those two names above are left on the table. You can go crazy like pigs in mud reading about the entire discussions leading up these two name choices here:

Oracle have been truly horrible and petty not letting the word Java be used in the new name. Everybody is going to keep calling it
(Enterprise) Java for years to come anyway. They wanted to off-load the technology, yet keep their control of the technology, have their Java cake and eat it, then make life for everybody who uses and loves Java harder.

What I did NOT want, and thankfully is not happening, is for the top-level specifications to have the word 'Eclipse' in them. Thankfully, common sense has prevailed, and the acronym EE4J will now I understand only be used for the Eclipse-specific implementation of the specs. Good. Phew.

Enterprise Java should not be considered now "an Eclipse project", it has a special status and special history, and the arguments that have been offered that the top-level project name has to include the word Eclipse because all other Eclipse projects do is typical Eclipse bullying. Yes, I said bullying.

My answer to the Eclipse naming convention argument ? Don't use that naming convention. You don't have to apply it, it's not a holy rule, unless you think Eclipse eclipses everything.

To the Eclipse Foundation: be nice. Java has a special status, and has devoted fans of non-Eclipse Java technologies such as NetBeans IDE, and Apache/Jakarta. Be nice. Respect the Java world outside Eclipse.

My other concerns, outside the matter of naming, is that my beloved NetBeans, which fairly blasts Eclipse IDE out of the water for JavaServer Faces (JSF) and XML work, will be chucked out as the default IDE for tutorials, and that GlassFish might also suffer under the Eclipse Foundation.

Eclipse does not Eclipse everything

I once worked on a project where an Eclipse-addict truly did not understand that UML2 is a version of the Unified Modeling Language (UML) from the Object Management Group (OMG), because all he seemed to do was read Eclipse documentation and confused it with the UML2 - Eclipse project. Not the fault of Eclipse Foundation of course, but in my experience, all too typical, because too often, Eclipse orbits around Eclipse with Eclipse developers speaking about Eclipse which eclipses everything because it's Eclipse and Eclipse has Eclipse projects that eclipse other projects except those that also orbit around Eclipse which is Eclipse and ...

I have used Eclipse IDE over the years, a lot. It is a good IDE, mostly. It is NOT "the standard" IDE for Java, and it also not the best for all tasks. NetBeans IDE is utterly awesome for Enterprise Java and JavaServer Faces (JSF) development (in combination with GlassFish, out of the box, or Payara), and it does EXACTLY what I need and ONLY what I need, without the clutter of Eclipse IDE.

Simply put: I get sick and tired of Eclipse-obsessed developers who know nothing about NetBeans IDE, whereas I do know about Eclipse. A lot.

I hope that NetBeans IDE more than survives, and really thrives, under this move of Enterprise Java.

PrimeFaces

Webel employs core JavaServer Faces (JSF) and the 3rd-party PrimeFaces toolkit as the primary rich, interactive web user interface technology for Enterprise Java web applications:

For demonstrations and examples, please visit the tutorial presentations and demonstration videos of the GreenDesk web application for modelling and environmental compliance tracking of office buildings, developed by Webel for GreenSoft.

Java Persistence API (JPA)

Webel employs the Java Persistence API (JPA) as the core database technology for Enterprise Java web application development in combination with JPA-compliant object-relational database mapping technologies (EclipseLink and Hibernate) for relational database management systems (MySQL, Oracle DB), as well as in combination with the JPA-compliant pure-object database ObjectDB. Core JavaServer Faces (JSF) and the PrimeFaces 3rd-party JSF GUI toolkit are used to create rich interactive web worksheets for Enterprise Java web applications from data and objects served via JPA and managed via Enterprise Java Beans employing Expert System strategies:

For demonstrations and examples, please visit the tutorial presentations and demonstration videos of the GreenDesk web application for modelling and environmental compliance tracking of office buildings, developed by Webel for GreenSoft.

Dr Darren Kelly's model-based software and systems engineering résumé

Please click here to download a printable PDF version of the dedicated Model-Based Engineering résumé of Dr Darren R. C. Kelly, proprietor of Webel IT, summarising his extensive professional experience with database-driven Enterprise Java web application development technologies, W3C XML and XML Schema data modelling, model-driven development and software architecture using graphical Unified Modeling Language™ (UML™), systems analysis using Systems Modeling Language™ (SysML™), semantic web and ontology modelling technologies such as RDF/S OWL, and promotion of these technologies through Webel IT training and online education.


Other résumé and CV versions

For a concise Web Technologies résumé - with a focus on Content Management System (CMS) web site development and web-related IT consultancy activities since 1999, especially PHP-driven Drupal™-CMS since 2007 - please visit:

- Dr Darren Kelly's online Web Technologies résumé

For a full-career biographical CV (intended as a reference only) please visit:

- Dr Darren Kelly's full-career Curriculum Vitae.

IT Consultant: software architect, systems analyst, Enterprise Java web application developer, Drupal CMS web site developer (Phase1)

When
17/01/2011 - 09/02/2014
Organisation(s)
Role(s)
IT Consultant, Domain Analyst, Requirements Analyst, Drupal CMS Web Developer
Tasks

Developed a unique JavaEE web application GreenDesk™ for analysing and tracking the complex data and documentation required for preparing applications compliant with the Green Star™ Office sustainable building rating system of the Green Building Council of Australia (GBCA).

The system uses Expert System technology in Java as an intermediary between rich interactive web user interface worksheets and model views using JavaServer Faces (JSF), and an underlying Enterprise Java domain entity database model - the Building Project Model, created using Parsing Analysis technology to map the Green Star Office specifications to domain model elements and rules.

After initially using an MySQL database with object-relational Java Persistence API (JPA) mapping with EclipseLink, then an object-relational Oracle DB with EclipseLink, a major migration was made to a JPA-compliant pure-object database ObjectDB, with significant improvements.

The PrimeFaces toolkit for JavaServer Faces (JSF) was used to enhance the rich web user interface.

The software engineering included frequent use of graphical Unified Modeling Language (UML) for requirements and domain analysis, model-driven Java design, Java code refactoring, documentation, and even proved useful for freestyle graphics presentations for non-experts. The closely related Systems Modeling Language (SysML) heavily influenced the Building Project domain model.

Custom object-oriented PHP scripting was used to generate Enterprise Java database entity classes directly from a Drupal CMS web site entity-relational database model of the Green Star Office technical manual’s specification for the green office building rating system of the Green Building Council of Australia (GBCA). Such novel and advanced automation of coding is a speciality of Webel IT Australia.

Drupal CMS web site development: Developed a GreenSoft company web site, a web site for the GreenDesk product, and the GreenBase site for resources on global environmental rating schemes.

Prepared investor presentations and held pitch meeting demonstrations for potential investors. Demonstrations included screencast tutorial videos made using ScreenFlow.

Created 3D logos and animated 3D logos using Swift3D.

For demonstrations and examples, please visit the tutorial presentations and demonstration videos of the GreenDesk web application for modelling and environmental compliance tracking of office buildings, developed by Webel for GreenSoft Pty Ltd, Australia.

GreenSoft Pty Ltd, Australia

Type of organisation
Company
Where
Sydney, Australia
Role(s)
IT Consultant, Software Architect, Enterprise Java Developer, Web Developer, Domain Analyst, Requirements Analyst, Systems Analyst, Database Engineer
For demonstrations and examples, please visit the tutorial presentations and demonstration videos of the GreenDesk web application for modelling and environmental compliance tracking of office buildings, developed by Webel for GreenSoft.

IT Consultant: software engineer, systems engineer, web developer

When
27/07/2010 - 16/02/2011
Organisation(s)
Role(s)
software engineer, systems engineer, web developer
Tasks

Performed domain analysis using UML Parsing Analysis (sentence-by-sentence mapping of technical text to UML relational and graphical models) of the Green Star Office v3 rating tool spreadsheets into an entity-relationship model and object-relational database representation, using a SysML-like model of domain elements: blocks, attributes, value types, quantities, parts, activities.

Developed a PHP-driven Drupal content management system as a Project Tracking CMS, including a relational parsing analysis of the GBCA Green Star Office v3 rating tool spreadsheets into a cross-navigable domain analysis entity-relationship model. Includes a representation of the credit groups of the Green Star process as activities allocated to human resources.

Performed demonstrations of the developmental ecoSmart web application concept to stakeholders, candidate users, and investors.

greeting.xhtml: An XHTML page that uses the JavaServer Faces Facelets tag libraries.

greeting.xhtml: An XHTML page that uses the JavaServer Faces Facelets tag libraries.

The Your First Cup: An Introduction to the Java EE Platform source text has not yet said whether greeting.xhtml "is" a Facelet, or just 'uses the the JavaServer Faces Facelets tag libraries'.

Also, it has not yet been explained what relationship (if any) the 'JavaServer Faces Facelets tag libraries' have with Expression Language (EL) tags already encountered during this UML™ Parsing Analysis demo.

Until further info becomes available in the source text these matters are simply noted.

Syndicate content