New IF for MU headers (was: MustUnderstand faults)

[Toshiyuki Kimura <to...@apache.org>]

Hi Chris, and All of folks,

  Now, I'd like to propose the following two interfaces to accord with
the past discussion.  The key words are, "sync problem (config-file vs.
APIs)", "limitation for extent of the impact as API changes", and "Axis
handler vs. JAX-RPC handler".

The MUhandler is a marker interface which indicates;
  - An implementation of this IF has capability to process MU headers.
  - MU headers, which are expected by the runtime, are for it.
  - All of other MU headers are for this user-implemented class.

The extendedMUhandler is a subinterface of MUhandler which indicates;
  - An implementation of this IF has capability to process MU headers.
  - A list of processable MU headers will be returned by a method,
    getActivatedMUheaders().
  - A list of delegated MU headers to runtime will be returned by a
    mothod, getDelegatedMUheaders().
  - The handleMUheaders(MessageContext context) will be invoked before
    any business logics in the user implementation, and it'll return
    a boolean value to indicate whether the process is success or not.

.........*.........*.........*.........*.........*.........*.........*
public interface MUhandler {
}

public interface extendedMUhandler extends MUhandler{
{
  // preprocessing of MU headers before starting any business logics
  public abstract boolean handleMUheaders(MessageContext context);

  // return a HashMap which contains processable MU headers
  public abstract HashMap getActivatedMUheaders();

  // return a HashMap which contains delegated MU headers to runtime
  public abstract HashMap getDelegatedMUheaders();
}
.........*.........*.........*.........*.........*.........*.........*

Any other ideas, or comments ?

-- 
Toshi <to...@apache.org>