I will enter it.
Also, another problem.
I use to be able to obtain the axis2 lib and axis2 services directory with the
following:
messageContext().getConfigurationContext().getRealPath("lib");
messageContext().getConfigurationContext().getRealPath("services");
Now, using:
sessionContext().getConfigurationContext().getRealPath("lib");
sessionContext().getConfigurationContext().getRealPath("services");
just resolves to the current working directory, not the actual location where
Axis2 is deployed as a webApp.
.../webApps/axis2/WEB-INF/lib
/services
I will open jira for this as well.
-----Original Message-----
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 4:56 PM
To: Tony Dean
Cc: [email protected]
Subject: Re: [axis2] changes in 1.0
Yes, please create one does not harm and keep the item fresh in everyone's
memory.
-- dims
On 6/2/06, Tony Dean <[EMAIL PROTECTED]> wrote:
> Dims,
> 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.
>
> Thanks.
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 02, 2006 3:46 PM
> To: [email protected]
> Subject: Re: [axis2] changes in 1.0
>
> Tony,
>
> Did anyone respond? Can u please file bugs for these?
>
> thanks,
> dims
>
> On 6/1/06, Tony Dean <[EMAIL PROTECTED]> 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,
> > soapFaultCode);
> >
> > messageContext.setProperty(SOAP12Constants.SOAP_FAULT_REASON_LOCAL_N
> > AME, soapFaultReason);
> >
> > messageContext.setProperty(SOAP12Constants.SOAP_FAULT_DETAIL_LOCAL_N
> > AM
> > 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="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header
> > /><soapenv:Body><soapenv:Fault><faultcode>soapenv:Client</faultcode><faultstring>unknown</faultstring><detail><Exception>org.apache.axis2.AxisFault
> > at
> > org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:102)
> > at
> > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
> > at
> > org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
> > at
> > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
> > at
> > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> > at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> > at
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> > at
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> > at
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> > at
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> > at
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> > at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> > at
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
> > at
> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
> > at
> > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> > at
> > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> > at
> > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> > at java.lang.Thread.run(Thread.java:534)
> > </Exception></detail></soapenv:Fault></soapenv:Body></soapenv:Envelo
> > pe
> > >
> >
> >
> > 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
> > [EMAIL PROTECTED]
> >
> > SAS... The Power to Know
> > http://www.sas.com
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
