I have a web application where i am using spring 3.0 rest mvc .The application runs perfectly fine on my local machine. But when in deploy the war in server(tomcat 6 & java 5) the below error occurs
Caused by: oracle.xml.parser.schema.XSDException: Duplicated
definition for: 'identifiedType'
I Googled and found that this issue is related to xmlparserv2.jar and this issue can be fixed by forcing the app to use apache xerces jars.
But i have not found any link explaining how to solve this issue.I do not want to changes at server level.
Can we fix these issues at application level?
Thanks in advance
My issue got resolved by including the xerces jars in the POm file
Related
I have a Java 11 application that works perfectly fine with Spring Boot v2.2.6.RELEASE, but it breaks when I upgrade to v2.2.7.RELEASE. The problem is that I get a java.lang.NullPointerException when reading the nested object:
jaxbUnmarshaller.unmarshal(new StringSource(xml)).getChild().foo();
I checked the SB release notes and this seems to be the breaking change: https://github.com/spring-projects/spring-boot/issues/21195
As migrating from Glassfish Jaxb 2.3.2 to 2.3.3 is a patch change, I would expect that this upgrade should require no changes from my side. I tried to check for some migration guide but found nothing at jaxb-ri page. Any idea would be welcome.
This sounds like a bug in the JAXB reference implementation. If you haven't already done so, I would search the RI's open issues for an existing report of your problem. If you don't find anything, I would then open an issue that describes your problem and includes a minimal sample that works with 2.3.2 and fails with 2.3.3.
maybe somebody can help me with my problem. Currently trying to get Camunda running within my Spring Boot App. The Core Camunda Parts i could get running, but now i would like to add also the WebApps of Camunda (Cockpit / Tasklist etc.)
i added the dependency:
<dependency>
<groupId>org.camunda.bpm.springboot</groupId>
<artifactId>camunda-bpm-spring-boot-starter-webapp</artifactId>
<version>7.13.0</version>
<scope>provided</scope>
I tried to access it via the localhost:8080/camunda/app/welcome/ but besides of the Loading indicator i cant see anything. In my Spring Boot Application instead I see that a lot of Java Script couldn't be found from Frontend Request. e.g getting the error 404 /localhost/camunda/require.js not found.
Has anybody any idea what i am doing wrong. I tried it once with an empty Spring Boot Project and there it was working fine, but adding it to an existing project causes this issue.
More information on your project (depenedency:tree) would be required to tell why. Most likely you have included incompatible versions. Clearing the browser cache or trying in a private window may also help.
You can always create a clean Spring Boot setup with compatible library / Spring Boot versions including engine, REST API, Web Apps (and possibly security, Camunda BPM assert) using https://start.camunda.com/.
I have my process(bpm file) defined as part of the Camunda Spring Boot project. I have a form attached to a Start Event. When I start my process I get "Form failure: Origin is not allowed by Access-Control-Allow-Origin" error.
I have checked Chrome console and found "XMLHttpRequest cannot load app:forms/my-form.html?noCache=1455724524763. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource" error message.
I had packaged the same process outside a Spring Boot project as a normal web app and deployed the war to Camunda Tomcat. It ran without any issue.
The issue happens when I package the same process as part of Camunda Spring Boot project.
Found 2 links describing similar issue but not helping much in terms of resolution.
https://github.com/plexiti/camunda-grails-plugin/issues/47
https://app.camunda.com/jira/browse/CAM-2146
Does Camunda Spring Boot project support embedded form. I have not seen any example of embedded form for Camunda Spring Boot.
I am pretty much stuck. So any help will be much appreciated.
This happens if the Tasklist can not determine the context path of the application. I just experienced that today in a customer training, when I undeployed a war file from a Wildfly.
A workaround could be to use an absolute path in the formKey, e.g. embedded:/mywebapp/forms/my-form.html
We had this problem as well. My coworker left this comment on the github issues of the project that you might find useful: https://github.com/camunda/camunda-bpm-spring-boot-starter/issues/39
I am working with jboss 6.2 that has resteasy standard version set to 2.3.7.
I need to use resteasy 3.0.8 and currently I am trying to achieve this result using maven and specifying that version in the pom, the correct resteasy is put in the war but seems like jboss keeps on using 2.3.7.
I am wondering if I am following the right path and if somebody can provide me some web resources to solve my issues.
I had the same issue.
This link could be usefull, it works great for me.
I'm trying to deploy an existing app to tc-server. I have been using this app on tomcat for a couple of years and the production version already runs on tc-server. I have installed the version of tc-server that comes with spring insight. Everything goes well until I deploy a war file that has a dependency on spring integration. I'm getting a no class def found error and it is complaining about a class called
org/springframework/integration/transformer/AbstractMessageProcessingTransformer
I opened up the spring integration jar that is bundled with my war in the WEB-INF lib and did not see that class.
I poked around in the tomcat instance that I created with the bat files in tc-server and see a later version of spring-integration i.e.
.\insight\collection-plugins\insight-plugin-spring-integration-1.9.2.SR1.jar
Since my war is now getting a class not found exception (whereas it deploys fine on my normal tomcat 6.29 ) I'm assuming that this other version of spring-integration is being seen by my app somehow. My app is configured to use spring-integration-1.0.4.
Does anyone know how to get around this problem?
1.0.4 is an extremely old version (3+ years old) the current release is 2.2.4. That class was introduced in 2.0.0.
So you probably have a classpath issue - insight needs a more recent version of Spring Integration on the classpath.
The insight plugin version (1.9.2.x) is not related to the Spring Integration version (but it needs a much more recent version than 1.0.4).