Indika, There are two issues with the proposed patch:
1. In ServerManager, it introduces a dependency on the new TaskScheduler class which itself depends on Quartz. These are runtime dependencies which implies that it will not be possible to run Synapse without having Quartz in the classpath (which I think is possible with the current code). 2. It has been suggested to reduce the dependencies of the various modules (see SYNAPSE-396). Since the patch introduces Quartz specific code in synapse-utils, it means that the transports will have a transitive dependency on Quartz. I think it would be better to move the code to a new module and to take advantage of this to make sure that synapse-core no longer has a direct dependency on Quartz (this should be possible by using the META-INF/services extension mechanism). Andreas On Sun, Oct 26, 2008 at 17:03, indika kumara <[EMAIL PROTECTED]> wrote: > Ohh...Sorry > It is [1] http://wso2.org/projects/mashup > > Thanks > Indika > > On Sun, Oct 26, 2008 at 9:30 PM, Andreas Veithen > <[EMAIL PROTECTED]> wrote: >> Indika, >> >> I think you forgot to add the link for reference [1]. >> >> Andreas >> >> On Sun, Oct 26, 2008 at 16:49, indika kumara <[EMAIL PROTECTED]> wrote: >>> Hi All >>> >>> There is a requirement to be reused task implementation at synapse by >>> another open source project [1]. It is better, if it can be done with >>> out depending on synapse core jar. >>> >>> I have abstract out the responsibility of gathering Task details from >>> a OMElement , serialize back into OMElement and Quartz scheduling >>> part. >>> >>> There is no single change in the synapse language API (synapse >>> configuration) or in the synapse 'startup' concept. Existing samples >>> and any Task implementation will works as no Task API or Task synapse >>> language API changes (I have tested the existing sample). This is a >>> just refractor with some additional codes. >>> >>> I didn't commit as I wanted to ask from community. Code changes are >>> attached with this email as a patch. If this is Ok, I will commit. >>> >>> Thanks >>> Indika >>> >>> --------------------------------------------------------------------- >>> 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]
