Glen, why ws/commons/transports? Why not ws/transports??
Even though we call ws/commons/transports or ws/transports those
components only valid for Axis2. Therefore I can not see the value of
having axis2 transport under WS [ I know I did +1 on the proposal.] :-\
We've moved away from commons in Axiom etc. - that is, packages no
longer say that and IMO that's better.
Yes. If we are moving the transport to ws , then it should not be inside
ws/commons , should be just ws/transport. But one thing we need to keep
in mind , we should not change the package name. If we do so we loose
the backward compatibility again.
With all these I think the time has come to think of moving Axis2 as TLP :)
Thank you!
Deepl
Sanjiva.
Deepal jayasinghe wrote:
Glen Daniels wrote:
[ Please refer to this thread for context :
http://markmail.org/message/lg3giq5kj74gjnxb
]
OK, let me make a concrete proposal here.
I hereby propose that we kick off a ws-commons "transports"
project. As with the other ws-commons projects, this would have its
own release schedule. All current ws-all committers would have
commit rights, and we'd add anyone from the Synapse team that would
like to work on transports, and isn't already a committer.
+1 for making a commons project for Axis2 transports. This will help
both Axis2 and other dependent projects such as Synapse.
Each transport within ws-commons Transports would be a separate
releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
each such transport would be releasable on its own with an
appropriate VOTE of the ws-commons committers.
Personally I would like to download all the transport as a single jar
, but I do not mind releasing them separately as long as you give
single jar as well.
Thank you!
Deepal
---------------------------------------------------------------------
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]
