Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread Romain Manni-Bucau
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

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread Leonardo Uribe
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

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread Romain Manni-Bucau
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 GM

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread 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

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread 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: @rman

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread 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

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread José Luis Cetina
i will try to reproduce it, the issue apparently is with ears 2014-09-04 15:12 GMT-05: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 G

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-04 Thread 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 be

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-09-03 Thread 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 e

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-01-15 Thread 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 i

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-01-15 Thread José Luis Cetina
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 >wrote: > > > I removed my faces 2.1.13 jars (api and imp) from tomee lib and add > myfaces > > api and impl 2.2.0 > > > > th

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-01-15 Thread Howard W. Smith, Jr.
On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina 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?

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-01-15 Thread Howard W. Smith, Jr.
Leonardo, Jose uses/deploys EARs. Maybe that is the issue. Has MyFaces 2.2 @ViewScoped been tested in an EAR. Jose, You need to provide more of your configuration and share that you usually deploy your app via EAR(s). right? On Wed, Jan 15, 2014 at 5:48 PM, Leonardo Uribe wrote: > Hi > > It

Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-01-15 Thread Leonardo Uribe
Hi It looks like something not directly related to MyFaces, it is like if the classpath is scanned twice, or like the bean is subscribed twice. I suppose it is a bug in OWB or in TomEE. Maybe you should report it in: https://issues.apache.org/jira/browse/TOMEE regards, Leonardo Uribe 2014/1/15

MyFaces 2.2.0 ViewScoped AmbiguousResolutionException

2014-01-15 Thread José Luis Cetina
Hi. I use TomEE 1.6.0 Final release with myfaces 2.1.13 and jdk 1.7 with this i was using the org.omnifaces.cdi.ViewScoped annotation with any problem, with the new release of myfaces 2.2.0 i decide to change from org.omnifaces.cdi.ViewScoped to javax.faces.view.ViewScoped then im gettin this Ambig