fate I can gve you another example!
fate (on client): Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
fate at $Proxy0.initialize(Unknown Source)
dan but if they don't have control of the server, how would the stack trace help the client?
fate at Test.main(Test.java:22)
fate then: Caused by: java.lang.InstantiationException: com.opensymphony.workflow.InvalidRoleException
fate Caused by: org.codehaus.xfire.fault.XFireFault: Couldn't instantiate service.
fate at org.codehaus.xfire.aegis.type.basic.BeanType.readObject(BeanType.java:99)
fate at org.codehaus.xfire.aegis.AegisBindingProvider.readParameter(AegisBindingProvider.java:131)
fate at java.lang.Class.newInstance0(Class.java:293)
fate on the server, on the other hand, we have:
fate WARNING: Error invoking service.
fate com.opensymphony.workflow.InvalidRoleException: You are restricted from initializing this workflow
fate at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:605)
fate at com.opensymphony.workflow.soap.BasicSOAPWorkflow.initialize(BasicSOAPWorkflow.java:105)
fate oh losing trace is fine, I'm bitching about losing the message
dan ok, that trace is a bad one
dan InvalidRoleException needs a default constructor
fate also, the undeclared exception is wrong, since InvalidRoleException is a subclass of WorkflowException
fate which is declared
dan or BeanType needs to be fixed
dan good point