Hi!
On Sun, Aug 16, 2009 at 08:35, Niklas Gustavsson wrote:
> On Sun, Aug 16, 2009 at 8:31 AM, Niklas Gustavsson
> wrote:
>>> Why is it better to return a null? If a XML element has no namespace
>>> declared, it lies in the "empty" namespace, so a empty string would
>>> conform to the standard.
>
On Sun, Aug 16, 2009 at 8:31 AM, Niklas Gustavsson wrote:
>> Why is it better to return a null? If a XML element has no namespace
>> declared, it lies in the "empty" namespace, so a empty string would
>> conform to the standard.
>
> Right, please revert the change.
I fixed it right away.
/niklas
On Sat, Aug 15, 2009 at 8:00 PM, Michael Jakl wrote:
> Since the change of rev802821 (null instead of empty string for
> namespaces) I'm getting NullPointer Exceptions for my testcases
> (coming from Render.java), they are not specific to my code (as far as
> I can see) but don't come up with the t
Hi!
Since the change of rev802821 (null instead of empty string for
namespaces) I'm getting NullPointer Exceptions for my testcases
(coming from Render.java), they are not specific to my code (as far as
I can see) but don't come up with the test-cases of vysper-core.
Why is it better to return a
