Re: change jvm settings (1.3.1 to 1.4.2) in websphere -- JAVA400-L

    After seeing Frances' reply, I wondered about Websphere Community
Edition, which is based on Geronimo.  I didn't think it would go over very
well if one could use JDK 1.5 on the entry level product and have to revert
to 1.4.2 on the heavyweight model.

    Turns out that, while one can use either IBM's or Sun's implementation,
WASCE requires JDK 1.4.2 as well.  See:

http://www-306.ibm.com/software/webservers/appserv/community/sysreq/

  In addition, for Geronimo itself:

"System Requirements
-------------------
You need a platform that supports the Sun JDK 1.4.2.  CORBA
support requires a Sun Java 1.4.2 VM (specifically 1.4.2_08
or a higher 1.4.2_* release)."

    See: Geronimo Release Notes
http://www.apache.org/dist/geronimo/1.0/RELEASE-NOTES-1.0.txt

    This aspect does cause some consideration because 1.6 is not that far
away.

    Listers may also be interested in JEE 5 status:  There's a preview
available, along with Glassfish ( open source app server ) and screencasts.
See:

http://blogs.sun.com/roller/page/paulsen?entry=start_using_java_ee_5

and

http://java.sun.com/javaee/5/index.jsp


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO       -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?            http://www.jguru.com/faq/Java400


----- Original Message ----- 
From: "Frances Stewart" <francess@xxxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Monday, February 20, 2006 7:25 PM
Subject: RE: change jvm settings (1.3.1 to 1.4.2) in websphere


> It's several things:
>    IBM ORB
>    Security extensions (JSSE, JCE)
>    Packaging changes (JDK bundles stuff we ship) causing classloader
>    problems
>    Serialization incompatibilities
>
>
> Frances Stewart
> WebSphere Application Server for iSeries, Technical Team Lead/Architect
>     External web site: http://www.iseries.ibm.com/websphere
>     Team web site: http://w3.rchland.ibm.com/~was
> E-mail: francess@xxxxxxxxxx
> IBM Rochester
>
>
>
>
>              "Joe Pluta"
>              <joepluta@plutabr
>              others.com>                                                To
>              Sent by:                  "'Java Programming on and around
>              java400-l-bounces         the iSeries / AS400'"
>              @midrange.com             <java400-l@xxxxxxxxxxxx>
>                                                                         cc
>
>              02/09/2006 07:30                                      Subject
>              AM                        RE: change jvm settings (1.3.1 to
>                                        1.4.2)  in websphere
>
>              Please respond to
>              Java Programming
>              on and around the
>               iSeries / AS400
>              <java400-l@midran
>                   ge.com>
>
>
>
>
>
>
> Hi Frances!  I hope the New Year has been good so far.
>
> I was wondering why WebSphere required a specific JDK.  I can understand
> there being a MINIMUM level for the JDK, but why would there be a maximum?
> What features are you using that makes it impossible to, for example, run
> WebSphere under Tiger?  It just seems to sort of go against the whole Java
> message when I can't upgrade my application to the next version of the
JDK.
>
> Joe
>
> > From: Frances Stewart
> >
> > Each WAS version requires a specific JDK level which cannot be changed.
> > WAS 5.0 = JDK 1.3.1
> > WAS 5.1 = JDK 1.4.2
> > WAS 6.0 = JDK 1.4.2.
>
>