Meeting 2012-02-22
by Jason Porter
The only thing I have to talk about is a date for 3.1.1. If people would
like to attend a meeting for that today great I'll be in IRC. If you'd
simply like to respond to this email we can do it that way as well.
We've talked about 3.1.1 simply being examples, better documentation and
some minor bug fixes.
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
12 years, 10 months
Fwd: Re: [jboss-as7-dev] help needed with responding to reported classloader leaks in (Rest, Rest WS, JPA, EJB3 activation/passivation, other)...
by Scott Marlow
https://community.jboss.org/message/716191 is an AS7 user forum thread
about application classloader leaks in a few different areas.
All of them involve a Seam 2.2.2 application using Resteasy 2.3.1. One
of the leaks is described in jira RESTEASY-660.
Is there something that the users application has to do, to get Seam
2.2.2 to call ResteasyProviderFactory.clearContextData() at the end of a
request?
Scott
-------- Original Message --------
Subject: Re: [jboss-as7-dev] help needed with responding to reported
classloader leaks in (Rest, Rest WS, JPA, EJB3 activation/passivation,
other)...
Date: Tue, 14 Feb 2012 07:33:29 -0500
From: Bill Burke <bburke(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
On 2/13/12 12:59 PM, Scott Marlow wrote:
> org.jboss.resteasy.util.ThreadLocalStack creates ThreadLocal pseudo-leak
> on AS 7: https://issues.jboss.org/browse/RESTEASY-660
> "
>
This may be Seam related.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
12 years, 10 months
Re: [seam-dev] JSTL + Maven + Seam 2.3
by Marek Novotny
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That is good point to think about. I have looked at the known issues and
generally it is not designed to be optimized and integrated technology
as it has got different process flow from JSF2.
I found this short and nice recommendation in a nutshell: Use JSTL to
control flow of JSF result. Use JSF to control flow of HTML result. Do
not bind attributes of view scoped beans to JSTL tag attributes, or you
must turn partial state saving off.
One additional thing is that JSTL namespace has changed from
xmlns:c=”http://java.sun.com/jstl/core”
to
xmlns:c=”http://java.sun.com/jsp/jstl/core”
I would say we will have to create a big warning with that information
in documentation.
P.S. Adding also seam-dev mailing list, some JSF2 expert can add some
important point too ;-)
On 02/05/2012 04:38 AM, Daniel Hinojosa wrote:
> Is jstl still supported for Seam 2.3 since JSF 2 I think is only
> supported in XHTML (actually I don't know that for sure, but going to check)
>
> --
> Daniel Hinojosa
> Programmer, Instructor, and Consultant
> dhinojosa(a)evolutionnext.com <mailto:dhinojosa@evolutionnext.com>
> http://www.evolutionnext.com
> http://www.abqjug.org
>
- --
Marek Novotny
- --
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8vkIMACgkQU4HO8G8hNxVafQCbBO7AayZpfqntKlMqcs1ovyfp
ZeIAoJVw9ehsQrHKQafXJTdLtlLD6njK
=GAvY
-----END PGP SIGNATURE-----
12 years, 11 months
