解析 /page.xhtml 时出错:跟踪错误[行: 42] 与元素类型“id”关联的属性“{1}”应使用左引号
Error Parsing /page.xhtml: Error Traced[line: 42] Open quote is expected for attribute "{1}" associated with an element type "id"
使用以下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解析器是否由于某种原因相处不融洽,或者我错过了什么?
Facelets是一种基于XML的视图技术,它使用XHTML + XML生成HTML输出。XML 有五个特殊字符,XML 解析器对其进行了特殊处理:
-
<
标记的开头。 -
>
标记的末尾。 -
"
属性值的开始和结束。 -
'
属性值的替代开始和结束。 -
&
实体的开头(以;
结尾)。
在您的特定情况下,JavaScript 字符串中未转义的<
触发了 XML 解析器启动标记。id
被识别为标签属性,然后它将搜索"
或'
等开放报价。但是,在您的特定情况下,您使用'
将其作为 JavaScript 字符串的引号进行转义。这完全解释了您得到的XML解析错误:
与元素类型"id"关联的属性"{1}"应使用开引号
从本质上讲,你在错误的地方编写JavaScript代码,XML文档而不是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 解析器会将块的内容解释为"普通"字符数据,而不是 XML,从而"按原样"解释 XML 特殊字符。
但是,更好的是将JS代码放在它自己的JS文件中,您可以通过<script src>
或JSF术语<h:outputScript>
包含该文件。
<h:outputScript name="functions.js" target="head" />
这样,您无需担心JS代码中的XML特殊字符。
另请参阅:
- 解析 XHTML 时出错:元素的内容必须包含格式正确的字符数据或标记 实体
- 名称必须紧跟在实体引用中的"&"之后
- 为 XHTML 编写 JavaScript
- Javascript复选框函数:;缺少:在属性id之后"
- 语法错误:缺少:在属性 ID 之后
- 如何使用Google Embed API获取选定的帐户ID和属性ID
- 快速会话 无法设置未定义的属性“id”
- 无法读取属性id成员路由
- 如何以编程方式获取属性Id、视图Id和帐户Id
- SyntaxError:属性id后缺少:
- JSON到带有Django的JS:SyntaxError:缺少:在属性id之后
- Angular JS TypeError:无法读取路由上未定义的属性“id”
- 在 IE8 之前替换了属性(“id”)
- 无效的属性 ID
- 在为 jquery 自动完成设置源代码时获取“语法错误:缺少:在属性 ID 之后”
- 如何根据属性 ID 获取内部 html
- j查询错误 - 语法错误:缺少:在属性 ID 之后
- 缺少解析错误:在属性 ID 之后
- Jquery:检查属性 id 是否有特定的模式
- 属性ID后缺少冒号,Firebase
- Dojo确认对话框'缺少:在属性id'之后;和'找不到节点'
- jQuery)SyntaxError:缺少:在属性id之后)
- Jquery获取最近一次单击的属性ID