On 7/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
I can tell you from years of painful experience, supporting some JSP tag
libraries that rendered complex output, that the golden file approach can be
really fragile and I'd never do it again :-). The problem we had is two
fold:
* Some changes that are innocuous in their effect on the runtime
(such as changing the order of attributes generated in an element)
will still break the golden file. False positive error reports are never
a productivity enhancer :-).
* If you deliberately change the output of a component, the tendency
of the developer is to just re-record the entire golden file, and forget
to examine whether some other bug was introduced (such as omitting
a child element or something). We found ourselves introducing
new errors when this occurred, which kind of defeats the purpose.
*snip*
This means that we are not testing the order in which attributes are
written, which we shouldn't be testing, since order doesn't mean
anything.
(http://wiki.apache.org/myfaces/Trinidad_RenderKit_test_framework)
Deliberately releasing components that don't work with the RI does not seem
like something that will increase the market acceptance of MyFaces
components. Instead, this would create (or increase) a perception that
MyFaces developers are not interested in compatibility. Also, given the
right.
fact that the RI has a 1.2 version available and MyFaces doesn't yet, it
seems likely to give people a reason to consider switching away.
Nope.
Not every company is going to *swtich* to Java EE 5 only because it is
now released. From what I learned at my last job is, that big
companies are going to have *solid* base for their technology stack. I
also know from a friend that they recently switched away from Java EE
1.2 to Java EE 1.4 (or from 2 -> 4, what ever the real name is...).
For usecase like "I have this unused webapp with five pages or six" I
think it is ok to switch to a *newer* technology stack (java ee 5).
But big companies, don't like to play a paying beta-tester. But the
last year showed that lot's of these *fast* apps are developed with
Rails etc.
For MyFaces, we started right now the development of JavaServer Faces
1.2 and asked for a TCK.
-Matthias
The best approach is to make the build system so powerful that running your
entire test suite against either the MyFaces or RI implementations is a
single command line parameter. Wendy's already done that for Shale (so we
have no excuses for the framework not supporting both :-), and I'm sure it
can be done for the component libraries too.
> Ciao,
> Mario
>
>
Craig
--
Matthias Wessendorf
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
