Without seeing your binding definition it's difficult to say why the exception is being thrown. You may be best off sticking with the structure and label-using approach until beta 4 is out in any case, since <mapping> is really intended for cases where a particular class is linked to a particular element name. Using a <structure> for each instance allows you to match the name to the class instance in context, and that sounds like what you want to do.

 - Dennis

chris wrote:

Hi all,

Im working on a binding problem right now that seems like it should be very simple, 
but having some newbie types of problems.

What I have, is the same type of object created from different element names.  So, the 
XML looks like this:
<Request>
 <RequestList>
   <RequestType> ... </RequestType>
   <RequestData> ... </RequestData>
 </RequestList>
 <AnotherRequestList>
   <RequestType> ... </RequestType>
   <RequestData> ... </RequestData>
 </AnotherRequestList>
</Request>

The objects created from RequestList and AnotherRequestList should be the same.

When I create the binding file with the RequestList as a structure, and a label, then 
add a 'using' attribute to the 'AnotherRequestList' all works fine.

If I create a <mapping> for the RequestList, and then try to map the structures to it, 
I get:
java.lang.IllegalStateException: Internal error - no instance creation
       ...




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

Reply via email to