John,
The NPE occurs in an assertion check. This is part of the validation logic. See the JIRA comments.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
| John Kaputin/UK/[EMAIL PROTECTED]
11/10/2006 08:51 AM |
|
Arthur,
when I run MessageTest-1G via ANT I see a NPE reported in the console but no stack trace info. I notice in WODEN-69 that you pasted in a stack trace for the original NPE. Was that output from running the ANT test harness or did you create that with a stand alone test client? Can I produce more verbose output when running via ANT?
The CM result file for MessageTest-1G does contain some data. So it looks like the parse worked, the reader returned a DescriptionElement, but then another NPE occurred when using the Component API to get the contents of the model into the CM interchange format. Looking at the output in the attached file it seems to have occurred after getting a SOAPBindingOperationExtension.
John Kaputin
SOAPservice.wsdlcm
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
