[
https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608312#action_12608312
]
Senaka Fernando commented on AXIS2C-1040:
-----------------------------------------
Hi Dushshantha,
Well there was an instance where a developer wanted to add this capability to
Axis2/C, sometime back (around 1 - 2 years back). Please do consider those
discussions as well. The static build is not an easily achievable task. As Bill
states, the approach I suggested was an alternate to what Frank spoke of. We
might have to adopt it since we need to make sure that both modes of operation
can co-exist. Also, please do check into the code to whether the issue has been
partially fixed.
Regards,
Senaka
> Use of AXIS2_EXPORT instead of AXIS2_EXTERN in a few places causes errors in
> static build
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2C-1040
> URL: https://issues.apache.org/jira/browse/AXIS2C-1040
> Project: Axis2-C
> Issue Type: Bug
> Components: util
> Reporter: Frank Huebbers
> Assignee: Dushshantha Chandradasa
>
> I have seen a few places where the typedef AXIS2_EXPORT is used instead of
> AXIS2_EXTERN. Doing a simple search, I have seen this in the following fiels:
> - axis2_msg_recv.h
> - msg_recv.c
> - raw_xml_in_out_msg_recv.c
> - svr_callback.c
> - mod_addr.c
> - http_transport_sender.c
> - http_receiver.c
> - http_svr_thread.c
> - tcp_transport_sender.c
> - tcp_svr_thread.c
> - tcp_receiver.c
> Note that the definitions are correct in the header files.
> Frank
--
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]
