[
https://issues.apache.org/jira/browse/AXIS2C-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547644
]
Senaka Fernando commented on AXIS2C-618:
----------------------------------------
Hi Dinesh,
I have managed to remove the dependency on HTTP Transport, by defining a new
include axis2_out_transport_info.h, and by using it instead of
axis2_http_out_transport_info.h in msg_ctx.c. Therefore, you now can go ahead
and implement a axis2_tcp_out_transport_info, as well as a
axis2_xmpp_out_transport_info and link the relevant libraries and remove the
dependency on HTTP.
Please refer the attached files, diff.txt and axis2_out_transport_info.h, for
the proposed patch.
Also, it happens to be that each transport uses a subset of HTTP transport
specific includes such as axis2_http_util and axis2_http_common, which has to
readily removed by creating there own implementations. Looking forward to work
on this.
In addition to that there also exists a dependency on HTTP in the client-API
which should also be thought of.
Regards,
Senaka
> Engine has a dependancy on HTTP transport.
> ------------------------------------------
>
> Key: AXIS2C-618
> URL: https://issues.apache.org/jira/browse/AXIS2C-618
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine, core/transport
> Reporter: Dinesh Premalal
> Attachments: diff.txt
>
>
> msg_ctx.c used a function axis2_msg_ctx_get_http_out_transport_info , which
> is defined in axis2_http_out_transport_info.h which leads to have a
> dependency on HTTP transport.
> Since this dependency , I happen to link axis2_http_util and
> axis2_http_common to build XMPP transport. it seems quite silly dependency :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
