You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lin Sun (JIRA)" <ji...@apache.org> on 2007/03/09 21:06:09 UTC

[jira] Created: (GERONIMO-2947) Axis2 - a few improvements to support handlerchain

Axis2 - a few improvements to support handlerchain
--------------------------------------------------

                 Key: GERONIMO-2947
                 URL: https://issues.apache.org/jira/browse/GERONIMO-2947
             Project: Geronimo
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: webservices
    Affects Versions: 2.0
         Environment: winxp + sun 1.5 SDK
            Reporter: Lin Sun
             Fix For: 2.0


Hi,

This is a working-in-progress patch that contains the following improvements to the handlerchain support:

1) updated the handlerchain test and a few other handler improvements Jarek did recently for Axis2.
2) add a Axis2Util class to help getting serviceQName, portQName and EndpointDescription from axisService.
3) add missing license statements in different files.
4) Provide an PortInfoImpl class...this is a temp solution.  Need to use the PortInfoImpl class from Axis2 and ask Axis2 to make the contructor public (will log an axis2 jira on that).
5) Create a BindingImpl object and set the handlerchain on it, passed the BindingImpl object to Axis2 by 

msgContext.setProperty(JAXWSMessageReceiver.PARAM_BINDING, binding);

but I still don't see the handleMessage below got called by Axis2 when running jaxws-war:

    public boolean handleMessage(SOAPMessageContext smc) {
        System.out.println(this + " handleMessage(): " + greeting);
        return true;
    }

I expect to see a 

org.apache.greeter_control.GreeterHandler@2a6e6c handleMessage(): Hello

after the post construct of the handler.   Comments/suggestions are welcome and needed!:-)

Lin





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


[jira] Closed: (GERONIMO-2947) Axis2 - a few improvements to support handlerchain

Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lin Sun closed GERONIMO-2947.
-----------------------------

    Resolution: Fixed

This is fixed by dims a while back ago.  close this issue.

> Axis2 - a few improvements to support handlerchain
> --------------------------------------------------
>
>                 Key: GERONIMO-2947
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2947
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0-M5
>         Environment: winxp + sun 1.5 SDK
>            Reporter: Lin Sun
>             Fix For: 2.0-M5
>
>         Attachments: G2947-simple.patch, G2947.patch
>
>
> Hi,
> This is a working-in-progress patch that contains the following improvements to the handlerchain support:
> 1) updated the handlerchain test and a few other handler improvements Jarek did recently for Axis2.
> 2) add a Axis2Util class to help getting serviceQName, portQName and EndpointDescription from axisService.
> 3) add missing license statements in different files.
> 4) Provide an PortInfoImpl class...this is a temp solution.  Need to use the PortInfoImpl class from Axis2 and ask Axis2 to make the contructor public (will log an axis2 jira on that).
> 5) Create a BindingImpl object and set the handlerchain on it, passed the BindingImpl object to Axis2 by 
> msgContext.setProperty(JAXWSMessageReceiver.PARAM_BINDING, binding);
> but I still don't see the handleMessage below got called by Axis2 when running jaxws-war:
>     public boolean handleMessage(SOAPMessageContext smc) {
>         System.out.println(this + " handleMessage(): " + greeting);
>         return true;
>     }
> I expect to see a 
> org.apache.greeter_control.GreeterHandler@2a6e6c handleMessage(): Hello
> after the post construct of the handler.   Comments/suggestions are welcome and needed!:-)
> Lin

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


[jira] Commented: (GERONIMO-2947) Axis2 - a few improvements to support handlerchain

Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480442 ] 

Lin Sun commented on GERONIMO-2947:
-----------------------------------

Looks like the axis2 handlerchain support is incomplete and I've marked handlerchain as incomplete Axis2 function in the web services support table.

Lin

