[jira] [Commented] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080942#comment-14080942 ] Kyle Thayer commented on AXIS2-5662: Good-morning! I have found some more detailed

[jira] [Updated] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Thayer updated AXIS2-5662: --- Description: Here is the stack trace that the client is getting: com.ca.ucf.api.UCFException:

[jira] [Updated] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Thayer updated AXIS2-5662: --- Description: Here is the stack trace that the client is getting: com.ca.ucf.api.UCFException:

[jira] [Resolved] (RAMPART-415) Upgrade Rampart to use latest wss4j 1.6.16

[ https://issues.apache.org/jira/browse/RAMPART-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved RAMPART-415. - Resolution: Fixed Upgrade Rampart to use latest wss4j 1.6.16

[jira] [Commented] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081376#comment-14081376 ] Andreas Veithen commented on AXIS2-5662: The stack trace shows that your are using

[jira] [Assigned] (AXIS2-5659) Improve WS-AddressingAndIdentity support in Axis2 to allow configuring any identity claims

[ https://issues.apache.org/jira/browse/AXIS2-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS2-5659: -- Assignee: Andreas Veithen Improve WS-AddressingAndIdentity support in Axis2 to allow

[jira] [Commented] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081458#comment-14081458 ] Kyle Thayer commented on AXIS2-5662: Dumb question! How do I know if I am using SJSXP

[jira] [Commented] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081494#comment-14081494 ] Andreas Veithen commented on AXIS2-5662: The package

[jira] [Commented] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081504#comment-14081504 ] Kyle Thayer commented on AXIS2-5662: Awesome! And which package belongs to Woodstox

[jira] [Commented] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.

[ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081522#comment-14081522 ] Kyle Thayer commented on AXIS2-5662: It appears the client is using 1.4.1 and not

[jira] [Commented] (AXIS2-5663) wsdl2java creates invalid java code with extension + choice

[ https://issues.apache.org/jira/browse/AXIS2-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081627#comment-14081627 ] Martin Gainty commented on AXIS2-5663: -- IF the test is choice and as long as we have