I have only just subscribed so I am unsure whether this question/comment has alrewady been posted. If so I apologise for the repeat.
I also apologise if this considered inappropriate for this forum.
Damon Goodyear
From: damongoodyear_at_hotmail.comTo: users_at_jaxb.dev.java.netSubject: Adding Behaviours with JAXBDate: Tue, 12 Feb 2008 17:19:09 +0000
This is half feedback half question. I am looking to use XML to store data for an engineering application and JAXB to marshall and unmarshall the data. There is quite a bit of data (all the physical data that describe the problem, temperatures, pressure, heat capacities etc) and if it were all accessed directly into a class along with the calculations that need to be done the classes would get very unwieldy. There is also the issue that if the data requirements changed during development and XJC were used then my finely tuned algorithm (ha! like a spark transmission radio) would be overwritten. I have read your article on Adding Behaviours and it seems a plausible but inelegant way around the problem. So my questions are 2 fold. First, are you aware of any developments in the way JAXB handles behaviours for future reference? Second, whether you are aware of any design patterns that provide a more elegant way of separating data access from data manipulation - that does not violate object oriented principles.
Damon Goodyear