axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal jayasinghe <>
Subject Re: Best way for refactoring ?
Date Sat, 18 Jun 2011 13:36:03 GMT
It is a good idea to reorganize the code into readable format, however
we need to make sure we are not going to introduce new bugs or remove
working code. IIRC, those are code are very sensitive, some code look
similar but has minor changes. So you need to be extra careful.

[If the code works fine, I would not change the code for only the future

> I started to refactor some codes in ADB RPCUtil and BeanUtil classes.
> My objectives are move repetitive codes into small manageable methods
> , breakdown long flows into some manageable format , increase the
> readability and make it clear for future enhancement. I'm not planning
> to change any functionality or public methods hence these modification
> will be local for above two classes.
> My approach is complete this refactoring in several steps ,
> refactoring repetitive codes , breakdown long flows can be potential
> steps. But I'm not sure whether I should commit final result of this
> refactoring at once or commit after each step (millstone ) so that
> others can review easily my modification.
> WDYT as a best approach for this ?
> Also reviews for these changes are highly welcome.
> Thanks !

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message