RPCMessageReceiver; response envelope dose not serialize properly ------------------------------------------------------------------
Key: AXIS2-2327 URL: https://issues.apache.org/jira/browse/AXIS2-2327 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Environment: Any Reporter: Saminda Wishwajith Abeyruwan Priority: Critical I've deployed Axis2 in Weblogic 9.2. For the service I used RPCMessageReceiver and part of response envelop is as follows, ====== <?xml version='1.0' encoding='utf-8'?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <ns:getSystemLogResponse xmlns:ns="http://org.apache.axis2/xsd"> <return> <appenderData> <facility xmlns:nil="http://www.w3.org/2001/XMLSchema-instance" nil:nil="true"></facility> <isFileAppender>false</isFileAppender> <isSysLogAppender>false</isSysLogAppender> <logFile nil:nil="true"></logFile> <name>AXIS2_MEMORY</name> <pattern>%5p [%d] %x %m%n</pattern> <sysLogHost nil:nil="true"></sysLogHost> <threshold>DEBUG</threshold> </appenderData> ... </return> </ns:getSystemLogResponse> </soapenv:Body> </soapenv:Envelope> ===== As you can see, //apenderData/facility has declared xmlns:nil="http://www.w3.org/2001/XMLSchema-instance" but //apenderData/logFile element is unbounded for "nil" prefix. Is this problem due to their implementation. Should I report to AXIOM as well. Now Weblogic has its own stax implementation. Apparently, system load Weblogic stax impl by default. On the other hand, Should't it be cleaner, if the namespace "http://www.w3.org/2001/XMLSchema-instance" bound to "xsi" prefix rather "nil" prefix. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]