[BATIK-400] Loaded document Vs created document

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 1.5
• Component/s: CSS
• Environment: Operating System: All; Platform: All
• Assignee: Batik Developer's Mailing list
• Reporter: Tonny
• Created: 28/Jul/03 01:08
• Updated: 16/Nov/04 19:05
• Resolved: 16/Nov/04 19:05

Description

The behaviour between loaded document and created document on the fly is
different due to documentURI/CSSBase.
On the loaded document the documentURI/CSSBase is pointing to the correct URL,
where in the created document the documentURI/CSSBase is null. Therefore, on the
created document some operation sometimes throw NullPointerException.
Some possible fix is by checking for null or put under try catch block for null.
Unfortunately, there are many part of CSS related stuff assuming that the
documentURI/CSSBase is exist and do the operation directly without checking
whether it is throw NullPointerException or not, make bug fixes hard to spot

Here is some sample of method that identified throw NullPointerException:
1) On package org.apache.batik.css.engine
Class CSSEngine
method getCSSBaseURI() // instead of return null, it throw NullPointerException
because the element.getCSSBase could be null also
method parseStyleDeclaration(String) // instead of throw DOMException, it throw
NullPointerException if documentURI is null

2) On package org.apache.batik.css.engine.value.svg
Class SVGPaintManager
method createValue(LexicalUnit lu, CSSEngine engine) // instead of throw
DOMException, it throw NullPointerException due to resolveURI throw
NullPointerException instead of return null