You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by "Sergei O. Naumov" <se...@mobicomk.ru> on 2002/02/05 19:53:55 UTC
Jetspeed 1.3a2 with JDK 1.4
Hi!
I just upgraded my JDK to 1.4 and found that Jetspeed crashes in this configuration. Can anyone,
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. :-)
Thanks much in advance,
Sergei
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed 1.3a2 with JDK 1.4
Posted by James Norman <jn...@taregon.com>.
I have had no luck with the JDK 1.4 either. Tomcat seems to run correctly
as well as my webapp built off the TDK. However Jetspeed throws many errors
at Servlet.init(). I tried removing xerces.jar, xalan.jar jaxp.jar, and
parser.jar and that caused many more errors.
----- Original Message -----
From: "Santiago Gala" <sg...@hisitech.com>
To: "Jetspeed Users List" <je...@jakarta.apache.org>
Sent: Friday, February 08, 2002 3:41 AM
Subject: Re: Jetspeed 1.3a2 with JDK 1.4
> 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:
<ma...@jakarta.apache.org>
> >For additional commands, e-mail:
<ma...@jakarta.apache.org>
> >
>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed 1.3a2 with JDK 1.4
Posted by Santiago Gala <sg...@hisitech.com>.
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: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>