Re: [castor-dev] XML binding for existing complex code base

[nataliya]

Hi Erik,

sorry for the delay in replying - although I have subscribed to the 
list, I don't seem to be getting any messages from the list and hence 
didn't realise someone has replied to mine :(

Have you considered using just plain java serialization instead of XML?
yes, we have, but we would like serialization to be human-readable and 
easy to edit - we often use xml configuration and would like to embed 
xmlised jfreecharts into our config files.

Cheers
Nataliya
      > -----Original Message-----
      > From: Nataliya Roberts [mailto:[EMAIL PROTECTED]
      > Sent: Thursday, September 11, 2003 8:17 PM
      > To: [EMAIL PROTECTED]
      > Subject: [castor-dev] XML binding for existing complex code base
      > 
      > 
      > 
      > Hi,
      > 
      > I am new to castor and am after an advise if what we 
      > want to do is 
      > possible to achieve with this technology.
      > 
      > We would like to use castor to marshall and unmarshall 
      > JFreeCharts 
      > (http://www.jfree.org/jfreechart/index.html) so we can 
      > use it in our 
      > programs. JFreeChart is an evolved software by now and 
      > not all objects 
      > are bean-like. We estimate there are over 140 
      > serializable objects in 
      > the code.
      > 
      > The main question is this: What would your suggestions 
      > be in regards as 
      > how to tackle something like this? And is it achievable 
      > at all with 
      > current castor?
      > 
      > So far I have tried using castor with mapping files, 
      > but came across 
      > some problems:
      > - Using castor on an object containing a collection 
      > where getters return 
      > unmodifiable collection produces an error 
      > (understandably). Is there 
      > some work around that I could use to overcome this 
      > problem (without 
      > changing source code)?
      > - Non-default constructors. JFreeChart source code has 
      > some of those. 
      > The work-around using "set-method" doesn't work in our 
      > case as castor 
      > expects the corresponding field to be an attribute 
      > (which means this 
      > should be a primitive type). The only information I 
      > could find on this 
      > is message on castor-dev list: 
      > http://www.mail-archive.com/[EMAIL PROTECTED]/msg05286.html
      > Are there plans to implement something like this?
      > Is there some way to use non-default constructors with 
      > non-primitive types?
      > 
      > 
      > Also, btw, marshalling objects containing 
      > java.awt.Rectangle seems to 
      > cause recursive loop when marshalling Rectangle and 
      > eventually "out of 
      > memory" error.
      > 
      > Thanks,
      > Nataliya
----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
       unsubscribe castor-dev