Asankha C. Perera wrote:
Andreas
I have indeed some local changes in the transport unit tests. I will
move the code to ws-commons once I have committed/reverted them and I
have karma in the WS project.
Yes, this should not be a problem and you will have this very soon.. I
will check with Glen on the Karma
By "make the individual transports define their own dependencies", do
you refer to the transports still remaining in Synapse?
Yes, but also the transports in WS-Commons too.. I mean generally this
would allow one to easily drop FIX etc, and its dependencies, and only
use them if required. This would work nicely with the suggestions Oleg
has been making for quite sometime now that Synapse has too many
dependencies :D
The transports in WS-Commons don't have so much dependencies. The mail
transport gets its dependency on JavaMail transitively from AXIOM and
JMS only depends on the JMS APIs and that dependency is already declared
in the right place. So there is not much to do.
For the transports in Synapse it would imply splitting up the
synapse-transports module into several Maven modules. Maybe the first
step is to get rid of the dependencies in Synapse's master POM and
declare them at module level as we discussed sime time ago in SYNAPSE-396.
asankha
---------------------------------------------------------------------
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]
