Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: domain of mwessendorf@gmail.com
 designates 209.85.219.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=ThXNZ3oRxDShaROg8o7M8kZE1/xENYOGHACiWGDIIFbnVRV4k1K2KQFRvze82LQlU5
         pWW9ccZUObiJt95CjmpaIUkAB518rRac2OWvVRwUCbbMuJIC/784M8OzKsc+j3JvVxYl
         ZlefcMq18+TCFoIPB0IAm/+ke1eMiJVZaQyFY=
MIME-Version: 1.0
Sender: mwessendorf@gmail.com
In-Reply-To: <8f985b960904270836w7a0c8d55lf91e3b632e941b08@mail.gmail.com>
References: <49E85CDD.7000409@J4Fry.org> <49F599C0.407@J4Fry.org>
	 <gt49eb$m2s$1@ger.gmane.org>
	 <71235db40904270554v2103b8a5na1aa9a1117476b3f@mail.gmail.com>
	 <gt4ahu$r8t$1@ger.gmane.org>
	 <71235db40904270608g596cab6bm5775a66280220fcf@mail.gmail.com>
	 <49F5B06C.4040105@J4Fry.org>
	 <71235db40904270620s74b6724bp8d32c86f5c3b44a3@mail.gmail.com>
	 <71235db40904270625g7176a1c2l20a01dd64ea0e16e@mail.gmail.com>
	 <8f985b960904270836w7a0c8d55lf91e3b632e941b08@mail.gmail.com>
Date: Mon, 27 Apr 2009 17:42:26 +0200
Message-ID: <71235db40904270842x4c6d19e4gea75fde74a5dd961@mail.gmail.com>
Subject: Re: [VOTE] MyFaces 2.0 optimization options
From: Matthias Wessendorf <matzew@apache.org>
To: MyFaces Development <dev@myfaces.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 27, 2009 at 5:36 PM, Mike Kienenberger <mkienenb@gmail.com> wro=
te:
> Unfortunately, I don't have any knowledge about the ajax work you are
> all doing. However, I am -1 on anything that tries to intentionally
> break spec compatibility, such as reusing the f: namespace. =A0 Even if
> it's not explicitly spelled out, we know that it's against the spirit
> of the spec. =A0I find it impossible to believe that there are not
> better approaches. =A0 And the reality is that the actual tags used in
> the namespace are under the control of the user anyway. =A0 If someone
> wanted to map mfx: as f:, it's trivial to do so in both jsp and in

JSP is dead. All the new JSF 2.0 features don't work with JSP
(unless one goes ahead and provides an extension for that,
e.g an t:ajax handler for JSP)

-Matthias

> facelets. =A0 But why would we encourage that behavior?
>
>
> On Mon, Apr 27, 2009 at 9:25 AM, Matthias Wessendorf <matzew@apache.org> =
wrote:
>> ok, let's start with t:ajax
>>
>> We can always add a new JAR, for mfx:ajax...
>> But to get this started, I am fine with the following:
>>
>> 1.) +1
>> 2.) +1
>> 3.) -0
>> 4.) +1 (I will do that some when later)
>>
>> I think this now we have some kinda agreement, right ?
>>
>> On Mon, Apr 27, 2009 at 3:20 PM, Matthias Wessendorf <matzew@apache.org>=
 wrote:
>>> On Mon, Apr 27, 2009 at 3:17 PM, Ganesh <ganesh@j4fry.org> wrote:
>>>> Hi,
>>>>
>>>> The mf:ajax solution is the only one that completely breaks compatibil=
ity
>>>> with Mojarra. Applications using mf:ajax would simply fails on Mojarra=
. None
>>>
>>> not when that is an extra JAR, that is just shipped with the myfaces
>>> core release.
>>>
>>> -M
>>>
>>>> of solutions [1] to [3] would do so. Alex and me don't have a binding =
vote,
>>>> but it'll be us implementing this and we are both -1 on mf:ajax.
>>>>
>>>> mf:ajax is also worse than t:ajax because it doesn't bring myfaces
>>>> Javascript to Mojarra users. The Mojarra Javascript needs a lot of
>>>> improvement...
>>>>
>>>> Best Regards,
>>>> Ganesh
>>>>>
>>>>> -1 b/c that adds an odd dependency to tomahawk...
>>>>> mfx:xyz does make sense to be the home for myfaces core "improvements=
".
>>>>>
>>>>> -M
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>


--=20
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf