Re: Problem updating to WebObjects 5.2.2
Re: Problem updating to WebObjects 5.2.2
- Subject: Re: Problem updating to WebObjects 5.2.2
- From: petite_abeille <email@hidden>
- Date: Wed, 29 Oct 2003 12:19:33 +0100
Hi Chuck,
On Oct 29, 2003, at 06:15, Chuck Hill wrote:
I'm happy about that. The Java API changed between 1.3 and 1.4.
Right... this happen from time to time, isn't it?
Sometimes more than others. :-)
Changes are like the weather: unpredictable.
But that is older software running on a newer JVM (i.e. the 5.2.1 that
sort
of, mostly ran under 1.4.1)
As far as I can tell, WebObjects 5.2.1 frameworks where running very
fine under Java 1.4.1.
, not newer software running on an older JVM, no?
Right. But I still don't get why WebObjects 5.2.2 couldn't be Java
1.3.1 compatible.
I dunno, they must have used something or it would run OK on 1.3!
Looks like it. Perhaps someone in the know would care to shade some
much needed light on which highly critical Java 1.4.1 feature(s)
WebObjects incorporates?
For me is it the extended support in the JCE, JASS, JNDI, etc. etc.
Oh, my... getting an headache just looking at that many acronyms at
once...
JCE (aka Java Cryptography Extension [1])? How does that fit in the
picture? Doing some highly sensitive work for some unnamed three letter
organization? Use a more solid library.
And is not JSSE (aka Java Secure Socket Extension [2]) more relevant in
this case?
What is (J)ASS? The Solaris Security Toolkit [3]?
JNDI (aka Java Naming and Directory Interface [4])? Would not something
like UDDI (aka Universal Description, Discovery and Integration [5]) be
more relevant?
As far as J2SE goes, migrating from java.net.URL to java.net.URI is one
of the very few compelling reason to create a Java 1.4 dependency.
As far as J2EE goes, Java Management Extensions (aka JMX [6]) could be
construed as another one. But this is nowhere to be seen as far as
WebObjects goes. Or am I missing something?
Some of that was available as add ons for 1.3.1, but not all of it,
and none of
the parts I wanted to use.
That's interesting, but this thread is about WebObjects 5.2.2
apparently creating frivolous dependencies with Java 1.4.1, not your
secret wishes and desires.
The extensions I mentioned above, to start with.
To be honest, I have a hard time to see how any of the above alphabet
soup fit in the WebObjects bouillabaisse.
Plus compatibility with
anything reasonably new in Java. I don't see any new tools or
libraries
being built for 1.3.1. Its over. I have seen a lot of things that I
wanted to use that required Java 1.4.1.
Ok. That you may not be able to run the latest pr0n client is somewhat
unfortunate, but what does it has to do with WebObjects?
I did not want to run an
unsupported WO configuration so I was forced to pass them by (or pay
through the nose for compatible commercial versions).
Hmmm... examples?
More is more (except
on some UNIXii where less is more, but that is another incredibly bad
play
on words masquerading as a command line tool).
Cheers,
PA.
[1] http://java.sun.com/products/jce/
[2] http://java.sun.com/products/jsse/
[3] http://wwws.sun.com/software/security/jass/
[4] http://java.sun.com/products/jndi/
[5] http://www-124.ibm.com/developerworks/oss/uddi4j/
[6] http://java.sun.com/products/JavaManagement/
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.