Note that you can use the direction="input" attribute on the <binding> element in this case to simplify your binding definition (and the generated code). This was kind of buried in the beta 3 docs, I've made it more prominent in beta 3a.
- Dennis
John Crossman wrote:
In this case, I'm only concerned about unmarshalling. So I assume the problem you describe will not affect my specific case. (?)
-----Original Message-----
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 9:37 PM
To: John Crossman
Cc: [EMAIL PROTECTED]
Subject: Re: [jibx-users] Name not allowed for CDATA (why?)
Whoops, I just realized this is the problem area that's been listed on the status page since beta 3 and is still an issue. The problem with this is that it'll always marshal as an empty element (even if the field value is null). There is a way around this, though, which is to use a test-method for the structure that just returns true if the field value is non-null. I'll document this in the beta 3a docs (which I'm just finishing up).
- Dennis
John Crossman wrote:
>Thanks Dennis. That worked.
>
>Is the reason bug-fix on usage="optional" for structures related to >these scenarios? Or would I have no problem in using:
>
> <structure name="c" usage="optional">
> <value style="cdata" field="cdataValue" usage="optional"/>
> </structure>
>
>If I need the bug fix, do I need to run a build against latest source >in cvs or can I just download the latest zip?
>
>Thanks
>
>J.
>
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ jibx-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jibx-users
