Actually you raise some valid points here, at least for the myfaces
subprojects we have this matrix:

http://wiki.apache.org/myfaces/CompatibilityMatrix?highlight=%28matrix%29

I personally think such a combined matrix is only maintainable in a wiki
way if you do not have a central testing ground for those things.

Might be a good idea to open a central matrix on one of the wikis
somewhere for intra project dependenies.

Werner


Carsten Kaiser schrieb:
> Let me comment on this from a newbie's point of view:
> We started using JSF with a little project this year and we really went
> through all this pains/problems, which caused the project almost to fail 
> at all...
> I think, it is not the common JSF or even the MyFaces documentation 
> responsible for that, but the lack of any documentation about the 
> interdependencies between all the different modules/implementations! The 
> JSF specification defines very flexible extension mechanism, e.g. the 
> chain of variable resolvers, and each of the modules uses them in its own 
> way, which results in situations, where plugging in a new module means to 
> break other functionality, you have just hardly managed to be working 
> correctly. And that does not happen only when using different libraries 
> but also within one library itself. So one configuration might be suitable 
> for the first component, but is definitely not for the next one. This 
> problem is hard to solve especially when several people working in 
> parallel on a library/module in a not really coordinated way!
> 
> So maybe it would be helpful, if beside any xdoc documentation providing 
> detailed information about a component there would be some kind of central 
> dependency matrix allowing each one to figure out which components work 
> together safely within a certain configuration scenario, e.g. server side 
> state handling etc.! Unfortunately, I guess, such a matrix cannot be 
> maintained by any interested user like the Wiki, since this requires a lot 
> of inside know how about the whole implementation.
> 
> BTW: Congratulations! I think, everyone of you does a great job within 
> this project!
> 
> Regards,
> CAK
> 
> 
> 

Reply via email to