Thanks Brindy.
Saminda
On Thu, Aug 14, 2008 at 4:32 PM, brindy <[EMAIL PROTECTED]> wrote:
>
> Hi Saminda,
>
> #3 is just a pleasant side effect of the service consumption, nothing that
> needs to be done by this project. For instance, after I register my
> service
> in the usual OSGi way... eve
Hi Saminda,
#3 is just a pleasant side effect of the service consumption, nothing that
needs to be done by this project. For instance, after I register my service
in the usual OSGi way... every other bundle in the OSGi framework can access
it, Axis2 can expose it as a web service and (for exampl
Hi Brindy,
1) No dependency on any specific web service implementation
> 2) The service is available natively to other OSGi bundles
> 3) Other remoting mechanisms (in addition to or instead of web services,
> e.g. AMF) can use the same mechanism
>
> So I guess I am looking for confirmation this is
Hi,
I'd say dont do it this way
AXIS 1.4 is no longer being maintained
you could use base64 encoding with axis 1.4
Cheers,
Wolfgang
--- On Thu, 8/14/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Subject: Axis 1.4 and MTOM
> To: axis-dev@ws.apach
Hi all,
I've been exchanging a view comments with Davanum who asked me to post this
here.
I like the work done so far on integrating OSGi with Axis2 but for it to be
really useful, bundles should not have to be coupled to Axis2. I believe
this is the plan anway, but just thought I should shar
Hi group,
I am currently trying to implement an axis 1.4 web service (with a
client) with attachments using MTOM.
Somewhere it was said, that this is also possible with axis 1.4. But
unfortunately I don't get it working. I'm sending the attachments from
the server side via MTOM, but I can't
