Ok...
they moved the BUG to be SPEC specific, which means (to my understanding)
that this won't be solved in the near future. See the spec ticket here:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=662as there was no veto on using "trinidad", I committed it to the source;
There shouldn't be big issues with that ... and if they fix the behavior,
we can always change it and release note the issue, but I guess there
is almost on problem with that...
-Matthias
On Wed, Nov 4, 2009 at 11:54 AM, Matthias Wessendorf <
matzew@...> wrote:
> As there are some limitations (see TRINIDAD-1603) and picking an ugly one, like
>
> <faces-config>
>
> <name>
> org_apache_myfaces_trinidad
> </name>
> ...
>
> </faces-config>
>
> doesn't make much sense, what do folks think about picking a
> simplified version ?
>
> <faces-config>
> <name>
> trinidad
> </name>
> ...
> </faces-config>
>
> There shouldn't be much issues with "trinidad" as the (kinda) unique name...
>
> Thoughts ?
>
> -Matthias
>
>
> On Tue, Oct 20, 2009 at 7:04 PM, Andy Schwartz
> <
andy.g.schwartz@...> wrote:
>> Hey Matthias -
>>
>> I like "org.apache.myfaces.trinidad".
>>
>> Just out of curiosity I sent email to the EG to see what other folks
>> have done. I don't think we need to wait for that info, but I will
>> pass along any responses.
>>
>> Andy
>>
>
>
>
> --
> 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/mwessendorftwitter:
http://twitter.com/mwessendorf