Problems with @ViewScoped and @PreDestroy have been identified in the
spec and a fix is slated for JSF 2.2:
http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-905
You guys might want to comment on it.
Stan
On 11/16/2012 9:50 AM, Mark Struberg wrote:
Hi Radu!
Congratulations, you
Quoting Matthias Wessendorf mat...@apache.org:
+1
doesn't hurt to have our app/framework working with both (see [1]).
I totally agree. You should make sure your app always runs with
either JSF impl so that you can switch based on which impl runs your
final app better.
Actually even
I'm pretty sure 2.0.1 has a memory leak on undeploy. Mojarra had an
undeploy leak and it took a long time to track it down. The same test
I was using on Mojarra also failed on MyFaces but I haven't had time
to track down the leak in MyFaces.
Maybe this is fixed in 2.0.2? If not maybe
Thanks Werner. Hope someone can take a look before 2.0.3.
Stan
Quoting Werner Punz werner.p...@gmail.com:
Am 15.10.10 14:04, schrieb ssilv...@redhat.com:
I'm pretty sure 2.0.1 has a memory leak on undeploy. Mojarra had an
undeploy leak and it took a long time to track it down. The same
Quoting Bruno Aranda brunoara...@gmail.com:
Using tomcat 7 I get this warning...
SEVERE: The web application [/editor-2.0-SNAPSHOT] created a ThreadLocal
with key of type [java.lang.ThreadLocal] (value
[java.lang.threadlo...@41649a55]) and a value of type
Quoting Jakob Korherr jakob.korh...@gmail.com:
The ThreadLocal should be cleared upon undeploy, but this does not
cause the memory leak mentioned by Stan.
I disagree. That could easily be the cause as was the case with Mojarra.
You will get a PermGen error in about an hour.
The PermGen
https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1820
Quoting Werner Punz werner.p...@gmail.com:
Stan can you give us some info what the issue in Mojarra was?
It might help us to track our problem down.
My personal guess we that it might the our class instantiation code in
shared,
Yes, the goal is to allow any version and any implementation of JSF.
That's why you will see Initialized 3 JSF configurations:
[Mojarra-1.2, MyFaces-2.0,
Mojarra-2.0]
Just to be clear, it's AS6 SNAPSHOT, not AS5. The AS6 CR1 release
will be out in a few weeks but you can get a nightly
MyFaces 2.0.1 will be included in milestone 4. I just added it over
the weekend. If you build JBoss AS from trunk you can play around
with it.
The doc for JSF integration is here:
http://www.jboss.org/jbossas/docs/6-x/Component-Documentation/jsf.html
You'll want to look at part 2 and part
Quoting Leonardo Uribe lu4...@gmail.com:
I have planned to start that release procedure for 2.0.2 today or tomorrow,
so I think we could release 2.0.3 on November.
That's good.
Since the tighter integration with JBoss annotation scanning hasn't
been tested, I'll be surprised if we don't
That's OK. I guess I can do the SPI implementations on my end but it
might not make it into JBoss AS6 GA. Let's concentrate on the MyFaces
SPI's for now. How does MyFaces handle the SPI's like Mojarra has?
I'm sure it's OK to look at Mojarra code since it's GPL2, right? If
not, you can
Can you look at javadoc comments?
Quoting Matthias Wessendorf mat...@apache.org:
Well, looking at the RI is for sure not OK.
I didn't see a problem with the previous provided links (the JBoss
code), however
I have not opened any of the provided links yet.
-Matthias
On Thu, Aug 5, 2010 at
Quoting David Jencks david_jen...@yahoo.com:
I haven't and wont look at the mojarra code but I think you are looking for
org.apache.myfaces.config.annotation.LifecycleProvider
Looks like that takes care of spec section 5.4 (injection,
@PreDestroy, @PostConstruct).
How do you deal with
Hi guys,
Would you like to see MyFaces Core ship with JBoss AS6? If so, read on.
If you've been around MyFaces awhile, you probably remember that
JBoass AS used to ship with MyFaces instead of Mojarra. It was
regrettable, but at the time Mojarra was far ahead spec-wise and the
powers
14 matches
Mail list logo
