Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Based on the feedback raised in on the mailing list discussion. http://ofbiz.135035.n4.nabble.com/Framework-Cleanup-Options-Tidy-Up-amp-Refactor-tt4676797.html#none

We are looking to initiating work to clean up areas of the framework by refactoring.

Planning and Approach

Initial Approach

Initial Deliverables

Initial Milestones

Milestone / Deliverable Planning and Tracking

Scope

Everything including core API interfaces ?? (Need to clarify this so it is totally clear - what does everything mean??)


Initial Areas for Refactoring

Initial ideas suggested by Taher.


  Refactor Reason / Issue   
1EntitySaxReader EntitySaxReader implements javolution interfaces and looks hideous    
2HtmlFormRendererHtmlFormRenderer is 3000 lines of code and the interfaces it implements
are also huge 		   
3 XmlFormRendererXmlFormRenderer does not implement more than half of the methods    
4Dependencies on Deprecated Classes / ConstructorsLots of dependencies on deprecated classes / constructors (e.g.
HtmlScreenRenderer, FoScreenRenderer) 		   
5Start.javaLots of dependencies on deprecated classes / constructors (e.g.
HtmlScreenRenderer, FoScreenRenderer) 		   
6Implementations with no interfacesImplementations with no interfaces (e.g. TemporalExpression, GroupModel,
Cache, etc ...) 		   
      
      
      


 

  • No labels