Hi Sagara!  Please let me know if you have any question or comment when you
look at it.

Ping


On Tue, Jul 12, 2011 at 7:44 AM, Sagara Gunathunga <
sagara.gunathu...@gmail.com> wrote:

> In fact initially I was followed  AXIS2-4170 with Ping and still on my
> list. Right now I'm in the middle of some ADB improvements , once I
> finished them or if I get free time will look into these.
>
> Thanks !
>
> On Tue, Jul 12, 2011 at 12:57 AM, Afkham Azeez <afk...@gmail.com> wrote:
> > Hi,
> > We will be looking at these issues. Sagara has been working on some
> > improvements to the codegen stuff in the past few weeks. Sagara, can you
> > please assign these issues to yourself and take a look?
> > Thanks
> > Azeez
> >
> > On Mon, Jul 11, 2011 at 12:06 PM, Ping Liu <pingpinga...@gmail.com>
> wrote:
> >>
> >> In Axis2 Jira issues (Issues => Unresolved: By Component => codegen)
> >>
> >> Following issues have patches and are probably fixed.  However, no one
> has
> >> verified and committed the fix.
> >>
> >> AXIS2-2811
> >> AXIS2-3037
> >> AXIS2-4170
> >> AXIS2-4859
> >>
> >> I fixed AXIS2-4170 and attached the patch one month ago.  Meanwhile, I
> >> also sent two e-mail notifications to request verification and checkin.
> But
> >> I haven't received any reply since then.
> >>
> >> After browsing through all unresolved issues in codegen, I surprisingly
> >> found mine is not the only case.  There are a few more as shown in the
> above
> >> list.
> >>
> >> AXIS2-2811 had fixed patch three years ago!!  AXIS2-3037 has patch
> >> submitted in 2008 and AXIS2-4859 has patch since last year.  But nobody
> >> evaluates and commits these patches.
> >>
> >> There are also some issues with limited information -- typically with no
> >> WSDL attached.  The following are some examples.
> >>
> >> AXIS2-4250
> >> AXIS2-4414
> >> AXIS2-4455
> >> AXIS2-5015
> >>
> >> Some were filed long time ago.  There is no way to know whether these
> >> issues are still valid.
> >>
> >> My suggestion to the issue management is:
> >>     - please take a review for all issues periodically
> >>     - please evaluate patches
> >>     - please review issues with limited information and send request to
> >> original reporter for WSDL and reevaluation
> >>
> >> I am hesitating to continue working on issues and thinking maybe it is
> >> better to send this suggestion first.
> >>
> >> Thanks!
> >>
> >> Ping
> >
> >
> > --
> > Afkham Azeez
> > Director of Architecture; WSO2, Inc.; http://wso2.com,
> > Member; Apache Software Foundation; http://www.apache.org/
> >
> > email: az...@wso2.com cell: +94 77 3320919
> > blog: http://blog.afkham.org
> > twitter: http://twitter.com/afkham_azeez
> > linked-in: http://lk.linkedin.com/in/afkhamazeez
> >
> > Lean . Enterprise . Middleware
> >
> >
>
>
>
> --
> Sagara Gunathunga
>
> Blog      - http://ssagara.blogspot.com
> Web      - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>
>

Reply via email to