Stephen McConnell wrote: > > I think you need something like two alternative implementation classes - > for example, the current DefaultConfigurationBuilder (for compatibility) > and a new JAXPConfigurationBuilder. The JAXPConfigurationBuilder > compilation could be excluded with a few lines in the ant build file if > the javax.xml classes are unavailable. At runtime we can test the vm > version (or available classes) in order to select the actual builder > class to use. It will always test TRUE. The reason is that Avalon is build with Xerces which have the JAXP parsers available.
- JDK 1.4beta and DefaultConfigurationBuilder Stephen McConnell
- Re: JDK 1.4beta and DefaultConfigurationBuilder Peter Donald
- Re: JDK 1.4beta and DefaultConfigurationBuilder Berin Loritsch
- Re: JDK 1.4beta and DefaultConfigurationBuilder Peter Donald
- Re: JDK 1.4beta and DefaultConfigurationBuilder Berin Loritsch
- Re: JDK 1.4beta and DefaultConfigurationBuilder Peter Donald
- RE: JDK 1.4beta and DefaultConfigurationBuilder Stephen McConnell
- Re: JDK 1.4beta and DefaultConfigurationBuilder Berin Loritsch
- RE: JDK 1.4beta and DefaultConfigurationBuilder Berin Loritsch
- RE: JDK 1.4beta and DefaultConfigurationBuilder Stephen McConnell
- RE: JDK 1.4beta and DefaultConfigurationBuilder Stephen McConnell
S/MIME Cryptographic Signature