Hi
I thought a lot about FactoryFinder and how we can extend it. I'll do a
resume, describing the problem in detail and providing some alternatives.
This could be a little bit redundant, but it is necessary to gain a better
understanding about what's going on and the direction to take.
On Feb 10, 2011, at 9:39 PM, Leonardo Uribe wrote:
Hi David
There are some points to take into consideration for myfaces-api jar
1. It is preferred that myfaces-api have the less amount of compile or
runtime dependencies to work. Right now, myfaces 2.0.x api and impl only
require:
Imo myfaces-api is pretty much bound to myfaces-impl. Like el-api is bound to
the el-impl most of the times. (sadly)
LieGrue,
strub
--- On Fri, 2/11/11, David Jencks david_jen...@yahoo.com wrote:
From: David Jencks david_jen...@yahoo.com
Subject: Re: Issue 2995 - Leo please read
To: MyFaces
, David Jencks david_jen...@yahoo.com wrote:
From: David Jencks david_jen...@yahoo.com
Subject: Re: Issue 2995 - Leo please read
To: MyFaces Development dev@myfaces.apache.org, Leonardo Uribe
lu4...@gmail.com
Date: Friday, February 11, 2011, 6:23 PM
On Feb 10, 2011, at 9:39 PM, Leonardo Uribe
Hi David
There are some points to take into consideration for myfaces-api jar
1. It is preferred that myfaces-api have the less amount of compile or
runtime dependencies to work. Right now, myfaces 2.0.x api and impl only
require:
commons-beanutils-1.8.3.jar
commons-codec-1.4.jar
Hi seems this went a little bit under, I only can apologize for this,
and I assume everyone else is my opinion also, given the importance of
this bug I guess Leo should have a serious look at it and integrate it
Asap, I cannot really since this is not my domain, but more Leos who has
worked on
Hi
I already saw the patch, but I forget to do some comments about it.
First of all, 2.0.4 is a quick fix release, so new features or improvements
are not being considered for this one.
The patch provided on MYFACES-2995 cannot be applied it its current form.
The reason is it suggest a new
If it is for OSGI only I think the bundle only is fine with me
If not I dont have any problem to add an integration module, where all
the container specfic integration stuff can move into if it is not
hostable in our core.
Might be worthwhile to add such a module anyway so that we can isolate
This is NOT for osgi. The ee classloading model does not require a separate
classloader for each war in an ear, whereas currently the myfaces api
implementation assumes that web apps can be distinguished by the thread context
classloader. So the idea behind the patch is to provide a way to
