[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster-devel] Announce: JMS

To: xmlblaster-devel at server.xmlblaster.org
Subject: Re: [xmlblaster-devel] Announce: JMS
From: Michele Laghi <laghi at swissinfo.org>
Date: Wed, 01 Oct 2003 11:38:10 +0200
In-reply-to: <3F79CF98.2070105 at swissinfo.org>
Organization: Eclettic Technologies
References: <3F733923.7000408 at swissinfo.org> <1064564753.5143.41.camel at pra> <3F7466FF.2020100 at swissinfo.org> <1064911065.10722.30.camel at pra> <3F79CF98.2070105 at swissinfo.org>
Reply-to: xmlblaster-devel at server.xmlBlaster.org
Sender: owner-xmlblaster-devel at server.xmlBlaster.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210

Hi,

> ...

It is clear to me how to handle that in Destination but I don't know how to handle that in a portable way in the ConnectionFactory. My idea was to put the names of these properties in ConnectionMetaData and then set these vendor specific properties in the Destination objects

Of course that was not the idea. These should not be set by the Destination but by the MessageProducer and MessageConsumer

Michele

References:
- [xmlblaster-devel] Announce: JMS
  - From: Michele Laghi <laghi at swissinfo.org>
- Re: [xmlblaster-devel] Announce: JMS
  - From: Peter Antman <pra at mint.se>
- Re: [xmlblaster-devel] Announce: JMS
  - From: Michele Laghi <laghi at swissinfo.org>
- Re: [xmlblaster-devel] Announce: JMS
  - From: Peter Antman <pra at mint.se>
- Re: [xmlblaster-devel] Announce: JMS
  - From: Michele Laghi <laghi at swissinfo.org>

Prev by Date: Re: [xmlblaster-devel] Socket test with thread leak?
Next by Date: Re: [xmlblaster-devel] Socket test with thread leak?
Previous by thread: Re: [xmlblaster-devel] Announce: JMS
Next by thread: Re: [xmlblaster-devel] Socket test with thread leak?
Index(es):
- Date
- Thread