Is the XUpdate the only thing that doesn't work?   I had a lot
of problems getting my first XUpdate to work.   If everything
else works, then let's take this to the users list.

Mark

[EMAIL PROTECTED] wrote:

> I agree.  A move to compatibility with 1.4 shouldn't isolate any of the
> Xindice users/committers, therefore a readme/faq should be created for
> users with 1.4.  I would gladly create that document, if I were able to get
> it to work ;).  I have quite a bit of knowlege of ejb architectures, but no
> intimate knowlege of CORBA.
>
> Kevin Ross
> www.bredex.com
>
>
>                     "Mark J. Stang"
>                     <[EMAIL PROTECTED]       To:     [EMAIL PROTECTED]
>                     hlink.net>            cc:
>                                           Subject:     Re: CORBA/XUpdate and 
> JDK1.4     [was XUpdate Example:
>                     06/10/2002             
> org.apache.xindice.client.corba.db.APIException]
>                     09:17 AM
>                     Please respond
>                     to xindice-dev
>
>
>
> Kevin,
> Normally, I would think we would want to be compatible with
> the latest version.   However, that might require forking the
> code.   That will require a great deal more work than one
> source tree.   The issue that I see is that I need to be able to
> run Xindice on Mac OS X and the Mac is only at 1.3.*.
> Also, several of the developers on this list only have Mac
> OS X and they wouldn't be able to contribute.
>
> >From what I have seen from monitoring the list since
> 1.4 came out, the problems are conflicts between the
> the jars that come with 1.4 and the ones that Xindice
> needs.   So, we don't necessarily need to move to
> 1.4, we just need an install procedure/FAQ that
> describes how.
>
> If the list does decide to move to 1.4, then we need a
> full and last 1.3 release for the rest of us, that will
> hold us over until Apple releases 1.4.
>
> IMHO,
> Mark
>
> [EMAIL PROTECTED] wrote:
>
> > Who is the maintainer of the CORBA interface?  The stack trace I receive
> > really gives me no indication of the real issue.  I'm believe there is a
> > conflict with JDK1.4, but where? Client? Server?  On both platforms I am
> > using the standards override mechanism, but still receive this error when
> > performing an xupdate.  There is no stack trace or error message on the
> > server side.
> >
> > Would the CORBA maintainer be able to recreate this problem with JDK 1.4,
> > then provide a patch, or detailed instructions about how to get around
> > this?
> >
> > There are many posts on the list regarding jdk 1.4 and Xindice, but there
> > doesn't seem to be a solid answer, just some voodoo black magic fixes
> that
> > (may) work.
> >
> > What is the source of the problem?
> >
> > Isn't this a good candidate for the FAQ?
> >
> > Even though 1.4 is not recommended, isn't it time that Xindice starts
> > moving in the direction of 1.4 compatibility?
> >
> > Thanks!
> >
> > Kevin Ross
> > www.bredex.com
> >
> >
> >                     "Mark J. Stang"
> >                     <[EMAIL PROTECTED]       To:
> [EMAIL PROTECTED]
> >                     hlink.net>            cc:
> >                                           Subject:     Re: XUpdate
> Example: org.apache.xindice.client.corba.db.APIException
> >                     06/04/2002
> >                     11:52 PM
> >                     Please respond
> >                     to xindice-dev
> >
> >
> >
> > Which version of java are you running?   Do you have any jars
> > left over from previous installs?
> >
> > Mark
> >
> > Kevin Ross wrote:
> >      Hello all,
> >
> >      I wrote a few components about 4 months back that worked fine.I had
> to
> >      leave off that project, but I'm glad to say that I'm back to working
> >      with Xindice.
> >
> >      After several hours of reacclimating myself and encountering
> problems
> >      with XUpdate, I decided to scrap getting my code to work, in favor
> of
> >      the examples.Specifically, org.apache.xindice.examples.XUpdate
> (after
> >      adding at least one document).The example yields the same exact
> error
> >      that I received while trying my existing code.Can anyone shed some
> >      light on this?
> >
> >      org.apache.xindice.client.corba.db.APIException:
> >      IDL:org/apache/xindice/client/corba/db/APIException:1.0
> >
> >
> atorg.apache.xindice.client.corba.db.APIExceptionHelper.read(APIExceptionHelper.java:112)
>
> >
> >      at org.apache.xindice.client.corba.db.
> _CollectionStub.queryCollection
> >      (_CollectionStub.java:669)
> >
> >      at
> >
> org.apache.xindice.client.xmldb.services.XUpdateQueryServiceImpl.updateResult(XUpdateQueryServiceImpl.java:171)
>
> >
> >      at
> >
> org.apache.xindice.client.xmldb.services.XUpdateQueryServiceImpl.update(XUpdateQueryServiceImpl.java:192)
>
> >
> >      atorg.apache.xindice.examples.XUpdate.main(XUpdate.java:88)
> >
> >      XML:DB Exception occured 1 Query Processing Error
> >
> >      Also, am I missing something, or is there just no logging in the
> >      client or server sides?I've got no problem discovering these issues
> >      for myself, but the lack of logging is quite discouraging for
> someone
> >      new to the codebase?
> >
> >      Thanks in advance,
> >
> >      Kevin Ross
> >
> > --
> > Mark J Stang
> > Architect
> > Cybershop Systems
> >   (See attached file: markstang.vcf)
>
> --
> Mark J Stang
> Architect
> Cybershop Systems
>
> (See attached file: markstang.vcf)

--
Mark J Stang
Architect
Cybershop Systems

begin:vcard 
n:Stang;Mark
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
fn:Mark Stang
end:vcard

Reply via email to