Hi

Like another user on this list - I'm trying to generate a sort of  
modular set of bindings for my data access objects. My process is to  
generate my core classes, run the binding and then create the jar.  
Now, with the classes that are using these core pre-enhanced classes,  
I have some bindings which reference those classes. To generate the  
bindings for these classes, I unjar the core classes, add then to the  
paths, and then run the binding over the consumer classes (for want  
of a better term). When I actually come down to running the consumer  
classes, I use the original jar file (with the bound classes) and  
these bound consumer classes. It works quite well.

To make this fully modular, I'd like to use the original binding file  
from the core classes, and just include that in my consumer classes.

i.e.

core-binding.xml
<binding>
        <mapping name="CoreObject" class="CoreObject">
                <!--    Some value elements... -->
        </mapping>
</binding>


consumer-binding.xml
<binding>
        <include path="core-binding.xml"/>
        <mapping name="ConsumerObject" class="ConsumerObject">
                <value name="aCoreObject" field="aCoreObject"/>
        </mapping>
</binding>


However - this doesn't work, as it gives me an array out-of-bounds- 
exception (stack trace at the end of the email) at runtime.

If I change the consumer binding around, and use a stub core definition
<binding>
        <mapping name="ConsumerObject" class="ConsumerObject">
                <value name="aCoreObject" field="aCoreObject"/>
        </mapping>
        
        <mapping name="CoreObject" class="CoreObject"/>
</binding>

this mapping works.

Now, this might be something to do with the fact that I'm using jibx  
to do data binding in xfire. Does the include actually behave in a  
slightly different way to manually including mapping elements?

Cheers,

Hiren

java.lang.ArrayIndexOutOfBoundsException: 7
         at org.codehaus.xfire.jibx.JibxType.<init>(JibxType.java:58)
         at org.codehaus.xfire.jibx.JibxTypeCreator.createDefaultType 
(JibxTypeCreator.java:15)
         at  
org.codehaus.xfire.aegis.type.AbstractTypeCreator.createTypeForClass 
(AbstractTypeCreator.java:102)
         at  
org.codehaus.xfire.aegis.type.AbstractTypeCreator.createType 
(AbstractTypeCreator.java:334)
         at  
org.codehaus.xfire.aegis.AegisBindingProvider.getSuggestedName 
(AegisBindingProvider.java:226)
         at  
org.codehaus.xfire.service.binding.DefaultServiceConfiguration.getOutPar 
ameterName(DefaultServiceConfiguration.java:174)
         at  
org.codehaus.xfire.service.binding.ObjectServiceFactory.getOutParameterN 
ame(ObjectServiceFactory.java:1033)
         at  
org.codehaus.xfire.service.binding.ObjectServiceFactory.addOperation 
(ObjectServiceFactory.java:794)
         at  
org.codehaus.xfire.service.binding.ObjectServiceFactory.initializeOperat 
ions(ObjectServiceFactory.java:720)
         at  
org.codehaus.xfire.service.binding.ObjectServiceFactory.create 
(ObjectServiceFactory.java:418)

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to