Thanks, Hiram
Are the attached files what you mean? (I haven't tested to make sure they
work).
Is some part of the jbossmq-service.jar required for jbossmq to work,
whereas the rest is an example of how to set up usage of it? If so, can we
package the required part into a jboss-service.xml in a sar? If you let me
know which parts are required/optional I will try out the packaging.
Thanks
david jencks
On 2001.09.10 16:18:57 -0400 Hiram Chirino wrote:
> >From: David Jencks <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: jboss-dev <[EMAIL PROTECTED]>
> >Subject: [JBoss-dev] Mbean package deployment and undeployment
> >Date: Mon, 10 Sep 2001 14:16:17 -0400
> ....
> >
> >(As part of the jbosscx reorganization, all jca related classes are in
> the
> >jbosscx.sar, which contains the mbean configuration for the
> >ConnectionManagerFactoryLoaders and the RARDeployer. The jbossmq
> >configuration is now in a jbossmq-service.xml file, which depends on the
> >jbosscx.sar ( and causes it to be recursively deployed). The
> configuration
> >for the Hypersonic-based DefaultDS is in hsql-default-service.xml, which
> is
> >also autodeployed.)
> >
>
> JBossMQ does not depend on jbosscx.sar... The MDB and JMS RA stuff is
> what
> depends on jbosscx.sar. the jbossmq-service.xml file needs to get split
> into two files to show this.
>
> Regards,
> Hiram
>
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at
> http://explorer.msn.com/intl.asp
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: jbossmq-service.xml,v 1.2 2001/09/09 05:40:47 d_jencks Exp $ -->
<!--
| This is where you can add and configure your MBeans.
|
| *ATTENTION*
|
| The order of the listing here is the same order as
| the MBeans are loaded. Therefore if a MBean depends on another
| MBean to be loaded and started it has to be listed after all
| the MBeans it depends on.
-->
<server>
<classpath archives="
jbossmq.jar"/>
<!-- ==================================================================== -->
<!-- JBossMQ -->
<!-- ==================================================================== -->
<mbean code="org.jboss.mq.server.JBossMQService"
name="JBossMQ:service=Server"/>
<!--
| The StateManager is used to keep JMS perisitent state data.
| For example: what durable subscriptions are active.
-->
<mbean code="org.jboss.mq.server.StateManager"
name="JBossMQ:service=StateManager">
<attribute name="StateFile">conf/default/jbossmq-state.xml</attribute>
</mbean>
<!-- The PersistenceManager is used to store messages to disk. -->
<mbean code="org.jboss.mq.pm.file.PersistenceManager"
name="JBossMQ:service=PersistenceManager">
<attribute name="DataDirectory">db/jbossmq/</attribute>
</mbean>
<!--
| InvocationLayers are the different transport methods that can
| be used to access the server.
-->
<mbean code="org.jboss.mq.il.jvm.JVMServerILService"
name="JBossMQ:service=InvocationLayer,type=JVM">
<attribute name="ConnectionFactoryJNDIRef">java:/ConnectionFactory</attribute>
<attribute name="XAConnectionFactoryJNDIRef">java:/XAConnectionFactory</attribute>
</mbean>
<mbean code="org.jboss.mq.il.rmi.RMIServerILService"
name="JBossMQ:service=InvocationLayer,type=RMI">
<attribute name="ConnectionFactoryJNDIRef">RMIConnectionFactory</attribute>
<attribute name="XAConnectionFactoryJNDIRef">RMIXAConnectionFactory</attribute>
</mbean>
<mbean code="org.jboss.mq.il.oil.OILServerILService"
name="JBossMQ:service=InvocationLayer,type=OIL">
<attribute name="ConnectionFactoryJNDIRef">ConnectionFactory</attribute>
<attribute name="XAConnectionFactoryJNDIRef">XAConnectionFactory</attribute>
</mbean>
<mbean code="org.jboss.mq.il.uil.UILServerILService"
name="JBossMQ:service=InvocationLayer,type=UIL">
<attribute name="ConnectionFactoryJNDIRef">UILConnectionFactory</attribute>
<attribute name="XAConnectionFactoryJNDIRef">UILXAConnectionFactory</attribute>
</mbean>
<!--
| The following three line create 3 topics named:
|
| testTopic, example, bob
-->
<mbean code="org.jboss.mq.server.TopicManager"
name="JBossMQ:service=Topic,name=testTopic"/>
<mbean code="org.jboss.mq.server.TopicManager"
name="JBossMQ:service=Topic,name=example"/>
<mbean code="org.jboss.mq.server.TopicManager"
name="JBossMQ:service=Topic,name=bob"/>
<!--
| The following 9 line create 9 topics named:
|
| testQueue, controlQueue, A, B, C, D, E, F, ex
-->
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=testQueue"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=controlQueue"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=A"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=B"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=C"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=D"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=E"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=F"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=ex"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=DLQ"/>
<!-- The JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name=":service=JMSProviderLoader,name=JBossMQProvider">
<attribute name="ProviderName">DefaultJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JBossMQProvider
</attribute>
<attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
<attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
</mbean>
</server>
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: jbossmq-ra-service.xml,v 1.2 2001/09/09 05:40:47 d_jencks Exp $ -->
<!--
| This is where you can add and configure your MBeans.
|
| *ATTENTION*
|
| The order of the listing here is the same order as
| the MBeans are loaded. Therefore if a MBean depends on another
| MBean to be loaded and started it has to be listed after all
| the MBeans it depends on.
-->
<server>
<classpath archives="
jbosscx.sar,
jbossmq-service.xml"/>
<!-- ==================================================================== -->
<!-- JBossMQ JCA adapter and mdb configuration -->
<!-- ==================================================================== -->
<!-- The server session pool for Message Driven Beans -->
<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
</attribute>
</mbean>
<!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="JCA:service=ConnectionFactoryLoader,name=JmsXA">
<attribute name="JndiName">JmsXA</attribute>
<attribute name="RARDeployerName">JCA:service=RARDeployer</attribute>
<attribute name="ResourceAdapterName">JMS Adapter</attribute>
<attribute name="ConnectionManagerFactoryName">MinervaXACMFactory</attribute>
<attribute name="ConnectionManagerProperties">
# Pool type - uncomment to force, otherwise it is the default
#PoolConfiguration=per-factory
# Connection pooling properties - see
# org.jboss.resource.connectionmanager.PoolParameters
MinSize=0
MaxSize=10
BlockingTimeoutMillis=5000
CleanupEnabled=false
IdleTimeoutEnabled=false
InvalidateOnError=false
TrackLastUsed=false
GCIntervalMillis=120000
GCMinIdleMillis=1200000
IdleTimeoutMillis=1800000
MaxIdleTimeoutPercent=1.0
</attribute>
<attribute name="PrincipalMappingClass">
org.jboss.resource.security.ManyToOnePrincipalMapping
</attribute>
<attribute name="PrincipalMappingProperties">
</attribute>
</mbean>
</server>
