[jira] Commented: (AXISCPP-38) bugs in WSDD Allowed Methods code

[ax...@ws.apache.org]

The following comment has been added to this issue:

     Author: John Hawkins
    Created: Fri, 15 Oct 2004 8:38 AM
       Body:
The current behaviour of the allowed methods attribute in the .wsdd is as
follows tested with the interop base sample.

- The last method name is picked up "IF" a space exists after that last
method name. (The .wsdd s distributed with releases contain a space after
the last method name. But I guess there need not be a space for it to be
picked up and should be fixed??)

- The * now works and allowes all methods of the service to be invoked.
(look at closed issue 147)

sanjaya.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-38?page=comments#action_54201

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-38

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-38
    Summary: bugs in WSDD Allowed Methods code
       Type: Bug

     Status: Reopened

    Project: Axis-C++
 Components: 
             Deployment / Registries
   Fix Fors:
             1.1 Final
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Sam Lang

    Created: Thu, 15 Jan 2004 4:35 PM
    Updated: Fri, 15 Oct 2004 8:38 AM
Environment: Operating System: Other
Platform: Other

Description:
The WSDD allowed methods stuff is broken.  The WSDDDocument::AddAllowedMethods
function never adds the last method in the list to the allowed methods.  Also,
if there's only one allowed method, it never gets added.  The * feature is also
broken.  I'm submitting patches to fix these bugs so that the allowed methods
code works properly.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira