Falk Langhammer wrote:
[EMAIL PROTECTED] wrote:Yes, I should have qualified my comment to say there's only a problem when the references are directly items in the collection. I'll clarify this on the status page, since it can be a major issue and there's no good workaround at present (except to wrap the object reference within another object).
This is a known issue, which I'll add to the status page. The problem is with forward references to objects from collections. If your XML defines the IDs before the references to them from inside the collections there won't be a problem; this obviously doesn't help if you're stuck with XML documents that use forward references.
We used three different forward references to objects from collections in our binding. Two of them work just fine. This one fails.
The difference is that the collection which fails contains the id-ref directly.
The two collections which work contain a mapping to some type which then contains the id-ref (as a <value>). This works. In the document, the id-defs occurr after their id-refs.
To show forward references which work, I attached our binding.
Falk
- Dennis
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
jibx-devs mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-devs
