Think I found it.  Line 199, AbstractResponseElement, was calling
writeEmptyElement, which I'm guessing is "ended" by default.  Replaced
with writeElement, then it no longer crashes.

I noticed that part of the output is url encoded, which makes it
difficult to read.  not going to track that down just yet, thought I'd
mention it though.

However, this doesn't address the null logger, which I'm afraid is over
my head right now.  In my local copy, I'm just going to leave it as a
System.out.println call.

Thanks
gene

Gene McCullough wrote:
> something was definitely out of sync.  refreshed from dev CVS, rebuilt,
> same result, only:
> java.lang.NullPointerException
>         at
> org.keel.services.model.defaultmodel.AbstractResponseElement.toString(AbstractResponseElement.java:184)
>         at
> org.keel.services.model.defaultmodel.DefaultModelResponse.toString(DefaultModelResponse.java:523)
>
>
> in my trial and error so far, it comes down to a null logger throwing
> the npe.  Behind that, something seems to be calling endEntity too many
> times that is causing the initial exception.
>
> still investigating.
>
> Thanks
> gene
>
> Raoul Pierre wrote:
>
>>Gene,
>>
>>
>>>
>>>
>>>
>>>>I get a Null pointer exception invariably now when I output the response
>>>>as a String.
>>>>
>>>>java.lang.NullPointerException
>>>>       at
>>>>org.keel.services.model.defaultmodel.AbstractResponseElement.toString(AbstractResponseElement.java:184)
>>>>
>>>>       at
>>>>org.keel.services.model.defaultmodel.DefaultModelResponse.toString(DefaultModelResponse.java:492)
>>>>
>>>>  
>>
>>The line number above is strange. I just cheked out
>>svc-model-defaultmodel from cvs and line 492 is not inside
>>DefaultModelResponse.toString(). Can you check your version.
>>
>>
>>>I'm not getting any logging from AbstractResponseElement, and when I
>>>replaced the this.log.error() entry with a System.out.println, the null
>>>pointer went away.  (from the catch block in toString)
>>>
>>>Is this related to the logging problem you had Pierre?  I am having
>>>problems with the xmlwriter, but they were why the catch block was then
>>>throwing the npe.  I'll track down my xmlwriter issues.  it looks like
>>>its having problems with my outputs.
>>>
>>>
>>
>>I'm out for 3 hours.
>>
>>Pierre
>>
>>
>>http://keelframework.org/documentation.shtml
>>Keelgroup mailing list
>>Keelgroup@list...
>>http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>>
>
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> Keelgroup@list...
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>
http://keelframework.org/documentation.shtml
Keelgroup mailing list
Keelgroup@list...
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com