Did you know.. over 15 WAS CE developers are committers (and in some cases PMR members) in the Apache Geronimo project? Did you know that WAS CE is IBM's distribution of Apache Geronimo?
WAS CE is not a fork of Apache Geronimo
Apache Geronimo is available in several different flavors that can differ by which open source components are used for the servlet container (Jetty or Tomcat) and webservices (CXF or Axis2). Today, IBM's distribution is based on the the version of Geronimo that uses Tomcat and Axis2:
WAS CE 220.127.116.11 also contains many patches from the very latest versions of Apache Geronimo. Check out the complete list here:
Each release of WAS CE goes through an extensive QA cycle. We report and fix bugs in the Apache Geronimo community then the fixes are pulled from the open source community back into the WAS CE release under development.
WAS CE service refreshes are developed with similar discipline .. bugs are identified and fixed in the Apache Geronimo open source community, then fixes are selectively pulled from the community into the WAS CE service stream. Fixes pulled into the WAS CE service stream are carefully screened and peer reviewed to manage the risk of introducing function regression.
Do you want to have some very direct influence over what goes into WAS CE? It's trivial... here's how:
See a bug fix in Geronimo that you would like to see in CE? First check to see if it is already fixed in CE (CHANGES.txt file, referenced above), if not, post a pointer to the Geronimo JIRA in this thread and the CE developers take a look at it.
Interested in taking a deeper dive? If you see a problem in CE 18.104.22.168, you can, with near certainty, replicate the exact same problem in the Tomcat/Axis2 assembly of Geronimo 2.1.1. Jump into the source code, debug the problem, work up a patch and open a Geronimo JIRA. We'll review the patch and consider picking it up in the next CE service stream update. It's that easy.
If you see a bug or feature request opened in Apache Geronimo JIRA issue tracker,
http://issues.apache.org/jira/browse/GERONIMO that you want to see fixed in CE, drop a URL pointing to the issue into this thread.
I have a couple of requests before you get started:
Please Do Not post bug reports to this thread. Feel free to start new threads to discuss bugs. This thread is strictly for expressing an interest in issues reported against Apache Geronimo that you would like to see fixed in WAS CE.
PLEASE DO NOT mention WAS CE or IBM in Apache Geronimo community JIRA issues. Even though many IBM'ers are involved in the Geronimo community, out of respect for the other non-IBM'ers in that community, we CANNOT allow commercial IBM work to occur in the Geronimo community. Geronimo JIRAs mentioning IBM and/or WAS CE will be deleted out of respect for the Geronimo community. If you want to make comments or open Apache Geronimo JIRAs, you must do so in the context of an Apache Geronimo release, not WAS CE.
WAS CE Development
Founding Member, Apache Software Foundation
This topic has been locked.
7 replies Latest Post - 2012-08-21T09:48:56Z by SystemAdmin
Pinned topic Feature and JIRA Requests: WAS CE 2.1
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-08-21T09:48:56Z at 2012-08-21T09:48:56Z by SystemAdmin
Re: Feature and JIRA Requests: WAS CE 2.12009-04-21T15:54:53Z in response to Bill.StoddardI changed the PortOffset value to 10 in <WASCE_HOME>/var/config/client-substitutions.properties file. Now when I run shutdown.sh script, it gives the following error:
Locating server on port 1099... Could not communicate with the server.
But it works when I run the following command:
$ shutdown.sh --port 1109
So I think shutdown.sh is not recognizing the PortOffset value.
Janet_Han 060000141H45 PostsACCEPTED ANSWER
Re: Feature and JIRA Requests: WAS CE 2.12009-04-22T01:33:40Z in response to SystemAdminHi Quadir,
The behavior you described below works as design, refer to the doc for details: http://publib.boulder.ibm.com/wasce/V2.1.1/en/shutdown.html
Meanwhile, samiliar command like deploy.bat|deploy.sh also needs --port parameter if the server is not started with the default port: http://publib.boulder.ibm.com/wasce/V2.1.1/en/deploy.html
Janet_Han 060000141H45 Posts
smdelfin 120000JEAY1 PostACCEPTED ANSWER
Re: Feature and JIRA Requests: WAS CE 2.12010-07-06T03:29:23Z in response to Bill.StoddardWhere can I request a VMWare appliance that contains the latest WAS-CE?
It's like WAS-CE running on Ubuntu with DB2-Express C, or something like that.
It would be very helpful if we could just download something that already works without too much configuration.