Sergei O. Naumov wrote: >Hi! >I just upgraded my JDK to 1.4 and found that Jetspeed crashes in this configuration. >Can anyone, > java + crash = Virtual Machine problem. This is a hard rule. We are suposed to be unable to crash the javaVM no matter what we do. So, check that your jdk installation is sane, and check for pending bugs on jdk.
On the other side, I tried running it with jdk1.4beta in linux, and I was unable to get everything running (I was trying tomcat 4.0x at the same time. I never learn, no matter my age.) I have seen some hard to debug problems related with jdk1.4beta, as JAXP and TRAX are inside it, and the version inside clashes with ours. The problems are related with Xerces and Xalan. > >please, tell whether this is a vialble configuration or not? I see that 1.4's >performance is >way better than 1.3, so it seems more attractive. :-) > It should be viable soon. If you want to give it a try, try: - remove completely xerces.jar, xalan.jar jaxp.jar, parser.jar from the tomcat installation and jetspeed war. - if it works (maybe partially) great. - If not, we will have to find a way for having a consistent set of JAXP parser and TRAX transformer loaded, via configuration. Most, if not all, direct dependencies from xerces and xalan are currently removed from jetspeed. We still have some SAX1 calls, deprecated in SAX2, including Castor generated code. But SAX1 calls will not break any time soon. I stopped trying because I thought other people would clarify the way to go (update xerces/xalan, special builds without javax.jaxp and javax.trax packages,...) so my effort was somehow redundant. If you really want it to happen, give it a try. > >Thanks much in advance, > > Sergei > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
