ODP: Axis1: access to HttpRequest?
Hello, I tried and tested just the simple solution by sublaclassing the AxisServlet: import java.io.IOException; import javax.servlet.ServletException; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import org.apache.axis.transport.http.AxisServlet; import org.apache.log4j.Category; public class MyAxisServlet extends AxisServlet { protected static Category cat = Category.getInstance("MyAxisServlet"); public ScoringServlet() { } public void init() throws javax.servlet.ServletException { cat.debug("@ INIT CALLED "); super.init(); } public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { cat.debug("@ doGet CALLED "); super.doGet(request, response); } public void doPost(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException { cat.debug("@ doPost CALLED "); super.doPost(req, res); } public void initQueryStringHandlers() { cat.debug("@ initQueryStringHandlers CALLED "); super.initQueryStringHandlers(); } } Then you need to modify web.xml in Axis web app and registed your calss as AxisServlet : AxisServlet Apache-Axis Servlet ma.package.MyAxisServlet sincerely Olek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ODP: Logging request messages in Axis running in JBoss
Hello, There is a handler usage described in user guide and the sample handler is used just for logging. I think you could achieve you goal defining one handler for requestFlow and the another in responseFlow. The problem you will encounter will be as mine, that I described in my first message on this list : in case of error the response handler is not called by Axis. sincerely Olek PB Polsoft, Poznan, Poland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis error: SAXParseException: Content is not allowed in tra iling section
Hello, It seems that your sevice returns something that is not considered to be a proper XML by parser at the Axis client side. Particulary this error means that some other charactes than "<" are at the beggining of the documnet. I suggest you to use "org.apache.axis.utils.tcpmon" described in Axis user guide and wtach what exactly flows as a response message. sincerely Olek Polsoft, Poznan, Poland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to handle Faults with Handler ?
Hello, I tried to use configuration to use the handler when Axis provides SOAP Fault response for wrong requets. The problem is that the handler gets invoked only when the service is properly invoked. When some error occurs Axis provides response on itself and does not call my handler. I placed the responseFlow configuration within Service configuration and for http transport and for globalConfiguration with no success. The handler is invoker three times when everything goes well, but not invoked when error occures. Is there any way to configure handler that is invoked when error occurs ? I am particulary interested in such cases when error occures before my service is called (eg. wrong XML in request). sincerely Olek Polsoft, Poznan, Poland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]