jruby-jms 1.1.0-java
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/Gemfile +8 -0
- data/Gemfile.lock +36 -0
- data/HISTORY.md +52 -0
- data/LICENSE.txt +201 -0
- data/README.md +205 -0
- data/Rakefile +30 -0
- data/examples/advanced/session_pool.rb +37 -0
- data/examples/client-server/replier.rb +29 -0
- data/examples/client-server/requestor.rb +40 -0
- data/examples/file-to-q/files_to_q.rb +51 -0
- data/examples/file-to-q/q_to_files.rb +44 -0
- data/examples/invm/invm.rb +44 -0
- data/examples/invm/log4j.properties +58 -0
- data/examples/jms.yml +149 -0
- data/examples/performance/consumer.rb +25 -0
- data/examples/performance/producer.rb +31 -0
- data/examples/producer-consumer/browser.rb +24 -0
- data/examples/producer-consumer/consumer.rb +24 -0
- data/examples/producer-consumer/consumer_async.rb +41 -0
- data/examples/producer-consumer/producer.rb +25 -0
- data/examples/publish-subscribe/publish.rb +24 -0
- data/examples/publish-subscribe/subscribe.rb +31 -0
- data/lib/jms.rb +20 -0
- data/lib/jms/bytes_message.rb +52 -0
- data/lib/jms/connection.rb +529 -0
- data/lib/jms/imports.rb +21 -0
- data/lib/jms/logging.rb +50 -0
- data/lib/jms/map_message.rb +91 -0
- data/lib/jms/message.rb +285 -0
- data/lib/jms/message_consumer.rb +117 -0
- data/lib/jms/message_listener_impl.rb +79 -0
- data/lib/jms/message_producer.rb +59 -0
- data/lib/jms/mq_workaround.rb +70 -0
- data/lib/jms/object_message.rb +26 -0
- data/lib/jms/oracle_a_q_connection_factory.rb +48 -0
- data/lib/jms/queue_browser.rb +28 -0
- data/lib/jms/session.rb +473 -0
- data/lib/jms/session_pool.rb +168 -0
- data/lib/jms/text_message.rb +31 -0
- data/lib/jms/version.rb +3 -0
- data/nbproject/private/private.properties +3 -0
- data/nbproject/private/rake-d.txt +5 -0
- data/parallel_minion.gemspec +21 -0
- data/test/connection_test.rb +160 -0
- data/test/jms.yml +111 -0
- data/test/log4j.properties +32 -0
- data/test/message_test.rb +130 -0
- data/test/session_pool_test.rb +86 -0
- data/test/session_test.rb +140 -0
- metadata +113 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 601d2d745dab0bb052eaf0516faabda7afcc4ef3
|
4
|
+
data.tar.gz: 66a1ea9158a02a782acb728c890c4654c48cb67c
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: b0a7f76e0fc27018d8de20761f57be8f181a5c3aac528e657df4cfe8943db3ad0efaa5485c79a5d5d911495229090fd2088dd530091f3d81fd8dd12f03aa3eeb
|
7
|
+
data.tar.gz: 1970f9dabe77b456b70e1cd8ed519db44d827a6b9e245fc04e143b6f631344869bfc6d9f5db9d8bd1ccff223258e0cb195369ca32d4a6f914437eaa369a85981
|
data/Gemfile
ADDED
data/Gemfile.lock
ADDED
@@ -0,0 +1,36 @@
|
|
1
|
+
GEM
|
2
|
+
remote: http://rubygems.org/
|
3
|
+
specs:
|
4
|
+
activesupport (4.0.2)
|
5
|
+
i18n (~> 0.6, >= 0.6.4)
|
6
|
+
minitest (~> 4.2)
|
7
|
+
multi_json (~> 1.3)
|
8
|
+
thread_safe (~> 0.1)
|
9
|
+
tzinfo (~> 0.3.37)
|
10
|
+
atomic (1.1.14)
|
11
|
+
atomic (1.1.14-java)
|
12
|
+
gene_pool (1.3.2)
|
13
|
+
i18n (0.6.9)
|
14
|
+
minitest (4.7.5)
|
15
|
+
multi_json (1.8.4)
|
16
|
+
rake (10.1.1)
|
17
|
+
shoulda (3.5.0)
|
18
|
+
shoulda-context (~> 1.0, >= 1.0.1)
|
19
|
+
shoulda-matchers (>= 1.4.1, < 3.0)
|
20
|
+
shoulda-context (1.1.6)
|
21
|
+
shoulda-matchers (2.5.0)
|
22
|
+
activesupport (>= 3.0.0)
|
23
|
+
thread_safe (0.1.3)
|
24
|
+
atomic
|
25
|
+
thread_safe (0.1.3-java)
|
26
|
+
atomic
|
27
|
+
tzinfo (0.3.38)
|
28
|
+
|
29
|
+
PLATFORMS
|
30
|
+
java
|
31
|
+
ruby
|
32
|
+
|
33
|
+
DEPENDENCIES
|
34
|
+
gene_pool
|
35
|
+
rake
|
36
|
+
shoulda
|
data/HISTORY.md
ADDED
@@ -0,0 +1,52 @@
|
|
1
|
+
## 1.0.0 (2012-10-21)
|
2
|
+
|
3
|
+
* Issue #10 Support WebSphereMQ V7
|
4
|
+
* Issue #11 Add GenePool dependency for ConnectionPool
|
5
|
+
* Include version
|
6
|
+
|
7
|
+
## 0.11.2 (2011-06-01)
|
8
|
+
|
9
|
+
* Issue #8 Add ability to set Producer delivery mode using a Symbol
|
10
|
+
* Include ActiveMQ InVM working example along with Log4J properties file
|
11
|
+
|
12
|
+
## 0.11.1 (2011-05-25)
|
13
|
+
|
14
|
+
* Fixes the condition where a bad session keeps being re-used in a session pool.
|
15
|
+
It is now removed from the pool anytime a JMS exception has occurred
|
16
|
+
|
17
|
+
## 0.11.0 (2011-04-18)
|
18
|
+
|
19
|
+
* Compatibility with JRuby 1.6
|
20
|
+
* I hate doing this, but unfortunately there is a small breaking change in this release:
|
21
|
+
** We can no longer pass symbols into the following methods:
|
22
|
+
*** jms_delivery_mode
|
23
|
+
*** jms_delivery_mode=
|
24
|
+
** Just rename existing uses of the above methods to:
|
25
|
+
*** jms_delivery_mode_sym
|
26
|
+
*** jms_delivery_mode_sym=
|
27
|
+
* Added Session Pool - requires GenePool as a dependency if used
|
28
|
+
* Generate warning log entry for any parameters not known to the ConnectionFactory
|
29
|
+
* Use java_import for all javax.jms classes
|
30
|
+
** Rename all Java source files to match new names
|
31
|
+
|
32
|
+
## 0.10.1 (2011-02-21)
|
33
|
+
|
34
|
+
* Fix persistence typo and add message test cases
|
35
|
+
|
36
|
+
## 0.10.0 (2011-02-10)
|
37
|
+
|
38
|
+
* Refactoring interface
|
39
|
+
|
40
|
+
## 0.9.0 (2011-01-23)
|
41
|
+
|
42
|
+
* Revised API with cleaner interface
|
43
|
+
* Publish GEM
|
44
|
+
|
45
|
+
## 0.8.0 (2011-01-22)
|
46
|
+
|
47
|
+
* Release to the wild for general use
|
48
|
+
|
49
|
+
## 2008, 2009, 2010
|
50
|
+
|
51
|
+
* Previously known as jms4jruby
|
52
|
+
* Running in production at an enterprise processing a million messages a day
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright 2008, 2009, 2010, 2011 J. Reid Morrison, Inc.
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,205 @@
|
|
1
|
+
## jruby-jms
|
2
|
+
|
3
|
+
* http://github.com/reidmorrison/jruby-jms
|
4
|
+
|
5
|
+
### Introduction
|
6
|
+
|
7
|
+
jruby-jms attempts to "rubify" the Java JMS API without
|
8
|
+
compromising performance. It does this by sprinkling "Ruby-goodness" into the
|
9
|
+
existing JMS Java interfaces, I.e. By adding Ruby methods to the existing
|
10
|
+
classes and interfaces. Since jruby-jms exposes the JMS
|
11
|
+
Java classes directly there is no performance impact that would have been
|
12
|
+
introduced had the entire API been wrapped in a Ruby layer.
|
13
|
+
|
14
|
+
In this way, using regular Ruby constructs a Ruby program can easily
|
15
|
+
interact with JMS in a highly performant way. Also, in this way you are not
|
16
|
+
limited to whatever the Ruby wrapper would have exposed, since the entire JMS
|
17
|
+
API is available to you at any time.
|
18
|
+
|
19
|
+
### Install
|
20
|
+
|
21
|
+
jgem install jruby-jms
|
22
|
+
|
23
|
+
### Simplification
|
24
|
+
|
25
|
+
One of the difficulties with the regular JMS API is that it uses completely
|
26
|
+
separate classes for Topics and Queues in JMS 1.1. This means that once a
|
27
|
+
program writes to a Queue for example, that without modifying the source code
|
28
|
+
the program it cannot write to a topic.
|
29
|
+
|
30
|
+
jruby-jms fixes this issue by allowing you to have a Consumer or Producer that
|
31
|
+
is independent of whether it is producing or consuming to/from
|
32
|
+
or a Topic or a Queue. The complexity of which JMS class is used is taken care
|
33
|
+
of transparently by jruby-jms.
|
34
|
+
|
35
|
+
## Concepts & Terminology
|
36
|
+
|
37
|
+
### Java Message Service (JMS) API
|
38
|
+
|
39
|
+
The JMS API is a standard interface part of Java EE 6 as a way for programs to
|
40
|
+
send and receive messages through a messaging and queuing system.
|
41
|
+
|
42
|
+
For more information on the JMS API: http://download.oracle.com/javaee/6/api/index.html?javax/jms/package-summary.html
|
43
|
+
|
44
|
+
### Broker / Queue Manager
|
45
|
+
|
46
|
+
Depending on which JMS provider you are using they refer to their centralized
|
47
|
+
server as either a Broker or Queue Manager. The Broker or Queue Manager is the
|
48
|
+
centralized "server" through which all messages pass through.
|
49
|
+
|
50
|
+
Some Brokers support an in-JVM broker instance so that messages can be passed
|
51
|
+
between producers and consumers within the same Java Virtual Machine (JVM)
|
52
|
+
instance. This removes the need to make any network calls. Useful
|
53
|
+
for passing messages between threads in the same JVM.
|
54
|
+
|
55
|
+
### Connection
|
56
|
+
|
57
|
+
In order to connect to any broker the Client JMS application must create a
|
58
|
+
connection. In traditional JMS a ConnectionFactory is used to create connections.
|
59
|
+
In jruby-jms the JMS::Connection takes care of the complexities of dealing with
|
60
|
+
the factory class, just pass the required parameters to Connection.new and
|
61
|
+
jruby-jms takes care of the rest.
|
62
|
+
|
63
|
+
### Queue
|
64
|
+
|
65
|
+
A queue is used to hold messages. The queue must be defined prior to the message
|
66
|
+
being sent and is used to hold the messages. The consumer does not have to be
|
67
|
+
active in order to send messages.
|
68
|
+
|
69
|
+
### Topic
|
70
|
+
|
71
|
+
Instead of sending messages to a single queue, a topic can be used to publish
|
72
|
+
messages and allow multiple consumers to register for messages that match the
|
73
|
+
topic they are interested in
|
74
|
+
|
75
|
+
### Producer
|
76
|
+
|
77
|
+
Producers write messages to queues or topics
|
78
|
+
|
79
|
+
ActiveMQ Example:
|
80
|
+
|
81
|
+
```ruby
|
82
|
+
require 'rubygems'
|
83
|
+
require 'jms'
|
84
|
+
|
85
|
+
# Connect to ActiveMQ
|
86
|
+
config = {
|
87
|
+
:factory => 'org.apache.activemq.ActiveMQConnectionFactory',
|
88
|
+
:broker_url => 'tcp://localhost:61616',
|
89
|
+
:require_jars => [
|
90
|
+
"~/Applications/apache-activemq-5.7.0/activemq-all-5.7.0.jar",
|
91
|
+
"~/Applications/apache-activemq-5.5.0/lib/optional/log4j-1.2.17.jar"
|
92
|
+
]
|
93
|
+
}
|
94
|
+
|
95
|
+
JMS::Connection.session(config) do |session|
|
96
|
+
session.producer(:queue_name => 'ExampleQueue') do |producer|
|
97
|
+
producer.send(session.message("Hello World"))
|
98
|
+
end
|
99
|
+
end
|
100
|
+
```
|
101
|
+
|
102
|
+
### Consumer
|
103
|
+
|
104
|
+
Consumers read message from a queue or topic
|
105
|
+
|
106
|
+
ActiveMQ Example:
|
107
|
+
|
108
|
+
```ruby
|
109
|
+
require 'rubygems'
|
110
|
+
require 'jms'
|
111
|
+
|
112
|
+
# Connect to ActiveMQ
|
113
|
+
config = {
|
114
|
+
:factory => 'org.apache.activemq.ActiveMQConnectionFactory',
|
115
|
+
:broker_url => 'tcp://localhost:61616',
|
116
|
+
:require_jars => [
|
117
|
+
"~/Applications/apache-activemq-5.7.0/activemq-all-5.7.0.jar",
|
118
|
+
"~/Applications/apache-activemq-5.5.0/lib/optional/log4j-1.2.17.jar"
|
119
|
+
]
|
120
|
+
}
|
121
|
+
|
122
|
+
JMS::Connection.session(config) do |session|
|
123
|
+
session.consume(:queue_name => 'ExampleQueue', :timeout=>1000) do |message|
|
124
|
+
p message
|
125
|
+
end
|
126
|
+
end
|
127
|
+
```
|
128
|
+
|
129
|
+
## Overview
|
130
|
+
|
131
|
+
jruby-jms is a complete JRuby API into the Java Messaging Specification (JMS) V1.1
|
132
|
+
followed by several JMS Providers.
|
133
|
+
|
134
|
+
## Threading
|
135
|
+
|
136
|
+
A JMS::Connection instance can be shared between threads, whereas a session,
|
137
|
+
consumer, producer, and any artifacts created by the session should only be
|
138
|
+
used by one thread at a time.
|
139
|
+
|
140
|
+
For consumers, it is recommended to create a session for each thread and leave
|
141
|
+
that thread blocked on Consumer.receive. Or, even better use Connection.on_message
|
142
|
+
which will create a session, within which any message received from the specified
|
143
|
+
queue or topic will be passed to the block.
|
144
|
+
|
145
|
+
## Logging
|
146
|
+
|
147
|
+
jruby-jms detects the logging available in the current environment.
|
148
|
+
When running under Rails it will use the Rails logger, otherwise it will use the
|
149
|
+
standard Ruby logger. The logger can also be replaced by calling Connection.logger=
|
150
|
+
|
151
|
+
## Dependencies
|
152
|
+
|
153
|
+
### JMS V1.1 Provider
|
154
|
+
|
155
|
+
In order to communicate with a JMS V 1.1 provider jruby-jms needs the jar files supplied
|
156
|
+
by the JMS provider. As in the examples above the jar files can be specified in
|
157
|
+
the configuration element :require_jars. Otherwise, the jars must be explicitly
|
158
|
+
required in the Ruby code:
|
159
|
+
|
160
|
+
```ruby
|
161
|
+
require "~/Applications/apache-activemq-5.7.0/activemq-all-5.7.0.jar"
|
162
|
+
```
|
163
|
+
|
164
|
+
### JRuby
|
165
|
+
|
166
|
+
jruby-jms has been tested against JRuby 1.5.1, 1.6.1, and 1.7.0 RC2
|
167
|
+
|
168
|
+
## Contributing
|
169
|
+
|
170
|
+
Once you've made your great commits:
|
171
|
+
|
172
|
+
1. [Fork](http://help.github.com/forking/) jruby-jms
|
173
|
+
2. Create a topic branch - `git checkout -b my_branch`
|
174
|
+
3. Push to your branch - `git push origin my_branch`
|
175
|
+
4. Create an [Issue](http://github.com/reidmorrison/jruby-jms/issues) with a link to your branch
|
176
|
+
5. That's it!
|
177
|
+
|
178
|
+
## Meta
|
179
|
+
|
180
|
+
* Code: `git clone git://github.com/reidmorrison/jruby-jms.git`
|
181
|
+
* Home: <http://github.com/reidmorrison/jruby-jms>
|
182
|
+
* Bugs: <http://github.com/reidmorrison/jruby-jms/issues>
|
183
|
+
* Gems: <http://rubygems.org/gems/jruby-jms>
|
184
|
+
|
185
|
+
This project uses [Semantic Versioning](http://semver.org/).
|
186
|
+
|
187
|
+
## Author
|
188
|
+
|
189
|
+
Reid Morrison :: reidmo@gmail.com :: @reidmorrison
|
190
|
+
|
191
|
+
## License
|
192
|
+
|
193
|
+
Copyright 2008 - 2012 J. Reid Morrison
|
194
|
+
|
195
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
196
|
+
you may not use this file except in compliance with the License.
|
197
|
+
You may obtain a copy of the License at
|
198
|
+
|
199
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
200
|
+
|
201
|
+
Unless required by applicable law or agreed to in writing, software
|
202
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
203
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
204
|
+
See the License for the specific language governing permissions and
|
205
|
+
limitations under the License.
|