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 "Bill Blough (JIRA)" <ji...@apache.org> on 2019/08/17 18:23:00 UTC
[jira] [Updated] (AXIS2C-1640) use built-in HTTP server also for
non-SOAP content
[ https://issues.apache.org/jira/browse/AXIS2C-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Blough updated AXIS2C-1640:
--------------------------------
Labels: patch (was: )
> use built-in HTTP server also for non-SOAP content
> --------------------------------------------------
>
> Key: AXIS2C-1640
> URL: https://issues.apache.org/jira/browse/AXIS2C-1640
> Project: Axis2-C
> Issue Type: Improvement
> Components: core/transport
> Affects Versions: 1.6.0
> Reporter: Thomas Gentsch
> Priority: Minor
> Labels: patch
> Attachments: example, genericserver.patch, memleak.patch
>
>
> I'm using Axis2c as a SOAP service in a project. Since there is already a built-in HTTP server, I was thinking whether it is possible to use that to provide a basic HTML GUI server in the same process that acts as SOAP server.
> I have played with this for a while and with a rather small set of changes this is possible (see attached patch and examples).
> At the same time while testing I encountered (using valgrind) quite a couple of memory leaks and a corruption - patch attached.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org