javabeans - Java POJO Design with 200 variables -


i have design java bean 200 variables? correct way? (or) should break bean smaller logical beans , add main bean

p.s: have extract data legacy system , generate xml using castor

whether break down depends on requirements of application building.

if me, consider keeping separate beans, 1 bean castor needs deserialize xml (using dto pattern), other beans make information more usable , generated dto.

it absolutely depends on application , data though. have seen beans in financial apps have on 200 fields (complex derivatives) , breaking beans down smaller related beans add opportunity error.


Comments

Popular posts from this blog

asp.net mvc - SSO between MVCForum and Umbraco7 -

Python Tkinter keyboard using bind -

ubuntu - Selenium Node Not Connecting to Hub, Not Opening Port -