[ https://issues.apache.org/jira/browse/XMLBEANS-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470246#comment-17470246 ]
Andreas Beeker commented on XMLBEANS-567: ----------------------------------------- I've fixed some disabled test regarding the extension interfaces. Beside the javaparser, you'll also need the javaparser-symbol-solver-core jar. Please try it again with the trunk version. If it doesn't work, please provide me the test files. > Problems with XMLBeans Extension Interfaces Feature > --------------------------------------------------- > > Key: XMLBEANS-567 > URL: https://issues.apache.org/jira/browse/XMLBEANS-567 > Project: XMLBeans > Issue Type: Task > Affects Versions: Version 5.0.0 > Reporter: Dmitry Lastochkin > Priority: Major > > Hello! In our project we are using [XMLBeans Extension Interfaces > Feature|https://cwiki.apache.org/confluence/display/XMLBEANS/ExtensionInterfacesFeature]. > When we compile the TypeSystem (using {{SchemaTypeSystemCompiler.compile}}), > we add the jar with our extension classes to classpath parameter. In XMLBeans > 2.4 it works perfectly. But when we updated to XMLBeans 5.0.0, we encountered > the following error during an extensions validation: > {code} > Interface 'SomeInterface' not found." > {code} > As far as I understand, this is because > {{org.apache.xmlbeans.impl.config.Parser}} does not search classes in > classpath (only in files). > When we added the sources of the extension interface to the parameters, > TypeSystem compiled successfuly. But then we ran into another problem. When > XMLBeans generates java files from XSD, it uses simple class names (instead > of fully qualified names as it was in XMLBeans 2.4.0) for the classes that > are used in methods of the extension interface (like parameters types or > return types). And therefore the geneted files cannot be compiled if the > extension classes are in a different package. > Are those changes (ingorning classpath when searching for extenstions and > using simple names for extenstion classes in code generation instead of fully > qualified names) were made intentionally? Such limitations are hard to work > around, making an upgrade from older XMLBeans version very complicated. -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org