This is a little off topic, but slightly related...I've actually been
attempting to find a solution for creating Jython stored procedures within
an Oracle database. I've successfully loaded the jython libraries into the
database, but there are a few invalid classes (such as PySingleton) which
refer to AbstractStringBuffer and StringBuffer. Those classes are not
available within the Oracle JVM for some reason. I loaded the jython binary
because I was not sure if the Oracle JVM would be capable of compiling
Has anyone else attempted a similar solution? Just thought I'd throw it out
there and see.
----- Original Message -----
From: "Frank Wierzbicki" <fwierzbicki@...>
To: "Steve Vinoski" <vinoski@...>
Cc: "Jython-Dev" <jython-dev@...>
Sent: Thursday, July 06, 2006 2:49 PM
Subject: [Jython-dev] Staying JDK 1.2 compatible (was: basic pickling)
>> > I forgot to ask, does the brute force approach depend on the new Java
>> > 5 APIs fro code points? We are trying to stay JDK 1.2 compatible, and
>> > do not want to depend on Java 5...
>> Can I ask the reason for wanting to stay compatible with JDK 1.2?
> I guess the reason to stay compatible with JDK 1.2 is to maximize the
> potential environments where Jython can be used. For example, the
> JDK that comes on some phones is limited to JDK 1.2 and many (most?)
> application servers are currently limited to (I believe) JDK 1.3. I
> think Jython should be careful with increasing the minimum version of
> the JDK, to avoid closing potential users out.
> That being said, we also have to balance that with the limited
> resources (mainly number of active developers on Jython). That is one
> of the reasons we are changing the minimum JDK from 1.1 to 1.2 (that
> and collections integration). While I really want to be more
> aggressive with the minimum JDK (I'd love to use java.nio.* from JDK
> 1.4 and the much better threading support from JDK 1.5) I don't think
> it is time for that yet.
> I am considering making JDK 1.4 the minimum when we start working on
> Jython 2.4, and perhaps incrementing in that fashion from then on (so
> Jython 2.5 has JDK 5 as the min, then Jython 2.6 has JDK 6 as the min,
> etc) Since both CPython and Java follow an approximate 18 month
> release cycle -- I think this might be a reasonable path (so we always
> use the JDK that was about 36 months old when a particular CPython
> came out).
> Whether or not that works is acceptable, I definitely plan on being
> very aggressive with the minimum JDK when we start to plan for Jython
> 3000. I expect we will use whatever JDK is in beta when the planning
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> Jython-dev mailing list