|
Revision 2695
(checked in by douglm, 3 years ago)
|
JBoss support. First stage in deploying applications as services in jboss.
Restructure shell script builds to provide platform specific options. Use that feature to create jboss services (sar files) that can be deployed within the server.
All this work is based on jboss 5.1.0.GA
In addition there is some partial support for geronimo. This is not complete
|
| Line | |
|---|
| 1 |
# |
|---|
| 2 |
# activemq jndi.properties |
|---|
| 3 |
# |
|---|
| 4 |
java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory |
|---|
| 5 |
|
|---|
| 6 |
# use the following property to configure the default connector |
|---|
| 7 |
java.naming.provider.url = tcp://localhost:61616?trace=true |
|---|
| 8 |
|
|---|
| 9 |
// Allows us to handle container differences |
|---|
| 10 |
org.bedework.connection.factory.name=java:activemq/QueueConnectionFactory |
|---|
| 11 |
|
|---|
| 12 |
# use the following property to specify the JNDI name the connection factory |
|---|
| 13 |
# should appear as. |
|---|
| 14 |
connectionFactoryNames = activemq/QueueConnectionFactory |
|---|
| 15 |
|
|---|
| 16 |
# register some queues in JNDI using the form |
|---|
| 17 |
# queue.[jndiName] = [physicalName] |
|---|
| 18 |
queue.queue/sysevents = bedework.sysevents |
|---|
| 19 |
|
|---|
| 20 |
queue.queue/syseventslog = bedework.sysevents.logger |
|---|
| 21 |
|
|---|
| 22 |
queue.queue/monitor = bedework.sysevents.monitor |
|---|
| 23 |
|
|---|
| 24 |
queue.queue/schedulerIn = bedework.scheduleIn |
|---|
| 25 |
|
|---|
| 26 |
queue.queue/schedulerOut = bedework.scheduleOut |
|---|
| 27 |
|
|---|
| 28 |
queue.queue/crawler = bedework.crawler |
|---|
| 29 |
|
|---|
| 30 |
# register some topics in JNDI using the form |
|---|
| 31 |
# topic.[jndiName] = [physicalName] |
|---|
| 32 |
#topic.MyTopic = example.MyTopic |
|---|
