When I call oneway service with remote invoker and fault happens on server, there should be no fault propagated to the client. Now it is.
This is by design to allow consumers to deal with runtime faults. It was an enhancement added in 1.0 and is definitely not a bug. The only thing that can/should really change here is adding the ability to detect an application fault (via Exchange.sendFault()) and not return those. Today, all faults are passed back to the consumer in case they want to know the outcome of an exchange. That said, we can detect and restrict this behavior to only report runtime faults. Not a beta blocker.
Keith and I have discussed this and we have decided to close this as it is expected behaviour at present.