Bernd Fondermann wrote:
>
> Steve Brewin wrote:
> > Serge Knystautas wrote:
> >
> > <<snipped>>
> >
> >>>On the InetAddress side, I see that dnsjava is an SPI for
> >>
> >>dns lookups.
> >>
> >>>Adding "sun.net.spi.nameservice.provider.1=dns,dnsjava" we
> >>
> >>would make
> >>
> >>>all the dns calls to use dnsjava the way we configured it.
> >>>
> >>>Should we use the spi approach or try to propagate the
> >>>DNSServer.staticMethods usage we currenlty use sometimes??
> >>
> >>I thought we had already gone the spi approach, or at least had
> >>considered it at one point.  I thought there was some issue with
> >>different results, but I don't remember any specifics.
> >
> >
> > It isn't clear from a quick search of
> http://www.dnsjava.org, but I believe
> > that the spi capability was added in v2. We first switched
> when it was at
> > v1.
> >
> > Shame really, as we now have explicit dependencies on the
> dnsjava packages
> > and have added some workarounds in parts to accomodate the
> specifics of
> > dnsjava's behaviour. It would be good to revert to the SPI
> approach for V3,
>
> The pure SPI approach would mean to base the usage of dnsjava
> on a Sun
> specific property. Direct usage of dnsjava sounds more
> reliable to me as
> long as James runs on other vendor's JVMs. They may or may
> not support
> "sun.net.spi...".

Googling 'sun.net.spi +IBM' and 'sun.net.spi +IBM +Linux' finds hits
revealing that this was indeed a problem, but is fixed. This may or may not
be the case with other vendors VMs. However, I think this covers most of the
potential deployments.

It does raise an interesting question. I know its early days in our
evolution to a fully testable codebase, but should we consider incorporating
tests on a selected range of VMs? What we have here is an example of the
true Java mantra, "write once, test everywhere".

Alternatively, perhaps we could add pages to the Wiki in which people could
record the environments in which they have successfully run each release of
James.

-- Steve


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to