I'm trying to subscribe to a topic using Smack XMPP. I am doing
MultiUserChat muc = new MultiUserChat(conn2, "calendar.appointment.create");
muc.join("AF");
When I view the admin/topics.jsp page in the browser, it shows the topic as
calendar.appointment.create/AF
I can send to that topic fro
gruikman wrote:
>
> I try to embed an activeMQ 5.2.0 broker in a camel-2.0M1 server with
> Spring 2.5.6 and Xbean 3.5 following the activemq tutorials but I get some
> problems...
>
>
>
> I change the
> "http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd"; into
> "http://activemq.
Using ActiveMQ 5.2.0, I have a junit test where I make a durable subscription
to a topic with a selector
String selector = "TD_A_ALARM_TYPE = '0'";
consumer = session.createDurableSubscriber((Topic)destination,
consumerName, selector, false);
I get messages where that property is specified.
huntc wrote:
>
> I'm curious as to what is trying to be achieved here. Could you please
> explain why it is useful to perform a naming/directory lookup for a queue
> or topic name?
>
My use case is probably due to my newbie status with JMS.
Session.createTopic javadocs imply that normal JMS us
janylj wrote:
>
> I tried ActiveMQ JNDI support. It seems to me only for testing, because
> the administrative objects are specified in the jndi.properties of client
> machine. There is no centralized place to manage the ConnectionFactory or
> Destination. And we could not control who could acce
I managed to get topics bound to JNDI, but only by putting them in
jndi.properties with
java.naming.factory.initial =
org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provider.url = vm://localhost
topic.directory.user.changepassword = directory.user.changepassword
topic.bla.bla.
I'm a newbie to JMS. I have an embedded broker configured in my Spring XML
config running inside my app.
My app is acting as a messaging gateway, receiving non JMS messages from
another system and I'm trying to t
Using ActiveMQ, I want to send UTF8 encoded XML. BytesMessage seems the most
appropriate although the JMS javadocs state that TextMessage is for XML - (I
disagree as UTF8 is not 'text', i.e. a sequence of chars in Java, it's a
sequence of bytes - this is like using application/xml instead of text
I have an embedded broker started via a Spring ApplicationContext using the
activemq.xml file shipped with standard 5.2.0.
When shutting down my Container and closing the Spring context, I get some
exceptions logged. The first is at DEBUG level
2009-03-05 15:25:20,765 DEBUG[VMTransport]:
org.ap