Hi Werner, I get the picture. It is not certain that this issue will be resolved in R1.1.1.2. I understand also your current living/situation. Well I was was considering the option of diving into the source code myself. After having debugged and traced the marshalling execution I decide not to continue. Is there any specific design documentation on castor xml? I would like have some overview of the castor marshalling situation.
Thanks Urso " Werner Guttmann" > Urso, > > there's a user that has offered some of his time to help us with this > issie. Unfortunately, I have not heard back since that initial offer. > > We'll try to get CASTOR-1342 into 1.1.2, but I don't think that this > will be possible without any additional help from the community. I for > myself, am trying to find a balance between my desire to spend as much > time as possible with my second daughter (and the mother behind this > little miracle) that was born a few weeks ago, my role as a committer > with an open source project and my day job (from which I tend to make a > living) > > Having said that, if somebody was to offer me (or the project) some > incentive to pick this issue up and deal with it according to your > (professional) priorities, I am sure this would be picked up immediately. > > If that's not an option, please have a look at the (preliminary) patches > attached to the issue and see whether you can help us coming up with a > solution. As far as I remember, there's plenty of guidelines and > suggestions already available. > > Regards > Werner > > Urso G.R. Wieske wrote: >> Hi Folks, >> >> I have checke with JIRA and issue "CASTOR-1342 UNRESOLVED Proxied >> classes >> need to be identified and receive special processing" is planned to be >> resolved in the next release 1.1.2 of Castor. >> >> I have put my hope on this release since I am hoping that this issue is >> resoved in R1.1.2. >> This issue with marshalling has been on the agenda for a long time. >> Until this morning (June 11th, 2007) I check the status of this issue, >> but >> it's still unresolved. >> >> Can someone of the team say if this issue is likely to be resolved in >> the >> next release? (It is next week already release 1.1.2) >> >> >> Kind regards, >> >> Urso >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
