Oleg,
It seems to me that the MDB are working ok with spyderMQ now. I think Peter
might be a better person to ask if you should remove openjms since he was
the one integrating it with jBoss..
Regards,
Hiram
----- Original Message -----
From: "Oleg Nitz" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Thursday, December 28, 2000 1:47 AM
Subject: Re: [jBoss-Dev] CVS update: jboss/src/etc/conf/default spyderMQ.xml
spyderMQ.properties jboss.jcml
> Hi Hiram,
>
> Is MDB support now based on SpyderMQ?
> That's great.
> Can we remove
>
> exolabcore-0.1.jar
> log4j.jar
> openjms-client-patched-0.5.1.jar
> openjms-patched-0.5.1.jar
> openjms-pool.jar
> openjms-rmi-patched-0.5.1.jar
>
> from lib/ext now? These files take near 1 Mb.
>
> Regards,
> Oleg
>
> jBoss CVS Development wrote:
> > User: hiram
> > Date: 00/12/27 14:46:03
>
> > Modified: src/etc/conf/default spyderMQ.properties jboss.jcml
> > Added: src/etc/conf/default spyderMQ.xml
> > Log:
> > Bringing spyderMQ up to version 0.6. Added the MDB support for it
that Peter had implemented.
>
> > Revision Changes Path
> > 1.3 +0 -29 jboss/src/etc/conf/default/spyderMQ.properties
>
> > Index: spyderMQ.properties
> > ===================================================================
> > RCS file:
/products/cvs/ejboss/jboss/src/etc/conf/default/spyderMQ.properties,v
> > retrieving revision 1.2
> > retrieving revision 1.3
> > diff -u -r1.2 -r1.3
> > --- spyderMQ.properties 2000/12/18 10:20:10 1.2
> > +++ spyderMQ.properties 2000/12/27 22:46:02 1.3
> > @@ -1,32 +1,3 @@
> > -# Those are the physical topics known by the server
> > -
> > -knownTopics = metrics, beancache
> > -
> > -# Those are the physical queues known by the server
> > -
> > -knownQueues = testQueue
> > -
> > -# Those are the users:password:clientID known by the server
> > -
> > -knownIds = john:needle:johnClientID, sahra:spot
> > -
> > -# Classnames for the invocation layer
> > -
> > -DistributedTopicConnectionFactoryClassName =
org.spydermq.distributed.server.DistributedTopicConnectionFactoryRMIImpl
> > -DistributedQueueConnectionFactoryClassName =
org.spydermq.distributed.server.DistributedQueueConnectionFactoryRMIImpl
> > -
> > -ConnectionReceiverClassName =
org.spydermq.distributed.server.ConnectionReceiverOIL
> > -#ConnectionReceiverClassName =
org.spydermq.distributed.server.ConnectionReceiverRMIImpl
> > -
> > -DistributedJMSServerClassName =
org.spydermq.distributed.server.DistributedJMSServerOIL
> > -#DistributedJMSServerClassName =
org.spydermq.distributed.server.DistributedJMSServerRMIImpl
> > -
> > # [Log level] valid values are : LOG_EVERYTHING, LOG_NOTICE,
LOG_ERRORS
> > LogLevel = LOG_ERRORS
> > -
> > -# By default the server startup logic will start a JNDI server (JNP).
> > -# You may not want it to, ie., you already have one running. To
> > -# prevent the launch set the following variable to any non-null
value.
> > -
> > -DoNotStartJNDI = yo
>
>
>
>
> > 1.10 +11 -1 jboss/src/etc/conf/default/jboss.jcml
>
> > Index: jboss.jcml
> > ===================================================================
> > RCS file: /products/cvs/ejboss/jboss/src/etc/conf/default/jboss.jcml,v
> > retrieving revision 1.9
> > retrieving revision 1.10
> > diff -u -r1.9 -r1.10
> > --- jboss.jcml 2000/12/18 10:19:14 1.9
> > +++ jboss.jcml 2000/12/27 22:46:02 1.10
> > @@ -113,8 +113,18 @@
> > <attribute name="Configuration">file URL to jetty.xml e.g.
file:/usr/local/jboss/dist/conf/default/jetty.xml</attribute>
> > </mbean>
> > -->
> > -
> > +
> > + <!-- For Message Driven Beans -->
> > <mbean code="org.jboss.spydermq.SpyderMQService"
name="DefaultDomain:service=SpyderMQ" />
> > + <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name=":service=JMSProviderLoader,name=SpyderMQProvider">
> > + <attribute name="ProviderName">SpyderMQProvider</attribute>
> > + <attribute
name="ProviderAdapterClass">org.jboss.jms.jndi.SpyderMQProvider</attribute>
> > + </mbean>
> > + <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
name=":service=ServerSessionPoolMBean,name=StdJMSPool">
> > + <attribute name="PoolName">StdJMSPool</attribute>
> > + <attribute
name="PoolFactoryClass">org.jboss.jms.asf.StdServerSessionPoolFactory</attri
bute>
> > + </mbean>
> > +
>
> > <!-- Make sure you change EmbeddedTomcat to Jetty if you are using
Jetty -->
> > <mbean code="org.jboss.deployment.J2eeDeployer"
name="J2EE:service=J2eeDeployer">
>
>
>
> > 1.1 jboss/src/etc/conf/default/spyderMQ.xml
>
> > Index: spyderMQ.xml
> > ===================================================================
> > <?xml version="1.0" encoding="UTF8"?>
>
> > <Server>
>
> > <!-- Setup the persistence settings -->
> > <PersistenceManager>
> > <DataDirectory>../../spyderMQ/</DataDirectory>
> > </PersistenceManager>
>
> > <!-- The physical topics known by the server -->
> > <Topic><Name>testTopic</Name></Topic>
> > <Topic><Name>example</Name></Topic>
> > <Topic><Name>bob</Name></Topic>
>
> > <!-- The physical queues known by the server -->
> > <Queue><Name>testQueue</Name></Queue>
> > <Queue><Name>controlQueue</Name></Queue>
> > <Queue><Name>A</Name></Queue>
> > <Queue><Name>B</Name></Queue>
> > <Queue><Name>C</Name></Queue>
> > <Queue><Name>D</Name></Queue>
> > <Queue><Name>E</Name></Queue>
> > <Queue><Name>ex</Name></Queue>
>
> > <!-- The users known by the server -->
> > <UserManager>
> > <User>
> > <Name>john</Name>
> > <Password>needle</Password>
> > <Id>DurableSubscriberExample</Id>
> > </User>
> > <User>
> > <Name>sahra</Name>
> > <Password>spot</Password>
> > </User>
> > </UserManager>
>
> > <!-- The invokation layers the server will expose -->
> > <InvocationLayer>
> > <Name>OIL</Name>
> >
<TopicConnectionFactoryJNDI>TopicConnectionFactory</TopicConnectionFactoryJN
DI>
> >
<QueueConnectionFactoryJNDI>QueueConnectionFactory</QueueConnectionFactoryJN
DI>
> >
<XATopicConnectionFactoryJNDI>XATopicConnectionFactory</XATopicConnectionFac
toryJNDI>
> >
<XAQueueConnectionFactoryJNDI>XAQueueConnectionFactory</XAQueueConnectionFac
toryJNDI>
> >
<ReceiverClass>org.spydermq.distributed.server.ConnectionReceiverOIL</Receiv
erClass>
> >
<ServerClass>org.spydermq.distributed.server.DistributedJMSServerOIL</Server
Class>
> > </InvocationLayer>
> > <InvocationLayer>
> > <Name>UIL</Name>
> >
<TopicConnectionFactoryJNDI>UILTopicConnectionFactory</TopicConnectionFactor
yJNDI>
> >
<QueueConnectionFactoryJNDI>UILQueueConnectionFactory</QueueConnectionFactor
yJNDI>
> >
<XATopicConnectionFactoryJNDI>UILXATopicConnectionFactory</XATopicConnection
FactoryJNDI>
> >
<XAQueueConnectionFactoryJNDI>UILXAQueueConnectionFactory</XAQueueConnection
FactoryJNDI>
> >
<ReceiverClass>org.spydermq.distributed.server.ConnectionReceiverUIL</Receiv
erClass>
> >
<ServerClass>org.spydermq.distributed.server.DistributedJMSServerUIL</Server
Class>
> > </InvocationLayer>
> > <InvocationLayer>
> > <Name>RMI</Name>
> >
<TopicConnectionFactoryJNDI>RMITopicConnectionFactory</TopicConnectionFactor
yJNDI>
> >
<QueueConnectionFactoryJNDI>RMIQueueConnectionFactory</QueueConnectionFactor
yJNDI>
> >
<XATopicConnectionFactoryJNDI>RMIXATopicConnectionFactory</XATopicConnection
FactoryJNDI>
> >
<XAQueueConnectionFactoryJNDI>RMIXAQueueConnectionFactory</XAQueueConnection
FactoryJNDI>
> >
<ReceiverClass>org.spydermq.distributed.server.ConnectionReceiverRMIImpl</Re
ceiverClass>
> >
<ServerClass>org.spydermq.distributed.server.DistributedJMSServerRMIImpl</Se
rverClass>
> > </InvocationLayer>
>
> > </Server>
>
>
>
>
