Pierre,
Something was out of sync again, because the NPE is gone now, even
without the logkit.properties entry.
However, after updating with latest from CVS, I get the exception that
endEntity was called too many times.
DEBUG 2005-09-30 12:33:12.012
[svc-model-defaultmodel](org.keel.util.i18n.Translator.toString(Translator.java:231):)
Message key
"defaultmodel.response.xmlwriter.unable.create.string" not found
ERROR 2005-09-30 12:33:12.012
[svc-model-defaultmodel](org.keel.services.model.defaultmodel.DefaultModelResponse.toString(DefaultModelResponse.java:585):)
???defaultmodel.response.xmlwriter.unable.create.string???
java.io.IOException: Called endEntity too many times.
at
com.generationjava.io.xml.SimpleXmlWriter.endEntity(SimpleXmlWriter.java:184)
at
com.generationjava.io.xml.DelegatingXmlWriter.endEntity(DelegatingXmlWriter.java:121)
at
com.generationjava.io.xml.PrettyPrinterXmlWriter.endEntity(PrettyPrinterXmlWriter.java:142)
at
org.keel.services.model.defaultmodel.DefaultModelResponse.toString(DefaultModelResponse.java:537)
But, with the logging npe gone, my code no longer crashes.
Thanks,
gene
Raoul Pierre wrote:
> Gene,
>
>> 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)
>>
>>
>>
> May I ask you to use debug level with svc-model-defaultmodel. With the
> last CVS version (*), it's possible to put in logkit.properties:
>
> svc.model.defaultmodel.logkit.level=DEBUG
>
> Pierre
>
> PS (*): commited 4 days ago, as the 2d patch about the log trouble with
> Translator.
>
>
>
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
opensubscriber is not affiliated with the authors of this message nor responsible for its content.