Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of bimargulies@gmail.com
 designates 209.85.214.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=BzQnNn5qLGFvlHNhQdzCl50zqWWvFtxUWRVTOFsrWUPNGX3ASf2O0DIfCPcMWu8w1J
         +ciyycNaqPEdJxNf/IlK00UaQRdv0o+EVCfsw4oyABnR/9ZJU0gAgqIBsZC2yMPNOkjg
         fKOicXjNafFYOP6xbTO0Fm/yEh0vSqAtGwU7o=
MIME-Version: 1.0
Date: Sat, 2 Oct 2010 14:10:28 -0400
Message-ID: <AANLkTimqo2CUd0NS3HDWJ4WQW-Wg2YmbNKUDWEOUdpg5@mail.gmail.com>
Subject: More underinformed musing about JMS (JMS+Simple+Aegis)?
From: Benson Margulies <bimargulies@gmail.com>
To: CXF Dev <dev@cxf.apache.org>
Content-Type: text/plain; charset=UTF-8

Thanks for the help over on users.

I was having the following thought.

For some time now, I've been religiously using JAX-WS/JAX-B for
services I build at the day job, on the theory that this gives me
maximum digestibility for possible interoperation.

Recently, I've been working on setting up some components where
interop is not very interesting, but development efficiency is. The
penny dropped; this is howcome the long-ago XFire group ended up
inventing Simple/Aegis. Instead of 'yea, it will probably work if you
use the same SEI on both ends,' it's 'Absolutely: use the same SEI
(and beans, of course) on both sides and just don't worry about WSDL
files and code generators.'

OK, wonderful. Could I make this work with JMS?

I suppose I should try it and see what happens, but I wonder what the
experts think of the idea.