A more conservative approach would be to build an abstract base test case
that did the manual configuration operations (as you are doing them), for
the combination of components that you want to test, in its setUp() method.
Hmmm ... so AbstractJsfTestCase would be extended by
One might also have a look at the Trinidad RenderKit test framework,
which does a lot of work to make writing unit tests for renderers
oh so trivial, including parsing faces-config.xmls on the classpath.
http://wiki.apache.org/myfaces/Trinidad_RenderKit_test_framework
-- Adam
On 8/20/06,
From: "Dennis Byrne" [EMAIL PROTECTED] I would be suprised if you found a quick and easy way to do this. MyFaces core uses digester to unmarshal the config files. It then calls the API you mention. I would start digging around in org.apache.myfaces.config .
Or, another way would be to write
I am writing a unit test based on the Shale Test Framework for a Tomahawk
component. My current problem is the I need to add the default MyFaces and
Tomahawk components and renderers to the FacesContext. To date I have been
using facesContext.getApplication().addComponent(...) and
I would be suprised if you found a quick and easy way to do this. MyFaces core
uses digester to unmarshal the config files. It then calls the API you
mention. I would start digging around in org.apache.myfaces.config .
Dennis Byrne
-Original Message-
From: Paul Spencer [mailto:[EMAIL
On 8/20/06, Dennis Byrne [EMAIL PROTECTED] wrote:
I would be suprised if you found a quick and easy way to do this. MyFaces core uses digester to unmarshal the config files.It then calls the API you mention. I would start digging around in org.apache.myfaces.config .
One aggressive approach you
