[
https://issues.apache.org/jira/browse/AXIS2C-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682717#comment-13682717
]
Thomas Gentsch commented on AXIS2C-1640:
----------------------------------------
One more comment: I'm not the absolute expert in SOAP formalities, i.e. the
mechanism as described and provided as patch works TECHNICALLY, however I'm not
sure whether this is CONCEPTIONALLY the right way of doing it.
And, disclaimer: I have tested it a lot (on Linux), including valgrind - seems
to work nicely but no guarantees.
> 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
> Attachments: example, genericserver.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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
