Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <26417847.post@talk.nabble.com>
Date: Wed, 18 Nov 2009 15:37:22 -0800 (PST)
From: JeffSmith <y24jds@yahoo.com>
To: users@activemq.apache.org
Subject: Re: Compact Framework Support for NMS
In-Reply-To: <1258584427.4214.3.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <26417129.post@talk.nabble.com>
 <1258584427.4214.3.camel@localhost>


Wow - ok... Thanks for the quick response.

We were just in the process of designing a large application rewrite effort
on using ActiveMQ as our message provider with the need for a mix of Windows
CE handheld devices and full Windows XP devices at our many locations.

What are our options for these Windows CE devices?  I just started reading
about Apache Camel - but I'm not sure I fully understand it yet.  I know
that OpenMQ has a product called UMS which is a middle layer that accepts
HTTP requests and changes them to be messaging requests.  I haven't figured
out if that is the sort of thing Camel does as well or not...  I think that
sort of thing would work for us but I'm not sure if request/reply messaging
is correctly supported when doing HTTP.  I believe IBM MQ Series has a
similar thing, but I'm not sure yet.

Is there some sort of ActiveMQ technique to accept these messaging requests
from other "non-standard" languages or systems?

Thanks - Jeff


Timothy Bish wrote:
> 
> On Wed, 2009-11-18 at 14:43 -0800, JeffSmith wrote:
>> Is CF 2.0 still supported for NMS?  I grabbed the latest subversion code
>> and
>> am having all sorts of issues getting it to compile for CF 2.0.  I tried
>> google searching and saw one change that said something about support was
>> removed.  Is that true?  If so, what are the alternatives?  If not, and
>> it
>> should be working, then I am having both nant and VS configuration issues
>> that I will post on here for help.
>> 
>> Thanks - 
>> 
>> Jeff
> 
> We've stopped supporting .NETCF in NMS.ActiveMQ due to the size on
> complexity of the client and the limitations that the CF places on us.
> There is a plan in place to eventually release an NMS.Stomp client that
> is more suitable for use in resource constrained environments
> where .NETCF apps run.
> 
> Regards
> Tim.
> 
> 
> -- 
> Tim Bish
> http://fusesource.com
> http://timbish.blogspot.com/
> 
> 
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/Compact-Framework-Support-for-NMS-tp26417129p26417847.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.