Hi Linus,
I'm not certain exactly what you mean by this - is the issue that if you put a "label" on a structure with an ID value, then reuse that definition elsewhere with a "using" the ID value is not recognized? I wasn't aware of a problem with this, but it wouldn't surprise me. The label/using linkage is a mess, which is why I'm replacing it. And yes, the <template> implementation will handle IDs properly.
As for the ENTITY issue, this is a limitation of the XMLPull parsers currently available. I'd originally expected to replace the XMLPull parser interface with a StAX one, but StAX parsers seem to be moving very slowly. I may instead look into just adding ENTITY support to XPP3 post-production release (along with some other performance and usability enhancements I've discussed on the XMLPull list).
- Dennis
Linus Kamb wrote:
All of my objects carry along their ID values (database primary keys) along with a host of other accounting and management information. Those ID values are IDREF'd in places.
I would rather not have to enter in all that stuff in object mapping, but it seems that if I don't the IDREFs fail.
What is going to be the best way to go about doing this? Using a "map-as" or "using" don't seem to work because of the ID/IDREF issue. I tried adding an internal DTD entry, but the pull parser complained about an unexpanded entity reference.
Do you suppose the <template> elements will carry ID information forward?
-------------------------------------------------------
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-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-users
