Beside of a general interest about what's going on behind the scenes -
can you tell me why you want to use our proprietary classes instead of
the standard way, JNDI?
--
Andreas Mueller, [EMAIL PROTECTED], IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ, JMS Enterprise Messaging System, http://www.swiftmq.com
-----------------------------------------------------------------------
Support SwiftMQ! PLEASE vote for SwiftMQ as "Best Java Messaging Tool":
http://www.sys-con.com/java/readerschoice2001/
-----Original Message-----
From: Nathan Phelps <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Date: Tue, 30 Jan 2001 22:43:58 -0600
Subject: [developers] Using the com.swiftmq classes instead of JNDI?
>
> Well, I did a bit more looking concerning this topic, but haven't made
> it
> much further. I can figure out what classes to use but have absolutely
> no
> clue as to what arguments the methods expect. I cannot find any
> documentation of these classes at all, which doesn't surprise me since
> they
> are implementation classes. Anyway, can anyone provide me with any
> information at all? I didn't have much luck with my first post which I
> have
> included below.
>
> Thanks,
>
> Nathan Phelps
>
> -----Original Message-----
> From: Nathan Phelps [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 30, 2001 12:29 AM
> To: [EMAIL PROTECTED]
> Subject: [developers] Using the com.swiftmq classes instead of JNDI?
>
>
> How can I directly use the com.swiftmq classes and forgo JNDI?
>
> I do realize that looking up resources via JNDI is the best way to
> handle
> these situations. However, I'm interested in what exactly is going on
> behind the scenes. Specifically, how would the following code (from the
> samples) be implemented using the com.swiftmq classes instead of the
> JNDI
> code found in SampleUtilities?
>
> // Topics Sample
> topicConnectionFactory = (TopicConnectionFactory)
> SampleUtilities.jndiLookup(SampleUtilities.TOPICCONFAC);
> topicConnection = topicConnectionFactory.createTopicConnection();
> topic = (Topic) SampleUtilities.jndiLookup(topicName);
> topicSession = topicConnection.createTopicSession(false,
> Session.AUTO_ACKNOWLEDGE);
>
> // Queue Sample
> queueConnectionFactory = (QueueConnectionFactory)
> SampleUtilities.jndiLookup(SampleUtilities.QUEUECONFAC);
> queueConnection =
> queueConnectionFactory.createQueueConnection();
> queue = (Queue) SampleUtilities.jndiLookup(queueName);
> queueSession = queueConnection.createQueueSession(false,
> Session.AUTO_ACKNOWLEDGE);
>
> Thanks,
>
> Nathan
>
> P.S. Again, this is to satisfy my curiosity. I would certainly use
> JNDI in
> production.
>
> ------------------------------------------------------
> SwiftMQ developers mailing list * http://www.swiftmq.com
> To unsubscribe from this list, send an eMail to
> [EMAIL PROTECTED] and write in the body of your message:
> UNSUBSCRIBE developers <your-email-address>
> Archive: http://www.mail-archive.com/developers@mail.iit.de/
>
>
> ------------------------------------------------------
> SwiftMQ developers mailing list * http://www.swiftmq.com
> To unsubscribe from this list, send an eMail to
> [EMAIL PROTECTED] and write in the body of your message:
> UNSUBSCRIBE developers <your-email-address>
> Archive: http://www.mail-archive.com/developers@mail.iit.de/
>
>
>
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
