You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Saminda Wishwajith Abeyruwan (JIRA)" <ji...@apache.org> on 2007/03/15 10:09:09 UTC
[jira] Created: (AXIS2-2327) RPCMessageReceiver; response envelope
dose not serialize properly
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response
envelope dose not serialize properly
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ 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 : <AppenderData><facility 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>
> <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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response
envelope dose not serialize properly
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ 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>
> <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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2327) RPCMessageReceiver; response
envelope dose not serialize properly
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ 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>
> <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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-2327) RPCMessageReceiver; response envelope
dose not serialize properly
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-2327:
----------------------------------------
Assignee: Deepal Jayasinghe
> 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
> Assigned To: Deepal Jayasinghe
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2327) RPCMessageReceiver; response envelope
dose not serialize properly
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-2327.
--------------------------------------
Resolution: Fixed
fixed in current SVN
> 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>
> <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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2327) RPCMessageReceiver; response envelope
dose not serialize properly
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-2327:
-------------------------------------
Assignee: Eran Chinthaka (was: Deepal Jayasinghe)
This is an Axiom bug , as I can see Axiom is totaly depend on the underline parser. We need to overcome that.
Thanks
Deepal
> 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>
> <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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org