Hello All,
I did not get any reply for my posting so far. Any quick help would
be much helpful. I am planning to try out JAXB and/or JIBX as an alternative to
Castor 0.91. Please advise at the earliest.
Thanks & Regards,
Harish.V
> -----Original Message-----
> From: Vembu, Harish
> Sent: Monday, January 09, 2006 10:13 AM
> To: '[EMAIL PROTECTED]'
> Subject: Castor0.91 implementation
>
>
> Hello All,
> I would like to get valid inputs and suggestions for the Castor
> implementation in my project as given below. Are these below mentioned
> problems taken care in latest version of Castor1.0 ?
> Thanks in advance for your help.
>
> Thanks & Regards,
>
> Harish.V
> ________________________________________________________________________________________________
> Hi Harish (asuming Harish is your first name),
>
> would you please be so kind to post this to the dev mailing list, where
> it will be dealt with in the appropriate way.
>
> Regards
> Werner
>
> Vembu, Harish wrote:
> > Dear Werner,
> >
> > Its always nice to know a new group who are experts in an area
> > where you are just placed your feet.
> >
> > My query is regarding a design change to be suggested for an existing
> > solution implemented using Castor 0.91.
> >
> > The existing solution in brief:
> >
> > We have a J2EE portal application accessing another payment application
> > through JMS/MQ series. The communication with the Payment application -
> > Request and Response is through XML messages. Castor is used as for
> > marshalling/Unmarshalling of Java objects/ XML docs.
> >
> > The problem:
> > Becasue of the frequent changes to the XSD schemas there is a necessity to
> > tweak a lot with the Java code and also in the portal code. There is
> > problem in mapping of Date field and for XSD schema elements having same
> > names. Also when there are multiple elements with same name in XSD schema
> > then there are issues with respect to marshalling and unmarshalling to and
> > from Java objects. In short there is not 100 % mapping achieved. We need to
> > find a design solution to avoid this shortcoming in using Castor.
> >
>
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an intended
recipient then please promptly delete this e-mail and any attachment and all
copies and inform the sender. Thank you.
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
