-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hua,
To be honest, Axis2 at the moment is a bit big for your use case. We may be
looking at the smaller size use case in the
future, but right now, take a look at Apache Muse, they have a mini soap engine
(http://ws.apache.org/muse/docs/2.1.0/tutorial/04-review-artifacts-mini.html)
- -- dims
Liu, Hua (Maria) wrote:
| Hi,
|
|
|
| We have a running OSGi platform hosting a bunch of OSGi services, and
| would like to expose some of the OSGi services as web services using
| Axis2. The way we want to do this is to wrap Axis2 as an OSGi bundle and
| load into the platform, and this Axis2 bundle provides an interface that
| allows other OSGi services to expose/register themselves as web
| services. As a result, the same instance of a service is used for both
| SOAP invocations from remote clients and java method calls from OSGi
| services on the same machine.
|
|
|
| Since we also have very rigid requirements on small footprint including
| disk spaces and memory usage, we may only use a fraction of Axis2 to
| send/recv/parse SOAP messages and dispatch messages to appropriate
| services.
|
|
|
| So, how we can customize Axis2 to meet our needs? Which jar files we can
| remove? And, how to wrap Axis2 as an OSGi bundle?
|
|
|
| Thanks in advance,
|
| Hua
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFHzxlfgNg6eWEDv1kRAtNNAJ0ekQ04kjMM7cSXLkFdrqOA9EG1OgCfSEPb
Uqdx50VS4acmO/kM8s/uTXE=
=6Qri
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
