错误解析/page.xhtml：跟踪错误[line：42]对于与元素类型“id”关联的属性“{1}”，需要打开引号

Question

使用以下JavaScript / jQuery代码时：

$("#service_container").append("<p id=\"text\">SomeText</p>")  

我收到以下错误：

Error Parsing /dashboard.xhtml: Error Traced[line: 140] Open quote is expected for attribute "{1}" associated with an element type "id".  

这是堆栈跟踪：

javax.faces.view.facelets.FaceletException: Error Parsing /dashboard.xhtml: Error Traced[line: 140] Open quote is expected for attribute "{1}" associated with an  element type  "id".
at com.sun.faces.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:456)
at com.sun.faces.facelets.compiler.SAXCompiler.doMetadataCompile(SAXCompiler.java:439)
at com.sun.faces.facelets.compiler.Compiler.metadataCompile(Compiler.java:130)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.createMetadataFacelet(DefaultFaceletFactory.java:503)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.access$200(DefaultFaceletFactory.java:106)
at com.sun.faces.facelets.impl.DefaultFaceletFactory$2.newInstance(DefaultFaceletFactory.java:205)
at com.sun.faces.facelets.impl.DefaultFaceletFactory$2.newInstance(DefaultFaceletFactory.java:203)
at com.sun.faces.facelets.impl.DefaultFaceletCache$2.newInstance(DefaultFaceletCache.java:97)
at com.sun.faces.facelets.impl.DefaultFaceletCache$2.newInstance(DefaultFaceletCache.java:92)
at com.sun.faces.util.ExpiringConcurrentCache$1.call(ExpiringConcurrentCache.java:99)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.sun.faces.util.ExpiringConcurrentCache.get(ExpiringConcurrentCache.java:114)
at com.sun.faces.facelets.impl.DefaultFaceletCache.getViewMetadataFacelet(DefaultFaceletCache.java:146)
at com.sun.faces.facelets.impl.DefaultFaceletCache.getViewMetadataFacelet(DefaultFaceletCache.java:63)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.getMetadataFacelet(DefaultFaceletFactory.java:316)
at com.sun.faces.facelets.impl.DefaultFaceletFactory.getMetadataFacelet(DefaultFaceletFactory.java:246)
at com.sun.faces.application.view.ViewMetadataImpl.createMetadataView(ViewMetadataImpl.java:138)
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:241)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:121)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:646)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:344)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
at org.glassfish.tyrus.servlet.TyrusServletFilter.doFilter(TyrusServletFilter.java:295)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
at com.omegathings.security.AuthorizationFilter.doFilter(AuthorizationFilter.java:75)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:316)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:160)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:734)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:673)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:99)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:415)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:282)
at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:459)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:167)
at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:201)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:175)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:235)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:284)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:201)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:133)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:112)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:561)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:117)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:56)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:137)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:565)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:545)
at java.lang.Thread.run(Thread.java:745)  

我通过附加没有属性的元素来确保jQuery正在工作。 此外，[service_container] ID也是正确的，并分配给[ul] HTML元素 jQuery和Facelets解析器由于某种原因不能相处，还是我错过了什么？

Answer 1

Facelets是一种基于XML的视图技术，它使用XHTML + XML生成HTML输出。 XML有五个特殊字符，由XML解析器进行特殊处理：

• <标记的开头。
• >标记的结尾。
• "属性值的开头和结尾。
• '替代属性值的开始和结束。
• &实体的开头（以;结尾）。

在您的特定情况下，JavaScript字符串中未转义的<触发XML解析器启动标记。 id被识别为标记属性，然后会搜索"或'等公开引用。但是，在您的特定情况下，您使用\将其作为JavaScript字符串的引号进行转义。这完全解释了您获得的XML解析错误：

  

对于与元素类型“id”

相关联的属性“{1}”，需要打开引号

本质上，您在错误的位置编写JavaScript代码，而不是JS文件，因此您应该相应地转义所有XML特殊字符。

所以，基本上，

$("#service_container").append("<p id=\"text\">SomeText</p>")  

必须成为

$("#service_container").append("<p id="text">SomeText</p>")  

使其具有XML有效性。值得注意的是，一些解析器在某些字符序列中更宽容，大多数解析器可以继续使用>而不是转义它。

然而，这使得JavaScript代码更难以阅读和维护。正如Mozilla Developer Network的优秀文档Writing JavaScript for XHTML中所述，您应该将JavaScript代码放在字符数据（CDATA）块中。因此，在JSF术语中，那将是：

<h:outputScript>
    <![CDATA[
        // ...
    ]]>
</h:outputScript>

XML解析器会将块的内容解释为“普通的vanilla”字符数据，而不是XML，因此可以“按原样”解释XML特殊字符。

但是，更好的方法是将JS代码放在由<script src>包含的JS文件中，或者用JSF术语<h:outputScript>包含。

<h:outputScript name="functions.js" target="head" />

这样您就不必担心JS代码中的XML特殊字符了。

另见：

• Error parsing XHTML: The content of elements must consist of well-formed character data or markup
• The entity name must immediately follow the '&' in the entity reference
• Writing JavaScript for XHTML