You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilo Frotscher (JIRA)" <ji...@apache.org> on 2006/10/29 06:59:16 UTC
[jira] Created: (AXIS2-1541) When engaging a module with a service,
the module is engaged with each operation twice
When engaging a module with a service, the module is engaged with each operation twice
--------------------------------------------------------------------------------------
Key: AXIS2-1541
URL: http://issues.apache.org/jira/browse/AXIS2-1541
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Environment: Axis2 1.1 Snapshot of 29 Oct
Reporter: Thilo Frotscher
Priority: Critical
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);
}
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-1541) When engaging a module with a
service, the module is engaged with each operation twice
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-1541.
--------------------------------------
Resolution: Fixed
> When engaging a module with a service, the module is engaged with each operation twice
> --------------------------------------------------------------------------------------
>
> Key: AXIS2-1541
> URL: https://issues.apache.org/jira/browse/AXIS2-1541
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Axis2 1.1 Snapshot of 29 Oct
> Reporter: Thilo Frotscher
> Assigned To: Deepal Jayasinghe
> Fix For: 1.1.1
>
>
> 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);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-1541) When engaging a module with a
service, the module is engaged with each operation twice
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1541?page=all ]
Davanum Srinivas reassigned AXIS2-1541:
---------------------------------------
Assignee: Deepal Jayasinghe
> When engaging a module with a service, the module is engaged with each operation twice
> --------------------------------------------------------------------------------------
>
> Key: AXIS2-1541
> URL: http://issues.apache.org/jira/browse/AXIS2-1541
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: Axis2 1.1 Snapshot of 29 Oct
> Reporter: Thilo Frotscher
> Assigned To: Deepal Jayasinghe
> Priority: Critical
>
> 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);
> }
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1541) When engaging a module with a service,
the module is engaged with each operation twice
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1541?page=all ]
Deepal Jayasinghe updated AXIS2-1541:
-------------------------------------
Priority: Blocker (was: Critical)
Need to fix for this release.
> When engaging a module with a service, the module is engaged with each operation twice
> --------------------------------------------------------------------------------------
>
> Key: AXIS2-1541
> URL: http://issues.apache.org/jira/browse/AXIS2-1541
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: Axis2 1.1 Snapshot of 29 Oct
> Reporter: Thilo Frotscher
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> 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);
> }
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1541) When engaging a module with a service,
the module is engaged with each operation twice
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1541?page=all ]
Deepal Jayasinghe updated AXIS2-1541:
-------------------------------------
Fix Version/s: 1.1.1
Affects Version/s: 1.1.1
> When engaging a module with a service, the module is engaged with each operation twice
> --------------------------------------------------------------------------------------
>
> Key: AXIS2-1541
> URL: http://issues.apache.org/jira/browse/AXIS2-1541
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Axis2 1.1 Snapshot of 29 Oct
> Reporter: Thilo Frotscher
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
> Fix For: 1.1.1
>
>
> 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);
> }
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1541) When engaging a module with a
service, the module is engaged with each operation twice
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1541?page=comments#action_12446455 ]
Deepal Jayasinghe commented on AXIS2-1541:
------------------------------------------
I think it is better to fix for 1.1
comments ...... ???
> When engaging a module with a service, the module is engaged with each operation twice
> --------------------------------------------------------------------------------------
>
> Key: AXIS2-1541
> URL: http://issues.apache.org/jira/browse/AXIS2-1541
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: Axis2 1.1 Snapshot of 29 Oct
> Reporter: Thilo Frotscher
> Assigned To: Deepal Jayasinghe
> Priority: Critical
>
> 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);
> }
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1541) When engaging a module with a service,
the module is engaged with each operation twice
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1541?page=all ]
Deepal Jayasinghe updated AXIS2-1541:
-------------------------------------
Priority: Major (was: Blocker)
Fixed in the branch ,
I will keep the issue open since I did not fix the issue in the trunk
> When engaging a module with a service, the module is engaged with each operation twice
> --------------------------------------------------------------------------------------
>
> Key: AXIS2-1541
> URL: http://issues.apache.org/jira/browse/AXIS2-1541
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.1.1
> Environment: Axis2 1.1 Snapshot of 29 Oct
> Reporter: Thilo Frotscher
> Assigned To: Deepal Jayasinghe
> Fix For: 1.1.1
>
>
> 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);
> }
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org