axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Gallardo (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature
Date Mon, 28 Jan 2008 16:47:34 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nick Gallardo updated AXIS2-3448:
---------------------------------

      Description: 
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding some new capabilities
to the MTOM function.  This will mostly leverage existing infrastructure, but will also require
some additional functionality and coordination with the message model.  A quick summary of
the work to be done:

1. [DONE] Update the metadata APIs to reflect whether or not the MTOM configuration was found
on the endpoint.  

2. [DONE] Update the annotation processing code to pick off the @MTOM annotation when included
on an endpoint.

3. [DONE] Update the client creation code off of the ServiceDelegate to set the appropriate
values when the MTOMFeature is configured for client instances. 

4. Change the marshalling code to read the threshold and toggle MTOM when appropriate.  


Here are some examples of the new ways that MTOM can be configured.

Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
    ...   
}

After:
@WebService
@MTOM
public class MyServiceImpl {
    ...
}

Additionally, the threshold is configured as such.  

@WebService
@MTOM(enabled="true", threshold="2000")
public class MyServiceImpl {
    ...
}





On the client side, the configuration changes a little bit as well.  Here are a few examples
of how this will be done.

        
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);

Service service = Service.create(myServiceWSDL, serviceName);

MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);


  was:
JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding some new capabilities
to the MTOM function.  This will mostly leverage existing infrastructure, but will also require
some additional functionality and coordination with the message model.  A quick summary of
the work to be done:

1. Update the metadata APIs to reflect whether or not the MTOM configuration was found on
the endpoint.  

2. Update the annotation processing code to pick off the @MTOM annotation when included on
an endpoint.

3. Update the client creation code off of the ServiceDelegate to set the appropriate values
when the MTOMFeature is configured for client instances. 

4. Change the marshalling code to read the threshold and toggle MTOM when appropriate.  


Here are some examples of the new ways that MTOM can be configured.

Before:
@WebService
@BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
public class MyServiceImpl {
    ...   
}

After:
@WebService
@MTOM
public class MyServiceImpl {
    ...
}

Additionally, the threshold is configured as such.  

@WebService
@MTOM(enabled="true", threshold="2000")
public class MyServiceImpl {
    ...
}





On the client side, the configuration changes a little bit as well.  Here are a few examples
of how this will be done.

        
MTOMFeature mtom = new MTOMFeature();
mtom.setEnabled(true);
mtom.setThreshold(2000);

Service service = Service.create(myServiceWSDL, serviceName);

MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);


    Fix Version/s: 1.4

Marking completed items.

> JAX-WS 2.1: Support @MTOM and MTOMFeature
> -----------------------------------------
>
>                 Key: AXIS2-3448
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3448
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>            Reporter: Nick Gallardo
>            Assignee: Nick Gallardo
>             Fix For: 1.4
>
>
> JAX-WS 2.1 adds some new config options for enabling MTOM, along with adding some new
capabilities to the MTOM function.  This will mostly leverage existing infrastructure, but
will also require some additional functionality and coordination with the message model. 
A quick summary of the work to be done:
> 1. [DONE] Update the metadata APIs to reflect whether or not the MTOM configuration was
found on the endpoint.  
> 2. [DONE] Update the annotation processing code to pick off the @MTOM annotation when
included on an endpoint.
> 3. [DONE] Update the client creation code off of the ServiceDelegate to set the appropriate
values when the MTOMFeature is configured for client instances. 
> 4. Change the marshalling code to read the threshold and toggle MTOM when appropriate.
 
> Here are some examples of the new ways that MTOM can be configured.
> Before:
> @WebService
> @BindingType(SOAPBinding.SOAP11_HTTP_MTOM)
> public class MyServiceImpl {
>     ...   
> }
> After:
> @WebService
> @MTOM
> public class MyServiceImpl {
>     ...
> }
> Additionally, the threshold is configured as such.  
> @WebService
> @MTOM(enabled="true", threshold="2000")
> public class MyServiceImpl {
>     ...
> }
> On the client side, the configuration changes a little bit as well.  Here are a few examples
of how this will be done.
>         
> MTOMFeature mtom = new MTOMFeature();
> mtom.setEnabled(true);
> mtom.setThreshold(2000);
> Service service = Service.create(myServiceWSDL, serviceName);
> MyProxy proxy = service.getPort(portName, MyProxy.class, mtom);

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message