java.lang.IllegalStateException: Internal error: Expected MyClass on stack, found MyClass[]

I received the same error, but I was able to narrow it down to a more specific binding. At the moment, I suspect that it's the use of the "label/using" that's causing the problem - I'm trying to port it to an AbstractMapping, but if label/using is still accepted by the parse, it probably shouldn't cause compile errors ; ). Here's a small binding that reproduces the same problem (using jibx_1_1):

<binding>
<mapping name="OriginDestinationInformation"
class="com.travelocity.datatype.air.common.datasource.OriginDestinati
onInformationXmlHelper">
<value name="DepartureDateTime" get-method="getDepartureDateTime" set-method
="setDepartureDateTime"/>
<structure name="OriginLocation"
type="com.travelocity.datatype.air.common.AirportLocation"
get-method="getOriginLocation"
set-method="setOriginLocation"
value-style="attribute"
label="airport_location">
<value name="LocationCode" get-method="getLocationCode" set-method="setLoc
ationCode" />
<value name="CodeContext" get-method="getCodeContext" set-method="setCodeC
ontext" usage="optional"/>
</structure>

<structure name="TPA_Extensions" >
<structure name="DateFlexibility"
value-style="attribute"
usage="optional" >
<value name="NbrOfDays"
get-method="getDateFlexibility"
set-method="setDateFlexibility"
usage="optional"/>
</structure>
<collection get-method="getSisterDestinationLocations"
set-method="setSisterDestinationLocations"
usage="optional">
<structure name="SisterDestinationLocation"
type="com.travelocity.datatype.air.common.AirportLocation"
using="airport_location"/>
</collection>
<collection get-method="getSisterOriginLocations"
set-method="setSisterOriginLocations"
usage="optional">
<structure name="SisterOriginLocation"
type="com.travelocity.datatype.air.common.AirportLocation"
using="airport_location"/>
</collection>
</structure>
</mapping>

</binding>

Same binding file as above, added as attachment for convenience.

I notice this filed itself under jibx-1.0 (since I cloned an existing "cannot reproduce" issue after I was able to reproduce it), but I actually observed this behavior in jibx 1.1. Unfortunately, it doesn't look like JIRA lets me reclassify the version number.

Even smaller zip that consistently reproduces the problem, along with compilable source code.

Upon further testing, the problem seems to be limited to jibx-rc0 and up (including jibx-1.1, which is the latest release), and only occurs when you try to refer to a previously "label"-ed structure inside a collection (included binding.xml file demonstrates this exactly).

I'll continue to debug and see if I can pin down the precise cause.

I deprecated label/using because it was both too messy to implement and not flexible enough to be really useful. I can't take the time to support it, but I'll leave this bug open as a warning to anyone else working with it. Sorry...

I see there hasn't been commented on this issue in years, but i am using an old version of JiBX and i am having the same problem (stack error when using "using" inside a collection). It seems that if i write it out (a lot of redudancy) it seems to work.

I also tried the latest version of JiBX, but the binding format seems to have changed a lot as i get spammed with lots of errors and deprecated warnings (i have a rather large binding file).

What is/was the best way to handle this problem with the old version?