> Axis2 - a few improvements to support handlerchain
> --------------------------------------------------
>
>                 Key: GERONIMO-2947
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2947
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0
>         Environment: winxp + sun 1.5 SDK
>            Reporter: Lin Sun
>             Fix For: 2.0
>
>         Attachments: G2947.patch
>
>
> Hi,
> This is a working-in-progress patch that contains the following improvements to the handlerchain support:
> 1) updated the handlerchain test and a few other handler improvements Jarek did recently for Axis2.
> 2) add a Axis2Util class to help getting serviceQName, portQName and EndpointDescription from axisService.
> 3) add missing license statements in different files.
> 4) Provide an PortInfoImpl class...this is a temp solution.  Need to use the PortInfoImpl class from Axis2 and ask Axis2 to make the contructor public (will log an axis2 jira on that).
> 5) Create a BindingImpl object and set the handlerchain on it, passed the BindingImpl object to Axis2 by 
> msgContext.setProperty(JAXWSMessageReceiver.PARAM_BINDING, binding);
> but I still don't see the handleMessage below got called by Axis2 when running jaxws-war:
>     public boolean handleMessage(SOAPMessageContext smc) {
>         System.out.println(this + " handleMessage(): " + greeting);
>         return true;
>     }
> I expect to see a 
> org.apache.greeter_control.GreeterHandler@2a6e6c handleMessage(): Hello
> after the post construct of the handler.   Comments/suggestions are welcome and needed!:-)
> Lin

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


[jira] Updated: (GERONIMO-2947) Axis2 - a few improvements to support handlerchain

Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lin Sun updated GERONIMO-2947:
------------------------------

    Attachment: G2947-simple.patch

Hi, this is a simplified patch that can demonstrate the handlechain prob in Axis2.

> Axis2 - a few improvements to support handlerchain
> --------------------------------------------------
>
>                 Key: GERONIMO-2947
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2947
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0
>         Environment: winxp + sun 1.5 SDK
>            Reporter: Lin Sun
>             Fix For: 2.0
>
>         Attachments: G2947-simple.patch, G2947.patch
>
>
> Hi,
> This is a working-in-progress patch that contains the following improvements to the handlerchain support:
> 1) updated the handlerchain test and a few other handler improvements Jarek did recently for Axis2.
> 2) add a Axis2Util class to help getting serviceQName, portQName and EndpointDescription from axisService.
> 3) add missing license statements in different files.
> 4) Provide an PortInfoImpl class...this is a temp solution.  Need to use the PortInfoImpl class from Axis2 and ask Axis2 to make the contructor public (will log an axis2 jira on that).
> 5) Create a BindingImpl object and set the handlerchain on it, passed the BindingImpl object to Axis2 by 
> msgContext.setProperty(JAXWSMessageReceiver.PARAM_BINDING, binding);
> but I still don't see the handleMessage below got called by Axis2 when running jaxws-war:
>     public boolean handleMessage(SOAPMessageContext smc) {
>         System.out.println(this + " handleMessage(): " + greeting);
>         return true;
>     }
> I expect to see a 
> org.apache.greeter_control.GreeterHandler@2a6e6c handleMessage(): Hello
> after the post construct of the handler.   Comments/suggestions are welcome and needed!:-)
> Lin

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


[jira] Updated: (GERONIMO-2947) Axis2 - a few improvements to support handlerchain

Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lin Sun updated GERONIMO-2947:
------------------------------

    Attachment: G2947.patch

> Axis2 - a few improvements to support handlerchain
> --------------------------------------------------
>
>                 Key: GERONIMO-2947
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2947
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0
>         Environment: winxp + sun 1.5 SDK
>            Reporter: Lin Sun
>             Fix For: 2.0
>
>         Attachments: G2947.patch
>
>
> Hi,
> This is a working-in-progress patch that contains the following improvements to the handlerchain support:
> 1) updated the handlerchain test and a few other handler improvements Jarek did recently for Axis2.
> 2) add a Axis2Util class to help getting serviceQName, portQName and EndpointDescription from axisService.
> 3) add missing license statements in different files.
> 4) Provide an PortInfoImpl class...this is a temp solution.  Need to use the PortInfoImpl class from Axis2 and ask Axis2 to make the contructor public (will log an axis2 jira on that).
> 5) Create a BindingImpl object and set the handlerchain on it, passed the BindingImpl object to Axis2 by 
> msgContext.setProperty(JAXWSMessageReceiver.PARAM_BINDING, binding);
> but I still don't see the handleMessage below got called by Axis2 when running jaxws-war:
>     public boolean handleMessage(SOAPMessageContext smc) {
>         System.out.println(this + " handleMessage(): " + greeting);
>         return true;
>     }
> I expect to see a 
> org.apache.greeter_control.GreeterHandler@2a6e6c handleMessage(): Hello
> after the post construct of the handler.   Comments/suggestions are welcome and needed!:-)
> Lin

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