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
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
I did it. But now i have problems. I reporte a AmbiguousResolutionException
in other thread.
2014/1/15 Howard W. Smith, Jr.
> 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 impo
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?
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
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
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
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
Thanks
2014/1/15 Thomas Andraschko
> http://jsflive.wordpress.com/2013/07/17/jsf22-cdi-view-scope/
>
>
> 2014/1/15 José Luis Cetina
>
> > 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
> >
http://jsflive.wordpress.com/2013/07/17/jsf22-cdi-view-scope/
2014/1/15 José Luis Cetina
> 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
>
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
On Wed, Jan 15, 2014 at 2:27 AM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:
> FYI, I 'want' to migrate to MyFaces 2.2.0 in production, and I think I
> will do it anyway, but please answer my question above about this
> behavior/implementation/test-results-of-mine.
>
well, I'm running M
MyFaces 2.2.0 is working just as good as MyFaces 2.1.13 (has been working
over the last few months).
So, i guess MyFaces 2.2.0 is here to stay in my app. Thank you!
On Wed, Jan 15, 2014 at 2:54 AM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:
> Done (deployed MyFaces 2.2.0 with my app
Hi,
Tobago 1.0.x should run on Tomcat 7 and later. I'll update the webside:
http://myfaces.apache.org/tobago/compatibility.html
I've a running installation of a Tobago 1.0.x Application with Tomcat 7.0.47
Regards
Udo
Am 15.01.14 00:30, schrieb d.o@gmx.net:
> Hello all,
>
> Could you plea
14 matches
Mail list logo
