This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hii guys .. I am reading the schema and loading the data based on the schema defined in my file so if schema changes (field names, number of fields or its length) it won't affect my code. I want to implement the value object pattern but for that i should know each fields to crate my value object class so i can provide the getter and setters for the fields but that violates the dynamic schema generation as i have to provide manually each fields like
.Any views on this ?? or simply i should ignore this pattern and stick with my interface methods which has String  in signature instead of the Value Object...Any suggestions..??
SCJP 1.4<br />SCWCD 1.4(91%)<br />Working on SCJD -Bodgitt & Scrapper Constructions...<br /> <br />"It takes 43 muscles to frown & 17 to smile but it doen't take any to just sit there with a dumb look on your face .. Keep Smiling "
hiii Mihai .. I guess you don't get my question ..I have fieldName and fieldLength in the hash table.which supports dynamic schema which means i dont need to care about how many fields are there..whats there size..but challenge is if you know the fields at runtime then how do you design a value object class which has fields and its getter/setter ...note that i dont know anything about fields..it will be resolved at runtime from hashtable.. In this scenario how do you design your Value Object class where the fields should be known and you provide getter /setter for that...
After a huge hiatus I have again started looking at my SCJD assignment. Now regarding the dynamic database schema and using a value object I have the same question.Initially I thought of doing that having a field object with a name and value and a record object that has many field objects in it...Now the thing is this really is messy and I don't know how I can implement this end to end i.e in the front end as well.Its unlikely that I can add a couple of fields in my header and expect those fields to miraculously appear in my front end......Any inputs I am thinking of moving towards the plain old ValObj hard coded........ Another qn I had was the database schema is given to us so the only reason we parse the metadata is because we want to know the order of the fields in our dat file is it.......
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: How to define the member variables in value Object with dynamic schema