Gordon Sim wrote:
Robert Greig wrote:
As I say selectors are 'coming soon', there is a patch for XSLT based
selectors attached to QPID-530[1] if you are interested in
previewing that.
Out of curiosity, why XSLT? Is it to handle message body selection as
well as the more traditional headers?
On Tue, 2009-08-25 at 12:46 -0500, Rich Stephens wrote:
> It SHOULD BE:
>
> http://anonsvn.jboss.org/repos/rhmessaging/store/trunk/cpp
>
Got it, thanks. I'll fix that.
-
Apache Qpid - AMQP Messaging Implementation
Project:
On Tue, 2009-08-25 at 11:01 -0500, Rich Stephens wrote:
> I've been looking for information on an implementation of message
> persistence
> for qpidc-0.5.
>
> I found the entries in the FAQ at qpid.apache.org/faq.html. First off,
> the
> C++ repository link there is incorrect. It points to:
>
On Tue, 2009-08-25 at 11:01 -0500, Rich Stephens wrote:
> I've been looking for information on an implementation of message persistence
> for qpidc-0.5.
>
> I found the entries in the FAQ at qpid.apache.org/faq.html. First off, the
> C++ repository link there is incorrect. It points to:
> http://
Rich Stephens wrote:
I've been looking for information on an implementation of message persistence
for qpidc-0.5.
I found the entries in the FAQ at qpid.apache.org/faq.html. First off, the
C++ repository link there is incorrect. It points to:
http://anonsvn.jboss.org.repos/rhmessaging/store/tru
Cullen Davis wrote:
Gordon
1) The make is now running to completion ( if QPID_LOAD_MODULE is defined as a relative
path, the cpp/docs/man build fails when the "qpidd --help"invocation does not
find the ./src/.libs/sslconnector.so plugin)
2) Thank you for the clarification, I now understand wha
I've been looking for information on an implementation of message persistence
for qpidc-0.5.
I found the entries in the FAQ at qpid.apache.org/faq.html. First off, the
C++ repository link there is incorrect. It points to:
http://anonsvn.jboss.org.repos/rhmessaging/store/trunk/cpp -- it should be
Gordon
1) The make is now running to completion ( if QPID_LOAD_MODULE is defined as a
relative path, the cpp/docs/man build fails when the "qpidd --help"invocation
does not find the ./src/.libs/sslconnector.so plugin)
2) Thank you for the clarification, I now understand what you meant by
"stand
Cullen Davis wrote:
Gordon,
I do not have the qpidc package installed. I set and exported QPID_NO_MODULE_DIR=true. (I also tried QPID_NO_MODULE_DIR=1) I still get the "Unknown protocol: ssl (qpid/client/Connector.cpp:66)" error.
Does make check pass? In particular does the ssl_test run
Gordon,
I do not have the qpidc package installed. I set and exported
QPID_NO_MODULE_DIR=true. (I also tried QPID_NO_MODULE_DIR=1) I still get the
"Unknown protocol: ssl (qpid/client/Connector.cpp:66)" error.
In an earlier post, you stated that the sslconnector.so plugin should be
speci
Cullen Davis wrote:
I have not been able to get the SSL client connector to be loaded for the direct examples.
Per Gordon's instructions, I modified the direct/declare_queues.cpp example to add use a ConnectionSetting object when opening a Connection. I set the ConnectionSetting.protocol prop
I don't remember having this issue, sorry I can't be more helpful...
I'm not sure how you pinpoint the origin of the problem to the cname function
however. In the log it's referring to the camel function which should work fine
with 3 parameters. I didn't work on java for ages but it seems to me
12 matches
Mail list logo
