[
https://issues.apache.org/jira/browse/AXIS2C-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875848#action_12875848
]
nadir amra commented on AXIS2C-1142:
------------------------------------
One thing I plan on doing is to create an axutil_string_pair object that will
replace axis2_http_header. It basically will have the same functionality
(probably more) and will be more efficient (i.e. name/valye buffers will not
have to be malloc'ed unless sizes exceed default size. This should help
performance and eliminate axis2_http_header_free() calls, leaving the only
thing for us to deal in terms of moving out the transport stuff from the core
is the axis2_http_accept_record_free() API.
> Circular dependency between engine and http_common libraries
> ------------------------------------------------------------
>
> Key: AXIS2C-1142
> URL: https://issues.apache.org/jira/browse/AXIS2C-1142
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine, core/transport
> Affects Versions: 1.4.0
> Environment: CentOS 4.6 (linux), GCC 3.4.6/4.2.3
> Reporter: Steve Nairn
> Priority: Minor
> Attachments: http_common.patch
>
>
> Following discussion on the Axis2/C dev list, there is a circular dependency
> between libaxis2_engine and libaxis2_http_common.
> The http_common library contains references to a large number of symbols that
> are resolved by the engine library. Unfortunately the engine library contains
> references to axis2_http_accept_record_free and axis2_http_header_free, that
> are resolved by the http_common library. Therefore there is a circular
> dependency between the libraries.
> The circular dependency makes it very difficult to build these libraries on
> platforms that do not allow shared libraries to contain unresolved symbols
> (for example, Windows DLLs).
--
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]
