Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 5669 invoked from network); 16 Oct 2006 11:18:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Oct 2006 11:18:27 -0000 Received: (qmail 91083 invoked by uid 500); 16 Oct 2006 11:18:25 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 90859 invoked by uid 500); 16 Oct 2006 11:18:23 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 90848 invoked by uid 99); 16 Oct 2006 11:18:23 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 04:18:23 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of pzfreo@gmail.com designates 64.233.166.178 as permitted sender) Received: from [64.233.166.178] (HELO py-out-1112.google.com) (64.233.166.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 04:18:21 -0700 Received: by py-out-1112.google.com with SMTP id x31so2331765pye for ; Mon, 16 Oct 2006 04:18:00 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jrs+H3ORJc69g0xW+yB8Z5LqsbATFeaxxZDwf8URnwtmewQkosYlRKfMzTaPSKxMUGS4jt9zRvzYdqVtWwZnjNUXo1YVdizWt0tHSw+VIXLq8HyeKB5lxybfoG6wNmdooxGoWbYuRAHQc5EfZzusGI5YRlH5bhgB9e37cpRMhLw= Received: by 10.35.121.12 with SMTP id y12mr12640195pym; Mon, 16 Oct 2006 04:18:00 -0700 (PDT) Received: by 10.35.71.15 with HTTP; Mon, 16 Oct 2006 04:18:00 -0700 (PDT) Message-ID: <88f5d710610160418v5ee47401te38cbade464e809e@mail.gmail.com> Date: Mon, 16 Oct 2006 12:18:00 +0100 From: "Paul Fremantle" To: synapse-dev@ws.apache.org, "axis-dev@ws.apache.org" Subject: XML/JMS MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I'd like to bring up the issue of XML/JMS. I've been looking for a simple demo shows off Synapse and WSRM together (since these are two of my key interests (-: ) And I figured it would make a really nice demo to take XML/JMS messages and then add a SOAP body, and send them out using WSRM. I guess to do this we need the "REST" equivalent in the JMS transport. (I guess in the JMS case we better not talk about REST or we'll be in serious trouble) Let's call it POX then. In fact we could do more than just XML. Imagine a TEXT message comes in that isn't even XML, we could wrap it in a CDATA wrapper and pop it into a single element in the message. If an binary message came in we could pop it into an MTOM holder, same with an ObjectMessage. With a MapMessage we could do a simple wrapper into a name-value pairs. Of course none of this would be a "standard" so we'd have to document it clearly, but it would be pretty neat way of dealing with non-SOAP messages coming over JMS. In fact, if we followed the same rules on outbound, then you could bridge between two organizations with no coding: Org1 JMS queue -> Synapse -> SOAP(XML, MTOM, Text, etc)/WSRM -> Synapse -> Org2 JMS queue. Paul -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org