Re: [jibx-users] JiBX Best Practices

[Dennis Sosnoski]

I'm not sure exactly what you mean by the "traits" approach. The 
<template> is basically a reusable binding definition structure that's 
defined with a particular object type. You should be able to define 
multiple <template>s for the same object type and combine them in a 
<mapping> or <structure>, but they'd be in a particular order (or 
unordered and optional). That's getting into some pretty wierd code 
generation, though, so no guarantees.

 - Dennis
Guillaume Pothier wrote:
Right now there's no good way to share components of binding definitions 
(the label/using approach is fairly ugly, and probably still broken in 
some edge cases), so I think people end up using <mapping> more than 
they should. For beta 4 I'll be adding a <template> element to the 
binding definition to allow for reusable structures without the overhead 
of a <mapping> or the
   

Will the <template> element be similar to the "traits" approach, ie, a 
mapping can combine any number of templates? That would be real great!

 


-------------------------------------------------------
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