[jira] [Updated] (AXIS2-5673) AxisAdminServlet initialization causes a memory leak

[ https://issues.apache.org/jira/browse/AXIS2-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5673: --- Fix Version/s: 1.7.0 AxisAdminServlet initialization causes a memory leak

[jira] [Commented] (AXIS2-5673) AxisAdminServlet initialization causes a memory leak

[ https://issues.apache.org/jira/browse/AXIS2-5673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613416#comment-14613416 ] Andreas Veithen commented on AXIS2-5673: Not all patches are automatically merged

[jira] [Commented] (AXIS-1557) xs:datetime to Calendar

[ https://issues.apache.org/jira/browse/AXIS-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613425#comment-14613425 ] Andreas Veithen commented on AXIS-1557: --- Please create a new issue with the details

[jira] [Resolved] (AXIS-2296) Get the following exception when web service call is made by client : java.lang.NoSuchMethodException: org.apache.axis.encoding.ser.ArrayDeserializerFactory.create(java.l

[ https://issues.apache.org/jira/browse/AXIS-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-2296. --- Resolution: Not A Problem Get the following exception when web service call is made by client

[jira] [Issue Comment Deleted] (AXIS-2296) Get the following exception when web service call is made by client : java.lang.NoSuchMethodException: org.apache.axis.encoding.ser.ArrayDeserializerFactory.

[ https://issues.apache.org/jira/browse/AXIS-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS-2296: -- Comment: was deleted (was: ArrayDeserializerFactory donated by IBM has no such method ..calling

[jira] [Commented] (AXIS-2442) java file genrated using WSDL2JAVA fail to compile with 'too many parameters' error

[ https://issues.apache.org/jira/browse/AXIS-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14607608#comment-14607608 ] Andreas Veithen commented on AXIS-2442: --- Yes, the first build containing the fix

[jira] [Commented] (AXIS-2442) java file genrated using WSDL2JAVA fail to compile with 'too many parameters' error

[ https://issues.apache.org/jira/browse/AXIS-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604133#comment-14604133 ] Andreas Veithen commented on AXIS-2442: --- Thanks for identifying the exact revision of

[jira] [Resolved] (AXIS2-5307) Build failure with Java 7

[ https://issues.apache.org/jira/browse/AXIS2-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5307. Resolution: Fixed Build failure with Java 7 -

[jira] [Updated] (AXIS2-5307) Build failure with Java 7

[ https://issues.apache.org/jira/browse/AXIS2-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5307: --- Fix Version/s: 1.6.3 1.7.0 Build failure with Java 7

[jira] [Resolved] (AXIS-2910) DimeBodyPart.send does not close stream for dynamic content

[ https://issues.apache.org/jira/browse/AXIS-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-2910. --- Resolution: Fixed Fix Version/s: 1.4.1 Assignee: Andreas Veithen

[jira] [Commented] (AXIS2-5487) Attempted read on closed stream - II

[ https://issues.apache.org/jira/browse/AXIS2-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14525865#comment-14525865 ] Andreas Veithen commented on AXIS2-5487: I think that the theory about

[jira] [Resolved] (AXIS2-5685) RepositoryListener] - Error occurred while loading modules from classpath

[ https://issues.apache.org/jira/browse/AXIS2-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5685. Resolution: Duplicate RepositoryListener] - Error occurred while loading modules from

[jira] [Resolved] (AXIS2-5686) RepositoryListener] - Error occurred while loading modules from classpath

[ https://issues.apache.org/jira/browse/AXIS2-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5686. Resolution: Duplicate Fix Version/s: (was: 1.6.2) RepositoryListener] - Error

[jira] [Resolved] (AXIS2-5687) Nullpointer Exception

[ https://issues.apache.org/jira/browse/AXIS2-5687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5687. Resolution: Duplicate Nullpointer Exception - Key:

[jira] [Resolved] (RAMPART-422) WS-Trust with Kerberos Token

[ https://issues.apache.org/jira/browse/RAMPART-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved RAMPART-422. - Resolution: Invalid Please note that this is a bug tracker, not a forum. WS-Trust with

[jira] [Commented] (RAMPART-417) Support for transport binding Kerberos v5 authentication

[ https://issues.apache.org/jira/browse/RAMPART-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277627#comment-14277627 ] Andreas Veithen commented on RAMPART-417: - The best would actually be to finalize

[jira] [Resolved] (AXIS2-5684) Improper Resource Shutdown or Release in BaseUtils.java 246

[ https://issues.apache.org/jira/browse/AXIS2-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5684. Resolution: Fixed Fix Version/s: 1.7.0 Assignee: Andreas Veithen Improper

[jira] [Updated] (AXIS2-5684) Improper Resource Shutdown or Release in BaseUtils.java 246

[ https://issues.apache.org/jira/browse/AXIS2-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5684: --- Labels: (was: security) Improper Resource Shutdown or Release in BaseUtils.java 246

[jira] [Commented] (AXIS2-5684) Improper Resource Shutdown or Release in BaseUtils.java 246

[ https://issues.apache.org/jira/browse/AXIS2-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14272448#comment-14272448 ] Andreas Veithen commented on AXIS2-5684: This issue is not about a problem with a

[jira] [Moved] (AXIS2-5684) Improper Resource Shutdown or Release in BaseUtils.java 246

[ https://issues.apache.org/jira/browse/AXIS2-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-55 to AXIS2-5684: -- Component/s: (was: Base)

[jira] [Moved] (RAMPART-419) WS Security header is not being serialized when header element is not instance of org.apache.axiom.soap.SOAPHeader

[ https://issues.apache.org/jira/browse/RAMPART-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved AXIOM-459 to RAMPART-419: --- Component/s: (was: DOOM)

[jira] [Commented] (RAMPART-419) WS Security header is not being serialized when header element is not instance of org.apache.axiom.soap.SOAPHeader

[ https://issues.apache.org/jira/browse/RAMPART-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14142515#comment-14142515 ] Andreas Veithen commented on RAMPART-419: - Moved this issue from Axiom to

[jira] [Commented] (RAMPART-417) Support for transport binding Kerberos v5 authentication

[ https://issues.apache.org/jira/browse/RAMPART-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125073#comment-14125073 ] Andreas Veithen commented on RAMPART-417: - I'm a bit worried about the invocation

[jira] [Assigned] (RAMPART-417) Support for transport binding Kerberos v5 authentication

[ https://issues.apache.org/jira/browse/RAMPART-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned RAMPART-417: --- Assignee: Andreas Veithen Support for transport binding Kerberos v5 authentication

[jira] [Resolved] (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 resolved AXIS2-5659. Resolution: Fixed Fix Version/s: 1.7.0 Improve WS-AddressingAndIdentity support in

[jira] [Commented] (AXIS2-5329) ConcurrentModificationException from org.apache.axis2.osgi during startup

[ https://issues.apache.org/jira/browse/AXIS2-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118646#comment-14118646 ] Andreas Veithen commented on AXIS2-5329: No, the FAILURE status just means that

[jira] [Commented] (AXIS2-5646) An IllegalStateException with invalid BundleContext occurres during the shutdown process of Axis2 OSGi bundle

[ https://issues.apache.org/jira/browse/AXIS2-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118651#comment-14118651 ] Andreas Veithen commented on AXIS2-5646: No, this was just a transient build

[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=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=14079703#comment-14079703 ] Andreas Veithen commented on AXIS2-5662: The provided information is insufficient:

[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=14079766#comment-14079766 ] Andreas Veithen commented on AXIS2-5662:

[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=14079771#comment-14079771 ] Andreas Veithen commented on AXIS2-5662: BTW, if this is an existing project, then

[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=14079841#comment-14079841 ] Andreas Veithen commented on AXIS2-5662: In the network trace, the response looks

[jira] [Issue Comment Deleted] (AXIS-716) Multiple code generation problems ( wrong types generated, names with first cap, attribute referneces)

[ https://issues.apache.org/jira/browse/AXIS-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS-716: - Comment: was deleted (was: Combination is shown for complicated front as common jokes are

[jira] [Resolved] (RAMPART-416) Enable Rampart transport binding integration tests

[ https://issues.apache.org/jira/browse/RAMPART-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved RAMPART-416. - Resolution: Fixed Fix Version/s: 1.7.0 Assignee: Andreas Veithen

[jira] [Commented] (RAMPART-416) Enable Rampart transport binding integration tests

[ https://issues.apache.org/jira/browse/RAMPART-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067966#comment-14067966 ] Andreas Veithen commented on RAMPART-416: - {quote} Updated the patch to use Jetty

[jira] [Updated] (RAMPART-416) Enable Rampart transport binding integration tests

[ https://issues.apache.org/jira/browse/RAMPART-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated RAMPART-416: Affects Version/s: (was: 1.7.0) Enable Rampart transport binding integration tests

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14062518#comment-14062518 ] Andreas Veithen commented on RAMPART-415: - Applied the patch that updates Bouncy

[jira] [Assigned] (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 reassigned RAMPART-415: --- Assignee: Andreas Veithen Upgrade Rampart to use latest wss4j 1.6.16

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14060155#comment-14060155 ] Andreas Veithen commented on RAMPART-415: - I also tried to apply the patch to the

[jira] [Resolved] (AXIS2-5655) Stubs created in Axis2-1.5.1 is not compatible with Latest axis2-1.6.2 (No backward compatibility from 1.6.2 to 1.5.1)

[ https://issues.apache.org/jira/browse/AXIS2-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5655. Resolution: Not a Problem Please note that this is a bug tracking system, not a forum.

[jira] [Resolved] (AXIS2-5655) Stubs created in Axis2-1.5.1 is not compatible with Latest axis2-1.6.2 (No backward compatibility from 1.6.2 to 1.5.1)

[ https://issues.apache.org/jira/browse/AXIS2-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5655. Resolution: Not a Problem Stubs are not expected to be compatible across different major

[jira] [Resolved] (AXIS2-5646) An IllegalStateException with invalid BundleContext occurres during the shutdown process of Axis2 OSGi bundle

[ https://issues.apache.org/jira/browse/AXIS2-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5646. Resolution: Fixed Assignee: Andreas Veithen An IllegalStateException with invalid

[jira] [Resolved] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-4847. Resolution: Fixed Fix Version/s: 1.6.3 1.7.0 Assignee:

[jira] [Resolved] (AXIS2-5329) ConcurrentModificationException from org.apache.axis2.osgi during startup

[ https://issues.apache.org/jira/browse/AXIS2-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5329. Resolution: Fixed Fix Version/s: 1.6.3 1.7.0 Assignee:

[jira] [Commented] (AXIS2-5628) Axis OSGi Bundle doesn't provide AxisServices with original WSDL

[ https://issues.apache.org/jira/browse/AXIS2-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14008348#comment-14008348 ] Andreas Veithen commented on AXIS2-5628: Same comment here as for AXIS2-5329: you

[jira] [Commented] (AXIS2-5646) An IllegalStateException with invalid BundleContext occurres during the shutdown process of Axis2 OSGi bundle

[ https://issues.apache.org/jira/browse/AXIS2-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994491#comment-13994491 ] Andreas Veithen commented on AXIS2-5646: I also see some NullPointerException that

[jira] [Commented] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944546#comment-13944546 ] Andreas Veithen commented on AXIS2-4847: Yes, if you could contribute that

[jira] [Commented] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13941784#comment-13941784 ] Andreas Veithen commented on AXIS2-4847: Andy, do you know if there is any

[jira] [Commented] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13936230#comment-13936230 ] Andreas Veithen commented on AXIS2-4847: I believe that this is fixed by r1577348.

[jira] [Commented] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932461#comment-13932461 ] Andreas Veithen commented on AXIS2-4847: One of the big issues with the OSGi code

[jira] [Commented] (AXIS2-5634) javax.xml.stream.FactoryConfigurationError: Requested factory com.ctc.wstx.stax. WstxInputFactory cannot be located

[ https://issues.apache.org/jira/browse/AXIS2-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930477#comment-13930477 ] Andreas Veithen commented on AXIS2-5634: Short answer: you either need to replace

[jira] [Resolved] (AXIS-2900) Unable to compile generated classes:

[ https://issues.apache.org/jira/browse/AXIS-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-2900. --- Resolution: Fixed Fix Version/s: 1.4.1 Assignee: Andreas Veithen Unable to

[jira] [Commented] (AXIS-2901) Invalid java.lang.String_Element reference generated in java class

[ https://issues.apache.org/jira/browse/AXIS-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13913569#comment-13913569 ] Andreas Veithen commented on AXIS-2901: --- There is another workaround: I observed that

[jira] [Comment Edited] (AXIS-2899) adb-codegen REGEX expression failure on ^

[ https://issues.apache.org/jira/browse/AXIS-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13902666#comment-13902666 ] Andreas Veithen edited comment on AXIS-2899 at 2/16/14 9:26 AM:

[jira] [Resolved] (AXIS-2899) adb-codegen REGEX expression failure on ^

[ https://issues.apache.org/jira/browse/AXIS-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-2899. --- Resolution: Invalid Fix Version/s: (was: 1.5) Invalid. First of all, this is the

[jira] [Commented] (AXIS2-5329) ConcurrentModificationException from org.apache.axis2.osgi during startup

[ https://issues.apache.org/jira/browse/AXIS2-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13902695#comment-13902695 ] Andreas Veithen commented on AXIS2-5329: If I understand correctly, the code

[jira] [Updated] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4847: --- Attachment: AXIS2-4847.patch Attached patch submitted by Andy Schmidt for AXIS2-5329 (but

[jira] [Comment Edited] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13902698#comment-13902698 ] Andreas Veithen edited comment on AXIS2-4847 at 2/16/14 1:16 PM:

[jira] [Commented] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13902705#comment-13902705 ] Andreas Veithen commented on AXIS2-4847: First of all, I agree with Ancoron

[jira] [Commented] (AXIS2-4847) IllegalStateException: Can only register services while bundle is active or activating.

[ https://issues.apache.org/jira/browse/AXIS2-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13902746#comment-13902746 ] Andreas Veithen commented on AXIS2-4847: Note that an implementation for the

[jira] [Commented] (AXIS2-5329) ConcurrentModificationException from org.apache.axis2.osgi during startup

[ https://issues.apache.org/jira/browse/AXIS2-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898098#comment-13898098 ] Andreas Veithen commented on AXIS2-5329: Unfortunately you reformatted the content

[jira] [Commented] (AXIS2-5329) ConcurrentModificationException from org.apache.axis2.osgi during startup

[ https://issues.apache.org/jira/browse/AXIS2-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895910#comment-13895910 ] Andreas Veithen commented on AXIS2-5329: Andy, can you please attach your patch

[jira] [Updated] (RAMPART-409) Download page must not link to snapshots / nightly builds

[ https://issues.apache.org/jira/browse/RAMPART-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated RAMPART-409: Assignee: Andreas Veithen Download page must not link to snapshots / nightly builds

[jira] [Work started] (RAMPART-409) Download page must not link to snapshots / nightly builds

[ https://issues.apache.org/jira/browse/RAMPART-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RAMPART-409 started by Andreas Veithen. Download page must not link to snapshots / nightly builds -

[jira] [Resolved] (RAMPART-409) Download page must not link to snapshots / nightly builds

[ https://issues.apache.org/jira/browse/RAMPART-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved RAMPART-409. - Resolution: Fixed Fixed. See: http://axis.apache.org/axis2/java/rampart/download.html

[jira] [Commented] (AXIS2-5625) java.lang.LinkageError: javax/xml/stream/XMLStreamReader by using org.apache.axiom.om.impl.llom.OMStAXWrapper

[ https://issues.apache.org/jira/browse/AXIS2-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892510#comment-13892510 ] Andreas Veithen commented on AXIS2-5625: I think that this is because the Axiom

[jira] [Commented] (AXIS2-5597) The adressing module adds the addressing namespace declaration in the header element, which is not allowed by BP 1.2

[ https://issues.apache.org/jira/browse/AXIS2-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794083#comment-13794083 ] Andreas Veithen commented on AXIS2-5597: My argument is not based on the code from

[jira] [Commented] (AXIS2-5597) The adressing module adds the addressing namespace declaration in the header element, which is not allowed by BP 1.2

[ https://issues.apache.org/jira/browse/AXIS2-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794118#comment-13794118 ] Andreas Veithen commented on AXIS2-5597: Yes, the schemaValid attribute is indeed

[jira] [Comment Edited] (AXIS2-5597) The adressing module adds the addressing namespace declaration in the header element, which is not allowed by BP 1.2

[ https://issues.apache.org/jira/browse/AXIS2-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794083#comment-13794083 ] Andreas Veithen edited comment on AXIS2-5597 at 10/14/13 1:48 PM:

[jira] [Commented] (AXIS2-5597) The adressing module adds the addressing namespace declaration in the header element, which is not allowed by BP 1.2

[ https://issues.apache.org/jira/browse/AXIS2-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13793691#comment-13793691 ] Andreas Veithen commented on AXIS2-5597: [quote] For the envelope element it is

[jira] [Commented] (AXIS2-5597) The adressing module adds the addressing namespace declaration in the header element, which is not allowed by BP 1.2

[ https://issues.apache.org/jira/browse/AXIS2-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13728850#comment-13728850 ] Andreas Veithen commented on AXIS2-5597: BP1600 is a test case for R9980 which

[jira] [Moved] (RAMPART-403) Error constructing valid security header for a SAML policy

[ https://issues.apache.org/jira/browse/RAMPART-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved AXIS-2894 to RAMPART-403: --- Key: RAMPART-403 (was: AXIS-2894) Project: Rampart (was:

[jira] [Resolved] (AXIS-2895) unable to refer import org.apache.axis.client.*; in WebSphere7

[ https://issues.apache.org/jira/browse/AXIS-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-2895. --- Resolution: Incomplete unable to refer import org.apache.axis.client.*; in WebSphere7

[jira] [Moved] (AXIS2-5585) java.lang.Invocation Target error in eclipse-codegen-wizard-1.6.2

[ https://issues.apache.org/jira/browse/AXIS2-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved ABDERA-347 to AXIS2-5585: --- Fix Version/s: (was: 1.1) Affects Version/s: (was:

[jira] [Commented] (AXIS2-5578) Transport level information does not match with SOAP Message namespace URI

[ https://issues.apache.org/jira/browse/AXIS2-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672897#comment-13672897 ] Andreas Veithen commented on AXIS2-5578: Note that this is a bug tracker, not a

[jira] [Updated] (AXIS2-5578) Transport level information does not match with SOAP Message namespace URI

[ https://issues.apache.org/jira/browse/AXIS2-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5578: --- Fix Version/s: (was: 1.2) Transport level information does not match with SOAP

[jira] [Resolved] (AXIS2-5578) Transport level information does not match with SOAP Message namespace URI

[ https://issues.apache.org/jira/browse/AXIS2-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5578. Resolution: Invalid There is no evidence that the error is caused by a bug in Axis2. It is

[jira] [Commented] (AXIS2-5578) Transport level information does not match with SOAP Message namespace URI

[ https://issues.apache.org/jira/browse/AXIS2-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672821#comment-13672821 ] Andreas Veithen commented on AXIS2-5578: Kindly explain why you believe that the

[jira] [Resolved] (AXIS-2889) Unable to download

[ https://issues.apache.org/jira/browse/AXIS-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-2889. --- Resolution: Fixed Fix Version/s: 1.4.1 Assignee: Andreas Veithen Unable

[jira] [Commented] (AXIS2-5576) Missing build.xml in Axis2-1.6.2 Source Distribution

[ https://issues.apache.org/jira/browse/AXIS2-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663089#comment-13663089 ] Andreas Veithen commented on AXIS2-5576: This issue is a duplicate of AXIS2-5413.

[jira] [Commented] (AXIS2-5573) web service calls with empty namespace elements fail in 1.6.2

[ https://issues.apache.org/jira/browse/AXIS2-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659851#comment-13659851 ] Andreas Veithen commented on AXIS2-5573: There is some key information missing in

[jira] [Resolved] (AXIS2-5451) how can i map Multiple axis2 service to a jms destination ?

[ https://issues.apache.org/jira/browse/AXIS2-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS2-5451. Resolution: Invalid This is not a discussion forum, but a bug tracker.

[jira] [Moved] (AXIS2-5523) JMSSender executes unnecessary JNDI lookups

[ https://issues.apache.org/jira/browse/AXIS2-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-1 to AXIS2-5523: - Component/s: (was: JMS) JMS transport

[jira] [Moved] (AXIS2-5524) JMSSender should not use a shared session or producer

[ https://issues.apache.org/jira/browse/AXIS2-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-2 to AXIS2-5524: - Component/s: (was: JMS) JMS transport

[jira] [Moved] (AXIS2-5526) TCP transport server is closing the socket after having received the message

[ https://issues.apache.org/jira/browse/AXIS2-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-4 to AXIS2-5526: - Component/s: (was: TCP) JMS transport

[jira] [Updated] (AXIS2-5526) TCP transport server is closing the socket after having received the message

[ https://issues.apache.org/jira/browse/AXIS2-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5526: --- Component/s: (was: JMS transport) TCP transport TCP transport

[jira] [Moved] (AXIS2-5529) Supporting JMS Object Messages

[ https://issues.apache.org/jira/browse/AXIS2-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-7 to AXIS2-5529: - Component/s: (was: JMS) JMS

[jira] [Moved] (AXIS2-5528) JMS ServiceTaskManager isn't J2EE compliant (setExceptionListener not permitted) and fails on WebSphere AS 6.1

[ https://issues.apache.org/jira/browse/AXIS2-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-6 to AXIS2-5528: - Component/s: (was: JMS) JMS

[jira] [Moved] (AXIS2-5530) Use MessageFormatter Interface in the TCPTransportSender

[ https://issues.apache.org/jira/browse/AXIS2-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-8 to AXIS2-5530: - Component/s: (was: TCP) TCP Fix

[jira] [Moved] (AXIS2-5531) UDP Transport May Generate Weird URLs

[ https://issues.apache.org/jira/browse/AXIS2-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-9 to AXIS2-5531: - Component/s: (was: UDP) UDP Key:

[jira] [Moved] (AXIS2-5532) Add Multicast Capabilities to the UDP Transport

[ https://issues.apache.org/jira/browse/AXIS2-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-10 to AXIS2-5532: -- Component/s: (was: UDP) UDP Fix

[jira] [Moved] (AXIS2-5534) Caching InitialContexts in JMS transport sender

[ https://issues.apache.org/jira/browse/AXIS2-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-12 to AXIS2-5534: -- Component/s: (was: JMS) JMS

[jira] [Moved] (AXIS2-5533) NPE Thrown When Enabling the UDP Listener Globally

[ https://issues.apache.org/jira/browse/AXIS2-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-11 to AXIS2-5533: -- Component/s: (was: UDP) UDP Fix

[jira] [Moved] (AXIS2-5535) Setting the property 'transport.jms.CacheLevel' to 'consumer' fails.

[ https://issues.apache.org/jira/browse/AXIS2-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-13 to AXIS2-5535: -- Component/s: (was: JMS) JMS Fix

[jira] [Updated] (AXIS2-5535) Setting the property 'transport.jms.CacheLevel' to 'consumer' fails.

[ https://issues.apache.org/jira/browse/AXIS2-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-5535: --- Fix Version/s: 1.6.3 Setting the property 'transport.jms.CacheLevel' to 'consumer'

[jira] [Moved] (AXIS2-5536) JMS Transport Uses Temporary Topics for replyDestinationType, irrespective of transport.jms.ReplyDestinationType Value

[ https://issues.apache.org/jira/browse/AXIS2-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-14 to AXIS2-5536: -- Component/s: (was: JMS) JMS

[jira] [Moved] (AXIS2-5537) tcp transport problem: multithread blocking sending doesn't work

[ https://issues.apache.org/jira/browse/AXIS2-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen moved TRANSPORTS-15 to AXIS2-5537: -- Component/s: (was: TCP) TCP

<    3   4   5   6   7   8   9   10   11   12   >