[CITE-Forum] [CITE.SC] beta TEAM Engine updated 2010-09-21

Luis Bermudez lbermudez at opengeospatial.org
Thu Sep 23 17:04:57 EDT 2010


Do we know if this issue is related to this issue:
http://portal.opengeospatial.org/index.php?m=projects&a=view&project_id=85&tab=5&act=details&issue_id=225

And, because we are now enabling more logging messages ?

Luis

---
Luis Bermudez
The OGC: Making Location Count...
http://www.opengeospatial.org/contact




On Sep 22, 2010, at 4:46 AM, Carl Lindsay wrote:

> 
> Hi Kevin,
> 
> Thanks for the email and for updating the tests, however, I have just tried the 'Latest' tests and after Starting the tests and pointing them at our WFS I get the folowing error:
> 
> 
> HTTP Status 500 -
> 
> type Exception report
> 
> message
> 
> description The server encountered an internal error () that prevented it from fulfilling this request.
> 
> exception
> 
> org.apache.jasper.JasperException: Exception in JSP: /viewSessionLog.jsp:99
> 
> 96:       out.println("<h3>Test Suite: " + (Conf.getSuites().get(ts.getSourcesName())).getTitle() + "</h3>");
> 97: 
> 98:       ArrayList tests = new ArrayList();
> 99:       boolean complete = ViewLog.view_log(userlog, sessionId, tests, ViewLogTemplates, out);     
> 100:       out.println("<br/>");
> 101:       if (!complete) {
> 102:           out.println("<input type=\"button\" value=\"Resume executing these tests\" onclick=\"window.location = 'test.jsp?mode=resume&amp;session=" + sessionId + "'\"/>");
> 
> 
> Stacktrace:
> 	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:451)
> 	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)
> 	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
> 	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> 
> root cause
> 
> javax.servlet.ServletException: org.xml.sax.SAXParseException: Element type "sf:EntitÃ" must be followed by either attribute specifications, ">" or "/>".
> 	org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:841)
> 	org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:774)
> 	org.apache.jsp.viewSessionLog_jsp._jspService(viewSessionLog_jsp.java:240)
> 	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> 	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
> 	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
> 	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> 
> root cause
> 
> net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException: Element type "sf:EntitÃ" must be followed by either attribute specifications, ">" or "/>".
> 	net.sf.saxon.event.Sender.sendSAXSource(Sender.java:379)
> 	net.sf.saxon.event.Sender.send(Sender.java:185)
> 	net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:29)
> 	com.occamlab.te.util.LogUtils.readLog(LogUtils.java:93)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:171)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestList(LogUtils.java:232)
> 	com.occamlab.te.util.LogUtils.makeTestList(LogUtils.java:254)
> 	com.occamlab.te.ViewLog.view_log(ViewLog.java:148)
> 	org.apache.jsp.viewSessionLog_jsp._jspService(viewSessionLog_jsp.java:184)
> 	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> 	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
> 	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
> 	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> 
> root cause
> 
> org.xml.sax.SAXParseException: Element type "sf:EntitÃ" must be followed by either attribute specifications, ">" or "/>".
> 	org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
> 	org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
> 	org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> 	org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> 	org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
> 	org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
> 	org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> 	org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> 	org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> 	org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> 	org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> 	org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> 	org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> 	net.sf.saxon.event.Sender.sendSAXSource(Sender.java:371)
> 	net.sf.saxon.event.Sender.send(Sender.java:185)
> 	net.sf.saxon.IdentityTransformer.transform(IdentityTransformer.java:29)
> 	com.occamlab.te.util.LogUtils.readLog(LogUtils.java:93)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:171)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestListElement(LogUtils.java:202)
> 	com.occamlab.te.util.LogUtils.makeTestList(LogUtils.java:232)
> 	com.occamlab.te.util.LogUtils.makeTestList(LogUtils.java:254)
> 	com.occamlab.te.ViewLog.view_log(ViewLog.java:148)
> 	org.apache.jsp.viewSessionLog_jsp._jspService(viewSessionLog_jsp.java:184)
> 	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> 	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
> 	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
> 	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> 
> note The full stack trace of the root cause is available in the Apache Tomcat/5.5.28 logs.
> Apache Tomcat/5.5.28
> 
> 
> Any ideas what might have changed to cause this?  As the same deployed WFS was working before.
> 
> Regards,
> Carl
> 
> 
> -----Original Message-----
> From: cite-forum-bounces+carl.lindsay=snowflakesoftware.com at lists.opengeospatial.org [mailto:cite-forum-bounces+carl.lindsay=snowflakesoftware.com at lists.opengeospatial.org] On Behalf Of Kevin Stegemoller
> Sent: 21 September 2010 18:32
> To: compliance at opengeospatial.org; CITE SC; cite-forum at lists.opengeospatial.org
> Cc: Kevin Stegemoller
> Subject: [CITE-Forum] beta TEAM Engine updated 2010-09-21
> 
> Hello,
> 
> The TEAM Engine and some of the tests on the beta TEAM Engine have been 
> updated.  Please give the "-latest" tests a whirl and let us know of any 
> issues.
> 
> Since the engine has changed all are encouraged to test all scripts.  If 
> we have no complaints, it is expected that this engine will become the 
> production engine sometime on 30 Sept 2010.
> 
> The beta engine is available at http://cite.opengeospatial.org/te2/ .
> 
> The following TEAM Engine changes where made:
> 
>  * TEAM Engine version SF r430 - SOAP, logging support added by HMA.
>  * additional bugfixes and integration support by Chuck Morris.
> 
> The following test were updated:
> 
>  ** wfs-1.1.0-latest **
> 
> 2010-09-20 (aschmitz):
> - added missing colon in srs urn for wfs-1.1.0-Basic-GetFeature-tc38.4
> 
> 2010-09-16 (aschmitz):
> - fixed another occurrence of an empty PropertyName element when using 
> the BBOX filter by supplying a non-existant one (test 203.3)
> 
> Regards,
> 
> kevin
> 
> -- 
> -------------------------------------------------------
>  Kevin Stegemoller
>  The OGC: Making location count...
>  http://www.opengeospatial.org/contact
> -------------------------------------------------------
> _______________________________________________
> CITE-Forum mailing list
> CITE-Forum at lists.opengeospatial.org
> https://lists.opengeospatial.org/mailman/listinfo/cite-forum
> 
> _______________________________________________
> CITE.SC mailing list
> CITE.SC at lists.opengeospatial.org
> https://lists.opengeospatial.org/mailman/listinfo/cite.sc
> 




More information about the CITE-Forum mailing list