Yes it's important that XFire is WS-I compliant. Otherwise you had a bad position if you have to communicate with commercial tools like EAI provider as consumer for your services and they have problems reading your request or wsdl.
-----Ursprüngliche Nachricht----- Von: Andreas Schildbach (JIRA) [mailto:[EMAIL PROTECTED] Gesendet: Montag, 20. März 2006 09:44 An: [email protected] Betreff: [xfire-dev] [jira] Commented: (XFIRE-305) provide more meaningful exception messages [ http://jira.codehaus.org/browse/XFIRE-305?page=comments#action_61514 ] Andreas Schildbach commented on XFIRE-305: ------------------------------------------ Is it important (for XFire) that the WSDL is WS-I compliant? I take it WS-I compliance is just optional (but recommended) and WSDL files only need to be SOAP compliant. > provide more meaningful exception messages > ------------------------------------------ > > Key: XFIRE-305 > URL: http://jira.codehaus.org/browse/XFIRE-305 > Project: XFire > Type: Bug > Versions: 1.0 > Reporter: Andreas Schildbach > Assignee: Dan Diephouse > Attachments: checkAddress.wsdl > > > In a current project with client stubs generated from a WSDL, I get the exception below when actually invoking a service method on the service proxy. It is very much possible that I do not feed the correct values, however the exception gives no clue what is wrong. I propose to give descriptive error messages whereever possible. Exceptions like "Fault" or "NullPointerException" are just the programmers equivalent to the famous "An unknown error occured [ok] [cancel]". > Anyway, here is the exception: (comments on the concrete case are also > very welcome :-) > org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. > Nested exception is org.codehaus.xfire.fault.XFireFault: Fault > org.codehaus.xfire.fault.XFireFault: Fault > at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89) > at org.codehaus.xfire.client.Client.invoke(Client.java:267) > at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77) > at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57) > at $Proxy13.checkAddress(Unknown Source) > at com.o2.portal.services.soap.endpoint.connector.xfire.CheckAddressConnector.c heckAddress(CheckAddressConnector.java:105) > at com.o2.portal.services.soap.endpoint.connector.axis.CheckAddressConnectorTes t.testCheckAddress(CheckAddressConnectorTest.java:58) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRu nner.java:478) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner. java:344) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTest > Runner.java:196) Caused by: java.lang.NullPointerException > at org.codehaus.xfire.service.binding.AbstractBinding.writeParameter(AbstractBi nding.java:217) > at org.codehaus.xfire.service.binding.ServiceInvocationHandler.writeHeaders(Ser viceInvocationHandler.java:227) > at org.codehaus.xfire.client.Client.invoke(Client.java:261) > ... 20 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
