On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
I believe so but maybe it never worked correctly. Maybe I forgot to do
"jms.$PROPERTY" and just did "$PROPERTY" so it never complained about it.
Most likely is we used to just ignore the parameters so it silently
worked :) We should be able to
I believe so but maybe it never worked correctly. Maybe I forgot to do
"jms.$PROPERTY" and just did "$PROPERTY" so it never complained about it.
James.Strachan wrote:
>
> On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
>>
>> it used to work in v3
>
> Of the C# client? Are you sure?
>
> Note
On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
it used to work in v3
Of the C# client? Are you sure?
Note that the plumbing is in the C# code to deal with URI arguments;
but AFAIK we've not wired in all of the available properties yet. e.g.
DispatchAsync should be supported; though there's
it used to work in v3
James.Strachan wrote:
>
> The C# client doesn't support the various properties that the Java
> client supports
>
> On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
>>
>> When using the MNS C# client and using the following URL:
>>
>> tcp://localhost:61616?jms.useAsyncSen
The C# client doesn't support the various properties that the Java
client supports
On 2/13/07, sparky2708 <[EMAIL PROTECTED]> wrote:
When using the MNS C# client and using the following URL:
tcp://localhost:61616?jms.useAsyncSend=true&jms.dispatchAsync=true
I get an error message that says:
When using the MNS C# client and using the following URL:
tcp://localhost:61616?jms.useAsyncSend=true&jms.dispatchAsync=true
I get an error message that says:
"no such property useasyncsend on class: Connection"
Am I forming the URL correctly?
--
View this message in context:
http://www.nabb
