Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into ignore-unrecognized
- Loading branch information
Showing
222 changed files
with
23,382 additions
and
23,766 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
[bumpversion] | ||
current_version = 0.6.2 | ||
current_version = 0.6.3 | ||
commit = True | ||
tag = True | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
* test=auto | ||
|
||
# Specify lf for all source files | ||
*.py text eol=lf | ||
*.cpp text eol=lf | ||
*.c text eol=lf | ||
*.h text eol=lf | ||
|
||
*.xml text eol=lf | ||
*.txt text | ||
.gitignore text eol=lf | ||
.gitattributes text eol=lf |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,40 +1,40 @@ | ||
This example of using JPype and JMS contributed by David Morgenthaler | ||
Here is the message that accompanied it when he posted it on comp.lang.python : | ||
============================================================================= | ||
Your question intrigued me, so I gave it a try. And the anwer (at | ||
least for JMS Publish/Subscribe TextMessages) is YES. | ||
It includes: | ||
- Java classes for a publisher (src/messaging/JpypePublisher) and a | ||
subscriber (src/messaging/JpypeSubscriber). These Java classes, which | ||
do most of the dirty work of connecting to the JMS server, are used | ||
from python via jpype. | ||
- Java classes that test the publisher and subscriber | ||
(src/messaging/testJpepePublisher, src/messaging/testJpypeSubscriber) | ||
- A Java interface that is used by python for the JProxy | ||
- python scripts for publishing and subscribing | ||
- An build.xml for ant to build and run the Java classes | ||
The Java and python publishers and subscribers work in any reasonable | ||
combination (J pub/J sub, J pub/p sub, p pub/p sub, p pub/J sub, and | ||
even with multiple subscribers) | ||
Copy conveniently located folder. You'll find a build.xml for | ||
ant to build the Java. You'll have to edit (in the testers and in the | ||
python scripts) the naming and connection factory stuff for your | ||
situation. You'll also have to edit the python scripts to correctly | ||
locate your jvm and other classpath information. Once you're correctly | ||
configured, you can use ant to build and/or execute the Java (type | ||
"ant help"). And once the Java is built, you can try the python | ||
versions. | ||
I can't imagine that this approach wouldn't work for JMS Queues. And | ||
while I haven't tested it, I don't see anything preventing the use of | ||
other message types (BinaryMessage, ObjectMessage,...). | ||
BTW, I don't detect any noticable slowdown in the python versions from | ||
the Java versions (probably because of the strightforward conversion | ||
of python strings to Java Strings). | ||
This example of using JPype and JMS contributed by David Morgenthaler | ||
|
||
Here is the message that accompanied it when he posted it on comp.lang.python : | ||
============================================================================= | ||
Your question intrigued me, so I gave it a try. And the anwer (at | ||
least for JMS Publish/Subscribe TextMessages) is YES. | ||
|
||
It includes: | ||
- Java classes for a publisher (src/messaging/JpypePublisher) and a | ||
subscriber (src/messaging/JpypeSubscriber). These Java classes, which | ||
do most of the dirty work of connecting to the JMS server, are used | ||
from python via jpype. | ||
- Java classes that test the publisher and subscriber | ||
(src/messaging/testJpepePublisher, src/messaging/testJpypeSubscriber) | ||
- A Java interface that is used by python for the JProxy | ||
- python scripts for publishing and subscribing | ||
- An build.xml for ant to build and run the Java classes | ||
|
||
The Java and python publishers and subscribers work in any reasonable | ||
combination (J pub/J sub, J pub/p sub, p pub/p sub, p pub/J sub, and | ||
even with multiple subscribers) | ||
|
||
Copy conveniently located folder. You'll find a build.xml for | ||
ant to build the Java. You'll have to edit (in the testers and in the | ||
python scripts) the naming and connection factory stuff for your | ||
situation. You'll also have to edit the python scripts to correctly | ||
locate your jvm and other classpath information. Once you're correctly | ||
configured, you can use ant to build and/or execute the Java (type | ||
"ant help"). And once the Java is built, you can try the python | ||
versions. | ||
|
||
I can't imagine that this approach wouldn't work for JMS Queues. And | ||
while I haven't tested it, I don't see anything preventing the use of | ||
other message types (BinaryMessage, ObjectMessage,...). | ||
|
||
BTW, I don't detect any noticable slowdown in the python versions from | ||
the Java versions (probably because of the strightforward conversion | ||
of python strings to Java Strings). | ||
|
||
============================================================================= |
Oops, something went wrong.