Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
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 maxtorz...@gmail.com: 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. smithh032...@gmail.com 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
i will try to reproduce it, the issue apparently is with ears 2014-09-04 15:12 GMT-05:00 Leonardo Uribe lu4...@gmail.com: 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 maxtorz...@gmail.com: 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. smithh032...@gmail.com 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* --- -- --- *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 lu4...@gmail.com: 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 maxtorz...@gmail.com: 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. smithh032...@gmail.com 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 rmannibu...@gmail.com: @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 lu4...@gmail.com: 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 maxtorz...@gmail.com: 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. smithh032...@gmail.com 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
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 rmannibu...@gmail.com: 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 rmannibu...@gmail.com: @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 lu4...@gmail.com: 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 maxtorz...@gmail.com: 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. smithh032...@gmail.com 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
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 lu4...@gmail.com: 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 rmannibu...@gmail.com: 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 rmannibu...@gmail.com: @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 lu4...@gmail.com: 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 maxtorz...@gmail.com: 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. smithh032...@gmail.com 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
2014-09-04 16:04 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: 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 lu4...@gmail.com: 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 rmannibu...@gmail.com: 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 rmannibu...@gmail.com: @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 lu4...@gmail.com: 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 maxtorz...@gmail.com: 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. smithh032...@gmail.com 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
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 lu4...@gmail.com a écrit : 2014-09-04 16:04 GMT-05:00 Romain Manni-Bucau rmannibu...@gmail.com: 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 lu4...@gmail.com: 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 rmannibu...@gmail.com: 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 rmannibu...@gmail.com : @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 lu4...@gmail.com: 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 maxtorz...@gmail.com : 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. smithh032...@gmail.com 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? -- ---
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
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. smithh032...@gmail.com 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* ---
MyFaces 2.2.0 ViewScoped
Hi im currently using org.omnifaces.cdi.ViewScoped for my @Named beans, now with MyFaces 2.2.0 which package do i have to use for @ViewScoped and @Named for work togheter. Thanks
Re: MyFaces 2.2.0 ViewScoped
http://jsflive.wordpress.com/2013/07/17/jsf22-cdi-view-scope/ 2014/1/15 José Luis Cetina maxtorz...@gmail.com Hi im currently using org.omnifaces.cdi.ViewScoped for my @Named beans, now with MyFaces 2.2.0 which package do i have to use for @ViewScoped and @Named for work togheter. Thanks
Re: MyFaces 2.2.0 ViewScoped
Thanks 2014/1/15 Thomas Andraschko andraschko.tho...@gmail.com http://jsflive.wordpress.com/2013/07/17/jsf22-cdi-view-scope/ 2014/1/15 José Luis Cetina maxtorz...@gmail.com Hi im currently using org.omnifaces.cdi.ViewScoped for my @Named beans, now with MyFaces 2.2.0 which package do i have to use for @ViewScoped and @Named for work togheter. Thanks -- --- *SCJA. José Luis Cetina* ---
MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
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 AmbiguousResolutionException. This error only happend in Linux environment, if i run the same project in Windows this error never appears. I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 What could be wrong? Log: javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution found beans: ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder], Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default] from jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder], Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default] from jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionExceptionForBeans(InjectionExceptionUtil.java:104) org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionException(InjectionExceptionUtil.java:94) org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionException(InjectionExceptionUtil.java:71) org.apache.webbeans.container.InjectionResolver.resolve(InjectionResolver.java:699) org.apache.webbeans.container.BeanManagerImpl.resolve(BeanManagerImpl.java:925) org.apache.webbeans.container.InjectableBeanManager.resolve(InjectableBeanManager.java:201) org.apache.myfaces.cdi.util.BeanProvider.getContextualReference(BeanProvider.java:413) org.apache.myfaces.cdi.util.BeanProvider.getContextualReference(BeanProvider.java:144) org.apache.myfaces.cdi.impl.CDIManagedBeanHandlerImpl.getViewScopeBeanHolder(CDIManagedBeanHandlerImpl.java:64) org.apache.myfaces.cdi.impl.CDIManagedBeanHandlerImpl.generateViewScopeId(CDIManagedBeanHandlerImpl.java:92) org.apache.myfaces.view.ViewScopeProxyMap.getWrapped(ViewScopeProxyMap.java:76) org.apache.myfaces.view.ViewScopeProxyMap.size(ViewScopeProxyMap.java:89) javax.faces.component.UIViewRoot.saveState(UIViewRoot.java:1498) org.apache.myfaces.renderkit.ErrorPageWriter._writeComponent(ErrorPageWriter.java:846) org.apache.myfaces.renderkit.ErrorPageWriter.debugHtml(ErrorPageWriter.java:351) org.apache.myfaces.renderkit.ErrorPageWriter.handle(ErrorPageWriter.java:470) org.apache.myfaces.context.MyFacesExceptionHandlerWrapperImpl.handle(MyFacesExceptionHandlerWrapperImpl.java:301) javax.faces.context.ExceptionHandlerWrapper.handle(ExceptionHandlerWrapper.java:61) org.omnifaces.exceptionhandler.FullAjaxExceptionHandler.handle(FullAjaxExceptionHandler.java:162) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:287) javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
Re: MyFaces 2.2.0 ViewScoped
Hey, Jose. you should have used NetBeans 'Fix imports' option after removing Omnifaces package. i think you are using NetBeans (but I might be wrong). Fix imports would have gave you a dialog showing you the MyFaces 2.2 @ViewScoped package to import. On Wed, Jan 15, 2014 at 3:34 PM, José Luis Cetina maxtorz...@gmail.comwrote: Hi im currently using org.omnifaces.cdi.ViewScoped for my @Named beans, now with MyFaces 2.2.0 which package do i have to use for @ViewScoped and @Named for work togheter. Thanks
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
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 José Luis Cetina maxtorz...@gmail.com: 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 AmbiguousResolutionException. This error only happend in Linux environment, if i run the same project in Windows this error never appears. I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 What could be wrong? Log: javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution found beans: ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder], Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default] from jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder], Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default] from jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionExceptionForBeans(InjectionExceptionUtil.java:104) org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionException(InjectionExceptionUtil.java:94) org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionException(InjectionExceptionUtil.java:71) org.apache.webbeans.container.InjectionResolver.resolve(InjectionResolver.java:699) org.apache.webbeans.container.BeanManagerImpl.resolve(BeanManagerImpl.java:925) org.apache.webbeans.container.InjectableBeanManager.resolve(InjectableBeanManager.java:201) org.apache.myfaces.cdi.util.BeanProvider.getContextualReference(BeanProvider.java:413) org.apache.myfaces.cdi.util.BeanProvider.getContextualReference(BeanProvider.java:144) org.apache.myfaces.cdi.impl.CDIManagedBeanHandlerImpl.getViewScopeBeanHolder(CDIManagedBeanHandlerImpl.java:64) org.apache.myfaces.cdi.impl.CDIManagedBeanHandlerImpl.generateViewScopeId(CDIManagedBeanHandlerImpl.java:92) org.apache.myfaces.view.ViewScopeProxyMap.getWrapped(ViewScopeProxyMap.java:76) org.apache.myfaces.view.ViewScopeProxyMap.size(ViewScopeProxyMap.java:89) javax.faces.component.UIViewRoot.saveState(UIViewRoot.java:1498) org.apache.myfaces.renderkit.ErrorPageWriter._writeComponent(ErrorPageWriter.java:846) org.apache.myfaces.renderkit.ErrorPageWriter.debugHtml(ErrorPageWriter.java:351) org.apache.myfaces.renderkit.ErrorPageWriter.handle(ErrorPageWriter.java:470) org.apache.myfaces.context.MyFacesExceptionHandlerWrapperImpl.handle(MyFacesExceptionHandlerWrapperImpl.java:301) javax.faces.context.ExceptionHandlerWrapper.handle(ExceptionHandlerWrapper.java:61) org.omnifaces.exceptionhandler.FullAjaxExceptionHandler.handle(FullAjaxExceptionHandler.java:162) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:287) javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
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 lu4...@gmail.com wrote: 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 José Luis Cetina maxtorz...@gmail.com: 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 AmbiguousResolutionException. This error only happend in Linux environment, if i run the same project in Windows this error never appears. I removed my faces 2.1.13 jars (api and imp) from tomee lib and add myfaces api and impl 2.2.0 What could be wrong? Log: javax.enterprise.inject.AmbiguousResolutionException: Ambiguous resolution found beans: ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder], Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default] from jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class ViewScopeBeanHolder, Name:null, WebBeans Type:MANAGED, API Types:[java.io.Serializable,java.lang.Object,org.apache.myfaces.cdi.view.ViewScopeBeanHolder], Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.Default] from jar:file:/home/broncos/apache/tomee/apache-tomee-jaxrs-1.6.0/lib/myfaces-impl-2.2.0.jar!/org/apache/myfaces/cdi/view/ViewScopeBeanHolder.class org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionExceptionForBeans(InjectionExceptionUtil.java:104) org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionException(InjectionExceptionUtil.java:94) org.apache.webbeans.util.InjectionExceptionUtil.throwAmbiguousResolutionException(InjectionExceptionUtil.java:71) org.apache.webbeans.container.InjectionResolver.resolve(InjectionResolver.java:699) org.apache.webbeans.container.BeanManagerImpl.resolve(BeanManagerImpl.java:925) org.apache.webbeans.container.InjectableBeanManager.resolve(InjectableBeanManager.java:201) org.apache.myfaces.cdi.util.BeanProvider.getContextualReference(BeanProvider.java:413) org.apache.myfaces.cdi.util.BeanProvider.getContextualReference(BeanProvider.java:144) org.apache.myfaces.cdi.impl.CDIManagedBeanHandlerImpl.getViewScopeBeanHolder(CDIManagedBeanHandlerImpl.java:64) org.apache.myfaces.cdi.impl.CDIManagedBeanHandlerImpl.generateViewScopeId(CDIManagedBeanHandlerImpl.java:92) org.apache.myfaces.view.ViewScopeProxyMap.getWrapped(ViewScopeProxyMap.java:76) org.apache.myfaces.view.ViewScopeProxyMap.size(ViewScopeProxyMap.java:89) javax.faces.component.UIViewRoot.saveState(UIViewRoot.java:1498) org.apache.myfaces.renderkit.ErrorPageWriter._writeComponent(ErrorPageWriter.java:846) org.apache.myfaces.renderkit.ErrorPageWriter.debugHtml(ErrorPageWriter.java:351) org.apache.myfaces.renderkit.ErrorPageWriter.handle(ErrorPageWriter.java:470) org.apache.myfaces.context.MyFacesExceptionHandlerWrapperImpl.handle(MyFacesExceptionHandlerWrapperImpl.java:301) javax.faces.context.ExceptionHandlerWrapper.handle(ExceptionHandlerWrapper.java:61) org.omnifaces.exceptionhandler.FullAjaxExceptionHandler.handle(FullAjaxExceptionHandler.java:162) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:287) javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
Re: MyFaces 2.2.0 ViewScoped
I did it. But now i have problems. I reporte a AmbiguousResolutionException in other thread. 2014/1/15 Howard W. Smith, Jr. smithh032...@gmail.com Hey, Jose. you should have used NetBeans 'Fix imports' option after removing Omnifaces package. i think you are using NetBeans (but I might be wrong). Fix imports would have gave you a dialog showing you the MyFaces 2.2 @ViewScoped package to import. On Wed, Jan 15, 2014 at 3:34 PM, José Luis Cetina maxtorz...@gmail.com wrote: Hi im currently using org.omnifaces.cdi.ViewScoped for my @Named beans, now with MyFaces 2.2.0 which package do i have to use for @ViewScoped and @Named for work togheter. Thanks -- --- *SCJA. José Luis Cetina* ---
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
On Wed, Jan 15, 2014 at 4:40 PM, José Luis Cetina maxtorz...@gmail.comwrote: 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
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. smithh032...@gmail.com 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* ---
Re: MyFaces 2.2.0 ViewScoped AmbiguousResolutionException
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.comwrote: 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. smithh032...@gmail.com 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* ---
