maven-jaxb2-plugin

JAXB fails to generate Java classes for XBRL

守給你的承諾、 提交于 2019-12-01 14:42:37
问题 I'm trying to generate Java classes for types defined in XBRL. My build process is based on Maven 2, and here are my trials. I only paste the build section, which relies on some properties: package is the name of my target package catalog is the path and file name of the catalog. because I have no internet connection, I have amny entries, but I think those are always necessary -- TR9401 for XBRL resources -- SYSTEM http://www.xbrl.org/2003/XLink http/www.xbrl.org/2003/xl-2003-12-31.xsd SYSTEM

jaxb, xsd import not recognized

♀尐吖头ヾ 提交于 2019-12-01 07:55:30
问题 I have a big problem with jaxb plugin. I have a project A where I have src/main/resources/xsd/common.xsd file. In this project I use cxf-xjc-plugin to generate java classes. I have also my episod file under src/main/resources/META-INF called sun-jaxb.episode Next, I have project B which has maven dependency to project A. In this project I have src/main/resources/catalog.txt PUBLIC "http://www.some_path" "maven:GROUP_ID_OF_PROJECT_A:ARTIFACT_ID_OF_PROJECT_A:jar::!/common.xsd" In project B I

maven-jaxb2-plugin VS jaxb2-maven-plugin for multiple schemas

♀尐吖头ヾ 提交于 2019-12-01 05:53:24
I have multiple xsd schemas that I want to unmarshall into different packages under the same folder target/generated-sources/xjc . I tried both plugins and both seem to work fine with these 2 configurations but in case of maven-jaxb2-plugin the eclipse plugin keeps generating classes indefinitely (because of the forceRegenerate = true) but if I don't specify forceRegenerate it won't generate the second and third set of classes at all when I run mvn clean package Are there any issues with my configuration? jaxb2-maven-plugin <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jaxb2-maven

maven-jaxb2-plugin reusing commons XSD within same project

﹥>﹥吖頭↗ 提交于 2019-11-30 15:25:40
I have a project which has a schema A and B, both within the same namespace. Both import schema C which also uses the same namespace. How can I generate JAXB classes for A and B to separate packages, while reusing the JAXB classes from C generated to a commons package? I already know I should probably be using episodes and use the episode generated for schema C as bindings file for the separate executions of schema's A and B. Problem is I don't know how to refer to this generated episode file. Here's an example: <plugin> <groupId>org.jvnet.jaxb2.maven2</groupId> <artifactId>maven-jaxb2-plugin<

Maven trouble when trying to generate from WSDL file

流过昼夜 提交于 2019-11-30 04:49:00
Im trying to generate sources from a wsdl file, but I keep running into an error on my pom.xml that I believe might be my issue? Below is the error that I get from my pom, and my pom file. Also I cannot build the project with "mvn clean install". I just seem to get an error with no real cause. The error at the generates tag: Execution default of goal org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.12.3:generate failed: A required class was missing while executing org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.12.3:generate: com/sun/codemodel/CodeWriter ------------------------------------------------

How does one get JAXB-generated sources onto the Eclipse build path under m2e/Indigo?

故事扮演 提交于 2019-11-29 23:32:02
Under Helios/m2eclipse, when I generated jaxb sources they would be put on the Eclipse source path when I did an "Update Project Configuration". This doesn't happen with Indigo/m2e (initial release of 22 June 2011). What do I need to do to fix this? I'm using the standard maven-jaxb2-plugin, version 0.75. Eric In Eclipse go to "Install New Software" add the software site: http://bitstrings.github.com/m2e-connectors-p2/releases/ Select the "m2e connector for jaxb2" Once you get that plugin installed the jaxb2 plugin should integrate correctly with the new version of m2e. This info is from:

How does one get JAXB-generated sources onto the Eclipse build path under m2e/Indigo?

痞子三分冷 提交于 2019-11-28 20:53:08
问题 Under Helios/m2eclipse, when I generated jaxb sources they would be put on the Eclipse source path when I did an "Update Project Configuration". This doesn't happen with Indigo/m2e (initial release of 22 June 2011). What do I need to do to fix this? I'm using the standard maven-jaxb2-plugin, version 0.75. 回答1: In Eclipse go to "Install New Software" add the software site: http://bitstrings.github.com/m2e-connectors-p2/releases/ Select the "m2e connector for jaxb2" Once you get that plugin

Create a common xsd generated class to be used by other packages

冷暖自知 提交于 2019-11-27 21:21:11
I am trying to use the same generated class but in separate packages. So the structure should look something like this: com.test.common -commonType.java com.test.A -objectA.java com.test.B -objectB.java But i keep getting this: com.test.common -commonType.java com.test.A -objectA.java -commonType.java com.test.B -objectB.java -commonType.java My common.xsd looks like this: <?xml version="1.0"?> <xs:schema elementFormDefault="qualified" version="1.0" targetNamespace="http://test.com/magic/common" xmlns="http://test.com/magic/common" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:jaxb="http:/

Create a common xsd generated class to be used by other packages

北战南征 提交于 2019-11-27 04:30:29
问题 I am trying to use the same generated class but in separate packages. So the structure should look something like this: com.test.common -commonType.java com.test.A -objectA.java com.test.B -objectB.java But i keep getting this: com.test.common -commonType.java com.test.A -objectA.java -commonType.java com.test.B -objectB.java -commonType.java My common.xsd looks like this: <?xml version="1.0"?> <xs:schema elementFormDefault="qualified" version="1.0" targetNamespace="http://test.com/magic

Is there a way to deal with duplicate element definitions across multiple .xsd files in JAXB?

五迷三道 提交于 2019-11-26 22:51:15
问题 I have dozens and dozens .xsd files that I want to auto-generate code for. A couple of the files have duplicate names that clash when I try to generate all of them at the same time. I am focusing on just trying to get 2 of these to work. When I get these 2 working I will fix the rest. But I am just focusing on 2 of these files for now. I am not in control of them, they are from a vendor and follow a "standard" , so editing them is not an option for multiple reasons. I am using the maven-jaxb2