Fwd: [NOTICE] compromised jira passwords

Hi, just incase your like me and don't check committers regularly enough. Martin -- Forwarded message -- From: Joe Schaefer joe_schae...@yahoo.com Date: 10 April 2010 17:01 Subject: [NOTICE] compromised jira passwords To: committ...@apache.org Hello committers@, As you are

[jira] Created: (QPID-2499) Stale federation routes remain after route deletion.

Stale federation routes remain after route deletion. Key: QPID-2499 URL: https://issues.apache.org/jira/browse/QPID-2499 Project: Qpid Issue Type: Bug Components: C++ Broker

[jira] Updated: (QPID-2499) Stale federation routes remain after route deletion.

[ https://issues.apache.org/jira/browse/QPID-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated QPID-2499: - Attachment: fed-direct-stale-routes.sh run this script from the directory containing a built qpid/ svn

[jira] Created: (QPID-2500) Transport security for the WCF channel

Transport security for the WCF channel -- Key: QPID-2500 URL: https://issues.apache.org/jira/browse/QPID-2500 Project: Qpid Issue Type: New Feature Components: WCF/C++ Client Affects

[jira] Updated: (QPID-2500) Transport security for the WCF channel

[ https://issues.apache.org/jira/browse/QPID-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated QPID-2500: --- Attachment: QPID-2500-1.patch This patch provides the base functionality and security classes that

[jira] Updated: (QPID-2500) Transport security for the WCF channel

[ https://issues.apache.org/jira/browse/QPID-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated QPID-2500: --- Attachment: QPID-2500-3.patch Update WcfPerftest to use SSL and SASL plain Transport security for

[jira] Updated: (QPID-2500) Transport security for the WCF channel

[ https://issues.apache.org/jira/browse/QPID-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated QPID-2500: --- Attachment: QPID-2500-2.patch This patch updates the DTC plugin module to be able to parse data

[jira] Commented: (QPID-2482) Topic Exchange can duplicate messages.

[ https://issues.apache.org/jira/browse/QPID-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856025#action_12856025 ] Ken Giusti commented on QPID-2482: -- Good catch, Emmanuel. I'd like to open up a new jira

[jira] Commented: (QPID-2482) Topic Exchange can duplicate messages.

[ https://issues.apache.org/jira/browse/QPID-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856030#action_12856030 ] Rob Godfrey commented on QPID-2482: --- Emmanuel - can you give the explicit steps you used

[jira] Created: (QPID-2501) WCF Binding Configuration parameters

WCF Binding Configuration parameters Key: QPID-2501 URL: https://issues.apache.org/jira/browse/QPID-2501 Project: Qpid Issue Type: Improvement Components: WCF/C++ Client Affects Versions:

RE: [Windows c++] CMake Install target puts boost libs in prefix/bin/boost

Hi Andrew, I noticed that a few weeks ago you created a new directory in the install hierarchy bin/boost to which the boost dlls get copied. Is there a strong need for this separate directory? Yes, I believe so. I'm guessing that doing this makes it easier to create a separate WiX

RE: Status of qpid/tests/src/py/qpid_tests/broker_0_10?

Hi Gordon, On 04/12/2010 06:35 PM, Steve Huston wrote: Hi folks, I'm working on some testing for the Windows persistence stuff and ran across a seeming treasure trove of tests in qpid/tests/src/py/qpid_tests/broker_0_10/dtx.py. What's the status of these? I haven't found any

Examples

Hi All, Judging by some of the questions on the user list, I feel we could do a much better with our examples. (Also our examples should be more visible in the source tree and easily accessible from our release artefacts. However I believe that is a different discussion for another day.) I am

[JMS] ** Important ** Changing Default Destination Syntax to the new Addressing format from the 0.7 release !

Hi All, For the 0.6 release the destination syntax defaults to the old binding URL format. But as agreed earlier, we should change the default to the new addressing syntax from the 0.7 release. However if one needs to continue using the old syntax, then the following options will override the