Hi,
I have an webapp that runs fine in GF3.1.1 using Weld1.1 + CODI + JPA2 +
Hibernate4.2.6 + JSF2 + RichFaces4.3.4.
Then, when I try to deploy in GF4, server.log arises this error, and
searching on Internet, some people said this is a
problem with CODI, that is not compatible with JEE7 projects.
Hi Edilmar.
I had the same issues. There are incompatibilities apparently with JSF
2.2 that ships with GlassFish 4. And JSF 2.2 has some much improved CDI
features, such as proper @ViewScope.
Kay
On 10/30/2013 01:03 PM, Edilmar Alves wrote:
Hi,
I have an webapp that runs fine in GF3.1.1
Also, MyFaces 2.2 (beta, which has JavaEE7 JSF2.2 features) was
just/recently released (yesterday, I think). Feel free to give that a try.
TomEE and tomcat8 is and/or will be targeting JEE7.
is it a requirement to deploy to Glassfish 4, or you just want to deploy to
your local machine for
Or he can stick with Glassfish 3.1.2.2, which is GlassFish' last final
release targeting Java EE 6. Unless he wants to incorporated new
features that only Java EE 7 can provide, I'd say, stick with what
currently works. Or try alternatives, such as TomEE 1.5.2 or TomEE 1.6
which still targets
Hi friends,
Thanks for help!
Look at these situations...
1) Glassfish 3.1.1 and 3.1.2.2 has the same behaviour. But I use in
production 3.1.1 because there are many servers using my webapp with this
version, and it is not simple to upgrade.
2) I am testing Glassfish 4/JEE7 because Glassfish is
I'm looking at CDI 1.1 spec
http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html and ot looks like
@ConversationScope is already part of CDI 1.1, no CODI needed for that.
GlassFish 4 includes CDI 1.1 by way of Weld API 2.0
http://www.cdi-spec.org/download/ which is bundled inside the
Also, you might want to check with RichFaces. I found this blog
http://www.bleathem.ca/blog/2013/09/richfaces-434final-release-announcement.html
and the moderator mentions that full JSF 2.2 support is planned for
RichFaces 5. I had some of the same issues with PrimeFaces 3.5 which was
Hi,
I use CODI ConversationScoped and @Inject Conversation because it is better
than original CDI implementation.
I have many java files using CODI at this time.
Then, to go back to CDI, I will have to change many files, and I don't know
if the webapp will continue to work 100%,
because the
I think CODI is a great replacement for my actual environment, the only
problem is to deploy in GF4.
2013/10/30 Edilmar Alves edili...@gmail.com
Hi,
I use CODI ConversationScoped and @Inject Conversation because it is
better than original CDI implementation.
I have many java files using
Yeah, I think CODI was a good for some features that either didn't exist
in CDI 1.0 (like ViewAccessScoped) or were better implemented in CODI.
That said, CDI in Java EE 7 is much improved, and switching over to an
EE 7 profile and taking advantage of it may require you to make code
changes
hi edilmar,
apache deltaspike is the official successor of codi/seam/... (including
support for ee7+).
some parts (including codi-conversations) are still on our list, however,
you can try it with [1] (it's the same code - just different packages and
based on deltaspike).
@kay (and your comment
Thanks Gerhard.
I just Google'd the topic and also ran across DeltaSpike.
Sorry, I was a bit unaware of ConversationScoped and what it does and
that it was better implemented in CODI.
On 10/30/2013 04:33 PM, Gerhard Petracek wrote:
hi edilmar,
apache deltaspike is the official successor of
One could still investigate if @ConversatioScoped has improved in CDI
1.1 and is on par with how CODI 1.0.5 handles it. Again, I am not the
right person to discuss that annotation, but it's a thought.
On 10/30/2013 04:33 PM, Gerhard Petracek wrote:
hi edilmar,
apache deltaspike is the
those changes in v1.1 are better than nothing, but still not enough. codi
(grouped-)conversations follow quite different concepts.
most concepts provided by codi have been ported to deltaspike (with ee7 in
mind). however, ee7 only contains few of them out-of-the-box (and in some
cases just
Interesting conversation, and per your responses, Gerhard, I guess I can go
ahead and quote what I heard someone mentioned in another forum (or issue
tracker) about CODI being an inactive project...being superseded by
deltaspike.
I think Mark Struberg or one of your guys provided a slideshow
Nope, we didn't touch @ConversationScoped a bit in CDI-1.1.
The main changes in CDI-1.1 have been clarifications. But most of them are
already implemented in OWB and Weld, even in the CDI-1.0 targetting versions.
There have been a few good Extensions in the Extension area, scanning, etc in
Mark,
On Wed, Oct 30, 2013 at 7:05 PM, Mark Struberg strub...@yahoo.de wrote:
The main changes in CDI-1.1 have been clarifications. But most of them are
already implemented in OWB and Weld, even in the CDI-1.0 targetting
versions.
There have been a few good Extensions in the Extension area,
@mark:
the parameter conversationPropagation was added in 1.1.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2013/10/31 Mark Struberg strub...@yahoo.de
Nope, we
18 matches
Mail list logo
