Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

2016-08-12 14:57 GMT+02:00 Lazar Kirchev : > Thanks, Romain! > I asked for a fix because we have scenarios where we could not modify the > applications, so even a very simple change such as adding an empty > beans.xml does not help. > > Well tomcat allows you to enrich

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Thanks, Romain! I asked for a fix because we have scenarios where we could not modify the applications, so even a very simple change such as adding an empty beans.xml does not help. On Fri, Aug 12, 2016 at 3:52 PM, Romain Manni-Bucau wrote: > Well a workaround is to add

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Well a workaround is to add in WEB-INF/application.properties: openejb.cdi.activated=true this particular issue should be fixed for 7.0.2 even if plume distribution is "best effort" Romain Manni-Bucau @rmannibucau | Blog

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Ok, then the problem is in the integration of mojarra in tomee. Do you have any plans to integrate it fully so that it works without this "deficiency"? On Fri, Aug 12, 2016 at 2:18 PM, Romain Manni-Bucau wrote: > as mentionned owb is in the container and we fully

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

as mentionned owb is in the container and we fully integrate with myfaces. However mojarra ditribution doesn't get that deep integration and only works when CDI is activated. Romain Manni-Bucau @rmannibucau | Blog | Old

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Hi, I got exactly the same problem when deploying an app without beans.xml. However, I tried to deploy it on Tomcat + OpenWebBeans + Mojarra and it worked fine. What do you think? Regards, Lazar On Fri, Aug 5, 2016 at 7:25 PM, Romain Manni-Bucau wrote: > feel free to

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

feel free to edit the website to add that where you think it fits (with the small blue pen button) Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog | Github

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Totally agree on the fail. So, the good word here is that PLUME works, one simply needs to supply a beans.xml file. Anyway this can be documented very clearly somewhere? I mean, luckily, PLUS and Web Profile, which is probably the majority of downloads, adhere to the "optional" beans.xml and

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

beans.xml "is" optional (strictly speaking cause if you check what it does when not there you probably want to add it back) issue is OwbAppfactory expects CDI to be there, if there is no CDI need then i suspect it is skipped and mojarra integration behaves differently than myfaces one - failing

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

I have added both 7.0.1 PLUS and Web Profile to my NetBeans installation. I can take the same project, switch it to PLUS or Web Profile and deploy the simple web app successfully. NetBeans does NOT generate a beans.xml file anymore since that has been made optional in JSF 2.2 (I believe). In

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

looks like CDI was completely turned off for this app, is that possible? Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog | Github | LinkedIn

Re: Getting ConfigurationException: Factory ClientWindowFactory was not configured properly

Hi Romain. It's linked (see the pastebin link?). Kay > On Aug 5, 2016, at 10:50 AM, Romain Manni-Bucau wrote: > > Hello Kay, > > do you have the full stack? > > > Romain Manni-Bucau > @rmannibucau | Blog >