I've never worked on a project where developers make drastic API changes without first chatting with other committers, and then turning around and saying it's only partially done-- after committing it?
We could've told you up front that manually requiring event declaration is not practical:
<context-param>
<param-name>com.sun.faces.extensions.avatar.FacesEvents</param-name>
<param-value>
SuggestEvent:com.enverio.jsf.SuggestEvent:com.enverio.jsf.UISuggest
</param-value>
</context-param>
And creating a dependency between the component developer's naming scheme and the component user's web.xml
Enverio.SuggestEvent = function(clientId, phaseId) {
this.base = DynaFaces.FacesEvent;
this.base("SuggestEvent", clientId, phaseId);
}
>>>>>> On Mon, 07 Aug 2006 13:46:57 -0400, jacob_at_hookom.net said:
>
>JH> In the j1 demo, we followed the same convention as action events
>JH> (immediate), which was very simple to wire. The changes described
>JH> in the email require additional event artifacts and require each
>JH> event used for each component to be declared in the web.xml. Am I
>JH> correct?
>
>I suspect there is some misunderstanding here due to my implementation
>being incomplete and incompletely described. Can you please wait until
>I have a design review screencast before passing judgement or -gasp-
>talking about forking?
>
>Ed
>
>--
>| ed.burns_at_sun.com | {home: 407 869 9587, office: 408 884 9519 OR x31640}
>| homepage: | http://purl.oclc.org/NET/edburns/
>| aim: edburns0sunw | iim: ed.burns_at_sun.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe_at_jsf-extensions.dev.java.net
>For additional commands, e-mail: dev-help_at_jsf-extensions.dev.java.net
>