GPL-2.0-with-classpath-exception:. Modified BSD: jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettisonĮclipse Distribution License - v 1.0: Jakarta XML Binding APIĮPL 2.0: HK2 API module, HK2 Implementation Utilities, Jakarta Annotations API, OSGi resource locator, ServiceLocator Default Implementation, aopalliance version 1.0 repackaged as a module, jersey-core-common, jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettison This scenario is useful when REST applications are migrated from TomEE 1.7.x into TomEE 7.x or later and you want to keep the legacy JSON output from Jettison 1.3.7. W3C license: jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettisonĮDL 1.0: Jakarta Activation, jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettison This is a example on how to configure on TomEE 7.x or later the legacy JSON provider, Jettison, used by TomEE 1.7.x. Public Domain: jersey-core-common, jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettison GPL2 w/ CPE: HK2 API module, HK2 Implementation Utilities, Jakarta Annotations API, OSGi resource locator, ServiceLocator Default Implementation, aopalliance version 1.0 repackaged as a module, jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettison JQuery license: jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettison Here is my com.documentum module.Apache License, 2.0: jersey-core-common, jersey-inject-hk2, jersey-media-jaxb, jersey-media-json-jettison Next CMFE was for ansaction - so I added that, and I seem to have made it through the Documentum related errors. I ran into some log4j complaints, so I commented out the log4j.jar from the com.documentum module.xml and added a dependency to 4j. I knew the dfc.jar had a number of Jars referenced in its Manifest, so I took the full set of JARs included from EMC and dumped them into a module.well, actually I did that AFTER I realized that I had somehow been missing the one key file - dfc.jar - how it got lost I don't know? I thought it might be nice to have a DFC module, so I played with that for a while. I decided to try a slimmer project, and just have GWT and DFC in there. * Libs pulled in for Documentum/DFC (thanks so much for your help so far Stephen) Once you open a JAR file, all the java classes in the JAR file will be displayed. java) Click menu 'File Open File.' or just drag-and-drop the JAR file in the JD-GUI window jettison-1.5.4.jar file. #14 - dfc.jar contains com/documentum/fc/client/content/impl/LocalContentManager.class Download JD-GUI to open JAR file and explore Java source code file (.class. resteasy-jettison-provider-2.3.1.GA.jar.These are the 3rd-party JARS included in our WEB-INF/lib folder: I also followed this: - but I'm not sure I was able to do anything with the dependency reports from tattletale. It seems odd to me that I can't keep these libraries in WEB-INF/lib if they are only needed within the WAR?ġ9:18:50,087 ERROR (DeploymentScanner-threads - 1) ġ9:18:54,627 ERROR (Session pool worker) Exception in thread "Session pool worker" : com/documentum/fc/client/content/impl/LocalContentManagerġ9:18:54,628 ERROR (Session pool worker) at .disconnect(Session.java:245)ġ9:18:54,629 ERROR (Session pool worker) at .disconnectSessions(SessionPool.java:111)ġ9:18:54,635 ERROR (Session pool worker) at .flush(SessionPool.java:134)ġ9:18:54,636 ERROR (Session pool worker) at .flushAllPools(SessionPool.java:190)ġ9:18:54,636 ERROR (Session pool worker) at .$n(SessionPool.java:246)ġ9:18:54,637 ERROR (Session pool worker) Caused by: . from ġ9:18:54,637 ERROR (Session pool worker) at .findClass(ModuleClassLoader.java:190)ġ9:18:54,638 ERROR (Session pool worker) at .performLoadClassUnchecked(ConcurrentClassLoader.java:468)ġ9:18:54,638 ERROR (Session pool worker) at .performLoadClassChecked(ConcurrentClassLoader.java:456)ġ9:18:54,639 ERROR (Session pool worker) at .performLoadClassChecked(ConcurrentClassLoader.java:423)ġ9:18:54,639 ERROR (Session pool worker) at .performLoadClass(ConcurrentClassLoader.java:398)ġ9:18:54,640 ERROR (Session pool worker) at .loadClass(ConcurrentClassLoader.java:120)ġ9:18:54,640 ERROR (Session pool worker). I've tried various things, including creating a module: com.documentum with all the dependent jars, and added that dependency to my jboss-deployment-structure.xml. Currently I have all of the jar files in WEB-INF/lib, which works fine on JBoss 5.1 as well as OC4J. I'm moving to JBoss 7 from another app server, and I've worked through some issues, but having some trouble working out this issue.
0 Comments
Leave a Reply. |