Martin Cooper wrote:
Also, several of the existing MyFaces widgets are based on Prototype.
This *will* cause users problems when they deploy to a portal
environment, or when they try to use other libraries, or just other
Where is the problem with a portal deployment?
I do not see any more issues than the usual ones
you would have with any javascript.
JavaScript code in their pages.
You are referring to the Object bug which will be fixed
by the next version of prototype.
The main culprit of javascript itself is that it is such a
highly dynamic language that things like interfering scripts
can happen, and do happen.
(Perfect example the Prototyp object extension which broke
existing code, but is currently being fixed)
I've mentioned this before, but people
don't seem to have taken this seriously (or they just don't care, which
I hope isn't the case!).
Well those issues are taken seriously, but this is more a
problem of testing and fixing the stuff than trying to cover
it upfront, because you cannot really in javascript.
It is a problem you basically have to face in every
dynmically typed introspective scripting language.
Those problems are all the same no matter of being it smalltalk
ruby, javascript or whatever, interference problems
are very common in those languages which allow extensions and adjustment
and usually are covered by testing.
You might get similar issues on other levels with other libraries,
I do not see a specific problem with prototype as such,
the object extension problem is being fixed currently.
In the end I see the benefits of Prototype as being bigger
than the potential problems, which usually are addressed
very quickly by the developers.
The main benefit is very tight code, highly tested bugfree
base libraries, which are widely used by anyone using rails
and other frameworks.
But it is true that the prototype classes definitely need a namespace
prefix, that is the biggest problem I see with them as they are now.
Migrating those widgets to use the Oracle
framework, once it arrives, will almost certainly resolve these issues.
Well the main issue with the Tomahawk extensions and the ADF faces,
definitely is not the proto library, there are other non javascript
related issues to my knowledge, which have to be overcome.
