[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response envelope dose not serialize properly
[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503976 ] Deepal Jayasinghe commented on AXIS2-2327: -- What I mean was its totaly depend on underline parser's namespace context. 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 Assignee: Eran Chinthaka 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 isFileAppenderfalse/isFileAppender isSysLogAppenderfalse/isSysLogAppender logFile nil:nil=true/logFile nameAXIS2_MEMORY/name pattern%5p [%d] %x %m%n/pattern sysLogHost nil:nil=true/sysLogHost thresholdDEBUG/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]
[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response envelope dose not serialize properly
[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503991 ] Eran Chinthaka commented on AXIS2-2327: --- I just checked Axiom with the following code and I don't see any problem in the output. OMFactory omFactory = OMAbstractFactory.getOMFactory(); OMElement appenderData = omFactory.createOMElement(AppenderData, null); OMElement facility = omFactory.createOMElement(facility, null, appenderData); OMNamespace nilNS = facility.declareNamespace(http://www.w3.org/2001/XMLSchema-instance;, nil); facility.addAttribute(nil, true, nilNS); OMElement logfile = omFactory.createOMElement(logfile, null, appenderData); logfile.addAttribute(nil, true, nilNS); System.out.println(appenderData); Output : AppenderDatafacility xmlns:nil=http://www.w3.org/2001/XMLSchema-instance; nil:nil=true /logfile xmlns:nil=http://www.w3.org/2001/XMLSchema-instance; nil:nil=true //AppenderData So it forces me to think that this is a problem with Stax parser that you are using. 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 Assignee: Eran Chinthaka 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 isFileAppenderfalse/isFileAppender isSysLogAppenderfalse/isSysLogAppender logFile nil:nil=true/logFile nameAXIS2_MEMORY/name pattern%5p [%d] %x %m%n/pattern sysLogHost nil:nil=true/sysLogHost thresholdDEBUG/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]
[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response envelope dose not serialize properly
[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503993 ] Eran Chinthaka commented on AXIS2-2327: --- Saminda, Can you please confirm the observation and comment or resolve this issue? Thanks. 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 Assignee: Eran Chinthaka 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 isFileAppenderfalse/isFileAppender isSysLogAppenderfalse/isSysLogAppender logFile nil:nil=true/logFile nameAXIS2_MEMORY/name pattern%5p [%d] %x %m%n/pattern sysLogHost nil:nil=true/sysLogHost thresholdDEBUG/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]
