Dims
Yes, this will work if you don't mind another module being added to
axis2 :-)
I will first separate 1.5 dependent code and checkin http transport into
the kernel, and then create the new module
thanks
asankha
Davanum Srinivas wrote:
Asankha,
How about we have a tiny maven module for SSLEngine based classes
only? At this point, we are trying to stabilize 1.3 release and we
already do have some modules which are built only when using 1.5. this
will be just one more. The rest of the async classes can go into
kernel itself and hence usable with 1.4 and above. If someone needs
https then they can add the axis2-ssl-nio jar into the mix and run
under 1.5 jdk. Sounds reasonable?
thanks,
dims
On 6/20/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
Hi Dims..
I am going to commit the non-blocking http/s code into Axis2 trunk.
However this requires compilation with a JDK > 1.5. We could compile
into Java 1.4 code level, but the JDK used must be 1.5. This is because
we use the SSLEngine class to support https.
Do you think this will be a problem for anyone? or the nightly build
script etc? If so, should I leave the https support out - but I doubt
whether that will be meaningful.
Also, should I update any Maven1 scripts or are we using only Maven2 for
nightly builds and releases?
thanks
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]