[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489370 ] Amila Chinthaka Suriarachchi commented on AXIS2-2246: - I did not fixed it for 1.1.1 SNAPSHOT. it

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489328 ] Tim Buss commented on AXIS2-2246: - yes I saw it work for the 1.1.1 snapshot but I have not yet managed to get it to

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489295 ] Amila Chinthaka Suriarachchi commented on AXIS2-2246: - see your comment on 21/Mar/07 there you ha

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489172 ] Tim Buss commented on AXIS2-2246: - The fix I am refererring to is the "critical" null namespace for parameter elemen

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489107 ] Amila Chinthaka Suriarachchi commented on AXIS2-2246: - In this case only the possible option is t

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488541 ] Tim Buss commented on AXIS2-2246: - It appears that the main fix for this problem has not yet been included in Axis 1

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486855 ] Amila Chinthaka Suriarachchi commented on AXIS2-2246: - in your wsdl file you have made the namesa

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486888 ] Tim Buss commented on AXIS2-2246: - I assume you are referring to this paragraph of the WS-I basic profile. "Converse

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486829 ] Tim Buss commented on AXIS2-2246: - I have finally narrowed down the mysterious issue with the more complex schema an

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485584 ] Tim Buss commented on AXIS2-2246: - I should point out that I used the wsdl2java command line tool for the SNAPSHOT t

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485552 ] Tim Buss commented on AXIS2-2246: - I have confirmed the attached case is fixed using the AXIOM SNAPSHOT dated 23rd M

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483398 ] Amila Chinthaka Suriarachchi commented on AXIS2-2246: - As a temporaliy solution, you can deploy t

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483397 ] Amila Chinthaka Suriarachchi commented on AXIS2-2246: - you have to use the axiom-SNAPSHOTs. I thi

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483282 ] Tim Buss commented on AXIS2-2246: - I tried the March 21 07 axis2 snapshot but with the same result. I assume that i

[jira] Commented: (AXIS2-2246) Rpc-Literal Client and Server adb codegen create messages that are non WS-I complient

[ https://issues.apache.org/jira/browse/AXIS2-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483089 ] Amila Chinthaka Suriarachchi commented on AXIS2-2246: - The reason for your problem should be an i