I have an XML which is of size 8 MB. The size of this XML is increasing constantly. For picking up the data from this XML, we are using Castor.
The problem is that it is increasingly becoming very difficult to maintain this XML. And also, the XML is taking huge space in Cache memory as we are loading this XML from database during the server start-up itself.
Now we are looking a solution through which we can: 1. Split the XML into parts (for better maintainance) 2. Occupy less cache size
and still do the castoring for retrieving the data from the xml.
Thanks in advance
Cheers,<br />Hemanth...<br />(When opportunity doesn't knock, build a door.)
Since you are already "castoring", why not implement some functions that would 'write' the XML file into two or more logical parts. It should be something not overly complicated since you already have the Castor stuff in place.