Yes, I can. Component fileUpload Total Primefaces There's an attribute. acceptwhich could indicate the types of files to be displayed in the file selection dialogue. It should be remembered that:Atribut accept There's no way to deal with a brauser, but it's just a clue to the browser. The clue is based on the HTML Element INPUT Atribut Appendix accept♪ It's all up to the anti-brows, how it handles this attribute.Atribut accept Accepts at the inlet the type of parameters different from the attributes allowTypesSo just copy. allowTypes Total accept It won't work. The HTML-Element INPUT specification should be consulted to determine which parameters are to be transmitted. In brief, the MIME-type list or predetermined MIME-type groups are accepted. You can start acquainting. https://stackoverflow.com/a/10503561/1341148

Action to include support for multilingualism in JSF:Establish a sessional component with current language information and a language change function.@ManagedBean @SessionScoped public class LocaleController { public static Locale LOCALE_RU = new Locale("ru"); public static Locale LOCALE_EN = new Locale("en"); private Locale locale = LOCALE_RU; public Locale getLocale() { return locale; } public String selectLanguage(String selectedLanguage) { locale = convert(selectedLanguage); FacesContext.getCurrentInstance().getViewRoot().setLocale(locale); return FacesContext.getCurrentInstance().getViewRoot().getViewId() + "?faces-redirect=true";//перезагружаем страницу } public static Locale convert(String languageName) { if ("en".equals(languageName)) { return LOCALE_EN; } return LOCALE_RU; } public boolean isRu() { return LOCALE_RU.equals(locale); } } Indicate the language on the page: <f:view locale="#{localeController.locale}">Report on the language support and your language resource files in faces-config.xml♪ The title and space of the names indicate the version of JSF 2.2, if you have another version, the title will be different.<faces-config version="2.2" xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd"> <application> <locale-config> <default-locale>ru</default-locale> <supported-locale>ru</supported-locale> <supported-locale>en</supported-locale> </locale-config> <resource-bundle> <!--bundles - это имя папки с файлами ресурсов --> <base-name>bundles/translate</base-name> <var>translate</var> </resource-bundle> </application> </faces-config> Add language change buttons<p:commandLink value="English" action="#{localeController.selectLanguage('en')}" rendered="#{localeController.ru}"/> <p:commandLink value="Русский" action="#{localeController.selectLanguage('ru')}" rendered="#{not localeController.ru}"/> Fill language files. ♪ translate_en.properties Add. files=files♪ translate_ru.properties Add. files=файлыCorrect use of language resources on the page<h3>#{translate.files}</h3> where #{translate Recalls var of faces-config.xml

You lost two important features of the text. http://www.primefaces.org/showcase/ui/file/upload/basic.xhtml ♪No properties enctype="multipart/form-data" component h:formNo properties ajax="false" Ooh. p:commandButtonBecause of lack of first, the format of downloading of the file is compromised, because of the absence of the second one, it is not happening. submit It's all shape. After adding properties, the files are downloaded.

Faces Servlet in not processed web.xml .jsfTry calling. .xhtml or change servlet-mapping to:<servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.jsf</url-pattern> </servlet-mapping>

Good day, everyone!I'm getting news java.lang.IllegalStateException: state.isBusy() : false and all associated (trans aborted) have been resolved.As I understand, the Glassfish 4.1.1 server has an unresolved tag that causes a conflict of streams when dealing with trespassing techniques in bean bands (if I'm wrong and someone's got it all on this earring without a problem--- - describe it, tell me how it's organized. The problem was therefore resolved by the transition to WyldFly 10.01, where it worked as planned and stable.Of course you've changed the app. viewScoped instead Session where this was critical in the context of collateral security in JSF. Separate methods that may have been summoned by different services (tested to by Glassfish) did not help: mistakes continued to fall in the same amount, and WyldFly with the same JDBC Driver Postgrace was fine.Thank you all for your help!I don't close the question because there's still a lot of subtle things I have to face. I'll get the results and the trails here.

In order to update the JSF tools, it is necessary that the updated page block be a JSF component rather than some poor div-.Then we need to indicate what or what components to update. If you use Primefaces, you've got "comand" tags. update♪ It should list the clients &apos; idios of the updated components. (JSF fluxes use Atribut rerender)Your JSF page could look like: <h:form> <p:menu> <p:submenu label="Отделы" > <c:forEach var="dep" items="#{initIndex.deps}"> <p:menuitem value="#{dep.name.toUpperCase()}" actionListener="#{initIndex.showElementsOfDep(dep)}" update=":goods_block" oncomplete="showElementsOfDep()"/> </c:forEach> </p:submenu> </p:menu> </h:form> ... <h:panelGroup id="goods_block" layout="block"> Ништяки из отдела #{initIndex.curDep.name.toUpperCase(locale)} </h:panelGroup> Note that javascript-a challenge is often on the page, too.h:panelGroup ♪ span or divdepending on layout-а♪In addition to the declarative method, there are also policy options for updating. In the same Primefaces, this is done: RequestContext.getCurrentInstance().update("goods_block"); Special attention needs to be given to JSF IDs. It's possible to see in the tools of the browser developer what they're getting to be sure not to be wrong when they're transferred to javascript.By the way, two-to-one in :goods_block - it's not cool. That is how they should be placed on pages in the vast majority of cases. And the lack of this two-two thing in calling the method isn't a seal.Why would you do that? It's the last century. Because of @ViewScoped? But I think there's a ViewScoped for CDI. That's right. I don't use either. Maybe he's not better than the old one.

Use your properties onclick:<h:commandButton id="formsubmit" onclick="return registration()" action="reg" value="Регистрация"/> If registration() returns false♪ action Not called; if true - Yeah. action It'll be done.PS B Primefaces there's a ready component. http://www.primefaces.org/showcase/ui/misc/captcha.xhtml I think he's a much better fit in the JSF page code.

You have a problem with the fact that the variable $ at the end of the download of the document is lost to something else. The solution is to find where to keep it.Since you've got functional ads and their use in the same file, you just need to move the second block in the first. It'll work because you're keeping $ as a parameter of the auto-induced function.Also if another version is used on the page jquery - Use is a good idea. noConflict:(function ($) { $.fn.shuffle = function () { ... }; ... $(function () { .... $('.captcha_wrap ul').shuffle(); /*перемешиваем*/ }); })(jQuery.noConflict(true)); If it is not possible to do so, it may be possible to take advantage of the jquery &apos; s characteristic that it will transfer itself to the processor of the document &apos; s preparation:$(function ($) { .... $('.captcha_wrap ul').shuffle(); /*перемешиваем*/ }); $.noConflict(true); // Обязательно после всех ваших модулей! In both cases, it is required that your modules be connected immediately after the libraries you use.

You can use the ajax challenge and put the processor on it.page<h:commandButton ...> <f:ajax event="click" listener="#{bean.method}" onevent="hendler" .../> </h:commandButton> jsfunction hendler(data) { switch (data.status) { case "begin": // До отправления запроса break; case "complete": // Поле получения ответа на запрос break; case "success": // После применения обновлений запроса break; } } Depending on the nature of the action on your button, js, functions can be inserted either in a situation complete or success

Simple answer: with help FacesContext - no way. FacesContext exists for a specific window of a specific annex. Server connects. FacesContext There's no way to get involved in connections from the browser. Moreover, even within one annex FacesContext There's not all the stages of processing the request from the browser, but it comes after the chain reaches. FacesServlet.service♪ If we look at the process trails, dozens of processors (e.g. safety filters) can often be seen before the process reaches. FacesServlet♪Total: FacesContext There are only certain moments, and these moments arise only at the time of the browser &apos; s application, so it will not be possible simply to appeal at an arbitrary time. FacesContext♪However, the interaction of annexes can be done in other ways. Discussing these ways goes beyond the question, you can ask a separate question. I recommend that a self-study be undertaken before that, which will help to articulate the question well and thus receive a qualitative answer (general questions are not welcomed to Stackoverflow).PS This sessionMap is stored in the session and the session is permanently available on the server, as opposed to FacesContext♪ You can turn your research on this side. Another option is to create a communications manager who accepts clean-up requests from Annex B, Annex A (with standard integration protocols, e.g. REST/SOAP). In the Annex B code, make a certain check of the request when receiving customer calls. It's just abstractions, more specifically decide yourself or ask for community assistance.

You probably have a few versions of the library that conflict between you and me. Try running the flag application. -verbose:class a list of loaded classes and a name jar The file from where they come from.Next, maven Look at the dependence on this one. jar archives. This is done by the team. dependency:tree♪ And then you just rule out that addiction.

I solved this problem in this way, suddenly, who can help in this situation is the only thing I've found yet-- <p:focus for="name"/> I have a name here. It's a id element. <p:inputText id="name".../> It's an element that I'm more comfortable with. And for the button, I added a process and an update for "@form" I'd like you to keep your weights in place, but by updating the shape, you're gonna change the focus. If not actionListner, f:ajax listener If this is the case, it is necessary to use and execute to update the form. If anyone knows an alternative solution, let me know.

We can use it. varStatus.index and transmit it as a parameter of ajax request, e.g. through remoteCommand♪ <p:remoteCommand name="comm" action="#{bean.method()}"/> <ui:repeat varStatus="status"> <component onclick="comm([{name:'nameIndex', value: #{status.index}}])"/> </ui:repeat>

Here. http://showcase.bootsfaces.net/layout/navLinks.jsf There's got to be an example of Sidebar using ui:repeatI think that's exactly what you need. Here's a little refined example from their website:<b:listLinks> <ui:repeat var="musicStyle" value="#{navLinkBean.musicStyles}"> <b:navLink href="#{musicStyle.link}" value="#{musicStyle.name}" /> </ui:repeat> </b:listLinks> navLinkBean.musicStyles should return the list of references. musicStyle - it's a copy of the site on the list, and it's supposed to contain "Name - address"in the fields name and link respectively.PS I strongly recommend with all components Freamworth on his demonstration page before working with him, at least slip.

If the mountain doesn't go to Magometha, Magomet goes to the mountain. In other words, if the Framworth doesn't generate an event about changing the elbow, we'll generate it ourselves. It was the following.Seasons change class:public class LocaleChanged { } Class handling event of local shift:import javax.enterprise.event.Event; @javax.inject.Named @javax.enterprise.context.SessionScoped public class LocaleBean implements Serializable { @javax.inject.Inject private Event<LocaleChanged> localeChangedEvent; public void localeChanged(final ValueChangeEvent event) { FacesContext.getCurrentInstance().getViewRoot().setLocale(event.getNewValue().toString())); localeChangedEvent.fire(new LocaleChanged()); } } Class MenuViewin the process of changing the elbow:import javax.annotation.PostConstruct; import javax.enterprise.event.Observes; @javax.inject.Named @javax.faces.bean.ManagedBean @javax.enterprise.context.SessionScoped @javax.faces.bean.SessionScoped public class MenuView implements Serializable { private MenuModel model; public MenuModel getModel() { return model; } @PostConstruct public void init() { model = new DefaultMenuModel(); ResourceBundle messages = ResourceBundle.getBundle("i18n.messages", (Locale) getSession().getAttribute("locale")); DefaultSubMenu submenu = new DefaultSubMenu(messages.getString("Menu 1")); DefaultMenuItem item = new DefaultMenuItem(messages.getString("Item 1")); submenu.addElement(item); model.addElement(submenu); } private void onLocaleChanged(@Observes final LocaleChanged localeChanged) { init(); } } When you change the language, the menu is just recast.Reference should be made to the list of class annotations MenuView♪ Because of the use of mixed technology (Mixed)JSF + CDIshould be marked as a sessional two annotations - @javax.enterprise.context.SessionScoped for CDI and @javax.faces.bean.SessionScoped for JSF♪ Otherwise the bin will be re-established.The merit of this approach is that the bin, changing the elbow, loses the knowledge of the objects that need to change when changing the elbow. The object is "signed" to this event. This is a weak link.

What's going on in the server components is standard. Remote JVM Debug in your development environment.What happens in the browser is really bad. For AJAX- Ask me carefully to look at the answers in the browser's dormant, they often understand what happened. Like the answer is Validation Failedand you forgot to update the evidence display component. As a result, nothing happens.If something on the page doesn't work, we're gonna throw it out of it until it's working, until the hats are off. Then we gradually return and look after the addition of which component again broke. It's not a beautiful way, but I've been helped on several occasions.Can you add a component for PrimeFaces? p:logbut it doesn't help me. ♪ ♪

Such a question arose https://stackoverflow.com/questions/4347374/jsf-backing-beans-managedbean-or-cdi-beans-named It says that in the CDI you can use almost any class, while in mb you're going to have to use @ManagedBean class.

Yes, of course. First of all, you can change the whole subject, free-of-charge options. http://www.primefaces.org/showcase/ui/misc/themeSwitcher.xhtml ♪If there's a need to change a specific component, you'll be assisted by a browser pal and knowledge. CSS♪ In the palace, we pick the right component and watch it. HTML and style. For p:accordionPanel root current is divby name ui-accordion♪ We add to the page our styles that alter the Primefaces styles, this is an example of the alteration of the component type and the colour of the panel with the contents of the component: <h:form id="mainForm"> <p:accordionPanel> <p:tab title="Godfather Part I"> <h:panelGrid columns="2" cellpadding="10"> <h:outputText value="The story begins as Don Vito Corleone..."/> </h:panelGrid> </p:tab> <p:tab title="Godfather Part II"> <h:panelGrid columns="2" cellpadding="10"> <h:outputText value="Francis Ford Coppola's legendary..."/> </h:panelGrid> </p:tab> </p:accordionPanel> </h:form> &lt;style type="text/css"&gt; #mainForm .ui-accordion { font-family: "Courier New", Courier, monospace; } #mainForm .ui-accordion-content { background-color: aliceblue; } &lt;/style&gt; #mainForm .ui-accordion - it is a path to inform the browser that all elements with style .ui-accordion and inside the identifier mainForm, now get the style. This is a way to avoid touching the others. p:accordionPanel- You're on the page. If you want a change of style to affect everything p:accordionPanel-You're in the annex, #mainForm You should remove, take the style into a separate CSS file and import it on your page (most likely to do so in a template that should use all pages of the site).By adopting this approach, any components of PrimeFaces can be changed. If something doesn't work out, it'll probably be CSS, not PrimeFaces.

Yes, of course. First of all, you can change the whole subject, free-of-charge options. http://www.primefaces.org/showcase/ui/misc/themeSwitcher.xhtml ♪If there's a need to change a specific component, you'll be assisted by a browser pal and knowledge. CSS♪ In the palace, we pick the right component and watch it. HTML and style. For p:accordionPanel root current is divby name ui-accordion♪ We add to the page our styles that alter the Primefaces styles, this is the example of changing the print: <h:form id="mainForm"> <p:accordionPanel> <p:tab title="Godfather Part I"> <h:panelGrid columns="2" cellpadding="10"> <h:outputText value="The story begins as Don Vito Corleone..."/> </h:panelGrid> </p:tab> <p:tab title="Godfather Part II"> <h:panelGrid columns="2" cellpadding="10"> <h:outputText value="Francis Ford Coppola's legendary..."/> </h:panelGrid> </p:tab> </p:accordionPanel> </h:form> &lt;style type="text/css"&gt; #mainForm .ui-accordion { font-family: "Courier New", Courier, monospace; } &lt;/style&gt; #mainForm .ui-accordion - it is a path to inform the browser that all elements with style .ui-accordion and inside the identifier mainForm, now get the style. This is a way to avoid touching the others. p:accordionPanel- You're on the page. If you want a change of style to affect everything p:accordionPanel-You're in the annex, #mainForm You should remove, take the style into a separate CSS file and import it on your page (most likely to do so in a template that should use all pages of the site).By adopting this approach, any components of PrimeFaces can be changed. If something doesn't work out, it'll probably be CSS, not PrimeFaces.

There is a need to develop its authentication mechanism, which is being introduced in a very deep way into the subsoil of the application server, in the processing of the http://request. The javaee standard does not cover this aspect. Study the insides of a specific application server. And the application of the authentication module is already on standards.It's if you want to use all the javaee services, @RolesAllowed there... so that the user and his role in EJB can be recognized. ♪ ♪ If you can do it without it, you can find a solution on the filters. Like Apache Shiro. But there's no javaee there, there's a secrecy in it that's not in any way intertwined with javaee. It is possible to make a model authentication using a separate inlet server (with one for all or only for some applications).Keycloak has a lot of opportunities. Remember me isn't even the main one. There is an authentication mechanism for Wildfly servers, so standard annotations and EJB are working there. It's important to get your user base up there. It's not very complicated.