[jira] Updated: (QPID-2555) Qpid Info OSGI plugin

[ https://issues.apache.org/jira/browse/QPID-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorin Suciu updated QPID-2555: -- Attachment: InfoPlugin.xml InfoPlugin.pdf Hi Marnie, Thanks for the comments. I have

[jira] Created: (QPID-2702) --max-connections not work when using cluster

--max-connections not work when using cluster - Key: QPID-2702 URL: https://issues.apache.org/jira/browse/QPID-2702 Project: Qpid Issue Type: Bug Components: C++ Broker Affects

RE: Version and icon resources for Qpid cpp executables on Windows

On Mon, 2010-06-28 at 17:25 -0400, Steve Huston wrote: Hi Chuck, I'd like to add minimal resources, such as a version number and an icon, to windows executables and dlls produced by qpid-cpp. I see two paths to this goal and would like your opinion on how to get there. 1. Add

[jira] Created: (QPID-2703) Transaction Rollback does not restore consumer credit - TRUNK MERGE

Transaction Rollback does not restore consumer credit - TRUNK MERGE --- Key: QPID-2703 URL: https://issues.apache.org/jira/browse/QPID-2703 Project: Qpid Issue Type: Bug

[jira] Created: (QPID-2704) Provide scavenge() for SimpleQueueEntryList - TRUNK MERGE

Provide scavenge() for SimpleQueueEntryList - TRUNK MERGE - Key: QPID-2704 URL: https://issues.apache.org/jira/browse/QPID-2704 Project: Qpid Issue Type: Bug Components: Java

[jira] Commented: (QPID-2703) Transaction Rollback does not restore consumer credit - TRUNK MERGE

[ https://issues.apache.org/jira/browse/QPID-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883490#action_12883490 ] Martin Ritchie commented on QPID-2703: -- This change was only applied to the 0.5.x-dev

[jira] Commented: (QPID-2704) Provide scavenge() for SimpleQueueEntryList - TRUNK MERGE

[ https://issues.apache.org/jira/browse/QPID-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883491#action_12883491 ] Martin Ritchie commented on QPID-2704: -- This scavange() appraoch should be merged to

[jira] Created: (QPID-2705) Need a new Plug-in Architecture for the Java Broker

Need a new Plug-in Architecture for the Java Broker --- Key: QPID-2705 URL: https://issues.apache.org/jira/browse/QPID-2705 Project: Qpid Issue Type: Improvement Reporter: Danushka

[jira] Commented: (QPID-2705) Need a new Plug-in Architecture for the Java Broker

[ https://issues.apache.org/jira/browse/QPID-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883527#action_12883527 ] Danushka Menikkumbura commented on QPID-2705: - The current plug-in architecture

[jira] Assigned: (QPID-2705) Need a new Plug-in Architecture for the Java Broker

[ https://issues.apache.org/jira/browse/QPID-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danushka Menikkumbura reassigned QPID-2705: --- Assignee: Danushka Menikkumbura Need a new Plug-in Architecture for the Java

[jira] Commented: (QPID-2705) Need a new Plug-in Architecture for the Java Broker

[ https://issues.apache.org/jira/browse/QPID-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883530#action_12883530 ] Danushka Menikkumbura commented on QPID-2705: - I was able to get the broker

New Plug-in Architecture for the Java Broker

Hi Devs, Please provide your feedback on [1]. [1] - https://issues.apache.org/jira/browse/QPID-2705 Thoughts are highly appreciated. Thanks, -- Danushka Menikkumbura Apache Axis2 PMC Member Apache Qpid - World Domination through Advanced Message Queueing ; http://qpid.apache.org phone :

[jira] Commented: (QPID-2705) Need a new Plug-in Architecture for the Java Broker

[ https://issues.apache.org/jira/browse/QPID-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883533#action_12883533 ] Danushka Menikkumbura commented on QPID-2705: - Basically we need a factory class

Re: Version and icon resources for Qpid cpp executables on Windows

I agree with Andrew for his stated reasons. After thinking about it a little more how about this maybe a hybrid mix of #1 and #2 would work: 1. For each exe/dll, add a .rc file that puts some default version number and an Apache Qpid icon. The icon is an elegant Q with the Apache feather for

RE: Version and icon resources for Qpid cpp executables on Windows

All the version stuff can (should) be generated from the cmake config. The values are already in the CMakeLists.txt file. You'd use the same technique that's used to build the config.h file (and, I think, the doxygen input). There are also a variety of little 'Q' icons with the feather. I did

Re: Version and icon resources for Qpid cpp executables on Windows

On Tue, 2010-06-29 at 09:08 -0400, Chuck Rolke wrote: I agree with Andrew for his stated reasons. After thinking about it a little more how about this maybe a hybrid mix of #1 and #2 would work: 1. For each exe/dll, add a .rc file that puts some default version number and an Apache Qpid

RE: Version and icon resources for Qpid cpp executables on Windows

On Tue, 2010-06-29 at 10:06 -0400, Steve Huston wrote: All the version stuff can (should) be generated from the cmake config. The values are already in the CMakeLists.txt file. You'd use the same technique that's used to build the config.h file (and, I think, the doxygen input). Having

Problem running qpid tests on windows.

Newbie question - attempting my first windows build from a clean trunk. Got everything built, I can run qpidd and test clients like qpid-perftest no problem. However I can't run the test suite, specifically unit_test crashes with an unhandled exception. I notice in my build that there's an

Re: New Plug-in Architecture for the Java Broker

Hi Danushka, What benefits would have this approach versus the current OSGI mechanism (leaving aside the embedded felix)? Thank you, Sorin On Tue, Jun 29, 2010 at 1:53 PM, Danushka Menikkumbura danushka.menikkumb...@gmail.com wrote: Hi Devs, Please provide your feedback on [1]. [1] -  

Re: Problem running qpid tests on windows.

Those are debug builds. Try again building the solution but select the Release configuration in the Visual Studio pulldown. - Alan Conway acon...@redhat.com wrote: From: Alan Conway acon...@redhat.com To: Steve Huston shus...@riverace.com, Qpid Dev dev@qpid.apache.org, Andrew Stitcher

[jira] Assigned: (QPID-2702) --max-connections not work when using cluster

[ https://issues.apache.org/jira/browse/QPID-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned QPID-2702: - Assignee: Alan Conway --max-connections not work when using cluster

Re: New Plug-in Architecture for the Java Broker

Hi Sorin, To me the issue is not being able to use Qpid in another OSGi-fied application. Lets leave that aside for a while. Still I doubt OSGi fits in here. To me its like doing procedural programming inside OOP. There is nothing wrong with it; but why one would do that?. Thanks, Danushka On

[jira] Created: (QPID-2706) Visual Basic example includes a directory whose name contains a space

Visual Basic example includes a directory whose name contains a space - Key: QPID-2706 URL: https://issues.apache.org/jira/browse/QPID-2706 Project: Qpid Issue Type: Bug

[jira] Assigned: (QPID-2706) Visual Basic example includes a directory whose name contains a space

[ https://issues.apache.org/jira/browse/QPID-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-2706: -- Assignee: Ted Ross Visual Basic example includes a directory whose name contains a space

Re: New Plug-in Architecture for the Java Broker

Hi Danushka, Sorry, I am not exactly following but was wondering if you could elaborate on why OSGI does not fit in qpid java broker? For example I see ActiveMQ, ServiceMix, etc are using OSGI as well (not embedded as we do). Thank you, Sorin On Tue, Jun 29, 2010 at 4:22 PM, Danushka

RE: Problem running qpid tests on windows.

The changes I was thinking of are checked in, but there's a setting missing from config.h... Coming right up. Sorry for the confusion. -Steve -Original Message- From: Steve Huston [mailto:shus...@riverace.com] Sent: Tuesday, June 29, 2010 11:23 AM To: 'Chuck Rolke';

[jira] Created: (QPID-2707) Cmake build doesn't output all needed settings to build a valid shared library name for loading

Cmake build doesn't output all needed settings to build a valid shared library name for loading --- Key: QPID-2707 URL: https://issues.apache.org/jira/browse/QPID-2707

Re: New Plug-in Architecture for the Java Broker

Hi Sorin, I am not saying OSGi does not fit into the broker. Undoubtedly we should OSGi-fy the broker at some point. That will add modularity, multiple version support, hot deployment/update, etc into the broker. What I am saying is that the way OSGi is used in the current plug-in architecture

[jira] Resolved: (QPID-2707) Cmake build doesn't output all needed settings to build a valid shared library name for loading

[ https://issues.apache.org/jira/browse/QPID-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2707. Fix Version/s: 0.7 Resolution: Fixed Fixed on trunk r959067. Cmake build doesn't output

[jira] Created: (QPID-2708) Separate types library from common library.

Separate types library from common library. --- Key: QPID-2708 URL: https://issues.apache.org/jira/browse/QPID-2708 Project: Qpid Issue Type: Improvement Components: C++ Client Affects

[jira] Updated: (QPID-2708) Separate types library from common library.

[ https://issues.apache.org/jira/browse/QPID-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated QPID-2708: -- Attachment: libqpidtypes.patch Create separate qpidtypes library for the qpid::types namespace.

[jira] Updated: (QPID-2708) Separate types library from common library.

[ https://issues.apache.org/jira/browse/QPID-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated QPID-2708: -- Comment: was deleted (was: Create separate qpidtypes library for the qpid::types namespace.) Separate

[jira] Updated: (QPID-2708) Separate types library from common library.

[ https://issues.apache.org/jira/browse/QPID-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated QPID-2708: -- Attachment: (was: libqpidtypes.patch) Separate types library from common library.

[jira] Updated: (QPID-2708) Separate types library from common library.

[ https://issues.apache.org/jira/browse/QPID-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated QPID-2708: -- Attachment: libqpidtypes.patch Create a separate qpidtypes library. Separate types library from

[jira] Commented: (QPID-2708) Separate types library from common library.

[ https://issues.apache.org/jira/browse/QPID-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883705#action_12883705 ] Steve Huston commented on QPID-2708: The patch looks good, with the exception of small

[jira] Commented: (QPID-2708) Separate types library from common library.

[ https://issues.apache.org/jira/browse/QPID-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883715#action_12883715 ] Chuck Rolke commented on QPID-2708: --- Didn't we just do this a month ago? We had to back

[jira] Created: (QPID-2709) Replace the remaining references to the incubator

Replace the remaining references to the incubator - Key: QPID-2709 URL: https://issues.apache.org/jira/browse/QPID-2709 Project: Qpid Issue Type: Task Reporter: Emmanuel Bourg

[jira] Updated: (QPID-2709) Replace the remaining references to the incubator

[ https://issues.apache.org/jira/browse/QPID-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-2709: - Attachment: incubator.patch This patch updates the most visible references to the incubator. It

Re: New Plug-in Architecture for the Java Broker

Devs, Any other idea on this?. Please provide your feedback. Thanks, Danushka Hi Sorin, I am not saying OSGi does not fit into the broker. Undoubtedly we should OSGi-fy the broker at some point. That will add modularity, multiple version support, hot deployment/update, etc into the broker.