+1
Axis 1.X's AxisFault does have the capability to add and access headers
as you request below. You might want to crib whatever you can from there.
We might explore the utility of a WS-Addressing-specific fault subclass
which gives a nice API on top of the header-related stuff.
--G
Sanjiva Weerawarana wrote:
Most definitely +1 .. go for it!
Sanjiva.
On Wed, 2005-10-26 at 12:01 +0100, Steve Loughran wrote:
I am looking at the current axis fault stuff. Is anybody actively
working on this, or am I free to add enhancements?
Specifically:
1. All the bits of a SOAPFAult, including random XML
2. Axis1 features: stack trace extractions, hostname, http error codes.
3. Tweak how we map from a java fault to a SOAPFault. If a fault says
that it can provide a fault message then we ask it for it directly. This
lets people's classes (like my BaseFault) generate my own fault with no
intervention.
WS-A says that addressing faults are handled differently, with most of
the stuff in special headers, rather than just the body. How does Axis2
handle that in both generation and receipt? Maybe an AxisFault should
have a header section where you can add new header elements for both
outbound and inbound calls.
-steve
