Issue in wsdl2java ?

Hi All, I am working on issue, rampart-225. While working on it, I encountered an unusual structure in messages generated by the client. Later I found out that this unusual behavior is due to the way wsdl2java generates code. I have attached the policy which I am using. (policy.xml) Accordin

[jira] Commented: (AXIS2-4037) Content-ID must not contain unquoted colon characters

[ https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884970#action_12884970 ] Valery Ushakov commented on AXIS2-4037: --- The link to nightly builds doesn't seem to w

[jira] Commented: (AXIS2-4037) Content-ID must not contain unquoted colon characters

[ https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884961#action_12884961 ] Andreas Veithen commented on AXIS2-4037: @Valery: from AXIS2-4527: "my suggestion i

[jira] Commented: (AXIS2-4037) Content-ID must not contain unquoted colon characters

[ https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884960#action_12884960 ] Valery Ushakov commented on AXIS2-4037: --- As far as I can see WSCOMMONS-541 and r94749

[jira] Resolved: (AXIS2-4037) Content-ID must not contain unquoted colon characters

[ https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4037. Fix Version/s: 1.6 Resolution: Fixed This should be fixed by WSCOMMONS-541, and in p

[jira] Resolved: (AXIS2-4760) Content-Type still not parsed correctly in MTOM SOAP 1.2 messages

[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4760. Resolution: Incomplete Before investigating this issue further we need to determine if the

[jira] Updated: (AXIS2-4037) Content-ID must not contain unquoted colon characters

[ https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4037: --- Affects Version/s: 1.5 1.5.1 > Content-ID must not contain unquoted co

[jira] Assigned: (AXIS2-4037) Content-ID must not contain unquoted colon characters

[ https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS2-4037: -- Assignee: Andreas Veithen > Content-ID must not contain unquoted colon characters > ---

[jira] Commented: (AXIS2-3642) jibx libs coming in Axis2 distrib are renamed while still reffering in their manifests to old names

[ https://issues.apache.org/jira/browse/AXIS2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884927#action_12884927 ] Dennis Sosnoski commented on AXIS2-3642: Yes, this is being resolved for the JiBX 1

[jira] Commented: (AXIS2-4760) Content-Type still not parsed correctly in MTOM SOAP 1.2 messages

[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884922#action_12884922 ] Valery Ushakov commented on AXIS2-4760: --- Test messages were not generated by JavaMail

Re: Build failure in Axis2 trunk

The error indicates that your build picks up an outdated snapshot version of 1.2.9. The Axis2 trunk is correctly configured to load 1.2.9-SNAPSHOT from repository.apache.org. Maybe this is some issue specific to the build setup at WSO2? Andreas On Tue, Jun 29, 2010 at 11:56, Sameera Jayasoma wro

[jira] Resolved: (AXIS2-4761) Mustunderstand check fails for headers containing response parameters

[ https://issues.apache.org/jira/browse/AXIS2-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4761. --- Resolution: Fixed Thanks Lori The code is contributed in revision 960205. > Mustunderstand

[jira] Resolved: (AXIS2-4759) JMS transport prevents clean Axis2 shutdown

[ https://issues.apache.org/jira/browse/AXIS2-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4759. Resolution: Fixed Applied both patches. Thanks for your contribution! > JMS transport prev

[jira] Assigned: (AXIS2-4759) JMS transport prevents clean Axis2 shutdown

[ https://issues.apache.org/jira/browse/AXIS2-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS2-4759: -- Assignee: Andreas Veithen > JMS transport prevents clean Axis2 shutdown > -

[jira] Commented: (AXIS2-4760) Content-Type still not parsed correctly in MTOM SOAP 1.2 messages

[ https://issues.apache.org/jira/browse/AXIS2-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884905#action_12884905 ] Andreas Veithen commented on AXIS2-4760: Which JavaMail implementation and version

[jira] Resolved: (AXIS2-3642) jibx libs coming in Axis2 distrib are renamed while still reffering in their manifests to old names

[ https://issues.apache.org/jira/browse/AXIS2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-3642. Resolution: Won't Fix We are using the Maven artifacts from JIBX. If these JARs have manife

[jira] Updated: (AXIS2-4755) dynamic serviceclient: axisservice-names are not unique

[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4755: --- Fix Version/s: (was: 1.6) (was: 1.5.2) > dynamic serviceclient: ax