> In a way, it is analogous to the SQL specification(s) and
> implementations
In other words "Yes, you can write portable JMS code if you know what
you're doing"...
> 1) I can't make anything work on JRUn JMS
I've sent you corrections to your JMS example code off-list. As I've
said, I have code that runs unchanged on both JRun and Fiorano MQ (you
just change the provider URL - which is the host and port
combination).
> 2) OpenJMS has some very nice, working examples, with source (and a lot
> of proprietary jars). These run fine on OpenJMS but I have been
> unsuccessful porting any of them to JRun
I'm sorry that the examples provided with OpenJMS are so proprietary
that they only run on OpenJMS...
> So, what you stated above ("if you program against the javax.jms spec")
> you will likely have compatibility -- but it seems that very few people
> do!
You need to bear in mind that writing Java to manipulate JMS is not
exactly a novice task...
> lifted from the livedocs JRun JMS code fragment:
>
> private String providerurl = new String("localhost:2918");
>
> lifted from an OpenJMS code fragment:
>
> int jndiPort = 1099;
> String jndiHost = "localhost";
A provider URL is a host / port pair so I'd read these as pretty much
equivalent - and an indication that OpenJMS just uses a different
default port (not surprising - we configure Fiorano MQ to use a
variety of different ports).
> I realize that these are examples. meant to illustrate the code, rather
> than getting params from a config file -- but a newbie usually starts
> with examples like these and they have built-in incompatibilities and
> bad coding practices -- and, I guess the newbie is supposed to
> intuitively know this.
That's the problem with trying to start with someone else's example
code instead of reading and understanding all the docs and writing the
code yourself from scratch... :)
Seriously tho' an example is no use unless you understand what the
examples are trying to illustrate (in my experience, most examples are
really only trying to illustrate something that is explained in the
docs - rather than trying to be a replacement for the docs).
> Yeah, but you know what you're doing :).
If it's any consolation, I've had to spend a lot of time reading the
javax.jms API documentation...
--
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
