--
ask bjoern hansen, http://ask.netcetera.dk/ !try; do();
| [reply] |
I realize that this is a very old post, but I'll give my 0.2c anyway...
The only reason I would use Java over Perl is if my MQ Server requires a certain userID to be used for security reasons. With Perl and C, the userID of the client is passed on to the server and to the best of my knowledge, there's no getting around that. With Java, you can specify the userID of your liking.
Apart from that nuisance, I found that it's very easy to work with MQSeries through Perl and posted a write-up about it at usestrict.net
| [reply] |
There's a project where I work using MQSeries from Java. It is dog slow -- not because of MQSeries, but because of the design of the messages and the XML parsing involved in the Java code. The moral of this story is that it makes no difference which one you use as long as you pick a tool that you understand and can design well for. | [reply] |
In your case, I would recommend Java over perl for these
reasons:
(1) Its strong typing may coerce developers to maintain
a somewhat more maintainable design than perl.
(2) Java trades away power for readability; it's easy to
write horrible Java, but it's even easier to write horrible
perl.
(3) Typical 3rd-generation logic constructs are expected to
be used in Java. There's usually only one way to do it in
Java. This leaves fewer surprises for the maintainer. That
means people who aren't as familiar with Java can't do as
much damage to the program as a perl novice to a perl script.
If you don't need perl's power, by all means, use Java!
Be warned, however: automation and data processing are fun
in perl, while in Java they can be an absolute headache.
Rob | [reply] |
| [reply] |