axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (AXISCPP-71) Abstract Transport Layer & Parser Layer
Date Mon, 16 Aug 2004 10:44:20 GMT

   The following issue has been closed.

   Resolver: Samisa Abeysinghe
       Date: Mon, 16 Aug 2004 3:43 AM

Resolved by Susantha.

Parser and trasport abstraction layers are in place with 1.2 release.
One could use his/her preffered parser/trasport by implementing a concrete class inherited
from the abstract class that defines the required APIs.

For trasport, the base abstract class is defined in src/transport/SOAPTransport.h.
For parser, the base abstract class is defined in

(Please have a look at the API docs for more details)

View the issue:

Here is an overview of the issue:
        Key: AXISCPP-71
    Summary: Abstract Transport Layer & Parser Layer
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
             Basic Architecture
   Fix Fors:
             1.2 Final
             1.2 Beta

   Reporter: Sevwandi Abeysinghe

    Created: Wed, 28 Apr 2004 10:24 PM
    Updated: Mon, 16 Aug 2004 3:43 AM
Environment: All platforms

1) runtime parser

With existing code we decide which parser tobe used at compile time. We can have two shared
libraries (.dll / .so) for xerces and expat parsers and can select the parser to be used at
runtime by referring a configuration file the parser will be loaded at runtime.

2) dynamic transport (HTTP)

Change the transport abstraction layer and make the API as it can plug any transport layer
at runtime by using a configuration file and the transport layer should be as a library which
can be linked at runtime.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message