Great! Thanks for the follow up -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
On Wed, Jul 18, 2018 at 1:44 PM, Matthew Broadhead < [email protected]> wrote: > ok i fixed that. it was just a null attribute causing the problem. so > everything looks ok for now. thanks for your help > > > On 18/07/18 11:49, Matthew Broadhead wrote: > >> i have the problem now. this is the exception i get if i exclude xalan >> from fop. i have no idea what might cause this >> >> javax.xml.transform.TransformerException: >> java.lang.ArrayIndexOutOfBoundsException: >> 0 >= 0 >> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl >> .transform(TransformerImpl.java:737) >> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl >> .transform(TransformerImpl.java:343) >> at uk.me.kissy.external.entityBeans.UtilityDao.getXMLParse( >> UtilityDao.java:191) >> at uk.me.kissy.external.entityBeans.UtilityDao$$OwbNormalScopeP >> roxy0.getXMLParse(uk/me/kissy/external/entityBeans/UtilityDao.java) >> at uk.me.kissy.document.dao.DocumentElementDao.getBodyPDF(Docum >> entElementDao.java:395) >> >> On 17/07/18 19:35, Matthew Broadhead wrote: >> >>> i have upgraded from fop 2.2 to 2.3 and excluded xalan and xml-apis >>> again. it seems to be working ok at the moment on my development machine. >>> i will try again on production >>> >>> <dependency> >>> <groupId>org.apache.xmlgraphics</groupId> >>> <artifactId>fop</artifactId> >>> <version>${fop.version}</version> >>> <exclusions> >>> <exclusion> >>> <groupId>xalan</groupId> >>> <artifactId>xalan</artifactId> >>> </exclusion> >>> <exclusion> >>> <groupId>xml-apis</groupId> >>> <artifactId>xml-apis-ext</artifactId> >>> </exclusion> >>> <exclusion> >>> <groupId>xml-apis</groupId> >>> <artifactId>xml-apis</artifactId> >>> </exclusion> >>> </exclusions> >>> </dependency> >>> <dependency> >>> <groupId>org.docx4j</groupId> >>> <artifactId>docx4j</artifactId> >>> <version>${docx4j.version}</version> >>> <exclusions> >>> <exclusion> >>> <groupId>xalan</groupId> >>> <artifactId>xalan</artifactId> >>> </exclusion> >>> </exclusions> >>> </dependency> >>> >>> On 17/07/18 12:46, Jean-Louis Monteiro wrote: >>> >>>> This usually indicates you have the same class loaded into 2 different >>>> classloaders which makes them different. >>>> In this scenario, I would check if you don't have duplicate xalan jars >>>> in >>>> tomee/lib and in the WEB-INF/lib of your application. >>>> >>>> Hope it helps >>>> >>>> -- >>>> Jean-Louis Monteiro >>>> http://twitter.com/jlouismonteiro >>>> http://www.tomitribe.com >>>> >>>> On Tue, Jul 17, 2018 at 2:06 AM, Matthew Broadhead < >>>> [email protected]> wrote: >>>> >>>> i have a couple of problems... >>>>> >>>>> i have not been able to upgrade from TomEE 7.0.3 to 7.0.4 or 7.0.5 due >>>>> to >>>>> the error (it works fine in 7.0.3) >>>>> java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault >>>>> cannot be cast to org.apache.xml.dtm.DTMManager >>>>> >>>>> which occurs when i run the following code for Apache FOP >>>>> ClassLoader classLoader = Thread.currentThread().getCont >>>>> extClassLoader(); >>>>> URL filepath = classLoader.getResource(xslPath); >>>>> Reader xsl = new InputStreamReader(filepath.openStream()); >>>>> TransformerFactory transformerfactory = TransformerFactory.newInstance >>>>> (); >>>>> StreamSource ssXsl = new StreamSource(xsl); >>>>> Templates templates = transformerfactory.newTemplates(ssXsl); >>>>> Transformer transformer = templates.newTransformer(); >>>>> StringReader reader = new StringReader(xml); >>>>> StringWriter writer = new StringWriter(); >>>>> transformer.transform(new StreamSource(reader), new >>>>> StreamResult(writer)); >>>>> out = writer.toString(); >>>>> writer.close(); >>>>> reader.close(); >>>>> >>>>> My new problem is that I am using 7.0.5 in development and this code >>>>> (using a CXF webClient) works perfectly. >>>>> Collection<? extends Integer> leadids = webClient.accept(MediaType.APP >>>>> LICATION_JSON).getCollection(Integer.class); >>>>> List<Integer> leadids_ = new ArrayList<>(leadids); >>>>> >>>>> But when I deployed it to 7.0.3 it does not work. Is there any way to >>>>> slurp some JSON formatted like this >>>>> [1,2,3,4] >>>>> >>>>> I tried creating a wrapper like below but it didn't match >>>>> public class listWrapper { >>>>> private List<Integer> list; >>>>> // ... >>>>> } >>>>> >>>>> >>> >> >
