Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates
 66.249.92.173 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=kLA/JRSRD7jb4lzfGdZmU0NMVJES/2vNzeMMJ0KxMwzhZxX4q23ouu/QGJFbGUNSZzOj66Lj6MudchAmOSX850IcyGxQKv4K0ZGAxFZixDkd976cfiCE91WCezqCbBxrKAxPA50oauo1aKU3CjpCllucftuOECRPZJrYtJMRVlI=
Message-ID: <af2843cd0609251548j1daa94bdn7a89074dc0451994@mail.gmail.com>
Date: Mon, 25 Sep 2006 18:48:58 -0400
From: "Hiram Chirino" <hiram@hiramchirino.com>
Sender: chirino@gmail.com
To: activemq-users@geronimo.apache.org
Subject: Re: C# NMS client
In-Reply-To: <6495629.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6493106.post@talk.nabble.com> <6493191.post@talk.nabble.com>
	 <6494592.post@talk.nabble.com> <6495629.post@talk.nabble.com>

On 9/25/06, Rob Lugt <robert.lugt@cheynecapital.com> wrote:
>
>
> MikeyBoy wrote:
> >
> > Hi Rob that's for the reply. Somehow I assumed NMS could be used as a
> > stand-alone client. I looked at the ActiveMQ Windows binary and see it
> > contains no DLLs, just JARs. So do I need to build an ActiveMQ DLL
> > callable from .net?  TIA, M
> >
>
> Hi Mike
>
> No, the activemq-dotnet DLL contains two top-level namespaces: NMS and
> ActiveMQ; I'm not sure of the rationale for this. If you view the DLL in

The reason for the 2 namespaces is that the interfaces in NMS name
space can be implemented by other messaging systems and is not
ActiveMQ specific.

The ActiveMQ namespace has our implementation of the interfaces in the
NMS namespace.  If you use an object factory that creates the initial
ConnectionFactory for you, then your application code can stay
decoupled from ActiveMQ since it only needs to use the interfaces in
the NMS namespace.  But that can be a little tricky to setup, so most
folks just import the ConnectionFactory from activemq namespace
directly.

> VS.Net object browser you'll see all the namespaces it contains.
>
> You simply need to reference the DLL (which you're already doing I believe)
> and include the line:
>
> using ActiveMQ;
>
> in your source.
>
> Hope this helps
> Regards
> ~Rob
>
> --
> View this message in context: http://www.nabble.com/C--NMS-client-tf2333701.html#a6495629
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
Regards,
Hiram

Blog: http://hiramchirino.com