I found out
JiBX is a little picky on the binding file name format when using runtime
binding. The same file name works fine for bindings done in compile
time.
For example, there is a mapping file named "<myclass>.xml", which defines mapping for class "com.myco.package.myclass", everything works fine using runtime and compile time binding. However, if the mapping file name is changed to "<myclass>.config.jibx.xml", my application will have problem to find the binding factory for the class if the binding is done in runtime. Error message says "Binding <myclass> not found for class <com.myco.package.myclass>"
For example, there is a mapping file named "<myclass>.xml", which defines mapping for class "com.myco.package.myclass", everything works fine using runtime and compile time binding. However, if the mapping file name is changed to "<myclass>.config.jibx.xml", my application will have problem to find the binding factory for the class if the binding is done in runtime. Error message says "Binding <myclass> not found for class <com.myco.package.myclass>"
I wonder if
this is a bug or I have overlooked something.
Thanks,
Thanks,
