You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Akitoshi Yoshida (JIRA)" <ji...@apache.org> on 2007/03/02 10:09:50 UTC

[jira] Created: (SAND-10) username/password properties are not copied to a Call object by SenderWorker

username/password properties are not copied to a Call object by SenderWorker
----------------------------------------------------------------------------

                 Key: SAND-10
                 URL: https://issues.apache.org/jira/browse/SAND-10
             Project: Sandesha
          Issue Type: Bug
         Environment: Windows XP
Axis 1.4
Sandesha 1.0
            Reporter: Akitoshi Yoshida
         Assigned To: Davanum Srinivas


When a call is initiated from SenderWorker, the username/password properties of the original msgContext is not copied to this Call object in SenderWorker's prepareCall method. This results in the authentication error for calling password protected services.

To correct this problem, the username and password properties must be copied to the Call object as in:

org.apache.sandesha.server.SenderWorker#prepareCall

332c332,334
<         return call;
---
>         call.setUsername(rmMessageContext.getMsgContext().getUsername());
>         call.setPassword(rmMessageContext.getMsgContext().getPassword());
>        return call;

A similar problem exists for the createTerminateSeqMsg of RMMessageCreator.

org.apache.sandesha.util.RMMessageCreator#createTerminateSeqMsg

171a172,173
>         terSeqMsgContext.setUsername(rmMsgCtx.getMsgContext().getUsername());
>         terSeqMsgContext.setPassword(rmMsgCtx.getMsgContext().getPassword());




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Updated: (SAND-10) username/password properties are not copied to a Call object by SenderWorker

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SAND-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas updated SAND-10:
---------------------------------

    Assignee:     (was: Davanum Srinivas)

> username/password properties are not copied to a Call object by SenderWorker
> ----------------------------------------------------------------------------
>
>                 Key: SAND-10
>                 URL: https://issues.apache.org/jira/browse/SAND-10
>             Project: Sandesha
>          Issue Type: Bug
>         Environment: Windows XP
> Axis 1.4
> Sandesha 1.0
>            Reporter: Akitoshi Yoshida
>         Attachments: changed.zip
>
>
> When a call is initiated from SenderWorker, the username/password properties of the original msgContext is not copied to this Call object in SenderWorker's prepareCall method. This results in the authentication error for calling password protected services.
> To correct this problem, the username and password properties must be copied to the Call object as in:
> org.apache.sandesha.server.SenderWorker#prepareCall
> 332c332,334
> <         return call;
> ---
> >         call.setUsername(rmMessageContext.getMsgContext().getUsername());
> >         call.setPassword(rmMessageContext.getMsgContext().getPassword());
> >        return call;
> A similar problem exists for the createTerminateSeqMsg of RMMessageCreator.
> org.apache.sandesha.util.RMMessageCreator#createTerminateSeqMsg
> 171a172,173
> >         terSeqMsgContext.setUsername(rmMsgCtx.getMsgContext().getUsername());
> >         terSeqMsgContext.setPassword(rmMsgCtx.getMsgContext().getPassword());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Updated: (SAND-10) username/password properties are not copied to a Call object by SenderWorker

Posted by "Akitoshi Yoshida (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SAND-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Akitoshi Yoshida updated SAND-10:
---------------------------------

    Attachment: changed.zip

changed files are attached

SenderWorker.java
RMMessageCreator.java

the diffs to the sandesha 1.0 source
SenderWorker-diff.txt
RMMessageCreattor-diff.txt

> username/password properties are not copied to a Call object by SenderWorker
> ----------------------------------------------------------------------------
>
>                 Key: SAND-10
>                 URL: https://issues.apache.org/jira/browse/SAND-10
>             Project: Sandesha
>          Issue Type: Bug
>         Environment: Windows XP
> Axis 1.4
> Sandesha 1.0
>            Reporter: Akitoshi Yoshida
>         Assigned To: Davanum Srinivas
>         Attachments: changed.zip
>
>
> When a call is initiated from SenderWorker, the username/password properties of the original msgContext is not copied to this Call object in SenderWorker's prepareCall method. This results in the authentication error for calling password protected services.
> To correct this problem, the username and password properties must be copied to the Call object as in:
> org.apache.sandesha.server.SenderWorker#prepareCall
> 332c332,334
> <         return call;
> ---
> >         call.setUsername(rmMessageContext.getMsgContext().getUsername());
> >         call.setPassword(rmMessageContext.getMsgContext().getPassword());
> >        return call;
> A similar problem exists for the createTerminateSeqMsg of RMMessageCreator.
> org.apache.sandesha.util.RMMessageCreator#createTerminateSeqMsg
> 171a172,173
> >         terSeqMsgContext.setUsername(rmMsgCtx.getMsgContext().getUsername());
> >         terSeqMsgContext.setPassword(rmMsgCtx.getMsgContext().getPassword());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Updated: (SAND-10) username/password properties are not copied to a Call object by SenderWorker

Posted by "Akitoshi Yoshida (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SAND-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Akitoshi Yoshida updated SAND-10:
---------------------------------

    Attachment: changed.zip

changed files are attached

SenderWorker.java
RMMessageCreator.java

the diffs to the sandesha 1.0 source
SenderWorker-diff.txt
RMMessageCreattor-diff.txt

> username/password properties are not copied to a Call object by SenderWorker
> ----------------------------------------------------------------------------
>
>                 Key: SAND-10
>                 URL: https://issues.apache.org/jira/browse/SAND-10
>             Project: Sandesha
>          Issue Type: Bug
>         Environment: Windows XP
> Axis 1.4
> Sandesha 1.0
>            Reporter: Akitoshi Yoshida
>         Assigned To: Davanum Srinivas
>         Attachments: changed.zip
>
>
> When a call is initiated from SenderWorker, the username/password properties of the original msgContext is not copied to this Call object in SenderWorker's prepareCall method. This results in the authentication error for calling password protected services.
> To correct this problem, the username and password properties must be copied to the Call object as in:
> org.apache.sandesha.server.SenderWorker#prepareCall
> 332c332,334
> <         return call;
> ---
> >         call.setUsername(rmMessageContext.getMsgContext().getUsername());
> >         call.setPassword(rmMessageContext.getMsgContext().getPassword());
> >        return call;
> A similar problem exists for the createTerminateSeqMsg of RMMessageCreator.
> org.apache.sandesha.util.RMMessageCreator#createTerminateSeqMsg
> 171a172,173
> >         terSeqMsgContext.setUsername(rmMsgCtx.getMsgContext().getUsername());
> >         terSeqMsgContext.setPassword(rmMsgCtx.getMsgContext().getPassword());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org