jsf-2

问题 I get the following error. com.google.apphosting.api.ApiProxy$RequestTooLargeException: The request to API call datastore_v3.Put() was too large. I am using Objectify 4.0 and not uploading any file. I am using the DataStore for my app, but the only item above 1Mb is a _values blob in _ah_SESSION entity. The images of the console are in: http://goo.gl/qP7v7U I dont know how to troubleshoot the issue and even when the error has been asked before, my problem is that I am not using files and I am

问题 I am working with Primefaces 3.1 and I found a bug in the jquery.js used (the bug is described and fix here: http://forum.jquery.com/topic/datepicker-doesn-t-work-inside-fixed-div). I am wondering if there is an elegant way for replacing the .js? The replacement directly in the jar cannot be done because we are using Maven and I don't want to customise a library. Currently, I replaced the HeadRenderer to remove the jquery.js from the header and I added my own js file, but there's maybe a

问题 I am using JSR 303 Bean validation in my JSF 2.0 web application and it works fine with annotations. Now I would like to ignore annotations and configure validation rules using the validation.xml file, so this is what I did (I am using an eclipse dynamic web project) : Added validation.xml under WebContent/META-INF/validation.xml <?xml version="1.0" encoding="UTF-8"?> <validation-config xmlns="http://jboss.org/xml/ns/javax/validation/configuration" xmlns:xsi="http://www.w3.org/2001/XMLSchema

问题 I have a p:commandButton that actually is the logout button. It is placed in the north p:layoutUnit and if I press the enter key in any form it always log me out. I dont want that button to respond the enter key. How to do that? 回答1: Put a hidden button with no action in the logout form and capture the enter key via p:defaultCommand . <p:defaultCommand target="dummy"/> <p:commandButton id="dummy" process="@none" global="false" style="display:none;"/> 回答2: Nest the button within this form tag:

问题 with a lot of developers and plenty of juniors I want to disable certain components such as <p:spacer> to prohibit using components for html/css issues. I want to limit the available components for libraries like omnifaces / primefaces / richfaces to a whitelist / blacklist thing basically. Would this be a reasonable feature request for a library like omnifaces or is it to hard to build / to localized? 回答1: Basically, you can achieve this by providing a custom Application implementation

问题 I have an input field where user enters some product name. Depending on an entered name particular details of this product should be shown. On input change I'm getting the product from data source by the current field value and re-render product details using AJAX . So far user can not see product details until he enters correct name. Here is the code sample: <h:form> <h:inputText id="product" value="#{myBean.product}" required="true" converter="productConverter"> <a4j:ajax event="change"

问题 I have a JSF composite component which is a list of email addresses that can be dynamically added to, and deleted from: <composite:interface shortDescription="Display party email addresses"> <composite:attribute name="addressable" required="true"/> </composite:interface> <composite:implementation> <h:panelGroup layout="block" id="emails"> <h:dataTable id="emailList" value="#{cc.attrs.addressable.emailAddresses}" var="email" styleClass="data-list small-list" cellpadding="0" cellspacing="0"> <h

问题 I have a JSF page where I want to show a image. The image is stored in the database as a blob. The entity looks like this: @Entity public class Player { @Id @GeneratedValue(strategy = GenerationType.TABLE) private Long id; @Lob private byte[] pictureData; @Transient private StreamedContent streamedPicture; public StreamedContent getStreamedPicture() { if (streamedPicture == null && pictureData != null) { try { ByteArrayOutputStream os = new ByteArrayOutputStream(); os.write(pictureData);

问题 I'm getting deeper into JSF 2.0 at the moment and lacking a bit of understanding about the "transport" of managed bean properties from one view to the other. I searched a bit but haven't found a really good example, so if anyone could point me to a tutorial or explain the things a little bit I'd really grateful. So here is my scenario: I'm developing a small playground calendar application. The first view select.xhtml contains the calendar selector, where the user can pick a specific date:

问题 i want to disable the validation when the button add and button delete is pressed ,so i tried this <f:validateLength maximum="500" disabled="#{!empty param['mainForm:add_Button'] or !empty param['mainForm:delete_Button']}" /> The button add have already been disabled , however the button delete havent . And i dont know what's the problem ! This is my code , Can you guys help me to check it .Sorry for my bad english <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun