axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Dean" <>
Subject RE: [axis2] changes in 1.0
Date Fri, 02 Jun 2006 19:55:42 GMT
I believe Deepal opened a jira for serviceContext.getMyEPR().  I have not heard anything about
the axis fault problem.  My question is am I doing the right thing here?  I remember someone
saying that some of that code was going to be cleaned up making it somewhat easier and more
intuitive for creating faults.  Just wondering if I should be changing the way I'm doing things.
 If however, I am creating a custom fault the right way, it appears that it is not working
and I could open a jira if you think it necessary.


-----Original Message-----
From: Davanum Srinivas [] 
Sent: Friday, June 02, 2006 3:46 PM
Subject: Re: [axis2] changes in 1.0


Did anyone respond? Can u please file bugs for these?


On 6/1/06, Tony Dean <> wrote:
> Hi,
> Could you please answer a few questions in regard to changes that have been instituted
in 1.0.
> 1. I am now presented with a ServiceContext when service init() is invoked.  I would
like to obtain my endpoint address from it.
> serviceContext.getMyEPR(); returns null however.  Can you fix this?  I use to use messageContext.getTo(),
but it seems more appropriate to use the serviceContext since my endpoint address should be
static and not changing on a per call basis.
> 2. I had some code that created a custom SOAP fault that worked in 0.95.  It no longer
works.  It would create a soapFaultCode, soapFaultReason, and soapFaultDetail and add it to
the out-going message context as follows:
>                     messageContext.setProperty(SOAP12Constants.SOAP_FAULT_CODE_LOCAL_NAME,
>                     messageContext.setProperty(SOAP12Constants.SOAP_FAULT_REASON_LOCAL_NAME,
> messageContext.setProperty(SOAP12Constants.SOAP_FAULT_DETAIL_LOCAL_NAM
> E, soapFaultDetail);
> Now instead of my custom soap fault being returned, I get a generic Axis2 fault returned:
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv=""><soapenv:Header
>         at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(;
>         at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(;
>         at org.apache.axis2.engine.AxisEngine.receive(;
>         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(;
>         at org.apache.axis2.transport.http.AxisServlet.doPost(;
>         at javax.servlet.http.HttpServlet.service(;
>         at javax.servlet.http.HttpServlet.service(;
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(;
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(;
>         at org.apache.catalina.core.StandardWrapperValve.invoke(;
>         at org.apache.catalina.core.StandardContextValve.invoke(;
>         at org.apache.catalina.core.StandardHostValve.invoke(;
>         at org.apache.catalina.valves.ErrorReportValve.invoke(;
>         at org.apache.catalina.core.StandardEngineValve.invoke(;
>         at org.apache.catalina.connector.CoyoteAdapter.service(;
>         at org.apache.coyote.http11.Http11Processor.process(;
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(;
>         at;
>         at;
>         at org.apache.tomcat.util.threads.ThreadPool$;
>         at;
> </Exception></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope
> >
> Please to me how I can get this working again.  What is the best fail proof way to generate
my own fault data.  Do you have an api similar to SAAJ?
> Thanks.
> Tony Dean
> SAS Institute Inc.
> 919.531.6704
> SAS... The Power to Know
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Davanum Srinivas :

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message