[esb-java-dev] Joint Use case of WSAS and ESB

Davanum Srinivas dims at wso2.com
Mon Aug 27 17:25:06 PDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Team,

Am looking for a good joint use case of both WSAS and ESB together (in a production environment, needless to say! :) So
far the best i came up with was the following:

Deploy Axis1 legacy service AND a newer Axis2 Service on WSAS and drop in ESB jars to implement versioning/routing based
on some on-the-wire information (say SOAP12 goes to Axis2?). Am trying to think how we could encourage our customers to
upgrade from Axis1 to WSAS and a good versioning story seems to be something that will help folks decide to upgrade

Thoughts? Ideas? Comments? Any better scenarios?

In addition to settling down on one or a few scenarios, Can we please make sure that the next versions of WSAS and ESB
can co-exist say in the same servlet container (same war) and w/o opening additional sockets.

thanks,
dims

- --
Davanum Srinivas (dims at wso2.com)
Director, Customer Engagements, WSO2 (http://wso2.com)
Yahoo IM: dims Cell/Mobile: +1 (508) 415 7509
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFG02tigNg6eWEDv1kRAt5qAJ92MOxObBNe8F4ZJqE2gmF7UVWLGQCgzpIc
qCZOwCsndAKMrF7zjbTf+7M=
=8xqS
-----END PGP SIGNATURE-----




More information about the Esb-java-dev mailing list