Hi ,
Could you please answer a few questions about lifecycle and runtime contexts?
You have addressed the issue of service lifecycle by providing
init(ServiceContext) and destroy(ServiceContext) callbacks that are called
during service initialization and service destruction, respectively. Now as I
understand it you also have a setOperationContext(OperationContext) callback
that is called on every service invocation to provide an operation context.
>From the operation context, I can get the message context in one of two way it
>seems:
Map map = operationContext.getMessageContexts();
In this case, I'm not sure what to do with multiple message contexts. Can you
explain the need for a map?
MessageContext context = operationContext.getMessageContext(String);
In this case, I'm not sure what input String is designating. Can you explain?
If there is documentation, please direct me to it. I could not gather enough
information from your javadoc.
The reason that I need the message context in the first place is so that I can
create a detailed SOAP fault if an exception occurs:
messageContext.setProperty(SOAP12Constants.SOAP_FAULT_CODE_LOCAL_NAME,
soapFaultCode);
messageContext.setProperty(SOAP12Constants.SOAP_FAULT_REASON_LOCAL_NAME,
soapFaultReason);
messageContext.setProperty(SOAP12Constants.SOAP_FAULT_DETAIL_LOCAL_NAME,
soapFaultDetail);
Maybe there is a better way to create custom, detailed faults now so that I do
not need to set message context properties. Please let me know that as well.
Thank you for your time!
-Tony
Tony Dean
SAS Institute Inc.
919.531.6704
[EMAIL PROTECTED]
SAS... The Power to Know
http://www.sas.com
