ws-muse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Jemiolo (JIRA)" <>
Subject [jira] Updated: (MUSE-138) AxisIsolationLayer is not initalised with operation context for Axis 1.1RC2
Date Fri, 03 Nov 2006 15:12:17 GMT
     [ ]

Dan Jemiolo updated MUSE-138:

      Component/s: Deployment - Axis2
    Fix Version/s: 2.1.0

Thanks for reporting this with Axis2, and for your support in trying to get them to fix this.
I don't understand why they're breaking this behavior in a minor release - setOperationContext(
) was the documented way to achieve startup tasks (at least according to the mailing list
 ;-)  ). I think we will just change setOperationContext( ) to init( ) in the current AxisIsolationLayer
class. If they're going to break compatibility there's not much we can do.

For this issue I will update to Axis 1.1 RC 2 and modify setOperationContext( ) to init( ).

> AxisIsolationLayer is not initalised with operation context for Axis 1.1RC2
> ---------------------------------------------------------------------------
>                 Key: MUSE-138
>                 URL:
>             Project: Muse
>          Issue Type: Bug
>          Components: Deployment - Axis2
>    Affects Versions: 2.0.0
>         Environment: WLS 9.2, Windows XPSP2, Axis 1.1RC2
>            Reporter: James Shiell
>         Assigned To: Dan Jemiolo
>             Fix For: 2.1.0
> The AxisIsolationLayer does not have the setOperationContext(OperationContext):void method
called, and hence throws a NullPointer exception when the handlerRequest method is invoked.
> This appears to be because Axis 2 1.1RC2 onwards no longer invoke the setOperationContext
method, instead relying purely on the init(OperationContext) method. This is done via the
org.apache.axis2.engine.DependencyManager class. 
> As a workaround, the AxisIsolationLayer class can be subclassed and init(..) implemented,
and this subclass used in the Axis 2 services.xml.

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:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message