axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka" <>
Subject RE: [jira] Commented: (AXIS2-65) Management support via JMX
Date Fri, 19 Aug 2005 11:07:45 GMT
For me this seems a policy issue for me.


First I think we have no problem of receiving messages with attachments w/
or w/o MTOM. So enabling MTOM means, we also concern about the OUT path.


Lets take the options we have. We can either enable MTOM for the whole
system or per service basis. Enabling for the whole system is too rigid,
IMO. The best option is WS - Policy. But since we don't have it now in Axis2
let's have some other solution. I'd like to propose the following


Lets talk about any client calling Axis2 server. Since Axis2 server can
handle anything, let's mandate the client to set a reference parameter, if
he can receive MTOM enabled attachments. This will enable the server to send
MTOM messages, if any, to the client. Client has the option of sending MTOM
attachments or not we have no problem with that.


What if, Axis2 client calls non-Axis2 server. I can't think of a solution
for this. 


So what do u all think abt it ? Comments ..





From: Thilina Gunarathne [] 
Sent: Thursday, August 18, 2005 7:35 PM
Subject: Re: [jira] Commented: (AXIS2-65) Management support via JMX


This is something to do when sending messages (only in outflow).... Whether
to send MTOMised messages or base64 encoded only... We can get this done
easily If we can set the enableMTOM property per service basis. 





On 8/19/05, Deepal Jayasinghe <> wrote: 

Hi Thilina;


I can not understand how do you enable MTOM per service basis , as I know
you are selecting MTOM basid buider at the transport by using MIME headers ,
and you can only identify the service when you come to dispatch phase. So
could you please explain what do you mean by enebeling MTOM perservice basis



~Future is Open~



----- Original Message ----- 

From: Thilina <>  Gunarathne 


Sent: Tuesday, August 16, 2005 3:16 AM

Subject: Re: [jira] Commented: (AXIS2-65) Management support via JMX


Hi all,

I hope configuring MTOM and file caching per service basis is also meant by
the follwoing statement.

 > 5.  it provide a way to edit parameters in each level (Global , service ,
opearation , module ,  

> handlers , Transport sender and recivers)

Sending this note just to make sure..... :)




On 8/16/05, Deepal Jayasinghe (JIRA) <
<> > wrote: 


Deepal Jayasinghe commented on AXIS2-65:

I like to have the following features in JMX 

1.   All the functionality provied by axis2 web admin should be there 
2.   It should be able to change global handler chain
3.   It should be able to remove service
4   it should be able to turn off an opeartion of a service 
5.  it provide a way to edit parameters in each level (Global , service ,
opearation , module , handlers , Transport sender and recivers) 
6. Engaging and disengaging module (s)

> Management support via JMX 
> --------------------------
>          Key: AXIS2-65
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: New Feature
>   Components: deployment
>     Reporter: Srinath Perera
>     Priority: Minor 


This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: 

"May the SourcE be with u" 

"May the SourcE be with u" 

View raw message