I closed most of these issues and mentioning the possibility of 2.x family for couple of reasons: 1. These issues were not bugs, rather better way of doing things. I would love to implement them right now, but that would mean we have to make some fundamental changes to the current implementation. So those are better done in a new implementation, which I thought could be 2.x 2. There issues were hanging there for so long and no one cared to fix them. Which basically mean to say that current Axis2/C works without them. So the indication was, no one bothered to attend them because there are better thing to do.

Thanks,
Samisa...

Damitha Kumarage wrote:
Supun Kamburugamuva wrote:

Hi,

If we are going to introduce changes that are not fit into the Axis2/C architecture, for me that implies we are going to change the Axis2/C architecture in 2.x. But I don't see any reason for changing the Axis2/C architecture.

I would like to replace the phrase
'fixing of which does not fit easily/naturally into the current Axis2/C architecture' with 'fixing of which does not fit easily/naturally into 1.x family' in my original mail ;-)

thanks
Damitha


Regards,
Supun..

On Thu, Apr 24, 2008 at 11:35 PM, Damitha Kumarage <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Hi,
    I can see lot of Jira's resolved, marked as moving the fix to 2.x
    family. I would like to open a wiki named Axis2/C 2.x suggestions,
    which summarize all the ideas taken from these jiras and also add
    reference to all these jiras there. This page can grow util we
    find one day that it is really neccessary to do a 2.x.
    One thing to notice here is the criteria we should follow to
    identifying the jiras, the fix of which should be moved to 2.x
    family. To me, the main criteria should be that the fixing of
    which does not fit easily/naturally into the current Axis2/C
    architecture.
    What do you think?
    thanks,
    Damitha

---------------------------------------------------------------------
    To unsubscribe, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    For additional commands, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Samisa Abeysinghe Director, Engineering; WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to