mojarra

问题 We have a huge EAR application with about 20 ejb-jar and war modules. For each war module that Mojarra starts, it seems it is trying to scan annotation on every other war. Other wars are unavailable to the classloader, so I get lot of exceptions. It eventually starts anyway, but it clutters my logs with warnings, and I guess application startup time could be much less without this (+100 seconds). To make it clear, I have following structure: EAR +- ejb1 +- ejb2 +- war1 +- war2 When Mojarra

问题 We have a huge EAR application with about 20 ejb-jar and war modules. For each war module that Mojarra starts, it seems it is trying to scan annotation on every other war. Other wars are unavailable to the classloader, so I get lot of exceptions. It eventually starts anyway, but it clutters my logs with warnings, and I guess application startup time could be much less without this (+100 seconds). To make it clear, I have following structure: EAR +- ejb1 +- ejb2 +- war1 +- war2 When Mojarra

问题 We have a huge EAR application with about 20 ejb-jar and war modules. For each war module that Mojarra starts, it seems it is trying to scan annotation on every other war. Other wars are unavailable to the classloader, so I get lot of exceptions. It eventually starts anyway, but it clutters my logs with warnings, and I guess application startup time could be much less without this (+100 seconds). To make it clear, I have following structure: EAR +- ejb1 +- ejb2 +- war1 +- war2 When Mojarra

问题 We have a huge EAR application with about 20 ejb-jar and war modules. For each war module that Mojarra starts, it seems it is trying to scan annotation on every other war. Other wars are unavailable to the classloader, so I get lot of exceptions. It eventually starts anyway, but it clutters my logs with warnings, and I guess application startup time could be much less without this (+100 seconds). To make it clear, I have following structure: EAR +- ejb1 +- ejb2 +- war1 +- war2 When Mojarra

问题 I tested new Flash scope in JSF2 but I found a major issue with it or I am lacking some knowledge. Having a page: <h:body> Value in flash: #{flash.text} <h:form> <h:inputText value="#{flash.text}" /> <h:commandButton value="Test" /> <!-- Same behavior with faces redirect --> </h:form> </h:body> I have a scenario: Put a value 'foo' and click Test I get 'Value in flash: foo' I open new page with the same adress I get 'Value in flash:' I open another new page with the same adress I get 'Value in

问题 How can I disallow Mojarra, injecting a javax.faces.ViewState hidden into my <form> s? I have a search <form method='GET'> which works first time my page is loaded (because my view-scoped bean is re-initialized correctly). But after an AJAX pagination in the page (over a PrimeFaces grid), Mojarra (or PrimeFaces?) injects a hidden javax.faces.ViewState into my form. Now when I submit the form it doesn't restart my view-scope bean because of javax.faces.ViewState input. The issue here is: I

问题 Recently I switched to mojarra from myfaces and noticed that primefaces datatable checkbox multiple row selection is not working. I have tried the exact sample program available at http://www.primefaces.org/showcase/ui/datatableRowSelectionRadioCheckbox.jsf With myfaces both single and multiple selection are working ,but with mojarra multiple selection is not working(selectedCars.length is 0 in setSelectedCars method) I have tried with mojarra 2.0.3 and mojarra 2.1.0 with primefaces 2.2.1 回答1

问题 It appears that if you use a selectManyCheckbox backed by a set that is proxied by hibernate you will run into problems with the dreaded LazyInitializationException. This has nothing to do with the state of the backing bean! After debugging Mojarra 2.1 I discovered that if you do not included the attribute collectionType it will attempt to clone the backing value class in the process validations phase, which in my case is PersistentSet. Of course adding any value to this will cause a

问题 According to this blog JSF is going stateless . Isn't the whole point of using JSF is that it makes saving and restoring state a chore . What is the point of JSF becoming stateless ? Can you please provide an example where this can be useful . 回答1: First of all, I would like to clarify that JSF isn't exactly "going stateless" at its whole own. JSF just adds a new feature enabling the developers to create stateless views/forms on demand. State saving is particularly helpful in dynamically

问题 According to this blog JSF is going stateless . Isn't the whole point of using JSF is that it makes saving and restoring state a chore . What is the point of JSF becoming stateless ? Can you please provide an example where this can be useful . 回答1: First of all, I would like to clarify that JSF isn't exactly "going stateless" at its whole own. JSF just adds a new feature enabling the developers to create stateless views/forms on demand. State saving is particularly helpful in dynamically