Thanks guys! -- I'll enjoy not maintaining my own branch!

James


At 5/31/2001 04:43 PM -0700, you wrote:


>On Thu, 31 May 2001, Scott Sanders wrote:
>
> > This seems reasonable.  I will add it.
> >
> > Thanks,
> > Scott Sanders
> >
>
>+1
>
>Craig
>
>
> > > Hi,
> > >
> > > I figured out my problem getting the digester to work in WL6.0:
> > >
> > > Apparently Weblogic is brain-dead when it comes to supporting JAXP1.1
> > > (they have everything built in as JAXP1.0).  So when the Digester asks
> > > the SAXParserFactory for a parser, it gets back a JAXP1.0 parser and it
> > > doesn't like that very much. (yes, regardless of which parser package I
> > > put in front of the classpath, and regardless of which java environment
> > > variables I set trying to force it to use a different parser).
> > >
> > > You can however instantiate a JAXP1.1 parser in the WL6.0 environment
> > > if you do it manually (without the factory) so my solution was to add
> > > the following constructor to the Digester.
> > >
> > >      /**
> > >       * Construct a new Digester with default properties and given
> > >       SAXParser. */
> > >      public Digester(SAXParser saxParser) {
> > >
> > >          super();
> > >
> > >          this.parser = saxParser;
> > >      }
> > >
> > > Please consider the addition of this constructor - as anyone working in
> > > WL6.0 (or any other environment with JAXP1.0 only) will have my same
> > > difficulties... and I'd rather not maintain my own copy of the
> > > Digester! difficulties... and I'd rather not maintain my own copy of
> > > the Digester!
> > > Thanks,
> > > James
> > >
> > >
> > > At 5/29/2001 01:26 PM -0600, I wrote:
> > >
> > >>Hi,
> > >>
> > >>Has anyone been able to get the digester working within the Weblogic
> > >>6.0  environment?
> > >>-- if so, can you please share your setup information?
> > >>(classpath, and XML registry settings)
> > >>
> > >>Thanks,
> > >>James
> >
> >

Reply via email to