You are viewing a plain text version of this content. The canonical link for it is here.
Posted to stonehenge-dev@incubator.apache.org by "Nicholas A Hauenstein (JIRA)" <ji...@apache.org> on 2010/02/25 21:59:28 UTC
[jira] Created: (STONEHENGE-120) Configuration mapping missing for
WSAS in Business Service Console Configuration
Configuration mapping missing for WSAS in Business Service Console Configuration
--------------------------------------------------------------------------------
Key: STONEHENGE-120
URL: https://issues.apache.org/jira/browse/STONEHENGE-120
Project: Stonehenge
Issue Type: Bug
Affects Versions: M2
Reporter: Nicholas A Hauenstein
Assignee: Nicholas A Hauenstein
Fix For: M2
There is no mapping present in the web.config of the business service console for the WSAS implementation. This will result in an ambiguous match exception whenever the service tries to create a proxy to access the service without specifying a binding configuration.
The only reason that this is necessary is because of how the configuration service responses are handled (the BS maps the OPS service identifier to a binding using app settings in the config file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (STONEHENGE-120) Configuration mapping missing for
WSAS in Business Service Console Configuration
Posted by "Nicholas A Hauenstein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STONEHENGE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas A Hauenstein updated STONEHENGE-120:
---------------------------------------------
Attachment: STONEHENGE-120.patch
This fixes the issue
> Configuration mapping missing for WSAS in Business Service Console Configuration
> --------------------------------------------------------------------------------
>
> Key: STONEHENGE-120
> URL: https://issues.apache.org/jira/browse/STONEHENGE-120
> Project: Stonehenge
> Issue Type: Bug
> Affects Versions: M2
> Reporter: Nicholas A Hauenstein
> Assignee: Nicholas A Hauenstein
> Fix For: M2
>
> Attachments: STONEHENGE-120.patch
>
> Original Estimate: 0.03h
> Remaining Estimate: 0.03h
>
> There is no mapping present in the web.config of the business service console for the WSAS implementation. This will result in an ambiguous match exception whenever the service tries to create a proxy to access the service without specifying a binding configuration.
> The only reason that this is necessary is because of how the configuration service responses are handled (the BS maps the OPS service identifier to a binding using app settings in the config file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (STONEHENGE-120) Configuration mapping missing for
WSAS in Business Service Console Configuration
Posted by "Nicholas A Hauenstein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STONEHENGE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas A Hauenstein closed STONEHENGE-120.
--------------------------------------------
Resolution: Fixed
Verified as fixed in revision 916532.
> Configuration mapping missing for WSAS in Business Service Console Configuration
> --------------------------------------------------------------------------------
>
> Key: STONEHENGE-120
> URL: https://issues.apache.org/jira/browse/STONEHENGE-120
> Project: Stonehenge
> Issue Type: Bug
> Affects Versions: M2
> Reporter: Nicholas A Hauenstein
> Assignee: Nicholas A Hauenstein
> Fix For: M2
>
> Attachments: STONEHENGE-120.patch
>
> Original Estimate: 0.03h
> Remaining Estimate: 0.03h
>
> There is no mapping present in the web.config of the business service console for the WSAS implementation. This will result in an ambiguous match exception whenever the service tries to create a proxy to access the service without specifying a binding configuration.
> The only reason that this is necessary is because of how the configuration service responses are handled (the BS maps the OPS service identifier to a binding using app settings in the config file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-120) Configuration mapping missing
for WSAS in Business Service Console Configuration
Posted by "Ben Dewey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STONEHENGE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856156#action_12856156 ]
Ben Dewey commented on STONEHENGE-120:
--------------------------------------
Nick,
This was committed with, http://svn.apache.org/viewvc?view=revision&revision=916532. Can you verify and close if its working.
> Configuration mapping missing for WSAS in Business Service Console Configuration
> --------------------------------------------------------------------------------
>
> Key: STONEHENGE-120
> URL: https://issues.apache.org/jira/browse/STONEHENGE-120
> Project: Stonehenge
> Issue Type: Bug
> Affects Versions: M2
> Reporter: Nicholas A Hauenstein
> Assignee: Nicholas A Hauenstein
> Fix For: M2
>
> Attachments: STONEHENGE-120.patch
>
> Original Estimate: 0.03h
> Remaining Estimate: 0.03h
>
> There is no mapping present in the web.config of the business service console for the WSAS implementation. This will result in an ambiguous match exception whenever the service tries to create a proxy to access the service without specifying a binding configuration.
> The only reason that this is necessary is because of how the configuration service responses are handled (the BS maps the OPS service identifier to a binding using app settings in the config file).
--
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