And that's exactly where I lose coherence. I'm not going to be writing any Java
code here, so want to do it all via config. I created a datasource config for
JBOSS as follows:
<connection-factories>
<!-- ==================================================================== -->
<!-- STOMP Stuff -->
<!-- ==================================================================== -->
<!-- STOMPConnect -->
<mbean code="org.codehaus.stomp.jms.StompConnect"
name="jboss.messaging:service=StompConnect,name=StompConnect">
<attribute name="ProviderName">StompConnect</attribute>
<attribute name="Uri">tcp://localhost:61616</attribute>
<attribute name="JNDIProvider">stomp/connect</attribute>
</mbean>
</connection-factories>
And get a funky exception. However, I think I'll get around that problem by
implementing a bean-dd xml section. What I firstly need to know is if I'm even
remotely on the right track, or else how do I actually "run" StompConnect.
Thanks again,
j/
-----Original Message-----
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: 26 February 2008 13:45
To: users@activemq.apache.org
Subject: Re: JBoss Messaging Stomp Configuration
Just create a StomConnect object, configure it with whatever
ConnectionFactory you want from JBoss and call its start() method.
Use whatever JBoss mechanisms you want (EJB/MBeans/spring) to configure that
e.g. here's the JavaDoc
http://stomp.codehaus.org/maven/apidocs/org/codehaus/stomp/jms/StompConnect.html
On 26/02/2008, Johann Ungerer <[EMAIL PROTECTED]> wrote:
> Indeed... ;)
>
> My problem is the documentation seems a little light, or I don't have enough
> of a frame of reference to make sense of it.
>
> Below the documentation from Stomp:
> If you use some kind of dependency injection framework like Spring you can
> configure StompConnect using XML if you prefer. Just configure the
> StompConnect POJO with
>
> the JMS ConnectionFactory instance
> you can provide a JNDI InitialContext if you prefer, though its typcially
> easier to just provide the JMS ConnectionFactory
> optionally you can provide the uri to expose the Stomp services on.
> i.e. the host name and port that Stomp clients will connect to. Typically
> this will default to tcp://localhost:61613 but it can be any hostname/port
>
> http://stomp.codehaus.org/Running+StompConnect
>
> That does not tell me much I'm afraid.
>
> So, if anyone knows how to demystify that, I'll be very grateful.
>
> Thanks,
>
> j/
>
> -----Original Message-----
> From: James Strachan [mailto:[EMAIL PROTECTED]
>
> Sent: 26 February 2008 13:19
> To: users@activemq.apache.org
> Subject: Re: JBoss Messaging Stomp Configuration
>
>
> On 26/02/2008, Johann Ungerer <[EMAIL PROTECTED]> wrote:
> > Hi James,
> >
> > See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=128884 for
> the response from JBOSS.
>
> So basically they are passing the buck :)
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
