The "complaint" you mentioned sounds like a runtime problem. Is that correct? If so, are you sure your classpath at runtime matches the classpath you used while binding (so that the expected factory class can be found within the appropriate package)?
- Dennis
Venkatesh Prasad Ranganath wrote:
Following is a snippet from the doc for "binding"
package - Java package used for created binding factory class. By default this is the same package as the class associated with the first *mapping* child element. If present, the value must be a Java package name (as in "org.jibx.runtime").
I specified package in two binding files and it complained. The situation was binding file A dealt with class in a package X in working directory M (binding package spec="X"), file B dealt with classes in package Y in working directory M and a package Z in working directory N (binding package spec="Y"). The complain was that Factory class for the second binding could not be found in directory N/Y. However, if I remove the package spec in the second binding file, things worked fine. Is this something that I am messing up? Or an issue in JiBX?
- Venkatesh
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
jibx-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-users
