[ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=comments#action_1237... ] Chris Laprun commented on JBPORTAL-1712: ---------------------------------------- and avoid java.io.NotSerializableException: org.jboss.ws.core.soap.DetailImpl problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=comments#action_1238... ] Thomas Heute commented on JBPORTAL-1712: ---------------------------------------- Can we set that with a higher priority ? At the moment in the 2.6 testsuite, the 2 tests which are failing are related to this issue. For that reason, we are getting used to ignore Hudson error reports which is not good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=all ] Chris Laprun resolved JBPORTAL-1712. ------------------------------------ Resolution: Rejected Actually, the tests are going through the WS stack as it is and I managed to fix them (by not using the unmarshalled exceptions but directly RemoteException and checking the error code) though I am not quite sure how changing code on the client has an impact on the test result... I suspect it has to do with JBoss WS somewhat flaky support for SOAPFaultException... I guess I will need to investigate this more. Closing this task. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira