Jacek, If you were using M6, then you wouldn't have seen line numbers in the stack trace. We've fixed that, so M7 will tell you file:line number info.
Regards, Jeremy On 07/02/07, Arthur Ryman <[EMAIL PROTECTED]> wrote:
Jacek, Thanks for reporting this problem. Apache-speak for bugs reporting is issue-tracking and we use Jira in Woden. [1] Please enter this report in Jira. You may need to register first. I also suggest you contribute this test case to the W3C test suite. We have one from Sparql and it exposed a lot of problems. [1] http://issues.apache.org/jira/browse/Woden 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] Jacek Kopecky <[EMAIL PROTECTED]> 02/06/2007 01:29 PM To Arthur Ryman/Toronto/[EMAIL PROTECTED] cc Subject woden bug report Dear Arthur, I downloaded Woden to validate some WSDL files and I uncovered what seems to be a bug. I failed to find a way to submit that bug on the Woden pages, so here goes. 8-) When I parse [1] with org.apache.woden.ant.WsdlCm, it dies on null pointer exception somewhere in one of the write() methods (it doesn't tell me the line). I added the appropriate message label on the wsdl:outfault element and it doesn't do the exception. Therefore I indirectly diagnose that the parser doesn't fill in the outfault message label when it's not present and returns null to the WsdlCm writer. http://www.w3.org/2002/ws/sawsdl/CR/wsdl2.0/04-fault-annotation.wsdl Best regards, Jacek
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
