jsf

empty EL expression on JSF datatable var attribute's field always false

余生颓废 提交于 2021-01-27 07:29:46
问题 I have the following EL expression which references a property on the var attribute: empty _item.addressLine1 addressLine1 is a String property on the Address bean, which is accessed via the personBean.person.addresses property which returns a Set<Address> . Here is the EL expression in context: <h:dataTable id="personBeanPersonAddresses" styleClass="data-table" value="#{forgeview:asList(personBean.person.addresses)}" var="_item"> <h:column> <f:facet name="header"> <h:outputText value=

empty EL expression on JSF datatable var attribute's field always false

假装没事ソ 提交于 2021-01-27 07:24:15
问题 I have the following EL expression which references a property on the var attribute: empty _item.addressLine1 addressLine1 is a String property on the Address bean, which is accessed via the personBean.person.addresses property which returns a Set<Address> . Here is the EL expression in context: <h:dataTable id="personBeanPersonAddresses" styleClass="data-table" value="#{forgeview:asList(personBean.person.addresses)}" var="_item"> <h:column> <f:facet name="header"> <h:outputText value=

Adding iframe to JSF components

我与影子孤独终老i 提交于 2021-01-27 04:33:09
问题 Is it possible to add an iframe to a JSF component(RichFaces, PrimeFaces) from backing bean? I need to embed externel webpages in my homepage. And user needs to set this url. I cannot use jQuery. I am not able to find any iframe equivalent JSF component. Is there any particular reason for this? 回答1: Just use plain HTML. <iframe src="#{bean.iframeUrl}"></iframe> The most probable reason why a component doesn't exist is because there would be no extra advantages to offer when wrapping it in a

凹凸技术揭秘 · 基础服务体系 · 构筑服务端技术中枢

こ雲淡風輕ζ 提交于 2021-01-15 09:08:39
前言 凹凸实验室从最初的前端团队成长为如今的全端团队,意味着我们不仅关注前端的技术能力,也重视全端及全栈的能力。在这一篇,我们从前端团队角度出发,阐述我们最初搭建服务端体系遇到的一些困难,已构建的服务体系架构,以及如何更好地助力业务增长。 些许似曾相识 首先,我们来看下日常工作中存在的一些场景。 场景A:在某些业务中,底层数据团队提供的数据接口并没有提供 HTTP 调用,需要去寻找其他服务端团队来封装,这时候需要等待其他团队排期,可能造成业务无法正常上线; 场景B:前端页面性能卡顿,由于调用接口过多,需要等待其他服务端团队聚合数据; 场景C:我们在一些项目需要SSR,前后端需要复用统一套模板; 场景D:我们内部孵化了一些项目,需要接口服务,需要等待其他服务端团队支持。 这些场景的背后,我们急需组建一个服务端研发团队来承担部分的业务服务开发以及更好地帮助团队未来发展。 成型 在团队组建上,主要采用「内部选拔」 + 「外部招聘」2 种方式。在团队发展上,我们主要经历了 3 个阶段。 雏形 在最初的阶段,选择以 NodeJS 作为服务端编程语言,主要以下有 2 点考虑: 团队大部分同学熟悉 Javascript,能够快速学习 NodeJS,上手成本较低; 在 SSR 方面有天然的优势,前后端能够共用部分代码。 在这个阶段,我们快速孵化了一系列的系统和平台,比如 Mock 平台

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

家住魔仙堡 提交于 2021-01-04 11:14:23
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

霸气de小男生 提交于 2021-01-04 11:10:53
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

╄→гoц情女王★ 提交于 2021-01-04 11:09:02
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

陌路散爱 提交于 2021-01-04 11:08:20
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

A reconnecting websocket can't connect to the server with FacesContext.getCurrentInstance() being resolved to null

柔情痞子 提交于 2021-01-04 11:07:33
问题 I have a plain Tomcat 8.5.47 having the following dependencies installed. <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.3.9</version> </dependency> <dependency> <groupId>org.jboss.weld.servlet</groupId> <artifactId>weld-servlet</artifactId> <version>2.4.8.Final</version> </dependency> <dependency> <groupId>javax.websocket</groupId> <artifactId>javax.websocket-api</artifactId> <version>1.1</version> </dependency> CDI seems to work fine, or at

Navigating to another page JSF

纵然是瞬间 提交于 2021-01-04 07:59:30
问题 I wrote a jsf application, this app inserts the data into mysql database and shows some of the inserted details in another page. I am successful in inserting the values into database, but unable to redirect to the other page even after writing the navigation rule. My action code <div align="center"><p:commandButton label="Submit" action="#{userData.add}" align="center" ajax="false" /></div> Navigation rule <managed-bean> <managed-bean-name>UserData</managed-bean-name> <managed-bean-class