Bharath,
It is fine to use the mailing list to respond directly to a person.
Sometimes, someone else may have the answer you were looking for and
chime in.
Yes, the fact that Tomahawk will have to wait for a new Core release is
discouraging. For now, I am using Tomahawk 1.1.4 with Core 1.1.5, built
locally so I have more control. I think Tomahawk 1.1.4 is pretty much
ready for production, so I would consider it pretty "safe" to use it
directly with the RI now. That's just my personal opinion after testing
it for a couple months (it hasn't changed in that time). We'll see what
some of the other users and devs have to say on that statement. :)
Aside from the release plans, really the best place to keep track of
release progress is the dev mailing list. You can easily search nabble
to find such threads, for example see [6].
[6]
http://www.nabble.com/MyFaces-1.1.5-Release-Status--tf2841335.html#a7933247
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Bharath Belagodu wrote:
> Jeff,
> I'm not addressing this email to the group,
>
> Yes, the website is working now.
> I read on the website that tomahawk 1.1.4 is going to be released in
> sync with Myfaces 1.1.5
>
> http://wiki.apache.org/myfaces/TomahawkRelease114
>
> The above wiki site mentions that the release of tomahawk is blocked
> till Myfaces 1.1.5 is released! Well, now I'll try to look at the
> roadmap of 1.1.5 but I read that it is TBD, if you know further
> information let me know. Thanks.
>
> -Bharath
>
> -----Original Message-----
> From: Jeff Bischoff [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 31, 2007 5:09 PM
> To: MyFaces Discussion
> Subject: Re: Javscript Issues with JSF 1.2, Tomahawk 1.1.3
>
> Bharath Belagodu wrote:
>> Jeff,
>> Appreciate the response.
>> Well, the website is not reachable at this time to download 1.1.4 but
> I
>
> Are you sure? I tried it just now. Hmm...
>
>> had an older copy of tomahawk 1.1.4 downloaded about 4wks ago, that
>> seemed to work with JSF 1.2. The basic problems with commandLink,
>> panelNavigation2 aren't occurring.
>>
>> Where can I find the differences between the two releases?
>
> [3] http://issues.apache.org/jira/browse/MYFACES
>
> There is almost SVN commit logs somewhere, not sure where.
>
>> When is
>> tomahawk 1.1.4 going to be released? Appreciate pointers to any URLs.
>>
>
> [4] http://svn.apache.org/repos/asf/myfaces/current/STATUS.txt
> [5] http://wiki.apache.org/myfaces/TomahawkRelease114
>
>> The problem went away but would be good to know what the problem is
> with
>> tomahawk 1.1.3! Thanks.
>>
>
> Hope you find it. :)
>
>> -Bharath
>>
>
> Regards,
>
> Jeff Bischoff
> Kenneth L Kurz & Associates, Inc.
>
>> -----Original Message-----
>> From: Jeff Bischoff [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, January 31, 2007 3:03 PM
>> To: MyFaces Discussion
>> Subject: Re: Javscript Issues with JSF 1.2, Tomahawk 1.1.3
>>
>> Bharath,
>>
>> Offhand, I can tell you there were some javascript changes to improve
>> compatibility since Tomahawk 1.1.3. Some of the devs like Martin would
>
>> know more on this. Just to narrow down which versions your problem is
>> affecting, can you also try with Tomahawk 1.1.4 rc from here [1] and
>> Tomahawk 1.1.5 nightly from here [2]?
>>
>> [1] http://people.apache.org/builds/myfaces/tomahawk-1.1.x/
>> [2] http://people.apache.org/builds/myfaces/nightly/
>>
>> Regards,
>>
>> Jeff Bischoff
>> Kenneth L Kurz & Associates, Inc.
>>
>> Bharath Belagodu wrote:
>>> Using JSF 1.2 with Tomahawk 1.1.3 is causing issues with several of
>> the
>>> components developed in our application. The dynamic menus and static
>>> menus developed using panelNavigation2 aren't working. There is
>>> javascript error detected. The javascript error is 'Object Expected'.
>>> So, I set to explore just a simple example of a commandLink.
>>>
>>>
>>>
>>> The below code has an error, I'm using the tomahawk's commandLink
>>> component.
>>>
>>>
>>>
>>> <t:commandLink action="welcome">
>>>
>>> <f:verbatim>› </f:verbatim>
>>>
>>> <t:outputText value="Test Client" />
>>>
>>> </t:commandLink>
>>>
>>>
>>>
>>> Changing the t:commandLink to h:commandLink works.
>>>
>>>
>>>
>>> Is tomahawk 1.1.3 not compatible with JSF 1.2? Previously we were
>> using
>>> myfaces-1.1.4 and it worked great.
>>>
>>>
>>>
>>>
>>>
>>> Also, another strange behavior with JSF 1.2 is that our xhtml files
>>> appear as raw files when being displayed in Mozilla browser, if I use
>> IE
>>> 6 or IE 7 there isn't an issue. This wasn't the case with
>> myfaces1.1.4.
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> -Bharath
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>
>
