We are using JBoss 7.1.1 and we basically dont pay anything to the Red Hat.
My first question is, since we are not paying for any support, this would be considers as JBoss community edition?
My next question is whats the current status of the JBoss support, is the community edition still considered as supported and where can I find this info?
I' m reading this notes, but I cant conclude anything from it?
There is no support for community bits. The notes that you referred to is applicable for only enterprise (EAP) bits.
JBoss AS project has been migrated to the JBoss WildFly community. The latest community release is WildFly 10 which is based on the JEE7 spec. JBoss AS 7 was a JEE6 implementation.
JBoss 7.1.1 AS isn't supported by RedHat (AS products have now been renamed to Wildfly, which is basically the free version of JBoss). Yes you could say that it is the "community edition" of JBoss.
EAP products such as JBoss 7 EAP are supported, but they are commerical and you have to pay a subscription fee for their usage and support. Redhat typically backports bugfixes, etc. from its commercial versions to AS products, but this isn't guranteed and there is no fixed support cycle or maintenance phases in the case of the latter.
Related
When i downloaded jdk ee few years ago, got "jdk-8u231-windows-x64.exe" file and installed it. It created "jdk1.8.0_231" folder and i have used it for JAVA_HOME.
But when i tried to download latest JDK EE now, i got "glassfish" folder in it.
What is this change ? Why is this change for ?
Note: I know Oracle gave Java EE to Eclipse and it is now called as Jakarta EE. But even in eclipse site or oracle site, i could only find glassfish downloads, not jdk ee.
Please help me to understand this.
Thanks
There is no such thing as a JDK EE.
JDK
A JDK is an implementation of the Java™ SE (Standard Edition) specifications. A JDK is composed of development tools such as a compiler, and of runtime tools that include a Java Virtual Machine (JVM) and an implementation of the standard libraries including the classes such as ArrayList, LocalDate, and so on.
The first sentence of the linked Wikipedia article on JDK is incorrect in claiming Oracle is the sole vendor. Oracle Corporation is but one of several vendors providing builds and installers for a JDK. Other vendors include, off the top of my head: Amazon, Azul Systems, Microsoft, Adoptium, SAP, BellSoft, Red Hat/IBM, Pivotal, and maybe more. Nowadays, most of these companies’ offerings are based largely or entirely on the open-source code base collaboratively built at the OpenJDK project. So you will find the quality and performance to be largely the same across these JDK products.
So your first chore is to choose a vendor and obtain and install a JDK. Some JDK products are free-of-cost and some require a fee. Be aware at the time of download. See Java Is Still Free for more information.
Choose a version of JDK appropriate to your choice of Jakarta EE product discussed below. Be aware that Java 8, 11, and 17 are the long-term support (LTS) versions of Java.
Jakarta EE
Jakarta EE, formerly known as Java EE (Enterprise Edition), is a collection of dozens of specifications for various kinds of enterprise-oriented software you may want to run on top of your Java SE JDK installation.
Most of these products are aimed at server-side usage. A few can also be used in desktop apps, such as Jakarta Bean Validation and Jakarta Contexts and Dependency Injection.
The Jakarta EE specifications are owned by the Eclipse Foundation, having been donated by Oracle Corp. Their further development is proceeding in a transparent open-source manner.
Several vendors provide implementations of the various Jakarta EE specifications. Some are available individually as a library to include in your app. And some vendors offer an assortment of products bundled together to be run as an application server.
The Glassfish product you mentioned in your Question is one such application server offering. Similar products from various vendors include Payara, Open Liberty, Wildfly, JBoss, and more.
Your second chore is to choose a vendor and obtain a Jakarta EE compliant application server product. You then install that on the same machine you installed the JDK.
If you are starting fresh on a new project, I would suggest using Java 17 with an app server compliant with Jakarta EE 9.1. Eclipse GlassFish 6.2.3 is one such product to consider. The Jakarta EE site maintains a list of compliant products.
I'm using GlassFish 3.1.2.2 on a AIX machine and it is working fine. The company's security policy requires me to upgrade it to the latest version, but everytime I try to deploy my application (the same that is working fine in version 3.1.2.2) I get the error Type javax.rcm.ResourceAttributes not present and a nasty stack trace afterwards.
I read the server's specification and it is not clear if it will run on AIX or not. Previous releases had a separate distribution specific for AIX, but that is not the case now.
Does anyone know if it just not compatible or if it is some sort of bug in the JDK implementation?
Kind regards,
Carlos Ferreira
GlassFish 4.x and higher is not "supported" on anything. The reason is that Oracle have withdrawn commercial support, so GlassFish is only available as an open source edition.
If you do need commercial support, the Payara project exists to provide commercial support and custom builds of GlassFish.
Coincidentally, there is a recently opened issue on their Github relating to known issues with GlassFish on the IBM JDK, so it is probably worth commenting on that issue (or creating a new one) with your errors and stack traces.
Payara Blue is the version of Payara that should run on IBM AIX on the IBM JDK. Get Payara Blue from the Payara WebSite Payara is derived from GlassFish 4.x Open Source Edition.
Recently I took over a relative old project, which is running on weblogic 9.2. I need work on some change requests. I don't know much about weblogic product.
The old DEV-Env is windows based, however I dont have a windows machine. I tried to download Weblogic9.2 for linux (32bits), however I cannot find the link on Oracle website, after quite a lot google, still no working link found.
So the options for me:
find out a working link, download weblogic9.2 and work with it
download and use the 10.x version from oracle
setup a windows box (we have the installer of weblogic9.2 for win)
the 3 is the last thing I want to do. If someone knows where can I get the 9.2 version, it would be great. If there is no weblogic9.2 available, can I work on weblogic10.x and release to 9.2 in production? how risky is it?
Developing in WLS 10.x and deploying in 9.2 may cause some trouble.
There are quite a no of features which have been upgraded in 10.x, such as Java 5 to 6, J2EE 1.4 to 5, Servlet 2.4 to 2.5, JSP 2.0 to 2.1, EJB 2.1 to 3.0.
While most of the features here do have backward compatibility, you have to be extra careful when you develop.
I would suggest to develop based on the lowest common denominator features only, and build on the same server you are deploying it to. (i.e. 10.x has a diff build, and 9.2.x has different one.)
EDIT: There seems to be a authentic binary available on PeopleSoft's FTP site.
It's definitely a risk. Different versions of Weblogic use different jars, so what works on 10.x may not work on 9.x. It's a good practice to have your QA and PROD environments as similar as possible including node setup and startup variables.
If your current PROD deployed code works on 10.x then I would upgrade your PROD environment to 10.x and continue your development on 10.x. If not then do what you can to have 9.x on your DEV environment as well.
I got interested in looking at JSF 2.0 as a potential technology to use. Does anybody know when this version is scheduled to come out and how active is the project in general?
Does anybody know when this version is scheduled to come out
JSF 2.0 is part of Java EE 6 (i.e. any Java EE 6 container supports it) and has been elaborated under JSR-314 (which is final since 01 Jul, 2009) but, as mentioned on the JCP web page:
Sun will deliver a Reference Implementation (RI) and Technology Compatibility Kit (TCK). The RI will be made available standalone and as part of the Java EE 6 platform.
The RI is Mojarra and is already available. As written in Mojarra 2.0.0 is available! (Oct 19, 2009):
There are several ways to obtain the
release.
GlassFish V3 promoted build 69 (out later this week)
Download directly from http://javaserverfaces.java.net
Download using Maven2 using information provided here
You actually don't need a full Java EE 6 server. For example, check out the post JSF 2.0 and Tomcat or Integrating JSF 2.0 and Weld with Tomcat6. But I'd simply go for GlassFish v3 (or JBoss 5.2+ which also supports JSF 2.0 + CDI).
how active is the project in general?
What project? The RI? What do you mean exactly? Well, Mojarra is used in GlassFish so I consider it as a serious project, with dedicated man power. However, I don't expect extreme activity now that the spec is final, only maintenance and bugfix releases.
JSF 2.0 was already final several months ago (19 october 2009) and it's indeed included in the Java EE 6 which was made final about one month ago (10 december 2009).
Although it's been released along with Servlet 3.0 API in Java EE 6, JSF 2.0 is backwards compatible with Servlet 2.5. So you can either download it separately and run on any Servlet 2.5 capable webcontainer like Tomcat 6.0, or just download a full fledged Java EE 6 implementation including it like Glassfish v3.
JSF 2.0 is included in Java EE 6, and Glassfish v3 currently supports it. It'll also run in WebSphere 7, with some effort.
Does anyone know if Red Hat has forked the code you download from JBOSS.org? I'm guessing that the answer is "yes", but I'd like to confirm it. I can't pin it down at the Red Hat site, and jboss.org giving me an HTTP 502 right now for some reason.
I know that Red Hat owns JBoss. Does that mean that the code they sell in JBoss Developer Studio for $99 a pop is identical to what I can download from JBOSS.org without paying a fee? Or have they forked the for-fee version in some way?
All the source code for Red Hat/JBoss products is available in opensource (in svn/cvs etc.), but the sold version is what is called the productized version.
What does productized mean ? It means as Michael says, it has additional tests/QA, it has the certified bits, it has matching doc's, etc. It also means that some features in the community version are disabled, removed or have a slightly different configuration default and slightly different packaging.
Examples of differences:
i.e. JBoss EAP comes bundled with Seam, JBoss AS does not.
The productized Seam 1.2 works on JBoss AS 4.3, Seam from .org did not
JBoss EAP has a 'production' profile which is tuned for production (i.e. hotdeploy disabled and other best practices which our support recommend), JBoss AS does not have that.
JBoss EAP gets supported and guaranteed cumulative patches for many years, JBoss AS from .org does not.
All of the above is about having a productized version that is supportable for a long period of time and hence much more about having a stable version than about having the latest-greatest cutting edge version of the latest development.
If you are looking for the bleeding edge then JBoss.org is for you.
To answer you question for Michael, "If I download the code from JBoss.org i'm sure to be using the same stuff that someone who buys it from Red Hat, correct?" - Then the answer to that is: It depends on the project.
Some projects are exactly the same, where as others have more visible differences BUT all features in the productized version is available in the .org version, but there might be some features that exist in .org that has been removed/disabled (see above).
So what to do? If you are looking for bleeding edge, use JBoss.org - if you are looking for making sure you are developing on the exact same set of binaries which JBoss/Red Hat can provide development and product support on for the next many years, then the $99 product from Red Hat you refer to (I assume you meant JBoss Developer Studio Portfolio) is your best option.
btw. the official answer to what the difference is between the community and enterprise (productized) versions is shown at http://www.jboss.com/products/community-enterprise/
For full disclosure: I'm the lead of JBoss Tools and JBoss Developer Studio.
No its not a fork as in different code - its build from the .org versions and put through various tests/QA environments, certified if necessary etc...
Its analagous to what goes on with Fedora and Red Hat Enterprise Linux (I think the idea is to have a similar model) - so if you look into that model it might help explain it better then I can.