Re: SV: bug in FacesServlet?
FYI solving it is as easy as https://github.com/apache/tomee/blob/a5088393dd32f167ab0869e955db194aa914dc67/tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEWorkaroundFacesServlet.java Le 26 mars 2016 09:13, "Dan Østerberg" a écrit : > Hi, > > I'd second that this is a bug. I don't know about the spec, but it > certainly makes sense to support nested contexts and thus a push / pop like > create / release. We stumbled upon this issue quite some time ago, when > dispatching to an error page from and exception handler. And we solved it > with an own FacesContext implementation that resets the previous context if > the current context during release is our own. > > Cheers, > Dan Østerberg > > -Opprinnelig melding- > Fra: Leonardo Uribe [mailto:lu4...@gmail.com] > Sendt: 26. mars 2016 03:07 > Til: MyFaces Discussion > Emne: Re: bug in FacesServlet? > > Hi > > It could be possible, I do not have all the details, but I have the > impression that happens on jsp, or at least I have seen that before. > MyFaces does what the spec says, but this part could not be well defined. > > It is clear the release should happen after the end of the lifecycle, but > since the rendering step is delegated to jsp in this case, after that point > there is no control, so the code just release in that point. The problem > here is we don't know what happens for different jsp containers. In my > understanding not every jsp implementation works the same, but as I said, I > have not entered into details. > > regards, > > Leonardo Uribe > > 2016-03-25 13:15 GMT-05:00 Romain Manni-Bucau : > > > Hi guys, > > > > org.apache.myfaces.context.servlet.FacesContextImpl#release does the > > release but javax.faces.webapp.FacesServlet#service doesn't handle > > context push/pop so if a JSF request does a JSF include (and retrigger > > the servlet) it will likely reset too early the context. > > > > Here a diagram hoping it helps: > > > > -> request > > -> FacesServlet > > -> setFacesContext > > -> FacesServlet > > -> anything relaunching a JSF "request" > > org.apache.myfaces.view.jsp.JspViewDeclarationLanguage#buildView does > > a forward for instance) > > -> setFacesContext > > -> setFacesContext > > -> releaseFacesContext > > -> end of lifecycle // oops faces context is null > > -> releaseFacesContext > > > > Romain Manni-Bucau > > @rmannibucau | Blog | Github | LinkedIn | Tomitriber > > >
bug in FacesServlet?
Hi guys,
org.apache.myfaces.context.servlet.FacesContextImpl#release does the
release but javax.faces.webapp.FacesServlet#service doesn't handle
context push/pop so if a JSF request does a JSF include (and retrigger
the servlet) it will likely reset too early the context.
Here a diagram hoping it helps:
-> request
-> FacesServlet
-> setFacesContext
-> FacesServlet
-> anything relaunching a JSF "request"
org.apache.myfaces.view.jsp.JspViewDeclarationLanguage#buildView does
a forward for instance)
-> setFacesContext
-> setFacesContext
-> releaseFacesContext
-> end of lifecycle // oops faces context is null
-> releaseFacesContext
Romain Manni-Bucau
@rmannibucau | Blog | Github | LinkedIn | Tomitriber
Re: No saved view state could be found in tomcat cluster
Can you debug the session during the request? Wonder if you hit a serialize instance replaced by just an id instead of the actual value. Client state saving would probably work then. Le 28 janv. 2016 07:03, "Jalal Almutawa" a écrit : > Thanks Mr. Romain, > > From what I understood, I have added: > > openejb.session-context = http > tomee.session-context.wrapper = http > > to the system.properties file, and changed the backing bean from JSF > managed to CDI managed. > > Now the session replication works without the need for the > ForceReplicationValve (all default tomcat cluster setup remains), but the > No saved view state error still get thrown on failover. > > Thanks, > Jalal > > On Wed, Jan 27, 2016 at 9:36 PM, Romain Manni-Bucau > > wrote: > > > Hi > > > > Quickly from the phone: > > > > > http://tomee-openejb.979440.n4.nabble.com/TomEE-cluster-and-cdibeans-td4664576.html > > has the needed config/system properties. > > Le 27 janv. 2016 18:05, "Jalal Almutawa" a > > écrit : > > > > > Hello, > > > > > > I could only find stateless failover in the TomEE documentation site. > > > Appreciate your guidance for the stateful part. > > > > > > Thanks, > > > Jalal > > > > > > On Wed, Jan 27, 2016 at 6:06 PM, Jalal Almutawa < > > jalal.almut...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > Because i just got to know about it from you now :) we were planning > to > > > go > > > > for plain Tomcat but then switched to TomEE but kept most of the > > previous > > > > setup. > > > > > > > > I will check TomEE's clustering now. > > > > > > > > Many thanks, > > > > Jalal > > > > On Jan 27, 2016 5:08 PM, "Romain Manni-Bucau" > > > > > wrote: > > > > > > > >> Hi > > > >> > > > >> TomEE has a built in cluster support, why didnt you use that? > > > >> > > > >> > > > >> Romain Manni-Bucau > > > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > >> <http://rmannibucau.wordpress.com> | Github < > > > >> https://github.com/rmannibucau> | > > > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > > >> <http://www.tomitribe.com> > > > >> > > > >> 2016-01-27 15:04 GMT+01:00 Jalal Almutawa >: > > > >> > > > >> > Hello, > > > >> > > > > >> > I have a TomEE 1.7.1 cluster setup using DeltaManager with a > > > >> > ForceReplicationValve that forces all JSF bean attributes to be > > > >> replicated > > > >> > between nodes. I also have a session-test JSF application with a > > > Session > > > >> > Scoped Managed Bean with a simple Integer "counter" to serve as a > > > >> > replication test. A facelet with an is used to > > > >> > increment the counter just to see if the replication works. > > > >> > > > > >> > Now replication works fine, I can see the incremented value of the > > > >> counter > > > >> > each type a hit the commandButton. The issue is that when we > > failover > > > >> > between nodes, MyFaces throws a No saved view state could be found > > > >> error. > > > >> > It then works when we refresh the page, but it will not maintain > the > > > >> POST > > > >> > request to increment the counter (e.g. counter=4, we click the > > > increment > > > >> > button, we get the error, we refresh the page, counter still = 4) > > > >> > > > > >> > Code for the session-test webapp: > > > >> https://github.com/jmutawa/session-test > > > >> > Code for the ForceReplicationValve: > > > >> > https://github.com/jmutawa/ForceReplicationValve > > > >> > > > > >> > We tried various configuration options in the web.xml (setting > state > > > >> saving > > > >> > in the client, setting serialize state in session to false, ..) > but > > > >> still > > > >> > same error. > > > >> > > > > >> > Appreciate if someone could tell us what are doing wrong. > > > >> > > > > >> > Thanks, > > > >> > Jalal > > > >> > > > > >> > > > > > > > > > >
Re: No saved view state could be found in tomcat cluster
Hi Quickly from the phone: http://tomee-openejb.979440.n4.nabble.com/TomEE-cluster-and-cdibeans-td4664576.html has the needed config/system properties. Le 27 janv. 2016 18:05, "Jalal Almutawa" a écrit : > Hello, > > I could only find stateless failover in the TomEE documentation site. > Appreciate your guidance for the stateful part. > > Thanks, > Jalal > > On Wed, Jan 27, 2016 at 6:06 PM, Jalal Almutawa > wrote: > > > Hi, > > > > Because i just got to know about it from you now :) we were planning to > go > > for plain Tomcat but then switched to TomEE but kept most of the previous > > setup. > > > > I will check TomEE's clustering now. > > > > Many thanks, > > Jalal > > On Jan 27, 2016 5:08 PM, "Romain Manni-Bucau" > > wrote: > > > >> Hi > >> > >> TomEE has a built in cluster support, why didnt you use that? > >> > >> > >> Romain Manni-Bucau > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog > >> <http://rmannibucau.wordpress.com> | Github < > >> https://github.com/rmannibucau> | > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > >> <http://www.tomitribe.com> > >> > >> 2016-01-27 15:04 GMT+01:00 Jalal Almutawa : > >> > >> > Hello, > >> > > >> > I have a TomEE 1.7.1 cluster setup using DeltaManager with a > >> > ForceReplicationValve that forces all JSF bean attributes to be > >> replicated > >> > between nodes. I also have a session-test JSF application with a > Session > >> > Scoped Managed Bean with a simple Integer "counter" to serve as a > >> > replication test. A facelet with an is used to > >> > increment the counter just to see if the replication works. > >> > > >> > Now replication works fine, I can see the incremented value of the > >> counter > >> > each type a hit the commandButton. The issue is that when we failover > >> > between nodes, MyFaces throws a No saved view state could be found > >> error. > >> > It then works when we refresh the page, but it will not maintain the > >> POST > >> > request to increment the counter (e.g. counter=4, we click the > increment > >> > button, we get the error, we refresh the page, counter still = 4) > >> > > >> > Code for the session-test webapp: > >> https://github.com/jmutawa/session-test > >> > Code for the ForceReplicationValve: > >> > https://github.com/jmutawa/ForceReplicationValve > >> > > >> > We tried various configuration options in the web.xml (setting state > >> saving > >> > in the client, setting serialize state in session to false, ..) but > >> still > >> > same error. > >> > > >> > Appreciate if someone could tell us what are doing wrong. > >> > > >> > Thanks, > >> > Jalal > >> > > >> > > >
Re: No saved view state could be found in tomcat cluster
Hi TomEE has a built in cluster support, why didnt you use that? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2016-01-27 15:04 GMT+01:00 Jalal Almutawa : > Hello, > > I have a TomEE 1.7.1 cluster setup using DeltaManager with a > ForceReplicationValve that forces all JSF bean attributes to be replicated > between nodes. I also have a session-test JSF application with a Session > Scoped Managed Bean with a simple Integer "counter" to serve as a > replication test. A facelet with an is used to > increment the counter just to see if the replication works. > > Now replication works fine, I can see the incremented value of the counter > each type a hit the commandButton. The issue is that when we failover > between nodes, MyFaces throws a No saved view state could be found error. > It then works when we refresh the page, but it will not maintain the POST > request to increment the counter (e.g. counter=4, we click the increment > button, we get the error, we refresh the page, counter still = 4) > > Code for the session-test webapp: https://github.com/jmutawa/session-test > Code for the ForceReplicationValve: > https://github.com/jmutawa/ForceReplicationValve > > We tried various configuration options in the web.xml (setting state saving > in the client, setting serialize state in session to false, ..) but still > same error. > > Appreciate if someone could tell us what are doing wrong. > > Thanks, > Jalal >
Re: @WebFilter not called when forwarding to login page
Can you share a project reproducing it? Can it be a mapping conflict? Le 12 mars 2015 11:54, "l.pe...@senat.fr" a écrit : > Dear all, > > I have a legacy application which performs hibernate session attachement > in a web filter. > > It works, excepting, sometimes, on a redirect by the container to the > login page. > > In my web.xml, I have : > > > FORM > > /login.xhtml > /login_failed.html > > > > > In login.xhtml, I use LogginBean to perform a "programmatic login". This > is where it just does not work sometimes. > > My web filter is set up using > > > HibernateSessionConversationFilter > fr.senat.faces.filters.HibernateSessionConversationFi > lter > > login-page-timeout > 60 > > > > HibernateSessionConversationFilter > *.xhtml > > > As you can see in the following stack trace, it is not called. > > What should I do to get it called even in this case ? > > Thanks in advance, > > Ludovic > > == > > LoginBean.getRedirectPage:339 > Hidden Source Calls > LoginBean$$OwbNormalScopeProxy0.getRedirectPage > GeneratedMethodAccessor373.invoke > DelegatingMethodAccessorImpl.invoke:43 > Method.invoke:606 > BeanELResolver.getValue:99 > CompositeELResolver.getValue:67 > FacesCompositeELResolver.getValue:179 > AstValue.getValue:183 > ValueExpressionImpl.getValue:184 > ELText$ELTextVariable.writeText:219 > ELText$ELTextComposite.writeText:131 > TextInstruction.write:45 > UIInstructions.encodeBegin:46 > UILeaf.encodeAll:507 > UIComponentBase.encodeAll:550 > UIComponentBase.encodeAll:550 > FaceletViewDeclarationLanguage.renderView:1891 > ViewHandlerImpl.renderView:313 > ViewHandlerWrapper.renderView:58 > ViewHandlerWrapper.renderView:58 > ViewHandlerWrapper.renderView:58 > RenderResponseExecutor.execute:116 > LifecycleImpl.render:267 > DeltaSpikeLifecycleWrapper.render:111 > LifecycleWrapper.render:31 > FacesServlet.service:200 > ApplicationFilterChain.internalDoFilter:303 > ApplicationFilterChain.doFilter:208 > Hidden Source Calls > WsFilter.doFilter:52 > ApplicationFilterChain.internalDoFilter:241 > ApplicationFilterChain.doFilter:208 > ApplicationDispatcher.invoke:748 > ApplicationDispatcher.processRequest:486 > ApplicationDispatcher.doForward:411 > ApplicationDispatcher.forward:338 > FormAuthenticator.forwardToLoginPage:423 > FormAuthenticator.authenticate:278 > AuthenticatorBase.authenticate:683 > AuthenticatorBase.invoke:473 > StandardHostValve.invoke:170 > ErrorReportValve.invoke:103 > AccessLogValve.invoke:950 > StandardEngineValve.invoke:116 > CoyoteAdapter.service:421 > AbstractHttp11Processor.process:1070 > AbstractProtocol$AbstractConnectionHandler.process:611 > JIoEndpoint$SocketProcessor.run:316 > Hidden Source Calls > ThreadPoolExecutor.runWorker:1145 > ThreadPoolExecutor$Worker.run:615 > TaskThread$WrappingRunnable.run:61 > Hidden Source Calls > Thread.run:745 > | > | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. > | > >
Re: hidden input not refreshed
issue solved! content type header was misread! sorry for the noise Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-01-02 12:54 GMT+01:00 Ludovic Pénet : > You can also give your input hidden an id and request its update this way. > Avoids re-sendind all form... > > Best regards, > > Le 2 janvier 2015 11:21:10 UTC+01:00, Romain Manni-Bucau < > rmannibu...@gmail.com> a écrit : > >> @this will just refresh the commandButton no? so it is really @form >> (goal would be to refresh the conversation id). >> >> Could it be a difference between MF and Mojarra - it is taken from CDI >> TCKs so I guess it was passed using mojarra? >> >> >> Romain Manni-Bucau >> @rmannibucau >> http://www.tomitribe.com >> http://rmannibucau.wordpress.com >> https://github.com/rmannibucau >> >> >> 2015-01-02 11:16 GMT+01:00 Thomas Andraschko : >> >>> I see Romain. It should work for the first button... >>> You could try to add execute="@this" but it should work without, too. >>> >>> 2015-01-02 11:01 GMT+01:00 Mert ÇALIŞKAN >>> : >>> >>> Yes, default value of f:ajax is @none. >>>> But also by default the element that triggers the request, which is >>>> in your case, will get re-rendered (refreshed with your >>>> statement). >>>> so your inputHidden will not be updated unless specified. >>>> >>>> Cheers, >>>> >>>> M. >>>> >>>> Oracle Java Champion >>>> Developer (http://www.t2.com.tr), Lecturer ( >>>> http://www.cs.hacettepe.edu.tr/kisiler.html), JUG Leader ( >>>> http://www.ankarajug.org), Author (http://www.amazon.com/author/mert) >>>> >>>> >>>> >>>> On Friday 2 January 2015 at 11:51, Thomas Andraschko wrote: >>>> >>>> Hey Romain, >>>>> >>>>> AFAIR the default for the render attribute of f:ajax is @none, so >>>>> >>>> therefore >>>> >>>>> it's expected. You would need to set it to e.g. render="@form" >>>>> >>>>> 2015-01-02 10:33 GMT+01:00 Romain Manni-Bucau >>>> >>>> (mailto:rmannibu...@gmail.com)>: >>>> >>>>> >>>>> Hi guys, >>>>>> >>>>>> >>>>>> in cdi tcks there is: >>>>>> >>>>>> >>>>>> >>>>> id="conversationId" /> >>>>>> >>>>>> >>>>> value="Begin conversation" id="beginConversationButton"> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> seems when ajax rendering is triggered h:inputHidden is not refresh, >>>>>> is it expected? >>>>>> >>>>>> >>>>>> Romain Manni-Bucau >>>>>> @rmannibucau >>>>>> >>>>>> http://www.tomitribe.com >>>>>> http://rmannibucau.wordpress.com >>>>>> https://github.com/rmannibucau >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> > -- > Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté. > > | > | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. > | > >
Re: hidden input not refreshed
@this will just refresh the commandButton no? so it is really @form (goal would be to refresh the conversation id). Could it be a difference between MF and Mojarra - it is taken from CDI TCKs so I guess it was passed using mojarra? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-01-02 11:16 GMT+01:00 Thomas Andraschko : > I see Romain. It should work for the first button... > You could try to add execute="@this" but it should work without, too. > > 2015-01-02 11:01 GMT+01:00 Mert ÇALIŞKAN : > >> Yes, default value of f:ajax is @none. >> But also by default the element that triggers the request, which is >> in your case, will get re-rendered (refreshed with your >> statement). >> so your inputHidden will not be updated unless specified. >> >> Cheers, >> >> M. >> >> Oracle Java Champion >> Developer (http://www.t2.com.tr), Lecturer ( >> http://www.cs.hacettepe.edu.tr/kisiler.html), JUG Leader ( >> http://www.ankarajug.org), Author (http://www.amazon.com/author/mert) >> >> >> >> On Friday 2 January 2015 at 11:51, Thomas Andraschko wrote: >> >> > Hey Romain, >> > >> > AFAIR the default for the render attribute of f:ajax is @none, so >> therefore >> > it's expected. You would need to set it to e.g. render="@form" >> > >> > 2015-01-02 10:33 GMT+01:00 Romain Manni-Bucau > (mailto:rmannibu...@gmail.com)>: >> > >> > > Hi guys, >> > > >> > > >> > > in cdi tcks there is: >> > > >> > > >> > > > > > id="conversationId" /> >> > > >> > > > > > value="Begin conversation" id="beginConversationButton"> >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > seems when ajax rendering is triggered h:inputHidden is not refresh, >> > > is it expected? >> > > >> > > >> > > Romain Manni-Bucau >> > > @rmannibucau >> > > http://www.tomitribe.com >> > > http://rmannibucau.wordpress.com >> > > https://github.com/rmannibucau >> > > >> > >> > >> > >> >> >>
Re: hidden input not refreshed
that's what is done (beginConversationButton): Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-01-02 10:51 GMT+01:00 Thomas Andraschko : > Hey Romain, > > AFAIR the default for the render attribute of f:ajax is @none, so therefore > it's expected. You would need to set it to e.g. render="@form" > > 2015-01-02 10:33 GMT+01:00 Romain Manni-Bucau : > >> Hi guys, >> >> >> in cdi tcks there is: >> >> >> > id="conversationId" /> >> >> > value="Begin conversation" id="beginConversationButton"> >> >> >> >> >> >> >> >> >> >> seems when ajax rendering is triggered h:inputHidden is not refresh, >> is it expected? >> >> >> Romain Manni-Bucau >> @rmannibucau >> http://www.tomitribe.com >> http://rmannibucau.wordpress.com >> https://github.com/rmannibucau >>
hidden input not refreshed
Hi guys, in cdi tcks there is: seems when ajax rendering is triggered h:inputHidden is not refresh, is it expected? Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
In an ear you have lib part and war libs. Mf only needs war part. If you put mf in lib part, mf needs to ensure it doesn't add again beans. For it you can generate a name for your beans in the extension. This name would be contextual and finally lib part will never be used normally but it will not create any conflict. Le 4 sept. 2014 22:18, "Leonardo Uribe" a écrit : > 2014-09-04 16:04 GMT-05:00 Romain Manni-Bucau : > > > but you can share in both something (common thing is the classloader) > > to match the bean (or name) you need. > > > > > I don't understand. MyFaces just provide the extension points. When and how > the extensions are called are up to CDI and maybe Tomee. I suppose the > AmbiguousResolutionException is caused because MyFaces is loaded twice by > Tomee (when it is using ear). Split that code in a separate jar will not > help. > > > > > > > Romain Manni-Bucau > > Twitter: @rmannibucau > > Blog: http://rmannibucau.wordpress.com/ > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > Github: https://github.com/rmannibucau > > > > > > 2014-09-04 22:38 GMT+02:00 Leonardo Uribe : > > > As you already know, MyFaces provide some extensions and those > extensions > > > register some CDI beans. But the way how the dependencies are loaded > are > > > controlled by Tomee and by the CDI implementation, in this case OWB. I > > have > > > tried in the past to avoid the CDI beans in the integration point, but > it > > > is not possible, you need one in order to hold the beans in the scope, > > and > > > you cannot access JSF from CDI (it works the opposite, access CDI from > > JSF). > > > > > > regards, > > > > > > Leonardo Uribe > > > > > > > > > 2014-09-04 15:25 GMT-05:00 Romain Manni-Bucau : > > > > > >> the issue is wars of an ear inherit from "lib" beans so mf shouldn't > > >> use it (can be done adding a bean with a generated name by webapp - > > >> and get the name from the servlet context for instance) > > >> > > >> on tomee side we can skip mf cdi beans in ear lib part if it can help > > >> > > >> > > >> Romain Manni-Bucau > > >> Twitter: @rmannibucau > > >> Blog: http://rmannibucau.wordpress.com/ > > >> LinkedIn: http://fr.linkedin.com/in/rmannibucau > > >> Github: https://github.com/rmannibucau > > >> > > >> > > >> 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau >: > > >> > @Leonardo: with ears? > > >> > > > >> > > > >> > Romain Manni-Bucau > > >> > Twitter: @rmannibucau > > >> > Blog: http://rmannibucau.wordpress.com/ > > >> > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > >> > Github: https://github.com/rmannibucau > > >> > > > >> > > > >> > 2014-09-04 22:12 GMT+02:00 Leonardo Uribe : > > >> >> Hi > > >> >> > > >> >> I have tested the latest snapshot from trunk and it is working with > > >> tomee > > >> >> 1.7.0. I don't see any exception from this side. > > >> >> > > >> >> regards, > > >> >> > > >> >> Leonardo Uribe > > >> >> > > >> >> > > >> >> 2014-09-03 17:23 GMT-05:00 José Luis Cetina >: > > >> >> > > >> >>> Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i > > want > > >> to > > >> >>> use myfaces 2.2.4 because i want to use the > > >> @javax.faces.view.ViewScoped (i > > >> >>> use the omnifaces viewscoped) and the f:viewAction. > > >> >>> > > >> >>> But again im getting > > >> javax.enterprise.inject.AmbiguousResolutionException: > > >> >>> Ambiguous resolution exception that i reported a few months ago, > > >> apparently > > >> >>> myfaces 2.2.4 is not working with ears in tomee 1.7.0. > > >> >>> > > >> >>> I already reported to tomee mailing list but @Romain sayed > > >> >>> > > >> >>> "think so but more a MF issue this time I think" > > >> >>> > > >> >>> @Leonardo > > >> >>> > > >> >>> > > >> >>> >
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
but you can share in both something (common thing is the classloader) to match the bean (or name) you need. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:38 GMT+02:00 Leonardo Uribe : > As you already know, MyFaces provide some extensions and those extensions > register some CDI beans. But the way how the dependencies are loaded are > controlled by Tomee and by the CDI implementation, in this case OWB. I have > tried in the past to avoid the CDI beans in the integration point, but it > is not possible, you need one in order to hold the beans in the scope, and > you cannot access JSF from CDI (it works the opposite, access CDI from JSF). > > regards, > > Leonardo Uribe > > > 2014-09-04 15:25 GMT-05:00 Romain Manni-Bucau : > >> the issue is wars of an ear inherit from "lib" beans so mf shouldn't >> use it (can be done adding a bean with a generated name by webapp - >> and get the name from the servlet context for instance) >> >> on tomee side we can skip mf cdi beans in ear lib part if it can help >> >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau : >> > @Leonardo: with ears? >> > >> > >> > Romain Manni-Bucau >> > Twitter: @rmannibucau >> > Blog: http://rmannibucau.wordpress.com/ >> > LinkedIn: http://fr.linkedin.com/in/rmannibucau >> > Github: https://github.com/rmannibucau >> > >> > >> > 2014-09-04 22:12 GMT+02:00 Leonardo Uribe : >> >> Hi >> >> >> >> I have tested the latest snapshot from trunk and it is working with >> tomee >> >> 1.7.0. I don't see any exception from this side. >> >> >> >> regards, >> >> >> >> Leonardo Uribe >> >> >> >> >> >> 2014-09-03 17:23 GMT-05:00 José Luis Cetina : >> >> >> >>> Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want >> to >> >>> use myfaces 2.2.4 because i want to use the >> @javax.faces.view.ViewScoped (i >> >>> use the omnifaces viewscoped) and the f:viewAction. >> >>> >> >>> But again im getting >> javax.enterprise.inject.AmbiguousResolutionException: >> >>> Ambiguous resolution exception that i reported a few months ago, >> apparently >> >>> myfaces 2.2.4 is not working with ears in tomee 1.7.0. >> >>> >> >>> I already reported to tomee mailing list but @Romain sayed >> >>> >> >>> "think so but more a MF issue this time I think" >> >>> >> >>> @Leonardo >> >>> >> >>> >> >>> >> >>> >> >>> 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. < >> smithh032...@gmail.com>: >> >>> >> >>> > if you are not able to use MyFaces 2.2 @ViewScoped, you may need to >> keep >> >>> > OmniFaces CDI @ViewScoped until someone helps you with your issue. >> >>> > >> >>> > Some months ago, I tested MyFaces 2.2 with OmniFaces CDI >> @ViewScoped; all >> >>> > of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I >> >>> > experienced no issues. My app is not packaged as an EAR. >> >>> > >> >>> > today, i am using MyFaces 2.2 @ViewScoped beans even though I still >> have >> >>> > OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). >> >>> > >> >>> > For the first day, running MyFaces 2.2, I am quite pleased. No >> issues to >> >>> > report, no exceptions in tomee/tomcat log files. >> >>> > >> >>> > >> >>> > >> >>> > On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina < >> maxtorz...@gmail.com >> >>> > >wrote: >> >>> > >> >>> > > I removed CODI and my app is package as ear. maybe i need to try >> tomee >> >>> > > 1.6.1-snapshot >> >>> > > >> >>> > > >> >>> > > 2014/1/15 Howard W. Smith, Jr. >> >>> > > >> >>> > > > On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina < >> >>> > maxtorz...@gmail.com >> >>> > > > >wrote: >> >>> > > > >> >>> > > > > I removed my faces 2.1.13 jars (api and imp) from tomee lib >> and add >> >>> > > > myfaces >> >>> > > > > api and impl 2.2.0 >> >>> > > > > >> >>> > > > >> >>> > > > that's exactly what I did and I don't get the error. >> >>> > > > >> >>> > > > Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, >> too? >> >>> > > > >> >>> > > >> >>> > > >> >>> > > >> >>> > > -- >> >>> > > --- >> >>> > > *SCJA. José Luis Cetina* >> >>> > > --- >> >>> > > >> >>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> --- >> >>> *José Luis Cetina* >> >>> --- >> >>> >>
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
the issue is wars of an ear inherit from "lib" beans so mf shouldn't use it (can be done adding a bean with a generated name by webapp - and get the name from the servlet context for instance) on tomee side we can skip mf cdi beans in ear lib part if it can help Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:23 GMT+02:00 Romain Manni-Bucau : > @Leonardo: with ears? > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-09-04 22:12 GMT+02:00 Leonardo Uribe : >> Hi >> >> I have tested the latest snapshot from trunk and it is working with tomee >> 1.7.0. I don't see any exception from this side. >> >> regards, >> >> Leonardo Uribe >> >> >> 2014-09-03 17:23 GMT-05:00 José Luis Cetina : >> >>> Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to >>> use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i >>> use the omnifaces viewscoped) and the f:viewAction. >>> >>> But again im getting javax.enterprise.inject.AmbiguousResolutionException: >>> Ambiguous resolution exception that i reported a few months ago, apparently >>> myfaces 2.2.4 is not working with ears in tomee 1.7.0. >>> >>> I already reported to tomee mailing list but @Romain sayed >>> >>> "think so but more a MF issue this time I think" >>> >>> @Leonardo >>> >>> >>> >>> >>> 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. : >>> >>> > if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep >>> > OmniFaces CDI @ViewScoped until someone helps you with your issue. >>> > >>> > Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all >>> > of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I >>> > experienced no issues. My app is not packaged as an EAR. >>> > >>> > today, i am using MyFaces 2.2 @ViewScoped beans even though I still have >>> > OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). >>> > >>> > For the first day, running MyFaces 2.2, I am quite pleased. No issues to >>> > report, no exceptions in tomee/tomcat log files. >>> > >>> > >>> > >>> > On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina >> > >wrote: >>> > >>> > > I removed CODI and my app is package as ear. maybe i need to try tomee >>> > > 1.6.1-snapshot >>> > > >>> > > >>> > > 2014/1/15 Howard W. Smith, Jr. >>> > > >>> > > > On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina < >>> > maxtorz...@gmail.com >>> > > > >wrote: >>> > > > >>> > > > > I removed my faces 2.1.13 jars (api and imp) from tomee lib and add >>> > > > myfaces >>> > > > > api and impl 2.2.0 >>> > > > > >>> > > > >>> > > > that's exactly what I did and I don't get the error. >>> > > > >>> > > > Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? >>> > > > >>> > > >>> > > >>> > > >>> > > -- >>> > > --- >>> > > *SCJA. José Luis Cetina* >>> > > --- >>> > > >>> > >>> >>> >>> >>> -- >>> --- >>> *José Luis Cetina* >>> --- >>>
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
@Leonardo: with ears? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-09-04 22:12 GMT+02:00 Leonardo Uribe : > Hi > > I have tested the latest snapshot from trunk and it is working with tomee > 1.7.0. I don't see any exception from this side. > > regards, > > Leonardo Uribe > > > 2014-09-03 17:23 GMT-05:00 José Luis Cetina : > >> Hi, i was trying to use MyFaces 2.2.4 with TomEE 1.7.0 JAX-RS, i want to >> use myfaces 2.2.4 because i want to use the @javax.faces.view.ViewScoped (i >> use the omnifaces viewscoped) and the f:viewAction. >> >> But again im getting javax.enterprise.inject.AmbiguousResolutionException: >> Ambiguous resolution exception that i reported a few months ago, apparently >> myfaces 2.2.4 is not working with ears in tomee 1.7.0. >> >> I already reported to tomee mailing list but @Romain sayed >> >> "think so but more a MF issue this time I think" >> >> @Leonardo >> >> >> >> >> 2014-01-15 17:14 GMT-06:00 Howard W. Smith, Jr. : >> >> > if you are not able to use MyFaces 2.2 @ViewScoped, you may need to keep >> > OmniFaces CDI @ViewScoped until someone helps you with your issue. >> > >> > Some months ago, I tested MyFaces 2.2 with OmniFaces CDI @ViewScoped; all >> > of my @ViewScoped beans were still OmniFaces CDI @ViewScoped, and I >> > experienced no issues. My app is not packaged as an EAR. >> > >> > today, i am using MyFaces 2.2 @ViewScoped beans even though I still have >> > OmniFAces 1.6.3 JAR/dependency (not using OmniFaces CDI @ViewScoped). >> > >> > For the first day, running MyFaces 2.2, I am quite pleased. No issues to >> > report, no exceptions in tomee/tomcat log files. >> > >> > >> > >> > On Wed, Jan 15, 2014 at 5:57 PM, José Luis Cetina > > >wrote: >> > >> > > I removed CODI and my app is package as ear. maybe i need to try tomee >> > > 1.6.1-snapshot >> > > >> > > >> > > 2014/1/15 Howard W. Smith, Jr. >> > > >> > > > On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina < >> > maxtorz...@gmail.com >> > > > >wrote: >> > > > >> > > > > I removed my faces 2.1.13 jars (api and imp) from tomee lib and add >> > > > myfaces >> > > > > api and impl 2.2.0 >> > > > > >> > > > >> > > > that's exactly what I did and I don't get the error. >> > > > >> > > > Jose, are you still using MyFaces CODI (1.5 or 1.6.x) and EAR, too? >> > > > >> > > >> > > >> > > >> > > -- >> > > --- >> > > *SCJA. José Luis Cetina* >> > > --- >> > > >> > >> >> >> >> -- >> --- >> *José Luis Cetina* >> --- >>
Re: dep error?
You are right but in TomEE and because of it we need to exclude these optional dependencies cause they are included otherwise because of assembly maven plugin. Provided is semantically weong but "behavior-ly" right. Le 5 août 2014 02:50, "Leonardo Uribe" a écrit : > Hi > > Instead use "provided", these dependencies are optional: > > > > org.apache.geronimo.specs > geronimo-jcdi_1.0_spec > 1.0 > compile > true > > > > > org.apache.geronimo.specs > geronimo-atinject_1.0_spec > 1.0 > compile > true > > > It is better to let it like that, because it is valid to use JSF 2.2 > artifacts without CDI. > > regards, > > Leonardo Uribe > > 2014-08-04 16:00 GMT-05:00 Romain Manni-Bucau : > > Hi guys > > > > just to mention 2.2.4 has: > > > > 40 [INFO] +- org.apache.myfaces.core:myfaces-api:jar:2.2.4:compile > > 41 [INFO] | +- > > org.apache.geronimo.specs:geronimo-jcdi_1.0_spec:jar:1.0:compile > > 42 [INFO] | \- > > org.apache.geronimo.specs:geronimo-atinject_1.0_spec:jar:1.0:compile > > > > Wouldn't it be better to set geronimo deps as provided? > > > > > > Romain Manni-Bucau > > Twitter: @rmannibucau > > Blog: http://rmannibucau.wordpress.com/ > > LinkedIn: http://fr.linkedin.com/in/rmannibucau > > Github: https://github.com/rmannibucau >
dep error?
Hi guys just to mention 2.2.4 has: 40 [INFO] +- org.apache.myfaces.core:myfaces-api:jar:2.2.4:compile 41 [INFO] | +- org.apache.geronimo.specs:geronimo-jcdi_1.0_spec:jar:1.0:compile 42 [INFO] | \- org.apache.geronimo.specs:geronimo-atinject_1.0_spec:jar:1.0:compile Wouldn't it be better to set geronimo deps as provided? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
Re: problem wit hvisualize a size of colletion into a datatable
It is in
Le 20 févr. 2014 20:04, "Mike Kienenberger" a écrit :
> A J2EE container should already provide jars with this functionality.
>
>
> http://en.wikipedia.org/wiki/Java_EE_version_history#Java_EE_6_.28December_10.2C_2009.29
>
> I'm not sure about tomee. Probably better to ask that question on the
> Tomee mailing list.
>
>
> On Thu, Feb 20, 2014 at 1:37 PM, maurojava
> wrote:
> > Tank you .
> > I use tomee so for use jstl i have to add the jars of jstl to
> web-inf/lib ?
> > Il giorno 20/feb/2014 18.42, "Mike Kienenberger [via MyFaces]" <
> > ml-node+s10567n117243...@n7.nabble.com> ha scritto:
> >
> >> Calling arbitrary methods like size() isn't supported in EL 2.1,
> >> although I think it might be in EL 2.2.
> >>
> >> Here's the way to do it that will work in any version of JSF.
> >>
> >> xmlns:jstl="http://java.sun.com/jsp/jstl/functions";
> >>
> >> [...]
> >> >> value="#{jstl:length(item.professors)} tot
> >> projects"/>
> >>
> >>
> >>
> >> On Thu, Feb 20, 2014 at 11:21 AM, maurojava <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=117243&i=0>>
> >> wrote:
> >>
> >> > From the projectController , i have a method: getCollectionProject
> that
> >> > return a List .
> >> > Each project contains a list of Professor .
> >> > SO into the last line i would show the amount of professors for the
> >> project
> >> > .
> >> >
> >> > The var item rappresent a project.
> >> > project contains a List
> >> > i write "#{item.professors.size()}" for get the amount of professors
> >> for
> >> > the project valutated form each iteration .
> >> >
> >> >
> >> > Whi into the last outputText :
> >> >
> >> >
> >> > it shows only the words tot projects and not show the value of
> listSize?
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > >> value="#{projectController.collectionProject}"
> >> > var="item">
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > value="#{item.professors.size()}
> >> tot
> >> > projects"/>
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >>
> http://myfaces.10567.n7.nabble.com/problem-wit-hvisualize-a-size-of-colletion-into-a-datatable-tp117242.html
> >> > Sent from the MyFaces - Users mailing list archive at Nabble.com.
> >>
> >>
> >> --
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://myfaces.10567.n7.nabble.com/problem-wit-hvisualize-a-size-of-colletion-into-a-datatable-tp117242p117243.html
> >> To unsubscribe from problem wit hvisualize a size of colletion into a
> >> datatable, click here<
> http://myfaces.10567.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=117242&code=bWF1cm8yamF2YTIwMTFAZ21haWwuY29tfDExNzI0MnwtMTExNzE4NzYyNQ==
> >
> >> .
> >> NAML<
> http://myfaces.10567.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >>
> >
> >
> >
> >
> > --
> > View this message in context:
> http://myfaces.10567.n7.nabble.com/problem-wit-hvisualize-a-size-of-colletion-into-a-datatable-tp117242p117244.html
> > Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
Re: Problems with a custom component when migrating from Glassfish(mojarra) to TomEE
in tomee you can also use mojarra but I'd just keep my component
portable with myfaces if possible
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-02-13 13:23 GMT+01:00 Thomas Andraschko :
> I don't think that anyone will port your complete code and give you a
> complete solution ;)
>
> The biggest problem is AFAIR that the renderer implementations are not in
> the API packages. So you have to rebuild all this functionality without
> dependencies to the Impl.
>
> e.g.
> Attribute,AttributeManager -> String[] with attribute namens
> Move all the utils functions to your own code (Util.componentIsDisabled,
> RenderKitUtils.getSelectItems. etc.)
>
> The most code doesn't really depent on the IMPL code.
>
>
> 2014-02-13 12:44 GMT+01:00 Rene Perschon :
>
>> Hi everyone!
>>
>> I'm currently migrating an application from Glassfish 3.1.1 to TomEE. Now
>> the problem is that this application contains a custom component which was
>> unfortunately coded with hard dependencies on com.sun.faces classes (maven
>> dependency jsf-impl).
>>
>> Now my question is how can i port this component in such a way that it is
>> independent from any concrete JSF implementation (or at least in such a way
>> that it works with MyFaces).
>>
>> Here's the component:
>>
>> import java.io.IOException;
>> import java.util.Iterator;
>> import java.util.Map;
>>
>> import javax.faces.component.UIComponent;
>> import javax.faces.component.UINamingContainer;
>> import javax.faces.component.ValueHolder;
>> import javax.faces.context.FacesContext;
>> import javax.faces.context.ResponseWriter;
>> import javax.faces.convert.Converter;
>> import javax.faces.model.SelectItem;
>> import javax.faces.model.SelectItemGroup;
>>
>> import com.sun.faces.renderkit.Attribute;
>> import com.sun.faces.renderkit.AttributeManager;
>> import com.sun.faces.renderkit.RenderKitUtils;
>> import com.sun.faces.renderkit.html_basic.MenuRenderer;
>> import com.sun.faces.util.RequestStateManager;
>> import com.sun.faces.util.Util;
>>
>> /**
>> * {@inheritDoc}.
>> */
>> public class CustomSelectManyCheckboxListRenderer extends MenuRenderer
>> {
>> /** {@inheritDoc}. */
>> private static final Attribute[] ATTRIBUTES =
>> AttributeManager.getAttributes(AttributeManager.Key.SELECTMANYCHECKBOX);
>> /** Representing the border string. */
>> private static final String BORDER = "border";
>> /** Representing the tr string. */
>> private static final String TR = "tr";
>> /** Representing the td string. */
>> private static final String TD = "td";
>> /** Representing the label string. */
>> private static final String LABEL = "label";
>> /** Representing the newline string. */
>> private static final String NEWLINE = "\n";
>> /** Representing the tab string. */
>> private static final String TAB = "\t";
>> /** Representing the class string. */
>> private static final String CLASS = "class";
>> /** Representing the style string. */
>> private static final String STYLE = "style";
>> /** Representing the valign string. */
>> private static final String VALIGN = "valign";
>>
>>
>> // -- Public
>> Methods
>>
>>
>> @Override
>> public void encodeEnd(FacesContext context, UIComponent component)
>> throws IOException
>> {
>>
>> rendererParamsNotNull(context, component);
>>
>> if (!shouldEncode(component))
>> {
>> return;
>> }
>>
>> ResponseWriter writer = context.getResponseWriter();
>> assert (writer != null);
>>
>> String alignStr;
>> Object borderObj;
>> boolean alignVertical = false;
>> int border = 0;
>>
>>
>>
>> if (null != component.getAttributes().get("layout"))
>> {
>> alignStr = (String) component.getAttributes().get("layout");
>> alignVertical = alignStr.equalsIgnoreCase("pageDirection");
>> }
>>
>> if (null != component.getAttributes().get(BORDER))
>> {
>> borderObj = compone
Re: @FlowScoped, @Named and @ManagedBean
DeltaSpike is not a CDI implementation but a helper library.
I think OWB supports FlowScoped at least it has been tested in TomEE
AFAIK, anyone can confirm?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-02-11 10:28 GMT+01:00 l.pe...@senat.fr :
> On 11/02/2014 03:30, Leonardo Uribe wrote:
>>
>> Hi
>
> Thank you for your quick reply.
>
> 2014-02-10 11:56 GMT-05:00 l.pe...@senat.fr :
>>>
>>> Dear all,
>>>
>>> I am starting to really use JSF 2.2. I am trying to use Faces Flows. I am
>>> starting with a very simple flow, whose name is "flow1".
>>>
>>> So, under src/main/webapp, I have a flow1 directory containing
>>>
>>> flow1-flow.xml
>>> flow1.xhtml
>>> flow1b.xhtml
>>>
>>> flow1-flow.xml contains :
>>>
>>>
>>> >> xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
>>> xmlns='http://xmlns.jcp.org/xml/ns/javaee'
>>> xsi:schemaLocation='http://xmlns.jcp.org/xml/ns/javaee
>>> http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd'
>>> version='2.2' >
>>>
>>>
>>> /accueil
>>>
>>>
>>>
>>>
>>>
>>> With such a simple config, using conventions would be a better choice
>>> than
>>> configuration, but I plan to add more things to it... :-)
>>>
>>> I use a @FlowScoped bean declared this way :
>>>
>>> @Named
>>> @FlowScoped("flow1")
>>> public class MinintFileContext implements Serializable {
>>>
>>>
>>> }
>>>
>>> and it does not work. I have the following exception :
>>>
>>> javax.servlet.ServletException: javax.servlet.ServletException:
>>> javax.el.ELException: javax.enterprise.context.ContextNotActiveException:
>>> WebBeans context with scope type annotation @FlowScoped does not exist
>>> within current thread
>>>
>>>
>>> To make it work, I have to use @ManagedBean instead of @Named.
>>>
>>> My first question is : I do not understand why... In my (obviously wrong)
>>> understanding, @Named was a super-set of CDI-managed beans, including
>>> @ManagedBean-s.
>>>
>>
>> @FlowScoped annotation is for CDI only, so it will not work for JSF
>> managed beans. In your case, I believe the bean is instantiated but it
>> is not stored in any context, so once is created is discarded, giving
>> the impression that the bean is working but it is not.
>>
>> In MyFaces it is possible to create a custom flow scope annotation for
>> other containers that works just like @FlowScoped, implementing
>> org.apache.myfaces.spi.FacesFlowProvider SPI interface. You are
>> already in CDI, so you don't need to bother about that.
>>
>> I have seen @Named annotation working with Spring, so it is not
>> something specific for CDI, but @FlowScoped depends of CDI API.
>
> I am using CODI 1.0.5 (I heavily use its @ViewAccessScoped annotation) with
> OpenWebBeans 1.2.1.
>
> So, I thought was ok on the CDI side...
>
> ...but after reading your mail, it seems to me that this CDI implementation
> was provided before JSF 2.2 release, and so that it must not include proper
> @FacesFlow support.
>
> Should I switch to another implementation, like DeltaSpike ?
>
> I must have misunderstood your mail from Sep 26 2013 (
> http://myfaces.10567.n7.nabble.com/JSF-2-2-status-amp-snapshot-usage-td115852.html
> ) inviting us to try Faces Flows in MyFaces 2.2.
>
> Thanks again,
>
> Ludovic
>
>
> |
> | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT.
> |
Re: [OT but still JSF]: Clustering, session replication, and database, too
@thomas: same on tomee + tomee has another integration for it, optimized for tomcat Le 20 oct. 2013 11:35, "Thomas Andraschko" a écrit : > Hey, > > JFYI: > MyFaces+OWB on Tomcat with MSM is working fine. > > Don't know about TomEE. > > Regards, > Thomas > > > 2013/10/20 Karl Kildén > > > Hello! I am also very interested in having more i.e. docs, examples and > > stuff for clustering across the tomee stack. The discussion came up on a > > jira some time ago and after that I asked Thomas to write a new post > about > > it (First part was great!). > > > > For example this is something that sounds really interesting and I want > to > > know more: > > > > * do not replicate the session over to other nodes! > > > > My scenarios are usually tomee with one war or tomcat with one war and > JSF, > > CDI, JPA only. > > > > > > On 20 October 2013 05:48, Howard W. Smith, Jr. > >wrote: > > > > > I had a question or two, since I have been reading "Java Summit - > > Pitfalls > > > in EE"[1] provided by Mark Struberg while having a discussion on tomee > > user > > > list. > > > > > > The following page stated the following: > > > > > > Page 134 > > > Clustering > > > > > > * We use 'asymmetric clustering' > > > * use sticky sessions > > > * backup away the session to a memcached after each > > > request > > > * do not replicate the session over to other nodes! > > > * Session-Replication always in node pairs. > > > * only restore the session from the memcached if a failover > > > happened > > > * msm can be integrated into OWB: > > > http://code.google.com/p/memcached-session-manager/ > > > > > > Since it says, 'We use asymmetric clustering' and other suggestions > were > > > made, I found it appropriate to direct my question(s) to MyFaces 'JSF' > > user > > > list and committers. > > > > > > is there some type of blog (or two or three) available that discuss how > > to > > > properly cluster a tomcat/tomee/openwebbeans/myfaces JSF web app? also, > > how > > > is the database replicated? I don't ever see database > cluster/replication > > > discussed by JSF developers; i recently had to search for database > > cluster > > > and saw 'replication', which is something i have not had to worry about > > > since my previous work involved database teams while i was doing > > > front-end/GUI software. > > > > > > now that i am doing java ee and jsf, i would love to know how to do > > > database clustering and/or replicating database while clustering JSF > > > webapp. Of course, right now, i only have one tomee which references > > > 'apache' derby (which is performing well, but I would love to get my > feet > > > wet and cluster my web app + database). i did search derby's mail list > > > archives and i learned about sequioa and HA-JDBC (High-Availability > > JDBC). > > > > > > i was hoping to get an answer from MyFaces 'JSF' > users/committers...based > > > on their experience. I think someone told me that they use mysql > > > (clustering); my preference is still 'apache' derby (smile). please > > > remember, i'm wondering if any blogs are available that discuss > > clustering > > > tomcat (preference = tomee) + JSF web app (with database) + memcached > > > session manager. > > > > > > Thomas has already started writing a blog[2] about this. I'm looking > > > forward to seeing sample config for it all (if available). :) > > > > > > [1] > > > > > > > > > http://people.apache.org/~struberg/eesummit2013/Java%20EE%20Summit%20-%20pitfalls%20in%20EE.pdf > > > > > > [2] > > > > > > > > > http://tandraschko.blogspot.com/2013/09/session-replication-clustering-failover.html > > > > > >
Re: [OT but still JSF]: Clustering, session replication, and database, too
Hi Tomcat/tomee session replication; memcached and custom session manager (hazelcast) solutions are different. Typically in some of them you accept SPoF, not in others. The perf are not the same too. Finally guarantees (synchronous or not persistence) can be different too. Mark info were consistent but adapted to his apps I think. The "theorical" solution is sometimes not enough... Was just to give some more inputs and dont believe in IT you have a single solution. PS: if tomee clustering has issues please help us working on it on trunk and tomee list Le 20 oct. 2013 07:30, "José Luis Cetina" a écrit : > I have a early experience with a "mini cluster" 2 servers using tomee + > memcached for session replication+ sticky session but using 1 only server > for database (i mean i dont use db replication). My jsf apps (ear) are > running in this mini cluster everithyng works fine except when i shutdown > tomee for do a re deploy i always see an xhtml parser error. I could never > configure it session replication with tomcat. > > In your web apps just use distributable tag in web.xml and all other are > configuration. You can use memcached to not only session replication even > thougth for savr information of your app and with this you can share > information between your nodes and with this you dont persist information > that could be "transient". > The result is incredible. > > As i sayed i could never configure session replication with tomcat, the > only way i could do it is using memcached session replication. > > I dont know if anybody here have any experience with this. > > Regards Howard. > El 19/10/2013 22:49, "Howard W. Smith, Jr." > escribió: > > > I had a question or two, since I have been reading "Java Summit - > Pitfalls > > in EE"[1] provided by Mark Struberg while having a discussion on tomee > user > > list. > > > > The following page stated the following: > > > > Page 134 > > Clustering > > > > * We use 'asymmetric clustering' > > * use sticky sessions > > * backup away the session to a memcached after each > > request > > * do not replicate the session over to other nodes! > > * Session-Replication always in node pairs. > > * only restore the session from the memcached if a failover > > happened > > * msm can be integrated into OWB: > > http://code.google.com/p/memcached-session-manager/ > > > > Since it says, 'We use asymmetric clustering' and other suggestions were > > made, I found it appropriate to direct my question(s) to MyFaces 'JSF' > user > > list and committers. > > > > is there some type of blog (or two or three) available that discuss how > to > > properly cluster a tomcat/tomee/openwebbeans/myfaces JSF web app? also, > how > > is the database replicated? I don't ever see database cluster/replication > > discussed by JSF developers; i recently had to search for database > cluster > > and saw 'replication', which is something i have not had to worry about > > since my previous work involved database teams while i was doing > > front-end/GUI software. > > > > now that i am doing java ee and jsf, i would love to know how to do > > database clustering and/or replicating database while clustering JSF > > webapp. Of course, right now, i only have one tomee which references > > 'apache' derby (which is performing well, but I would love to get my feet > > wet and cluster my web app + database). i did search derby's mail list > > archives and i learned about sequioa and HA-JDBC (High-Availability > JDBC). > > > > i was hoping to get an answer from MyFaces 'JSF' users/committers...based > > on their experience. I think someone told me that they use mysql > > (clustering); my preference is still 'apache' derby (smile). please > > remember, i'm wondering if any blogs are available that discuss > clustering > > tomcat (preference = tomee) + JSF web app (with database) + memcached > > session manager. > > > > Thomas has already started writing a blog[2] about this. I'm looking > > forward to seeing sample config for it all (if available). :) > > > > [1] > > > > > http://people.apache.org/~struberg/eesummit2013/Java%20EE%20Summit%20-%20pitfalls%20in%20EE.pdf > > > > [2] > > > > > http://tandraschko.blogspot.com/2013/09/session-replication-clustering-failover.html > > >
Re: Random JSF error: no saved view state could be found
Hmm, can be interesting if you have enough time to try to reproduce it in a shareable (on github?) project. I'm sure it is something "stupid" we don't see ATM. *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/1 Zmirc > Hi! > > Yes, I run Majorra on Tomee 1.6.0 from 13.09.20. I will switch today to > 13.10.01 to see if that bug with @Schedule leak disappeared. > > I understand your point of view and I agree. I have no idea which one has > the bug, just that I don't get it on Majorra. (I've just deleted myfaces > jars from Tomee and added Majorra 2.1.26 - nothing special) > > What settings should I give you? I didn't modify anything in Tomee, > excepting perm gen size, heap (on production) and a few more things in > setenv. Here's the setenv on my windows. (It's the same on linux also, just > as .sh) > > set JAVA_OPTS=%JAVA_OPTS% -XX:MaxPermSize=512m > set JAVA_OPTS=%JAVA_OPTS% -Dorg.apache.catalina.session.** > StandardSession.ACTIVITY_**CHECK=true > set JAVA_OPTS=%JAVA_OPTS% -Dopenejb.session-context=http > set JAVA_OPTS=%JAVA_OPTS% -Dfacebook4j.loggerFactory=** > facebook4j.internal.logging.**NullLoggerFactory > > So...the error happens randomly (just sometimes to some users) for all > pages that modify information and are backed by a @ViewScoped bean: > > The following logs are from Tomee 1.6.0 13.09.20. It happens the same on > 1.5.2. I moved on 1.6.0 hoping to get rid of it. > > javax.servlet.**ServletException: /dashboard/edit-profile.**xhtmlNo saved > view state could be found for the view identifier: > /dashboard/edit-profile.xhtml > at javax.faces.webapp.**FacesServlet.service(**FacesServlet.java:213) > ~[myfaces-api-2.1.12.jar:2.1.**12] > at org.apache.catalina.core.**ApplicationFilterChain.** > internalDoFilter(**ApplicationFilterChain.java:**305) > ~[catalina.jar:7.0.42] > at org.apache.catalina.core.**ApplicationFilterChain.**doFilter(** > ApplicationFilterChain.java:**210) ~[catalina.jar:7.0.42] > at > org.primefaces.webapp.filter.**FileUploadFilter.doFilter(**FileUploadFilter.java:77) > ~[primefaces-3.5.jar:na] > at org.apache.catalina.core.**ApplicationFilterChain.** > internalDoFilter(**ApplicationFilterChain.java:**243) > ~[catalina.jar:7.0.42] > at org.apache.catalina.core.**ApplicationFilterChain.**doFilter(** > ApplicationFilterChain.java:**210) ~[catalina.jar:7.0.42] > at > org.ocpsoft.rewrite.servlet.**RewriteFilter.doFilter(**RewriteFilter.java:199) > ~[rewrite-servlet-2.0.7.Final.**jar:2.0.7.Final] > at org.apache.catalina.core.**ApplicationFilterChain.** > internalDoFilter(**ApplicationFilterChain.java:**243) > ~[catalina.jar:7.0.42] > at org.apache.catalina.core.**ApplicationFilterChain.**doFilter(** > ApplicationFilterChain.java:**210) ~[catalina.jar:7.0.42] > at com.pingushare.boundary.**filter.ActivateAccountFilter.**doFilter(* > *ActivateAccountFilter.java:38) ~[ActivateAccountFilter.class:**na] > at org.apache.catalina.core.**ApplicationFilterChain.** > internalDoFilter(**ApplicationFilterChain.java:**243) > ~[catalina.jar:7.0.42] > at org.apache.catalina.core.**ApplicationFilterChain.**doFilter(** > ApplicationFilterChain.java:**210) ~[catalina.jar:7.0.42] > at com.pingushare.boundary.**filter.SecurityFilter.** > doFilter(SecurityFilter.java:**36) ~[SecurityFilter.class:na] > at org.apache.catalina.core.**ApplicationFilterChain.** > internalDoFilter(**ApplicationFilterChain.java:**243) > ~[catalina.jar:7.0.42] > at org.apache.catalina.core.**ApplicationFilterChain.**doFilter(** > ApplicationFilterChain.java:**210) ~[catalina.jar:7.0.42] > at com.pingushare.boundary.**filter.**ForceFreshPageAndWWWFilter.** > doFilter(**ForceFreshPageAndWWWFilter.**java:41) > ~[ForceFreshPageAndWWWFilter.**class:na] > at org.apache.catalina.core.**ApplicationFilterChain.** > internalDoFilter(**ApplicationFilterChain.java:**243) > ~[catalina.jar:7.0.42] > at org.apache.catalina.core.**ApplicationFilterChain.**doFilter(** > ApplicationFilterChain.java:**210) ~[catalina.jar:7.0.42] > at > org.apache.catalina.core.**StandardWrapperValve.invoke(**StandardWrapperValve.java:222) > ~[catalina.jar:7.0.42] > at > org.apache.catalina.core.**StandardContextValve.invoke(**StandardContextValve.java:123) > ~[catalina.jar:7.0.42] > at org.apache.tomee.catalina.**OpenEJBValve.invoke(**OpenEJBValve.java:45) > ~[tomee-catalina-1.6.0-**SNAPSHOT.jar:1.6.0-SNAPSHOT] > at > org.apache.catal
Re: Random JSF error: no saved view state could be found
Hi Do you run mojarra on tomee? Basically the exception you sent doesnt seem complete and is not usable to help. About "it works with mojarra so that's mf" it is a big shortcut. It can be a bug in mojarra which make it working too (im not saying it, just you dont know and you cant conclude since you were not able to give us any info on this issue we can use to work on it) In all cases of you handle to reproduce please share the whole logs and maybe your server settings. Tomee can be the cause too depending it. Le 30 sept. 2013 23:33, "Zmirc" a écrit : > Hi, Leonardo! > > Unfortunately, I've been very pressed by having to get it to work in > production, so I switched this project to Majorra. Happily enough, the > error didn't appear anymore, at least until now. > > I would have definitely loved to afford doing those tests, but it wasn't > possible unfortunately. > Anyway, by the fact that now it doesn't appear just by changin to Majorra, > it is obvious that there might be a hidden little bug somewhere in MyFaces, > otherwise it can't be explained. > > I'm so sorry that I can't reproduce it. It happened completely random. It > might be as you suggested, a problem in creating/reloading the state. You > know better than me those details. > > I would really like to have that bug discovered and fixed, because I was > quite used to MyFaces. > Thank you again for trying to help. > I hope something can be done about it. I know that, without being able to > reproduce it, it's a little bit hard, but I hope. > > Best, > Mircea > > On 9/27/2013 11:56 AM, Leonardo Uribe wrote: > >> Hi >> >> There is no magical solutions to you problem. You should check which value >> has javax.faces.ViewState request parameter in the POST request that >> causes >> the ViewExpiredException. Put a filter or a PhaseListener that logs that >> value when there is an incoming request to that view. The key point is to >> know if the view state token is there or not and if it has been altered >> somehow between the time the page is renderer and the time the button is >> clicked and the POST is sended. You need to log the token saved on the >> page >> too, to know the original value. >> >> One option I can imagine is that the value in the ViewState token is sent >> partially. The server received the trimmed token, it doesn't match because >> it is broken and it throws correctly the ViewExpiredException. But sounds >> unlikely, we need more evidence about what's going on. >> >> What I can say is the code in MyFaces Core is ok in that part and >> specifically the state management code has been tested exhaustively. It is >> quite unlikely to find a bug in that part. >> >> regards, >> >> Leonardo Uribe >> >> >> >> 2013/9/27 Zmirc >> >> Hi again! >>> >>> Any ideas / fixes for this bug? >>> It's still there and is completely random. >>> Moreover, I can't reproduce it. >>> >>> Please don't ignore it, because it's a real pain in the ... >>> It's screwing up the whole project, because some users get this bug >>> randomly, whenever they execute a post (command button). >>> >>> Thank you so so much in advance. >>> >>> >>> On 9/25/2013 12:17 PM, Zmirc wrote: >>> >>> Hi! Some users (few) of the app I work on experience a very strange error, which I can't yet reproduce. Moreover, it appears in less than 10~ of executions. Error: No saved view state could be found for the view identifier: /mypage.xhtml Application server: Apache Tomee 1.5.2 stable / 1.6.0-2013.09.20 dev (It happens on both). I use the MyFaces distribution that comes with each of them, so 2.1.10 / 2.1.12, so nothing new added. Part of web.xml | org.apache.myfaces.USE_ENCRYPTION>>> **name> false javax.faces.STATE_SAVING_METHOD client | So, no state view exception shouldn't happen, because state is on client. It was set on server before, but I thought maybe client will fix it, but nothing. There was actually no difference in the occurrence of that error. Moreover, it's not related to deploy/redeploy/restart, because encryption is false. I don't experience any problem with that. Execution flow: 1. Client opens xhtml page (JSF). 2. Client clicks on an command button to do various things, button connected to a public void method of a JSF @ViewScoped ManagedBean. 3. Yes, the method is void because I don't need to return a String to redirect to another page. I need to redirect to /page/id (example: /market/24, /profile/43), therefore methods that return a String as navigation destinations are useless, because I use:|FacesContext.** getCurrentInstance().getExternalContext().redirect(path);| 4. In ~90% of the cases, everything works perfectly and users are redirected to each specific page. In the rest of ~10 (ran
Re: config web.xml myfaces for use with primefaces
here is an app using pf in tomee (not sure about tomee versions since it is now a bit old so maybe it is no more up to date but the conf didnt change): https://github.com/rmannibucau/agoncal-application-petstore-ee6 here is the web.xml: https://github.com/rmannibucau/agoncal-application-petstore-ee6/blob/master/src/main/webapp/WEB-INF/web.xml *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/4/9 maurojava > please you can send me a complete web.xml for get myfaces to work with > primesfaces ? > and with rich faces? > > tank you very much > > mauro > > > > > -- > View this message in context: > http://myfaces.10567.n7.nabble.com/config-web-xml-myfaces-for-use-with-primefaces-tp114536p114544.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. >
