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 "Kent Tong (JIRA)" <ji...@apache.org> on 2006/05/01 15:11:46 UTC
[jira] Created: (AXIS2-650) inferInTransport() misses the
possibility that WS-Addressing is engaged on the operation level
inferInTransport() misses the possibility that WS-Addressing is engaged on the operation level
----------------------------------------------------------------------------------------------
Key: AXIS2-650
URL: http://issues.apache.org/jira/browse/AXIS2-650
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: core
Versions: 1.0
Environment: Axis2 1.0 RC4
Reporter: Kent Tong
Priority: Minor
inferInTransport() checks to ensure WS-Addressing is engaged. However, it only checks if the wsa module is engaged on the service level. If the module is engaged on the operation level, it will still trigger an exception saying wsa module is not engaged:
public static synchronized TransportInDescription inferInTransport(AxisConfiguration ac,
Options options,
MessageContext msgCtxt) throws AxisFault {
...
if (msgCtxt.getAxisService() != null) {
AxisService service = msgCtxt.getAxisService();
Iterator itr = service.getEngagedModules().iterator();
boolean found = false;
while (itr.hasNext()) {
AxisModule axisModule = (AxisModule) itr.next();
if (axisModule.getName().getLocalPart().indexOf(Constants.MODULE_ADDRESSING) >= 0) {
found = true;
break;
}
}
if (!found) {
throw new AxisFault(Messages.getMessage("2channelNeedAddressing"));
}
}
...
}
--
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
[jira] Resolved: (AXIS2-650) inferInTransport() misses the
possibility that WS-Addressing is engaged on the operation level
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-650?page=all ]
Deepal Jayasinghe resolved AXIS2-650:
-------------------------------------
Fix Version: 1.0
Resolution: Fixed
fixed
> inferInTransport() misses the possibility that WS-Addressing is engaged on the operation level
> ----------------------------------------------------------------------------------------------
>
> Key: AXIS2-650
> URL: http://issues.apache.org/jira/browse/AXIS2-650
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Versions: 1.0
> Environment: Axis2 1.0 RC4
> Reporter: Kent Tong
> Priority: Minor
> Fix For: 1.0
>
> inferInTransport() checks to ensure WS-Addressing is engaged. However, it only checks if the wsa module is engaged on the service level. If the module is engaged on the operation level, it will still trigger an exception saying wsa module is not engaged:
> public static synchronized TransportInDescription inferInTransport(AxisConfiguration ac,
> Options options,
> MessageContext msgCtxt) throws AxisFault {
> ...
> if (msgCtxt.getAxisService() != null) {
> AxisService service = msgCtxt.getAxisService();
> Iterator itr = service.getEngagedModules().iterator();
> boolean found = false;
> while (itr.hasNext()) {
> AxisModule axisModule = (AxisModule) itr.next();
> if (axisModule.getName().getLocalPart().indexOf(Constants.MODULE_ADDRESSING) >= 0) {
> found = true;
> break;
> }
> }
> if (!found) {
> throw new AxisFault(Messages.getMessage("2channelNeedAddressing"));
> }
> }
> ...
> }
--
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
[jira] Commented: (AXIS2-650) inferInTransport() misses the
possibility that WS-Addressing is engaged on the operation level
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-650?page=comments#action_12377312 ]
Deepal Jayasinghe commented on AXIS2-650:
-----------------------------------------
Addressing is global module , so no point of engaging such a module to a operation.
> inferInTransport() misses the possibility that WS-Addressing is engaged on the operation level
> ----------------------------------------------------------------------------------------------
>
> Key: AXIS2-650
> URL: http://issues.apache.org/jira/browse/AXIS2-650
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Versions: 1.0
> Environment: Axis2 1.0 RC4
> Reporter: Kent Tong
> Priority: Minor
>
> inferInTransport() checks to ensure WS-Addressing is engaged. However, it only checks if the wsa module is engaged on the service level. If the module is engaged on the operation level, it will still trigger an exception saying wsa module is not engaged:
> public static synchronized TransportInDescription inferInTransport(AxisConfiguration ac,
> Options options,
> MessageContext msgCtxt) throws AxisFault {
> ...
> if (msgCtxt.getAxisService() != null) {
> AxisService service = msgCtxt.getAxisService();
> Iterator itr = service.getEngagedModules().iterator();
> boolean found = false;
> while (itr.hasNext()) {
> AxisModule axisModule = (AxisModule) itr.next();
> if (axisModule.getName().getLocalPart().indexOf(Constants.MODULE_ADDRESSING) >= 0) {
> found = true;
> break;
> }
> }
> if (!found) {
> throw new AxisFault(Messages.getMessage("2channelNeedAddressing"));
> }
> }
> ...
> }
--
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