[jira] Updated: (AXIS2C-1040) Use of AXIS2_EXPORT instead of AXIS2_EXTERN in a few places causes errors in static build

["Bill Mitchell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Mitchell updated AXIS2C-1040:
----------------------------------


Dushshantha, I'm not sure which of the above suggestions you are calling the "discussed changes".  In particular, Frank made a change that works for him, although it binds the Axis2c client directly to using the http transport layer.  Whereas Senaka made an alternative sketch of a mechanism that might allow this to be inferred automatically in static mode, while dynamic mode continues to work as it does today.  

I would like to say that I symphathise with what Frank is trying to accomplish, as I too am interested in using Axis2C only on the client side.  In my project, I have not gotten to the point yet to decide whether installing the default Axis2C dynamic build on Windows will be acceptable, or whether some form of the static build would be easier for the client sites.  Were I to go with the static build, the inclusion of the http transport layer as part of the static build would be something I would want to consider.  So something along the lines of Senaka's suggestion for (4) would be interesting.  I haven't yet considered the implications, though, for the use of libcurl, whether there is some way to include libcurl in the static link, whether the "static" Axis2C build still uses a dynamic call to libcurl, or whether the use of libcurl requires the dynamic link.  

> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org