Hello,

I just mailed the hsql people to ask if they could move their classes in the default
package to org.hsql to avoid collisions with Jive, however, we can't force them to
do so, I'll get back with the feedback on this.

Regards,
Karl Avedal

Matt Adam Tucker wrote:

> Jospeh,
>
> Thanks for the input. We'll probably just modify Jive since that's the
> fastest fix for our Orion users. :) It would be cool if the Orion people
> fixed the problem eventually, though.
>
> -Matt
>
> On Wed, 9 Aug 2000, Joseph B. Ottinger wrote:
>
> > Um, no. It's not a bug in orion.
> >
> > It's a classpath issue, and literally a problem with hsql.jar, as
> > stated. $ORION/lib jars get put in the classpath, and since Tree.class in
> > hsql is in the default package, it's exposed according to java's rules. If
> > you want to blame Java, fine. Go for it. If you want to blame hsql,
> > fine. Go for it. In either case, blame is deserved (well, mostly for hsql,
> > but hey.) Orion is doing nothing to the classpath to make it behave
> > oddly. The solution is to fix hsql.jar, really, not modify orion or jive.
> >
> > On Wed, 9 Aug 2000, Chris Miller wrote:
> >
> > > Thanks for the reply Jeroen.
> > >
> > > As far as I can see, this is actually a bug in Orion - it's exposing the
> > > classes in hsql.jar (and probably the other /lib jars?) to JSP pages when it
> > > shouldn't be. I don't think Jive needs fixing?
> > >
> > > As for the hSQL scripts, I'm sorry but I don't have any - I'm actually using
> > > SQL Server (but I have a script for that if you want it?). My solution to
> > > the problem I described was to simply remove the hsql.jar file from
> > > /orion/lib since I'm not using it.
> > >
> > > ----- Original Message -----
> > > From: "J.T. Wenting" <[EMAIL PROTECTED]>
> > > To: "Orion-Interest" <[EMAIL PROTECTED]>
> > > Cc: "Matt Adam Tucker" <[EMAIL PROTECTED]>
> > > Sent: Wednesday, August 09, 2000 3:38 PM
> > > Subject: RE: Jive
> > >
> > >
> > > > I'm working on building Jive. I'll look into it and forward your message
> > > to
> > > > the main maintainers. Jive probably does not see the class, but the JSP
> > > > engine does. Maybe that's what is causing problems.
> > > > Have you been able to create the Jive database on hSQL? If so, can you
> > > send
> > > > in the SQL scripts for it? We want to have broad support.
> > > >
> > > > Jeroen T. Wenting
> > > > [EMAIL PROTECTED]
> > > >
> > > > Murphy was wrong, things that can't go wrong will anyway
> > > >
> > > > > -----Original Message-----
> > > > > From: [EMAIL PROTECTED]
> > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Miller
> > > > > Sent: Wednesday, August 09, 2000 15:13
> > > > > To: Orion-Interest
> > > > > Cc: [EMAIL PROTECTED]
> > > > > Subject: Jive
> > > > >
> > > > >
> > > > > Has anyone here used Jive (www.coolservlets.com/jive) with Orion
> > > (1.1.37)?
> > > > > I've just tried to set it up, and hit a problem because the
> > > > > orion/lib/hsql.jar file contains a class called 'Tree'. Jive also has a
> > > > > class called this, and when I try to use it in a JSP page, Orion finds
> > > > > Hypersonic's Tree class first.
> > > > >
> > > > > So the question is, should this Hypersonic class be visible to my
> > > > > JSP page?
> > > > > I would have thought not unless I explicitly used <%@ page import ... %>
> > > > >
> > > > > Has anyone else seen this problem?
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> > -----------------------------------------------------------
> > Joseph B. Ottinger               [EMAIL PROTECTED]
> > http://cupid.suninternet.com/~joeo      HOMES.COM Developer
> >


Reply via email to