Re: What happend to the Exoffice XA package?

Barry,

My main point with my post was to clarify that there are no outstanding
legal issues with the Exoffice contribution. I am not very familiar with
legal issues (let alone copyright or licensing issues) and I was afraid that
the package was removed for such reasons. (Some of you on this list may
remember that not long ago a widely publicized open source application
server project was closed because of obscure legal issues.)

Also, if support for this kind of functionality (transaction support -- even
if it is limited to isolated ("local") transactions) is discontinued as part
of PostgreSQL, for purely efficiency reasons I would have to consider to
integrate this package into my own package structure, which leads me back to
the tricky domain of legal concerns.

> 1)  The code is incomplete and doesn't support many aspects
> of the jdbc2
> extentions that one might expect.  Thus posting a

Where do you see incompleteness in the code? Does this incompleteness
relates to functionality relevant to PostgreSQL?

I think that a quick look at the package structure of the xa classes (there
is actually no structure, just one package) makes it obvious what they're
for (which aspects of the jdbc2 extensions they're cover). The only
extension these classes do not support seem to be RowSets. Since this
package does not contain a class named 'RowSet' (or even close to it), one
would instantly see (however novice she may be and even if she did not read
the pertaining section of the accompanying readme file [to be written :-)])
that this feature is not supported.

Also, I am not sure, if there should be a separate jdbc7.1-1.2ee.jar file.
This package implements optional/extended features which do not (should not)
conflict with the basic jdbc2 functionality. There could be one single
jdbc7.1-1.2.jar file with extensions, and if someone wants to use an
extensions uses it.

I suggest that we close this thread and continue the discussion on the
closely related "[JDBC] Submittal for JDBC Pooling driver (For 7.3)" thread,
since there's no point to maintain two separate threads on the same issue.

> Now having said all of that, I would be very interested in
> understanding
> how/why you use the functionality provided by these xa classes.

Please, refer to the thread "[JDBC] Submittal for JDBC Pooling driver (For
7.3)" on this same list.

Thank you.

Peter


> -----Original Message-----
> From: Barry Lind [mailto:barry@xythos.com]
> Sent: Wednesday, January 02, 2002 6:45 PM
> To: Kovács Péter
> Cc: pgsql-jdbc@postgresql.org
> Subject: Re: What happend to the Exoffice XA package?
>
>
> The code is still in CVS and can be built if you want.  It just isn't
> included in the prebuilt jars on the website for the
> following reasons:
>
> 1)  The code is incomplete and doesn't support many aspects
> of the jdbc2
> extentions that one might expect.  Thus posting a
> jdbc7.1-1.2ee.jar file
> is misleading.
>
> 2)  It gets very confusing to the novice user when they have
> the option
> to get a jdbc7.1-1.1.jar, jdbc7.1-1.2.jar and jdbc7.1-1.2ee.jar file.
> Which one should I get?  (Having two is already bad enough,
> and when we
> start supporting jdbc3 in the jdk1.4 we will be stuck supporing three)
>
> 3)  There has been little demand for prebuilt versions of this
> particular functionality.  You are the first person that has
> asked about
> it in over three months.
>
> Now having said all of that, I would be very interested in
> understanding
> how/why you use the functionality provided by these xa classes.
>
>
> thanks,
> --Barry
>
>
>
>
> Kovács Péter wrote:
>
> > Hi,
> >
> > The jdbc7.1-1.2.jar package which I downloaded a few weeks ago from
> > jdbc.postgresql.org, does not contain the XA package from
> Exoffice? Was this
> > package intentionally left out from this build. Are there
> (licencing???)
> > problems with this package? The package still appears under
> the CVS source
> > tree, and it works excellently for me (except for  a small
> and easy to
> > repair problem which I would eventually like to discuss).
> (Please, also see
> > my reply to "[JDBC] Submittal for JDBC Pooling driver (For 7.3)".)
> >
> > Thank you
> >
> > Peter
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister command
> >     (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
> >
> >
>
>