Hi again, I noticed that Steve came up with a patch, let me check on that first. It might be a better solution.
Regards, Senaka > Hi Supun, > > Yes, That needs to be sorted for the REST case. But, I believe that this > rather a bug in the REST portion of the engine, and the SOAP portion > should not be affected. BTW, it is better if we could split the engine's > dependent portions of HTTP common to another lib. Say, HTTP Core? > Thoughts? > > Regards, > Senaka > >> Hi Senaka, >> >> Did you mean something like providing a compile time flag for not >> including >> these stuff if rest is not needed? If that is the case we are in the >> same >> position when rest is needed (we have circular dependencies). >> >> Regards, >> Supun. >> >> On Thu, May 15, 2008 at 5:30 PM, Senaka Fernando <[EMAIL PROTECTED]> >> wrote: >> >>> Hi devs, >>> >>> AFAIK, this is because of the REST portions of the engine depending on >>> the >>> HTTP libraries. So if someone is not interested in REST can we instead >>> not >>> link these libraries? >>> >>> Regards, >>> Senaka >>> >>> > 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 >>> > >>> > >>> > 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] >>> > >>> > >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
