The goal of the plugin is to provide users with the latest stuff. It is not meant to provide the users with bug fixes in the latest AS. For that purpose users should use EAP.
Would you advise applying the ejb3-plugin jar" patch" on a JBOSS instance running on production if all went well in development and QA environments?
Philani Dlamini wrote:
Would you advise applying the ejb3-plugin jar" patch" on a JBOSS instance running on production
When you say production, are you implying the paid version of JBoss server or are do you mean the community release?
Using JBoss AS community version in production implies that whoever is using it will be supporting it themselves. So with regards to applying the ejb3-plugin, if it passes your QA then sure you are free to use it in production. It's the same deal as the JBoss AS that you are using - if you run into any issues, you either will have to fix/patch the issue yourself or wait for the issue to be fixed in the next community release.