"Content is not allowed in prolog"
Jeff Mutonho
I'm trying to get ant to transform some jmeter test results into
html.The ant target is defined as follows :
<xslt
in="${basedir}/loadtests/JMeterResults.jtl"
out="${basedir}/loadtests/JMeterResults.html"
style="${basedir}/jmeter-results-detail-report/jmeter-results-detail-report.xsl"/>
where jmeter-results-detail-report.xsl is an XSLT file for for
generating a detailed report from the result log file.However when I
run this task , I get the following error message:
[xslt] Processing D:\MAVEN-WORK\eportal-functional-tests\loadtests\JMeterRe
sults.jtl to D:\MAVEN-WORK\eportal-functional-tests\loadtests\JMeterResults.html
[xslt] Loading stylesheet D:\MAVEN-WORK\eportal-functional-tests\jmeter-res
ults-detail-report\jmeter-results-detail-report.xsl
[xslt] : Error! Content is not allowed in prolog.
[xslt] : Error! com.sun.org.apache.xml.internal.utils.WrappedRuntimeExcepti
on: Content is not allowed in prolog.
[xslt] Failed to process D:\MAVEN-WORK\eportal-functional-tests\loadtests\J
MeterResults.jtl
BUILD FAILED
D:\MAVEN-WORK\eportal-functional-tests\build.xml:14: javax.xml.transform.Transfo
rmerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.
internal.utils.WrappedRuntimeException: Content is not allowed in prolog.
What could be causing this ?
The "jmeter-results-detail-report.xsl" can be found at
http://www.programmerplanet.org/media/ant-jmeter/jmeter-results-detail-report.zip
if you wish to take a look at it.
--
Jeff Mutonho
GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042
Mike Morris
> [xslt] : Error! Content is not allowed in prolog.
I've seen the same thing in a totally different context (startup logs
from Blojsom where one plugin is missing/unconfigured). From memory
(hint: I may be totally off base here) it simply means that there is
some spurious extra text in the doctype declaration that the XML
parser is wingeing about. Probably safe to ignore.
--
This email is [X] bloggable [ ] ask first [ ] private
http://mikro2nd.net/
EarthStuff: http://mikro2nd.net/blog/planb/
TechStuff: http://mikro2nd.net/blog/mike/
----- A day without chillies is a day wasted ------
Jeff Mutonho
>
> I've seen the same thing in a totally different context (startup logs
> from Blojsom where one plugin is missing/unconfigured). From memory
> (hint: I may be totally off base here) it simply means that there is
> some spurious extra text in the doctype declaration that the XML
> parser is wingeing about. Probably safe to ignore.
>
Thanx Mike. I can't really ignore it though, because the transforming
of the jmeter report log to html is failing because of that.
I can't say I don't understand why Hani Suleiman is always flaming
Apache programmers :)
Mike Morris
> I can't say I don't understand why Hani Suleiman is always flaming
> Apache programmers :)
Like the Tomcat logs that say helpful things like "Webapp failed to
start" (in amidst a welter of stacktraces and other error messages)
without saying /which/ webapp died or /which/ config file was being
read... :-(
Of course I should just leap in and submit a patch... ;-)
Jeff Mutonho
>
> > I can't say I don't understand why Hani Suleiman is always flaming
> > Apache programmers :)
>
> Like the Tomcat logs that say helpful things like "Webapp failed to
> start" (in amidst a welter of stacktraces and other error messages)
> without saying /which/ webapp died or /which/ config file was being
> read... :-(
>
> Of course I should just leap in and submit a patch... ;-)
>
Lol...I hear you Mike.Flip...ROTFLMAO.What diagnostic value is an
error message such as : "Content is not allowed in prolog." .Huh?What
content?How about telling me what line the parsing is failing
on...unless it's programmatically impossible.But then again I forgot
"I should just leap in and submit a patch..." :)
--