Hi All,
While I doubt the need for removing recursion here (given the fact that
using more than a few url components will plainly be an overkill), it seems
to me that removing recursion from both the functions is quite straight
forward.
As it was mentioned earlier the function
On Sat, Nov 22, 2008 at 5:01 PM, Dumindu Pallewela [EMAIL PROTECTED]wrote:
Hi All,
While I doubt the need for removing recursion here (given the fact that
using more than a few url components will plainly be an overkill), it seems
to me that removing recursion from both the functions is quite
without using MIME4J.
thanks,
dims
On Sat, Nov 22, 2008 at 7:27 AM, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
On Thu, 2008-11-20 at 11:34 -0500, Davanum Srinivas wrote:
Oleg,
I totally agreed with you if you scroll back a few emails. Yes, we
need to fix *that*. Any patch to do that will be
-1.
I haven't been active in axis2 for a while now due to being knee deep in
Qpid. So please bear with me if I suddenly appear on this list. I started my
open source work with this project and it remains very dear to me and wants
to see the best for this project.
First up I have no objections
Dims
The package org.apache.axiom.mime defines the interfaces, and the
package org.apache.axiom.mime.impl which implements these using Mime4J.
I don't see why anyone else cannot implement these interfaces with any
other implementation..
Is your view on this still based on the following?
Asankha,
- Existing Axis2 test harness should work out of the box
- There should be no extra dependency jar (MIME4J) in the default
implementation.
Any patch that covers both will get my +1
thanks,
dims
On Sat, Nov 22, 2008 at 9:09 AM, Asankha C. Perera [EMAIL PROTECTED] wrote:
Dims
The
You know what. Am tired of this game of control. Just do whatever you
want. I withdraw my -1.
thanks,
dims
On Sat, Nov 22, 2008 at 10:18 AM, Davanum Srinivas [EMAIL PROTECTED] wrote:
Asankha,
- Existing Axis2 test harness should work out of the box
- There should be no extra dependency jar
Watching all the discussions. We are not ready and never will be. I
change my vote to -1.
thanks,
dims
On Sat, Nov 22, 2008 at 8:54 AM, Rajith Attapattu [EMAIL PROTECTED] wrote:
-1.
I haven't been active in axis2 for a while now due to being knee deep in
Qpid. So please bear with me if I
Watching all the discussions.
We are not ready and never will be.
I agree we are not ready. Saying we never will be is not helpful and
perpetuates the problem. I personally haven't given up on Apache or
the Apache process.
Paul
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC
It's my 2 cents. YMMV.
-- dims
On Sat, Nov 22, 2008 at 1:25 PM, Paul Fremantle [EMAIL PROTECTED] wrote:
Watching all the discussions.
We are not ready and never will be.
I agree we are not ready. Saying we never will be is not helpful and
perpetuates the problem. I personally haven't given
devs,
Please do not let the improvements to these projects go away. We all know
axis2 is a somewhat stable project, at the same time it is *not* perfect.
Thanks,
Ruwan
On Sun, Nov 23, 2008 at 6:36 AM, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
Davanum Srinivas wrote:
You know what. Am tired
11 matches
Mail list logo