Entry BOOT-INF/lib/jaxb-core-4.0.1.jar is a duplicate but no duplicate handling strategy has been set #33659
Comments
spring-projects-issues
added
the
status: waiting-for-triage
|
org.hibernate:hibernate-envers:6 . |
|
Another workaround: tasks.named('bootJar') { |
|
@HououinKyouma2000 Disabling boot repackaging will prevent the application from runnning as an executable jar and won't solve the underlying problem. @naihil I'm not sure excluding the dependency will solve the issue here, as excluding duplicates will exclude one of the jaxb-core jars: in this case, they're holding different content with classes located under different packages. This could lead to missing classes at runtime. It looks like spring-ws-core has a hard dependency on Spring Boot has been using the Glassfish RI for a while now, so I'm wondering if this is an oversight or even needed in spring-ws? Does the following work for your applications @naihil ? |
bclozel
added
the
for: team-meeting
Checked this variant, application builds and tests fine, fat jar contains jaxb-core-4.0.1.jar and jaxb-runtime-4.0.1.jar Variant with DuplicatesStrategy.EXCLUDE compiles and tests fine too, but fat jar contains jaxb-core-4.0.1.jar, jaxb-runtime-4.0.1.jar and jaxb-impl-4.0.1.jar |
|
Oops, close accidentally, reopen. |
spring-ws can migrate to org.glassfish.jaxb:jaxb-runtime from com.sun.xml.bind:jaxb-impl, as both contain same classes only differs with packing style. https://eclipse-ee4j.github.io/jaxb-ri/4.0.1/docs/release-documentation.html#deployment-maven-coordinates
In contrast to org.glassfish.jaxb artifacts, these(com.sun.xml.bind:jaxb-impl) jars have all dependency classes included inside. |
|
We've discussed this as a team and we've created a Spring WS issue to address this problem. See spring-projects/spring-ws#1305 |
bclozel
added
status: invalid
|
Hi @everyone, Execution failed for task ':war'.
I try to add this below in build.gradle, but still not work for me: bootWar { |
|
@yisivlay Your error occurred when running the |
|
@wilkinsona could you pls suggestion me clearly about this? |
|
The issue tracker isn't really the right place for this sort of support as it creates too much noise for those watching the repository. If you have further questions, please follow up on Stack Overflow. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. |
|
@wilkinsona Thanks for your suggestions! |
|
I have a similar problem when generating a service from a wsdl tutorials: and generate by xsd plugins {
id 'java'
id 'org.springframework.boot' version '3.1.5'
id 'io.spring.dependency-management' version '1.1.3'
}
group = 'group'
version = '0.0.1-SNAPSHOT'
java {
sourceCompatibility = '21'
}
ext.jaxwsSourceDir = "${buildDir}/generated/sources/jaxws"
configurations {
jaxb
jaxws
compileOnly {
extendsFrom annotationProcessor
}
}
sourceSets {
main {
java {
srcDir 'src/main/java'
srcDir 'build/generated/sources/jaxb'
srcDir jaxwsSourceDir
}
}
}
task genJaxb {
ext.sourcesDir = "${buildDir}/generated/sources/jaxb"
ext.schema = "src/main/resources/xsd/catalogs.xsd"
ext.binding = "src/main/resources/jxb/bindings.xjb"
outputs.dir sourcesDir
doLast() {
project.ant {
taskdef name: "xjc", classname: "com.sun.tools.xjc.XJCTask",
classpath: configurations.jaxb.asPath
mkdir(dir: sourcesDir)
xjc(destdir: sourcesDir, schema: schema, binding: ext.binding) {
arg(value: "-wsdl")
produces(dir: sourcesDir, includes: "**/*.java")
}
}
}
}
task wsimport {
description = 'Generate classes from wsdl using wsimport'
doLast {
project.mkdir(jaxwsSourceDir)
ant {
taskdef(name: 'wsimport',
classname: 'com.sun.tools.ws.ant.WsImport',
classpath: configurations.jaxws.asPath
)
wsimport(
keep: true,
destdir: jaxwsSourceDir,
extension: "true",
verbose: true,
wsdl: "https://secret.com/SERVICEWS/soap?wsdl",
xnocompile: true,
package: "com.mos.ehd") {
xjcarg(value: "-XautoNameResolution")
}
}
}
}
compileJava.dependsOn genJaxb
compileJava.dependsOn wsimport
repositories {
mavenCentral()
}
dependencies {
implementation 'org.springframework.boot:spring-boot-starter-web-services'
implementation 'org.springframework.boot:spring-boot-starter-validation'
implementation 'org.springframework.boot:spring-boot-starter-data-jpa'
implementation 'org.springframework.boot:spring-boot-starter-cache'
implementation 'org.flywaydb:flyway-core'
// support xml/xsd/wsdl
implementation 'wsdl4j:wsdl4j'
implementation 'com.sun.xml.ws:jaxws-rt:4.0.2'
jaxb('org.glassfish.jaxb:jaxb-xjc:4.0.4')
jaxws 'com.sun.xml.ws:jaxws-tools:4.0.2',
'jakarta.xml.ws:jakarta.xml.ws-api:3.0.0',
'jakarta.xml.bind:jakarta.xml.bind-api:4.0.1',
'jakarta.activation:jakarta.activation-api:2.1.2'
compileOnly 'org.projectlombok:lombok'
developmentOnly 'org.springframework.boot:spring-boot-devtools'
runtimeOnly 'org.postgresql:postgresql'
annotationProcessor 'org.springframework.boot:spring-boot-configuration-processor'
annotationProcessor 'org.projectlombok:lombok'
testImplementation 'org.springframework.boot:spring-boot-starter-test'
}
bootJar {
setDuplicatesStrategy(DuplicatesStrategy.WARN)
}
tasks.named('test') {
useJUnitPlatform()
}So far, I have no idea how to deal with this problem without setting a duplication strategy, which is incorrect. UPD: Problem solved: |
|
So it's just about replacing
You might want to add But other classes are also missing in 
So in my opinion, an easier drop-in replacement is just to exclude implementation("com.sun.xml.ws:jaxws-rt") {
exclude(group = "com.sun.xml.bind", module = "jaxb-impl")
}
runtimeOnly("org.glassfish.jaxb:jaxb-runtime") |
Simple gradle Spring Boot 3 project with Spring Data and Spring Web Services:
build.gradle:
Error:
The text was updated successfully, but these errors were encountered: