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
Hy Matthias ,
Well,
when I've uploaded your WAR file I get first this error :
Application error occurred during request processing.
Details:
java.lang.IllegalStateException: No Factories configured for this
Application. This happens if the faces-initialization does not work at all
Wendy Smoak schrieb:
On 8/18/06, Werner Punz [EMAIL PROTECTED] wrote:
Sorry I was not fully aware of that, I have been absent due
to health reasons for a while, until Gerald started
bugging me about the pending update.
I saw that-- you have my sympathies. :( If I had not been introduced
I started a small wiki page which should bring some order into the
component chaos:
http://wiki.apache.org/myfaces/ComponentMaintainers
this page should list the components after infrastructural category
and with the current core maintainer...
please add entries as you know them.
This will make
[
http://issues.apache.org/jira/browse/TOMAHAWK-579?page=comments#action_12429396
]
Christian Nolte commented on TOMAHAWK-579:
--
I am using the myfaces 1.1.3 implementation and get the same behaviour:
javax.servlet.ServletException:
Sorry but its been there all along.
Sean
On 8/20/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
Has this stuff been here all along and I somehow missed it when
looking for it, or was it added recently (in the last couple of
months)? I feel like a fool for not seeing it up to this point.
On
Hi All
Could you please throw some light regarding this below.
Thanks,
Girish
-Original Message-
From: Kumar, Girish
Sent: Thursday, August 17, 2006 12:06 PM
To: 'MyFaces Development'
Subject: Preserve Data Model
We have Application which used the PreserveDataModel = true
Do we want to list out who's responsible for components on the wiki?
It seems like ththis would encourage having people send email directly
an individual committer rather than the MyFaces community.
Once things are checked into the repository, we should all be
collectively responsible for the
On 8/21/06, Werner Punz [EMAIL PROTECTED] wrote:
Also after that we should think about deprecation of some of the
Tomahawk controls, we often have two controls doing the same
and now a third dojo based implementation which often is better
then ours.
We need to be careful about this. We have
Op ma, 21-08-2006 te 11:14 -0400, schreef Mike Kienenberger:
Do we want to list out who's responsible for components on the wiki?
It seems like ththis would encourage having people send email directly
an individual committer rather than the MyFaces community.
Hmm, good point.
Once things
Girish,
Please use the user mailing list. Thanks.
Dennis Byrne
-Original Message-
From: Kumar, Girish [mailto:[EMAIL PROTECTED]
Sent: Monday, August 21, 2006 09:31 AM
To: 'MyFaces Development'
Subject: Preserve Data Model
Hi All
Could you please throw some light regarding this
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
Jurgen Lust schrieb:
Op ma, 21-08-2006 te 11:14 -0400, schreef Mike Kienenberger:
Do we want to list out who's responsible for components on the wiki?
It seems like ththis would encourage having people send email directly
an individual committer rather than the MyFaces community.
Hmm, good
On 8/21/06, Werner Punz [EMAIL PROTECTED] wrote:
Jurgen Lust schrieb: Op ma, 21-08-2006 te 11:14 -0400, schreef Mike Kienenberger: Do we want to list out who's responsible for components on the wiki? It seems like ththis would encourage having people send email directly
an individual committer
Thanks for putting me already on the list, I will happily maintain the
partial Page Rendering Components after they are commited (which
should happen within the next days). I also very much appretiate the
Idea of having this List in the wiki.
So if I understood it correctly until some way of
Sorry, just noticed that there is already a newer post regarding this issue.
Still I would think that keeping track of for whom it is probably easiest to
test and fix a component seems like a good thing to do, or does
this somehow violate Apache policies or Apaches best practise?
(still somehow
On 8/21/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
Do we want to list out who's responsible for components on the wiki?
It seems like ththis would encourage having people send email directly
an individual committer rather than the MyFaces community.
I agree with Mike,
I saw the page this
On 8/21/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I get lot's of direct emails, I think Mike is right, that this can (orwill) increase the number of offline emails.You'd be amazed at how many personal Tomcat questions I still get, after not having worked on that project for several years,
Oh boy,
I belive that. I bet you also get lot's of stuff on Jakarta Commons.
:) and Struts ;)
On 8/21/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 8/21/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I get lot's of direct emails, I think Mike is right, that this can (or
will)
Ok valid points are risen, that it is not Apache like...
I think a vote on whether we keep the page or not
might be good...
as I said, I wanted to achieve a different purpose
for this, namely to have categorized which
components are dojoized, so that I have it easier
to test after dojo upgrades
I mean Mario and me talked about a thing like
fix 2 bugs a month. Also not really Apache, so why just
discussed stuff during a beer, or more ...
:)
On 8/21/06, Werner Punz [EMAIL PROTECTED] wrote:
Ok valid points are risen, that it is not Apache like...
I think a vote on whether we keep the
[ http://issues.apache.org/jira/browse/TOMAHAWK-441?page=all ]
Lance Frohman updated TOMAHAWK-441:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 1.1.5-SNAPSHOT
Resolution: Fixed
applied patches
Add orientation parameter
23 matches
Mail list logo
