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 "Juanda Zeng (JIRA)" <ji...@apache.org> on 2006/02/06 11:09:03 UTC
[jira] Created: (AXIS2-430) MessageIDs for WS-Addressing are not
valid (absolute) URIs
MessageIDs for WS-Addressing are not valid (absolute) URIs
----------------------------------------------------------
Key: AXIS2-430
URL: http://issues.apache.org/jira/browse/AXIS2-430
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: core, Integration
Versions: 0.94
Environment: Windows XP Pro, JBoss 3.2.3
Reporter: Juanda Zeng
Priority: Minor
An example of Axis2 generated MessageID: 88CCBC8E1CDD11F42711392097914632.
This causes interoperability issues when a .NET client (tested with WSE 3.0) tries to call an Axis2 web service with WS-Addressing enabled. The .NET client expects the MessageID to be in a valid (absolute) URI format, eg. uuid:aaaabbbb-cccc-dddd-eeee-wwwwwwwww (according to section 3.2 of WS-Addressing spec 20040810)
SUGGESTED RESOLUTION:
----------------------------------------------------------------
The affected Java classes are:
1. org.apache.axis2.util.Utils. Change:
newmsgCtx.setMessageID(UUIDGenerator.getUUID());
to:
newmsgCtx.setMessageID("uuid:" + UUIDGenerator.getUUID());
2. org.apache.axis2.description.OutInAxisOperationClient. Change:
messageId = UUIDGenerator.getUUID();
to:
messageId = "uuid:" + UUIDGenerator.getUUID();
3. org.apache.axis2.description.OutOnlyAxisOperationClient. Change:
messageId = UUIDGenerator.getUUID();
to:
messageId = "uuid:" + UUIDGenerator.getUUID();
NOTE:
----------------------------------------------------------------
This is indirectly related to issue AXIS2-92
--
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-430) MessageIDs for WS-Addressing are not
valid (absolute) URIs
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-430?page=all ]
Deepal Jayasinghe resolved AXIS2-430:
-------------------------------------
Fix Version: 0.95
Resolution: Fixed
Chinthka has fixed that issue in UUIDGenerator (line number 50)
thx Chinthaka
> MessageIDs for WS-Addressing are not valid (absolute) URIs
> ----------------------------------------------------------
>
> Key: AXIS2-430
> URL: http://issues.apache.org/jira/browse/AXIS2-430
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core, Integration
> Versions: 0.94
> Environment: Windows XP Pro, JBoss 3.2.3
> Reporter: Juanda Zeng
> Priority: Minor
> Fix For: 0.95
>
> An example of Axis2 generated MessageID: 88CCBC8E1CDD11F42711392097914632.
> This causes interoperability issues when a .NET client (tested with WSE 3.0) tries to call an Axis2 web service with WS-Addressing enabled. The .NET client expects the MessageID to be in a valid (absolute) URI format, eg. uuid:aaaabbbb-cccc-dddd-eeee-wwwwwwwww (according to section 3.2 of WS-Addressing spec 20040810)
> SUGGESTED RESOLUTION:
> ----------------------------------------------------------------
> The affected Java classes are:
> 1. org.apache.axis2.util.Utils. Change:
> newmsgCtx.setMessageID(UUIDGenerator.getUUID());
> to:
> newmsgCtx.setMessageID("uuid:" + UUIDGenerator.getUUID());
>
> 2. org.apache.axis2.description.OutInAxisOperationClient. Change:
> messageId = UUIDGenerator.getUUID();
> to:
> messageId = "uuid:" + UUIDGenerator.getUUID();
> 3. org.apache.axis2.description.OutOnlyAxisOperationClient. Change:
> messageId = UUIDGenerator.getUUID();
> to:
> messageId = "uuid:" + UUIDGenerator.getUUID();
> NOTE:
> ----------------------------------------------------------------
> This is indirectly related to issue AXIS2-92
--
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-430) MessageIDs for WS-Addressing are not
valid (absolute) URIs
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-430?page=comments#action_12365261 ]
Eran Chinthaka commented on AXIS2-430:
--------------------------------------
Hi Zeng,
I fixed this in revision 372447 on 26/01/2006, while I was fixing Axis2-414. Do you see this with the latest code or in the release ?
> MessageIDs for WS-Addressing are not valid (absolute) URIs
> ----------------------------------------------------------
>
> Key: AXIS2-430
> URL: http://issues.apache.org/jira/browse/AXIS2-430
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core, Integration
> Versions: 0.94
> Environment: Windows XP Pro, JBoss 3.2.3
> Reporter: Juanda Zeng
> Priority: Minor
>
> An example of Axis2 generated MessageID: 88CCBC8E1CDD11F42711392097914632.
> This causes interoperability issues when a .NET client (tested with WSE 3.0) tries to call an Axis2 web service with WS-Addressing enabled. The .NET client expects the MessageID to be in a valid (absolute) URI format, eg. uuid:aaaabbbb-cccc-dddd-eeee-wwwwwwwww (according to section 3.2 of WS-Addressing spec 20040810)
> SUGGESTED RESOLUTION:
> ----------------------------------------------------------------
> The affected Java classes are:
> 1. org.apache.axis2.util.Utils. Change:
> newmsgCtx.setMessageID(UUIDGenerator.getUUID());
> to:
> newmsgCtx.setMessageID("uuid:" + UUIDGenerator.getUUID());
>
> 2. org.apache.axis2.description.OutInAxisOperationClient. Change:
> messageId = UUIDGenerator.getUUID();
> to:
> messageId = "uuid:" + UUIDGenerator.getUUID();
> 3. org.apache.axis2.description.OutOnlyAxisOperationClient. Change:
> messageId = UUIDGenerator.getUUID();
> to:
> messageId = "uuid:" + UUIDGenerator.getUUID();
> NOTE:
> ----------------------------------------------------------------
> This is indirectly related to issue AXIS2-92
--
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