You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by "Gonzalez, Mark A" <ma...@lmco.com> on 2003/10/09 21:37:06 UTC
Running FOP on ColdFusion MX
Hi,
I am running into an interesting problem when trying to run FOP on Cold
Fusion MX for J2EE server. The current configuration is WebSphere 5.0,
running CFMX for J2EE.
When we try to execute the servlet from the coldfusion page (using the
java object commands)
the process starts running but then throws an exception. The stack
trace is as follows:
Error = java.lang.IllegalArgumentException:
org.apache.fop.svg.SVGElementMapping is not an ElementMapping
at org.apache.fop.apps.Driver.addElementMapping(Driver.java:464)
at
org.apache.fop.apps.Driver.setupDefaultMappings(Driver.java:314)
at org.apache.fop.apps.Driver.(Driver.java:222)
at ReportUtil.renderXMLWithFOP(ReportUtil.java:124)
at ReportUtil.buildReport(ReportUtil.java:77)
at ReportUtil.jspTest(ReportUtil.java:108)
at java.lang.reflect.Method.invoke(Native Method)
at coldfusion.runtime.java.JavaProxy.invoke(Unknown Source)
at coldfusion.runtime.CfJspPage._invoke(Unknown Source)
at
cfdsp_osha300_log2ecfm1640372303.runPage(/export/home1/projects/lmsii/op
t/WebSphere/AppServer/installedApps/sstst2/Macromedia ColdFusion
MX.ear/cfusion.war/DEV/Report/log.cfm:118)
at coldfusion.runtime.CfJspPage.invoke(Unknown Source)
at coldfusion.tagext.lang.IncludeTag.doStartTag(Unknown Source)
at coldfusion.filter.CfincludeFilter.invoke(Unknown Source)
at coldfusion.filter.ApplicationFilter.invoke(Unknown Source)
at coldfusion.filter.PathFilter.invoke(Unknown Source)
at coldfusion.filter.ExceptionFilter.invoke(Unknown Source)
at coldfusion.filter.BrowserDebugFilter.invoke(Unknown Source)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(Unknown
Source)
at coldfusion.filter.BrowserFilter.invoke(Unknown Source)
at coldfusion.filter.GlobalsFilter.invoke(Unknown Source)
at coldfusion.filter.DatasourceFilter.invoke(Unknown Source)
at coldfusion.CfmServlet.service(Unknown Source)
at coldfusion.bootstrap.BootstrapServlet.service(Unknown Source)
at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictSe
rvletInstance.java:110)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLi
fecycleServlet.java:174)
at
com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycle
Servlet.java:313)
at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLif
ecycleServlet.java:116)
at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.
java:258)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(Vali
dServletReferenceState.java:42)
at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(Servle
tInstanceReference.java:40)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispa
tch(WebAppRequestDispatcher.java:872)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRe
questDispatcher.java:491)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppReq
uestDispatcher.java:173)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:7
9)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInv
oker.java:199)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocati
on(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(Servle
tRequestProcessor.java:182)
at
com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSELis
tener.java:331)
at
com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection
.java:56)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:
432)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
The interesting thing is, if we move the servlet out of the coldfusion
environment and into its own war file and deploy it as its own
mini-application, everything works fine (BTW, commanline works fine
too). Given that, I suspected that there might be some library
conflicts between the needed FOP jars and those that are included with
Cold Fusion MX, however, after adding the needed JARS into WebSphere's
Classpath and using the Environment Check method to return the parser
versions, I am not so sure that is the issue. Here is the output from
the environment check:
EnvironmentCheck = {version.DOM.draftlevel=2.0fd
:
java.class.path=/export/home1/projects/lmsii/opt/WebSphere/AppServer/pro
perties :/export/home1/projects/lmsii/opt/WebSphere/AppServer/properties
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/lib/bootstrap.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/lib/j2ee.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/lib/lmproxy.jar
: version.JAXP=1.1
:
java.ext.dirs=/export/home1/projects/lmsii/opt/WebSphere/AppServer/java/
jre/lib/ext
:
foundclasses.sun.boot.class.path=[{xml-apis.jar-apparent.version=xml-api
s.jar from xalan-j_2_4_1
: lotusxsl-j_2_3_4 or lotusxsl-j_2_3_5 from factoryfinder-build of
xml-commons RIVERCOURT1
:
xml-apis.jar-path=/export/home1/projects/lmsii/opt/WebSphere/AppServer/i
nstalledApps/sstst2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/xml-apis.jar}]
: version.xerces2=Xerces-J 2.2.1
: version.xerces1=not-present
: version.xalan2_2=Xalan Java 2.4.1
: version.xalan1=not-present
: version.ant=Ant version 1.4.1 compiled on October 11 2001
: java.version=1.3.1_05
: version.DOM=2.0
: foundclasses.java.ext.dirs=[]
: version.crimson=present-unknown-version
:
sun.boot.class.path=/export/home1/projects/lmsii/opt/WebSphere/AppServer
/java/jre/lib/ext/ibmorb.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/java/jre/lib/ext/i
bmext.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/webchartsJava2D.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion MX.ear/cfusion.war/WEB-INF/cfusion/lib/fop.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/batik.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/xalan-2.4.1.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/xercesImpl-2.2.1.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/jimi-1.0.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/avalon-framework-cvs-20020806.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/installedApps/ssts
t2/Macromedia ColdFusion
MX.ear/cfusion.war/WEB-INF/cfusion/lib/xml-apis.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/java/jre/lib/rt.ja
r
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/java/jre/lib/i18n.
jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/java/jre/lib/sunrs
asign.jar
:/export/home1/projects/lmsii/opt/WebSphere/AppServer/java/jre/classes
: foundclasses.java.class.path=[]
: version.SAX=2.0
: version.xalan2x=Xalan Java 2.4.1}
Any thoughts or suggestions would be greatly appreciated.
Thanks,
Mark Gonzalez
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Running FOP on ColdFusion MX
Posted by Glen Mazza <gr...@yahoo.com>.
What version of FOP are you running?
--- "Gonzalez, Mark A" <ma...@lmco.com>
wrote:
> Hi,
>
> I am running into an interesting problem when trying
> to run FOP on Cold
> Fusion MX for J2EE server. The current configuration
> is WebSphere 5.0,
> running CFMX for J2EE.
> When we try to execute the servlet from the
> coldfusion page (using the
> java object commands)
> the process starts running but then throws an
> exception. The stack
> trace is as follows:
>
> Error = java.lang.IllegalArgumentException:
> org.apache.fop.svg.SVGElementMapping is not an
> ElementMapping
> at
>
org.apache.fop.apps.Driver.addElementMapping(Driver.java:464)
> at
>
org.apache.fop.apps.Driver.setupDefaultMappings(Driver.java:314)
> at
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org