When engaging a module with a service, the module is engaged with each operation twice

Not sure about the priority of this bug, but I think it might be critical...

I created a module that contains a module class. For testing purposes, method engageNotify log a message every time it is invoked. The logging message provides information about the kind of engagement. When I use the admin frontend to engage the module with a service, the logging messages indicate that the module is engaged twice with every service operation (engageNotify invoked twice per operation):

LogModule was engaged with service: MyService
LogModule was engaged with operation: Op1
LogModule was engaged with operation: Op1
LogModule was engaged with operation: Op2
LogModule was engaged with operation: Op2
LogModule was engaged with operation: Op3
LogModule was engaged with operation: Op3
LogModule was engaged with operation: Op4
LogModule was engaged with operation: Op4

Here's the implementation of engageNotify:

public void engageNotify(AxisDescription axisDescription) throws AxisFault {
StringBuilder msg = new StringBuilder();
msg.append("LogModule was engaged with");

if (axisDescription instanceof AxisServiceGroup)

{ msg.append(" service group: "); msg.append(((AxisServiceGroup)axisDescription).getServiceGroupName()); }

else if (axisDescription instanceof AxisService)

{ msg.append(" service: "); msg.append(((AxisService)axisDescription).getName()); }

else if (axisDescription instanceof AxisOperation)

{ msg.append(" operation: "); msg.append(((AxisOperation)axisDescription).getName()); }

System.out.println(msg);
}