Re: [OJB-developers] weekly status update

[David F. <dw...@la...>]

At 12:20 AM 1/1/1997 +0100, Thomas Mahler wrote:
>Hi all,
>
>here is the second edition of the weekly OJB status update.
>See the attached html file to see the status of your bug and feature
>requests.
>
>In the last week I used the JDK 1.3 dynamic Proxy concept to build an
>improvement of the OJB virtual proxy concept. Now you don't have to
>implement the proxy classes yourself, but can declare the usage of
>dynamic proxies in the the XML repository.
>
>This works great and avoids a lot of non-productive work from for
>app-developers using OJB.
>
>There is only one problem: this feature requires JDK 1.3 or later.
>
>I see 2 option to deal with this situation:
>1. just say OJB needs JDK 1.3 or later. Period.
>2. try to support a JDK 1.2 compliant version without this feature.
>
>Of course 1.) will save me a lot of work. But maybe some of you still
>rely on JDK 1.2 in certain production environments ? Please tell me if
>you need OJB running under JDK 1.2.
>
>The easiest way to provide a JDK 1.2 compliant version would be to use
>compiler switches in the code. Unfortunately Java does not have a
>preprocessor.
>What is the best solution in Java to provide this kind of preprocessing?
>Can we use ANT for this  work? Any hints are most welcome.

We could live with the JDK1.3 requirement, since we have other reasons
to require this already.   However, I think you can do conditional compiles
on classes with Ant by checking to see if certain classes exist.  That is
how we handle optional module support in OpenEMed now.  For example,
if the right POET classes don't exist, we don't compile POET support.
This is totally transparent.  You need to be careful how you handle 
constructors in
in this approach, but it is quite workable.

Dave

>regards,
>
>--Thomas