https://bz.apache.org/bugzilla/show_bug.cgi?id=65273
--- Comment #3 from Angelica Salazar <angelica.sala...@easesolutions.com> --- (In reply to Mark Thomas from comment #2) > First the good news. I can recreate this. I downloaded trail versions of > Jira and R4J, created a single issue, requested an export and saw the > exception and at the bottom of the stack trace: > > "Caused by: java.lang.ClassCastException: > org.apache.xerces.stax.XMLEventFactoryImpl cannot be cast to > javax.xml.stream.XMLEventFactory" > > The bad news is the Jira has its own class loader structure for plug-ins. I > suspect a change in this area may be a factor. That isn't something the > Tomcat team is going to be able to help with. > > I'm technically a committer for POI (I helped out with the ALv1 to ALv2 > license migration many, many years ago) but I do not know POI at all. I'll > have a look to see if I can create a simpler test case and/or find any clues > to what might be going on but the most likely result is that this issue will > be closed as INVALID as there isn't any evidence that points to a Tomcat > issue at the root if it. Hello Mark, May I ask for the steps you did to produce the error: "Caused by: java.lang.ClassCastException: org.apache.xerces.stax.XMLEventFactoryImpl cannot be cast to javax.xml.stream.XMLEventFactory"? An idea on the type of environment you installed it in will also be helpful as we're struggling to reproduce the issue on our own environments. After this, if it's not related to Apache Tomcat, please close the issue. I truly appreciate the response. Thank you and best regards, Angelica -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
