You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/08/16 11:55:20 UTC

[jira] Closed: (AXISCPP-48) Doc Style and RPC services mixup

Message:

   The following issue has been closed.

   Resolver: Samisa Abeysinghe
       Date: Mon, 16 Aug 2004 2:54 AM

This was fixed by Damitha
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-48

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-48
    Summary: Doc Style and RPC services mixup
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: FIXED

    Project: Axis-C++
 Components: 
             Basic Architecture
   Fix Fors:
             1.1 Final
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Samisa Abeysinghe

    Created: Thu, 8 Apr 2004 9:00 PM
    Updated: Mon, 16 Aug 2004 2:54 AM
Environment: Linux with Xerces parser and Apache 2

Description:
When Apache is started and base sample is run first and then doclitbase sample is run second doclitbase fails (base succeeds and dolitbase fails)

If I restart apache and run doclitbase first and then run base samle second, base fails (doclitbase succeeds and base fails)

This indicates that the behavior of the services are governed by the oerder in which they are loaded

I noticed that both doclitbase and base use the same set of 'allowedMethods' in server.wsdd. Hence I removed some of the 'allowedMethods' from base service in server.wsdd, restarted apache and ran base first and doclitbase second. Then the methods removed from base succeeded with doclitbase. This surely suggests a mix up with diferent styles of services. 

Please help fix this as soon as possible. 


---------------------------------------------------------------------
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