You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mike Youngstrom (JIRA)" <de...@myfaces.apache.org> on 2006/05/05 16:59:27 UTC
[jira] Created: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Installing Tomahawk breaks jsf-ri commandLink and Button components
-------------------------------------------------------------------
Key: TOMAHAWK-416
URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
Project: MyFaces Tomahawk
Type: Bug
Versions: 1.1.3-SNAPSHOT
Reporter: Mike Youngstrom
Priority: Blocker
It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Mike Youngstrom (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12378075 ]
Mike Youngstrom commented on TOMAHAWK-416:
------------------------------------------
I did some looking around the dummyform stuff. Although I'm not sure exactly what that is I noticed a couple of places where comments were made that the dummy form couldn't be rendered in the RI. Perhaps finding out why those cannot be rendered in the RI might be one path to take....however I'm still not sure, assuming that problem could be fixed, that would be the best approach to take since these renderers overriding the implementations renderers may still have other unforseen impacts on other implementations.
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Mario Ivankovits (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412100 ]
Mario Ivankovits commented on TOMAHAWK-416:
-------------------------------------------
It should be sufficient to comment
<renderer>
<component-family>javax.faces.Command</component-family>
<renderer-type>javax.faces.Button</renderer-type>
<renderer-class>org.apache.myfaces.renderkit.html.jsf.DummyFormHtmlButtonRenderer</renderer-class>
</renderer>
<renderer>
<component-family>javax.faces.Command</component-family>
<renderer-type>javax.faces.Link</renderer-type>
<renderer-class>org.apache.myfaces.renderkit.html.jsf.DummyFormHtmlLinkRenderer</renderer-class>
</renderer>
You wrote tomahawk-1.1.1 and tomahawk 1.1.2 - eventually you mixed up the versions?
Could you please recheck.
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Mario Ivankovits (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=all ]
Mario Ivankovits resolved TOMAHAWK-416:
---------------------------------------
Fix Version: 1.1.3
Resolution: Fixed
disabled the dummyForm feature by default
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
> Fix For: 1.1.3
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Scott Moore (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412060 ]
Scott Moore commented on TOMAHAWK-416:
--------------------------------------
Mario,
As you suggested, I tried to remove the commandLink and commandButton renderer from Tomahawk's faces-config.xml, though I may not have done it correctly, since I can't get it to work.
I expanded tomahawk-1.1.2.jar and edited META-INF/faces-config.xml. I commented out these elements:
<renderer>
<component-family>javax.faces.Command</component-family>
<renderer-type>javax.faces.Button</renderer-type>
<renderer-class>org.apache.myfaces.renderkit.html.jsf.DummyFormHtmlButtonRenderer</renderer-class>
</renderer>
<renderer>
<component-family>javax.faces.Command</component-family>
<renderer-type>javax.faces.Link</renderer-type>
<renderer-class>org.apache.myfaces.renderkit.html.jsf.DummyFormHtmlLinkRenderer</renderer-class>
</renderer>
<renderer>
<component-family>javax.faces.Command</component-family>
<renderer-type>org.apache.myfaces.Button</renderer-type>
<renderer-class>org.apache.myfaces.renderkit.html.ext.HtmlButtonRenderer</renderer-class>
</renderer>
<renderer>
<component-family>javax.faces.Command</component-family>
<renderer-type>org.apache.myfaces.Link</renderer-type>
<renderer-class>org.apache.myfaces.renderkit.html.ext.HtmlLinkRenderer</renderer-class>
</renderer>
I then created a new Tomahawk jar (tomahawk-1.1.1a.jar) and deployed that with my web applications. So my application was using Sun's RI (jsf-api 1.1 and jsf-impl 1.1_01), and my modified Tomahawk 1.1.2 jar.
The small webapp that I created for trying out the Tree2 component seemed to work fine. However, I couldn't even load the login page of the webapp that I eventually would like to add the Tree2 component to. It failed with the ERROR:
ERROR http-8080-Processor23 StandardWrapper[/gm:Faces Servlet] - Servlet.service() for servlet Faces Servlet threw exception
java.lang.NoSuchMethodError: org.apache.myfaces.renderkit.html.util.DummyFormUtils.isWriteDummyForm(Ljavax/faces/context/FacesContext;)Z
I also tried the above, commenting out different elements:
- A faces-config.xml with the HtmlButtonRenderer and HtmlLinkRenderer commented out
- A faces-config.xml with the DummyFormHtmlButtonRenderer and DummyFormHtmlLinkRenderer commented out
Those attempts did not work, either.
Did I understand your suggested workaround correctly? Should I try something else?
Thanks,
Scott
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Mario Ivankovits (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412102 ]
Mario Ivankovits commented on TOMAHAWK-416:
-------------------------------------------
please lets discuss possible solutions to still have a dummyForm functionality even with RI on myfaces-dev. Topic: "Make DummyForm RI compatible"
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Martin Marinschek (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412061 ]
Martin Marinschek commented on TOMAHAWK-416:
--------------------------------------------
The problem is that t:commandLink is not compatible with the RI.
so fast fix:
- don't override the renderer
proper fix:
- make t:commandLink compatible with the RI
regards,
Martin
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Scott Moore (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412202 ]
Scott Moore commented on TOMAHAWK-416:
--------------------------------------
Mario,
Sorry, I mistyped the Tomahawk version in a previous comment. I have been working with Tomahawk 1.1.2, _not_ 1.1.1.
Another mistake I had made in a previous comment was saying that:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I also tried the above, commenting out different elements:
- A faces-config.xml with the HtmlButtonRenderer and HtmlLinkRenderer commented out
- A faces-config.xml with the DummyFormHtmlButtonRenderer and DummyFormHtmlLinkRenderer commented out
Those attempts did not work, either.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I had made an error when creating the jar for the second test mentioned (which is exactly the workaround you describe above). I corrected the error, and with your recommended workaround, now have my webapps running with Sun's RI plus Tomahawk. The existing webapp works normally, without any negative impact on the links and buttons as I saw before, and the small webapp I created to try out Tree2 seems to work fine as well.
Thanks for the workaround & I hope a permanent fix is coming soon.
I will monitor myfaces-dev for DummyForm information. I see you started a thread yesterday called "DummyForm stuff."
Regards,
Scott
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Mario Ivankovits (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412030 ]
Mario Ivankovits commented on TOMAHAWK-416:
-------------------------------------------
Unhappily the only chance I see is to remove the commandLink and commandButton renderer from tomahawks faces-config.xml
It turns out the way I tried to move the dummyForm stuff to tomahawk was a little bit to naive in the context of JSF-RI ....
what a sh*** ....
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Mike Kienenberger (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412043 ]
Mike Kienenberger commented on TOMAHAWK-416:
--------------------------------------------
Looks like this also breaks MyFaces Core (without tomahawk) too:
http://www.nabble.com/ExtensionsFilter-now-mandatory--p4325444.html
On 5/10/06, Jonathan Harley <jo...@parkplatz.net> wrote:
> Hi, I've been trying out MyFaces 1.1.3 after previously using 1.1.1.
>
> Everything went fine except that all my h:commandLinks stopped
> working, because they were generating onClick javascript which
> called clear_linkDummyForm, but the javascript method itself was
> not being generated.
>
> After a bit of a search on the JIRA, I tried adding in the
> Tomahawk ExtensionsFilter (from Tomahawk 1.1.2), and lo,
> clear_linkDummyForm() is added to pages which have the
> ExtensionsFilter mapped and not to pages which don't.
>
> Is it really the case that the ExtensionsFilter is now mandatory
> to make basic (non-extension) JSF features work, or am I missing
> some new bit of config?
>
> I assume it must be the latter, because if ExtensionsFilter was
> mandatory, why not just roll its functionality into the core MyFaces
> servlet?
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Mike Youngstrom (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12378074 ]
Mike Youngstrom commented on TOMAHAWK-416:
------------------------------------------
Sorry, I didn't mean to say that tomahawk would be unusable but that the RI becomes unusable when using the latest version of Tomahawk. :)
Ok, let me try again to be a little more clear. I think before I just wanted to get your attention. :)
So, I investigated the problem and found the problem is in the dummyform extended renderers that override the standard renderers in the tomahawk faces-config(line 413-425).
I'm not familiar with the tomahawk architecture so I don't really know why these dummy form renderers need to be here. However, I think the core of the problem is that in the JSF-RI the command renderer renders the clear function and in MyFaces it appears the form renders the clear function. Because of this when you use JSF-RI's form renderer and a Myfaces command renderer the clear forms javascript function used in the myfaces command renderer is never rendered so the <h:commandLink/> rendered doesn't work.
I'm not sure who's domain the problem lies in. I'm not familiar with the reasons for tomahawk overriding the core provider link renderkits. I'm sure there is a good reason. But, if tomahawk is going to be overriding the renderers of other implementation's that seems to me like it may be the source of may compatability problems with other implemenations in the future.
I hope that is a better bug description. :) Any ideas or input? I'm open to suggestions.
Mike
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (TOMAHAWK-416) Installing Tomahawk breaks jsf-ri
commandLink and Button components
Posted by "Scott Moore (JIRA)" <de...@myfaces.apache.org>.
[ http://issues.apache.org/jira/browse/TOMAHAWK-416?page=comments#action_12412027 ]
Scott Moore commented on TOMAHAWK-416:
--------------------------------------
I have seen the same issue described in this bug. I am using Sun's RI, and adding the Tomahawk 1.1.2 jar to the classpath of my webapp breaks all of the h:commandLink elements throughout my app.
It's definitely not the MyFacesExtensionsFilter either; I've narrowed it down to just the presence of the Tomahawk jar in my classpath causing the issue.
By any chance, is there a workaround for this issue?
Sorry I don't have any helpful info to provide. I'm going to get the latest Tomahawk code and see if I can either suppress the commandLink issue or extract the Tree2 code in some usable way (that's the Tomahawk component I was excited about using). If I discover anything that may help with this bug, I'll post a patch or a comment.
> Installing Tomahawk breaks jsf-ri commandLink and Button components
> -------------------------------------------------------------------
>
> Key: TOMAHAWK-416
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-416
> Project: MyFaces Tomahawk
> Type: Bug
> Components: Extended CommandLink/CommandButton, NavigationMenuItem
> Versions: 1.1.3-SNAPSHOT
> Reporter: Mike Youngstrom
> Priority: Blocker
>
> It appears that the extended Link and Button renderers added to the tomahawk faces-config break JSF-RI's ability to correctly render Links and buttons. This is a serious issue. Coming up soon will be the first solo tomahawk release which is supposed to help show tomahawk's independence from myfaces core. Yet this release will be completely unusable on the only other major jsf implementation out there. Let me know if there is something the RI can do to help fix this problem.
> Mike
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira