Hi Ong,
Yes, the idea you mention is precisely one of the scenarios we are
implementing, as a SOAP interface on our iBus//Mobile product
(http://www.softwired-inc.com/products/mobile/mobile.html).
We already have the basic prototypes running; iBus//Mobile uses a
standard JMS provider - e.g. the iBus//MessageServer, BEA Weblogic.
Using this architecture, we can integrate diverse clients (mobile
devices, Java clients, non-Java clients) with the JMS backend services
with the SOAP & .NET services. All using the JMS as the consistent,
end-to-end paradigm.
iBus//Mobile R3.0 will be released 1Q 2002, with the above feature in
place.
Ciao
Rupal
Ong Boon Pang wrote:
>
> Hi,
>
> This is the idea I have... A soap client sends a soap message requests
> to a JMS server's inQueue/Topic using standard soap object. On the server
> end, A soap service listen to the JMS server for a soap message. Process
> the request, send its reply to JMS server outQueue/Topic. Client picks up
> the reply using standard soap object.
>
> Have anyone tried to connect the apache SOAP-Message portion to
> any JMS server?
>
> This will complete the SOAP message portion for adapting to MOM model.
> Like the latest Message EJB standard. This is how we can get away from
> using most of the EJB features. Hence, avoiding paying handsome amount
> for a EJB Application Server like iPlanet, WebLogic in most cases.
>
> I am still new in Apache SOAP (only 2/3 weeks), however the message part
> of soap that can talk to a smtp / pop server makes JMS not too impossible.
>
> Please help.
>
> cheers,
> Boon Pang
> [EMAIL PROTECTED]
--
Rupal Majmudar
Software Architect
[EMAIL PROTECTED]
Softwired Inc. www.softwired-inc.com
Technoparkstrasse 1, CH-8005 Zurich, Switzerland
tel +41-1-4452370 * fax +41-1-4452372
* e2e Java Messaging, Pure and Simple. *
** Latest news: http://www.softwired-inc.com/news/news.html **
*** Go Wireless: Shipping NOW: iBus//Mobile 2.1 ***
