Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 23970 invoked from network); 19 Aug 2005 11:13:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Aug 2005 11:13:48 -0000 Received: (qmail 36961 invoked by uid 500); 19 Aug 2005 11:13:40 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 36885 invoked by uid 500); 19 Aug 2005 11:13:40 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 36847 invoked by uid 99); 19 Aug 2005 11:13:39 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Aug 2005 04:13:39 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [209.68.5.16] (HELO relay02.pair.com) (209.68.5.16) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 19 Aug 2005 04:13:57 -0700 Received: (qmail 89172 invoked from network); 19 Aug 2005 11:13:33 -0000 Received: from unknown (HELO extremem) (unknown) by unknown with SMTP; 19 Aug 2005 11:13:33 -0000 X-pair-Authenticated: 220.247.192.12 From: "Eran Chinthaka" To: Subject: RE: [jira] Commented: (AXIS2-65) Management support via JMX Date: Fri, 19 Aug 2005 17:07:45 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C5A4E0.8A506000" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcWj+Zh2lnSVuNyYTdWyvIxyBJSMTwAp2knA In-Reply-To: X-Virus-Checked: Checked by ClamAV on apache.org Message-Id: <20050819111359.6729E10FB2B9@asf.osuosl.org> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C5A4E0.8A506000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 alternative. 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 .. Chinthaka _____ From: Thilina Gunarathne [mailto:csethil@gmail.com] Sent: Thursday, August 18, 2005 7:35 PM To: axis-dev@ws.apache.org 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. Thanx, ~Thilina 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 Thanks, Deepal ................................................................ ~Future is Open~ ----- Original Message ----- From: Thilina Gunarathne To: axis-dev@ws.apache.org 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..... :) ~Thilina On 8/16/05, Deepal Jayasinghe (JIRA) > wrote: [ http://issues.apache.org/jira/browse/AXIS2-65?page=comments#action_12318864 ] 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: http://issues.apache.org/jira/browse/AXIS2-65 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Reporter: Srinath Perera > Priority: Minor > > http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/JMX-front -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- "May the SourcE be with u" http://www.bloglines.com/blog/thilina http://webservices.apache.org/~thilina/ -- "May the SourcE be with u" http://www.bloglines.com/blog/thilina http://webservices.apache.org/~thilina/ ------=_NextPart_000_000C_01C5A4E0.8A506000 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 alternative.

 

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 ….

 

Chinthaka =

 

From: = Thilina Gunarathne [mailto:csethil@gmail.com]
Sent: Thursday, August = 18, 2005 7:35 PM
To: = axis-dev@ws.apache.org
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.

 

Thanx,

~Thilina

 

On 8/19/05, Deepal Jayasinghe <deepal@opensource.lk> 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

 

 

Thanks,
 Deepal
................................................................
~Future is Open~

 


 

----- Original Message ----- =

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..... = :)

 

~Thilina

 

On 8/16/05, Deepal Jayasinghe (JIRA) <jira@apache.org > wrote: =

   [ = http://issues.apache.org/jira/browse/AXIS2-65?page=3Dco= mments#action_12318864 ]

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: http://issues.apache.org/jira/browse/AXIS2-65
>      Project: Apache Axis 2.0 = (Axis2)
>         Type: New = Feature
>   Components: deployment
>     Reporter: Srinath Perera
>     Priority: Minor

>
> http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/JMX-fro= nt

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the = administrators:
   = http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira




--
"May the SourcE be with u"
http://www.bloglines.com/blog/thilina
http://webservices.apache.org/~thilina/




--
"May the SourcE be with u"
http://www.bloglines.com/b= log/thilina
http://webservices.apach= e.org/~thilina/

------=_NextPart_000_000C_01C5A4E0.8A506000--