flow-scope

ContextNotActiveException in simple Faces Flow with CDI

由 ﹥＞﹥吖頭↗ 提交于 2019-12-24 00:49:05
问题 Hy all ! I'm on a simple faces flow tutorial (Tutorial) but can't solve following error: 20:43:32,085 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (default task-14) Error Rendering View[/common/signup/signup.xhtml]: javax.el.ELException: /common/signup/signup.xhtml @17,53 value="#{signup.name}": org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.FlowScoped at com.sun.faces.facelets.el.TagValueExpression.getValue

Flow scope navigation to start page does not work

由 别来无恙 提交于 2019-12-12 14:21:57
问题 It is not so much a question, more of a note. With Glassfish4, in a JEE7 application I tried to use the flow scope using programmatic flow definition (java class annotated with @Produces @FlowDefinition). I navigated to the start page of the flow with a h:commandButton (just as it is done in the JEE7 tutorial example https://svn.java.net/svn/javaeetutorial~svn/trunk/examples/web/jsf/checkout-module. When I pressed the button it stayed on the same page, where the button was, instead of going

org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.faces.flow.FlowScoped

由 扶醉桌前 提交于 2019-12-11 07:53:38
问题 I´m trying to develop a simple example of new functionality of JSF 2.2, @FlowScope, I develop it with eclipse luna, glassfish 4.0, I guess the code is right cause I caught it on the web, probably the error is with the configuration of the project. Could anyone give me an Idea of what could be? Pleas ask me further information if it´s hard to understand with these few information but actually I don´t know what more I can write to help and this is my first question on stackoverflow. public

Can a faces flow be started from within a Servlet?

由 纵然是瞬间 提交于 2019-12-05 04:23:37
问题 I have a service, accessed by a servlet, which redirects the user to a login screen. The backing beans' scope is currently being changed from @ConversationScoped to @FlowScoped, as it's easier to handle. Is there a way to initialize a faces flow directly from within a servlet, without the indirection through an implicit action or a JSF forward/redirect? I am aware that @FlowScope is a JSF (2.2) scope and I was wondering if there might be a way to e.g. extend the FacesServlet or something

Exiting a JSF Flow

由 二次信任 提交于 2019-12-02 07:51:02
问题 I'm starting to use JSF Flows, and after reading some examples and the specs, I got it to work. I'm using the Packaging Flows in Directories method, as described in section 11.4.3.3 of the specification. It seems easier and more in line with the naming conventions already adopted since JSF 2.0. Bellow is my current directory structure. The flow id is wizard . I understand that there is a concept of exiting the flow by calling a return node . You see, by the image above, that I don't have a

How to disable jftfdi jffi query params in JSF

由 最后都变了- 提交于 2019-11-28 11:27:37
I tried the last version of JavaServer Faces 2.2 (Mojarra 2.2.4) and noticed changing my query string in this unwanted way: page.jsf?jftfdi=&jffi= instead of page.jsf I've found that it is the new JSF 2.2 feature. But these query params(jftfdi, jffi) spoil me SEO-friendly urls. How can I disable it? This is a bug in Mojarra. They should not have been appended when there's no means of any flow navigation configuration ( by the new @FlowScoped annotation and <j:flow-xxx> tags ). Basically, the OutcomeTargetRenderer class who's responsible for HTML output generation of the <h:link> and <h:button>

How to disable jftfdi jffi query params in JSF

由 拟墨画扇 提交于 2019-11-27 06:20:57
问题 I tried the last version of JavaServer Faces 2.2 (Mojarra 2.2.4) and noticed changing my query string in this unwanted way: page.jsf?jftfdi=&jffi= instead of page.jsf I've found that it is the new JSF 2.2 feature. But these query params(jftfdi, jffi) spoil me SEO-friendly urls. How can I disable it? 回答1: This is a bug in Mojarra. They should not have been appended when there's no means of any flow navigation configuration (by the new @FlowScoped annotation and <j:flow-xxx> tags). Basically,
订阅 flow-scope