It's interesting. You and Gordon both feel that way about
first-person pronouns in the site text. I'll change it to everyone,
no problem.
On Thu, Mar 28, 2013 at 11:10 AM, Steve Huston shus...@riverace.com wrote:
This looks really great, Justin! My only nit at this time is in the box at
the
On 03/28/2013 08:52 PM, Bill Freeman wrote:
So it occurs to me to ask whether the correspondence between named queue
and object id survives broker restarts?
I believe with QMFv2 and qpidd, the object identifiers for queues are
formed from the package, the class and the queue's name. So
Hi,
I noticed that the QueueQuery and ExchangeQuery commands (AMQP 0.10) are
not exactly protected using the ACL rules on the Java broker. Once the user
is allowed to access the virtual host in the ACLs, he seems to be able to
send the QueueQuery and ExchangeQuery requests and receive the
Tried with this new build but with the same problems, see the
connectionURLString property. The QPID 0.16+ AMQConnectionFactory has default
constructor that is used by Hermes to create the AMQConnectionFactory object.
The only way how to pass broker url is via connectionURLString property, but
I created a JIRA QPID-4676 (https://issues.apache.org/jira/browse/QPID-4676)
covering the second issue with the way the usernames are being created.
Thanks Regards
Jakub
On Thu, Feb 28, 2013 at 12:22 AM, Jakub Scholz ja...@scholz.cz wrote:
s, that might be an option as well. I remember there
It feels too small even on my small devices, and I think is making
assumptions that people use 2 windows (or more specifically, 2 windows with
our site in both) side by side
Hi Justin, first let me say that I'm currently without decent IT access, so
I've not had a chance to take a
On Fri, Mar 29, 2013 at 9:29 AM, Gordon Sim g...@redhat.com wrote:
On 03/28/2013 08:52 PM, Bill Freeman wrote:
So it occurs to me to ask whether the correspondence between named queue
and object id survives broker restarts?
I believe with QMFv2 and qpidd, the object identifiers for queues
Thanks Jakub. We took a quick look earlier and I am planning to do so
properly over the weekend and look to get it committed.
Robbie
On 29 March 2013 15:01, Jakub Scholz ja...@scholz.cz wrote:
I created a JIRA QPID-4676 (
https://issues.apache.org/jira/browse/QPID-4676)
covering the second
We are presently are using the Java broker have now found a need to send
message with the destination address in some messages different than the
default address for a session.
I was wondering if the Java Broker still has a problem with setting routing
key at message level (can not set the
