When using the core API there i s no such thing as a topic, we only deal with queues. Basically a topic consists of an address with multiple queues bound to it where each queue will have a consumer(subscriber).
If you are using JMS then i would recommend taking a look at the JMSServerManager, you could do something like:
[codeJMSServerManager ]jmsServer = new JMSServerManagerImpl(server);
jmsServer.createTopic(.....
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240985#4240985
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240985
The queue you created is a core queue.
The preferred way to create JMS destinations is using the JMSServerManagerImpl on top of the MessagingServer you created:
| Configuration configuration = new ConfigurationImpl();
| configuration.setPersistenceEnabled(false);
| configuration.setSecurityEnabled(false);
| configuration.setAcceptorConfigurations(transports);
| server = Messaging.newMessagingServer(configuration);
| JMSServerManager manager =new JMSServerManagerImpl(server);
|
| manager.createQueue(...);
| manager.createTopic(...);
|
| manager.start(); // will also start the underlying MessagingServer
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240983#4240983
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240983
I see,thanks.
Next time i will post my new topic about JCA in the JCA forum.
And i hava a question that it still work when not use jdbc driver ping and <check-valid-connection-sql> statement.Just as following:
<?xml version="1.0" encoding="UTF-8"?>
|
| <!DOCTYPE datasources
| PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
| "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd">
| <datasources>
| <local-tx-datasource>
| <jndi-name>testDs</jndi-name>
| <connection-url>jdbc:mysql://localhost:3306/test</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>root</user-name>
| <password>mysql</password>
| <min-pool-size>20</min-pool-size>
| <max-pool-size>50</max-pool-size>
| <metadata>
| <type-mapping>mySQL</type-mapping>
| </metadata>
| </local-tx-datasource>
| </datasources>
Is that right? Or is it the default mechanism of JBoss JNDI ds connection pooling?
Your replay will by most appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240977#4240977
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240977
I am trying to embed JBoss Messaging 2.0 beta to my application which uses JMS API. I can easily create JMS Queue this way:
SimpleString q = new SimpleString("jms.queue."+name);
server.createQueue(q, q, null, true, false);
where "server" is MessagingServer which i create this way:
Configuration configuration = new ConfigurationImpl();
configuration.setPersistenceEnabled(false);
configuration.setSecurityEnabled(false);
configuration.setAcceptorConfigurations(transports);
server = Messaging.newMessagingServer(configuration);
server.start();
However, I do not know how to create JMS Topic. Any hint, please?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240967#4240967
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240967
I'm work with jboss-5.1.0.GA-jdk6.
I can see the WSDL but if I try to do a call to the WS:
11:43:08,396 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:87)
I've inside $JBOSS_HOME/lib/ensored:
jbossws-native-saaj.jar
jbossws-native-jaxrpc.jar
jbossws-native-jaxws.jar
jbossws-native-jaxws-ext.jar
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240966#4240966
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240966