[
https://issues.apache.org/jira/browse/XMLBEANS-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538470#comment-17538470
]
Andreas Beeker commented on XMLBEANS-567:
-----------------------------------------
I've just updated the gradle build to export the necessary libs to build/libs.
So currently you need the following libs:
(ant-1.10.12.jar)
(ant-launcher-1.10.12.jar)
guava-31.0.1-jre.jar
javaparser-core-3.24.0.jar
javaparser-symbol-solver-core-3.24.0.jar
javassist-3.28.0-GA.jar
log4j-api-2.17.2.jar
Saxon-HE-11.3.jar
xmlbeans-5.1.0-SNAPSHOT.jar
xmlresolver-4.2.0-data.jar
xmlresolver-4.2.0.jar
the java call from your shell script is the following - with the above
xsdconfig:
{{$JAVA_HOME/bin/java -Xmx256m -classpath "$cp"
org.apache.xmlbeans.impl.tool.SchemaCompiler \}}
{{ -d $b/classes\}}
{{ -src $b/java \}}
{{ -out $jar \}}
{{ src/main XSD/EasyPO.xsd XSD/EasyPO.xsdconfig}}
> 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
> Attachments: xmlbeans-ie-tryout.tar
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
