Hi Frank,
There's definitely an inconsistency there - the runtime binding was
using everything up to the last '.' as part of the default binding name,
while the standalone binding compiler was just going to the first '.'.
I've changed the runtime binding to work the same way as the standalone
binding.
- Dennis
Frank Mena wrote:
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>"
I wonder if this is a bug or I have overlooked something.
Thanks,
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
jibx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-users
