db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Vester" <jimves...@gmail.com>
Subject Re: Running Code Analyzer
Date Thu, 20 Apr 2006 23:37:40 GMT
FYI,

we recently found an open source  tool called findbugs. It uses BCEL to
perform Byte code analysis.  You may want to run it against the code base.
It is quite good at identifying run time errors and or null pointers etc.

I haven't tried it against ddlutils.

http://findbugs.sourceforge.net/

On 4/20/06, Tom Schindl <tomatlinux@gmx.at> wrote:
>
> Tom Schindl wrote:
> > Tom Schindl wrote:
> >
> >>Sometimes code is better so here's a junit-Test to see what I mean.
> >>
> >>Another problem is that I can not run the unit-test directly from within
> >>eclipse because the DTD can not be resolved appropriately the
> >>LocalEntityResolver.resolveEntity() is never called.
> >>
> >>-------------------8<-------------------
> >>SCHWERWIEGEND: Parse Error at line 1 column 23: Document root element
> >>"database", must match DOCTYPE root "null".
> >>org.xml.sax.SAXParseException: Document root element "database", must
> >>match DOCTYPE root "null".
> >>      at
> >>
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException
> (Unknown
> >>Source)
> >>      at
> >>com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error
> (Unknown
> >>Source)
> >>-------------------8<-------------------
> >>
> >
> >
> > Well that's really interesting if you don't have a <!DOCTYPE>
> > declaration in the source document but set the validation to true the
> > entity resolver doesn't get called and you'll get a parsing exception.
> > All test cases I've looked at don't have a <!DOCTYPE> in them and so the
> > test are failing.
> >
> Sorry they are not failing but you'll only get SAXExceptions all other
> but parsing is not stopped because them.
>
> Tom
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message