Let me rephrase succinctly. :)
There should be a single place where generally applicable Axis2
transports get stored. It's fine for other projects to work on
transports, but the ideal situation is for those transports (assuming
they're generic enough) to migrate into the WS PMC as their final
destination, and be developed there.
So I'd like to see the transports in Synapse move into either:
ws-commons/transports/
or
axis2/transports/
And have development and testing continue there. As you say, dims,
there should never be stale code sitting anywhere.
Thoughts?
--Glen
Davanum Srinivas wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Glen,
If it is not maintained in Axis2, there's absolutely no point keeping it
here. Right?
- -- dims
Glen Daniels wrote:
| -1 from me to move them to Synapse.
|
| These transports (JMS, NIO, whatever) are going to be generally useful
| to any Axis2 user, so why make them go look in Synapse's codebase for
| them? I agree there should be a single place for them, but that place
| should be in Axis2, not somewhere else.
|
| I'd much rather see a separate transports module in Axis2 for the ones
| we want to support (this has been discussed before), and perhaps a
| "contrib" module to hold transports that others might develop in the
| future.
|
| --Glen
|
| Davanum Srinivas wrote:
| Under synapse...Sure. Perfect.
|
| -- dims
|
| Paul Fremantle wrote:
| | I agree there isn't any point keeping stale copies in Axis2. What
| | about building a separate module or even commons-transports?
| |
| | Paul
| |
| | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas
| <[EMAIL PROTECTED]> wrote:
| |> -----BEGIN PGP SIGNED MESSAGE-----
| |> Hash: SHA1
| |>
| |> Folks,
| |>
| |> Let's move JMS and Async NIO transports out of Axis2 into Synapse.
| There's
| |> no point keeping a stale copy in Axis2.
| |>
| |> WDYT?
| |>
| |> Thanks,
| |> dims
| |>
|>
- ---------------------------------------------------------------------
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]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDeg6gNg6eWEDv1kRAgTJAJ4pgrpoqNTuP1UdoeOBERFC33X5nwCfR4OX
bYHHcJchZyt/zGeZgRhgpfE=
=JxHH
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
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]
