AW: [jira] Commented: (TOMAHAWK-194) Wrong entry in AddRessource.properties causes Error-message

2006-08-11 Thread Schaal, Roland
Maybe you could write your comment to the open issue http://issues.apache.org/jira/browse/TOMAHAWK-15 so that somebody tries to fix it :) As it seems to be a maven-issue (http://www.mail-archive.com/users@myfaces.apache.org/msg20394.html) I don´t know how to do this... -Ursprüngliche

[jira] Commented: (TOMAHAWK-590) Unparsable lastModified : @lastModified@ should be no ERROR

2006-08-11 Thread Roland Schaal (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-590?page=comments#action_12427466 ] Roland Schaal commented on TOMAHAWK-590: Could it be even set to DEBUG-level as it should not affect anything mentioned in here

[jira] Created: (TOMAHAWK-592) panelTabbedPane: Duplicate class attributes

2006-08-11 Thread John Singleton (JIRA)
panelTabbedPane: Duplicate class attributes --- Key: TOMAHAWK-592 URL: http://issues.apache.org/jira/browse/TOMAHAWK-592 Project: MyFaces Tomahawk Issue Type: Bug Affects Versions: 1.1.3

[jira] Created: (MYFACES-1384) After switch from myfaces-impl-1.1.3 (release) to myfaces-1.1.5-SNAPSHOT, javascript throw error 'Object expected'

2006-08-11 Thread Serg Maslyukov (http://webmill.askmore.info) (JIRA)
After switch from myfaces-impl-1.1.3 (release) to myfaces-1.1.5-SNAPSHOT, javascript throw error 'Object expected' -- Key: MYFACES-1384 URL:

[jira] Updated: (TOMAHAWK-523) rowStyleClass does not resolve to an EL of var

2006-08-11 Thread JIRA
[ http://issues.apache.org/jira/browse/TOMAHAWK-523?page=all ] Ronald Müller updated TOMAHAWK-523: --- Status: Patch Available (was: Open) rowStyleClass does not resolve to an EL of var --

[jira] Commented: (TOMAHAWK-523) rowStyleClass does not resolve to an EL of var

2006-08-11 Thread Steve Rees (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-523?page=comments#action_12427511 ] Steve Rees commented on TOMAHAWK-523: - I believe that there are two problems (at least in the 1.1.3 version of tomahawk) in the renderer for the extended

tree2 component retains its state after sessin invaldation

2006-08-11 Thread Saama
I am using tree2 component as navigator in my application. The code is as follows: t:tree2 id=navMenu value=#{NavigationTreeHandler.expandedTreeData}

[jira] Commented: (TOMAHAWK-523) rowStyleClass does not resolve to an EL of var

2006-08-11 Thread JIRA
[ http://issues.apache.org/jira/browse/TOMAHAWK-523?page=comments#action_12427515 ] Ronald Müller commented on TOMAHAWK-523: no success on older releases :( its quit complicated to run the sources, especially the old versions. there

[jira] Created: (TOMAHAWK-594) When i use StreamingAddResource and put calendar componente in tabbed panel, the css styles is not added

2006-08-11 Thread JIRA
When i use StreamingAddResource and put calendar componente in tabbed panel, the css styles is not added Key: TOMAHAWK-594 URL:

[jira] Created: (TOMAHAWK-593) When i use StreamingAddResource and put calendar componente in tabbed panel, the css styles is not added

2006-08-11 Thread JIRA
When i use StreamingAddResource and put calendar componente in tabbed panel, the css styles is not added Key: TOMAHAWK-593 URL:

[jira] Created: (TOMAHAWK-595) When i use StreamingAddResource and put calendar componente in tabbed panel, the css styles is not added

2006-08-11 Thread JIRA
When i use StreamingAddResource and put calendar componente in tabbed panel, the css styles is not added Key: TOMAHAWK-595 URL:

Re: [jira] Commented: (TOMAHAWK-194) Wrong entry in AddRessource.properties causes Error-message

2006-08-11 Thread Mike Kienenberger
On 8/11/06, Schaal, Roland [EMAIL PROTECTED] wrote: Maybe you could write your comment to the open issue http://issues.apache.org/jira/browse/TOMAHAWK-15 so that somebody tries to fix it :) As it seems to be a maven-issue (http://www.mail-archive.com/users@myfaces.apache.org/msg20394.html) I

[jira] Updated: (TOMAHAWK-523) rowStyleClass does not resolve to an EL of var

2006-08-11 Thread Mike Kienenberger (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-523?page=all ] Mike Kienenberger updated TOMAHAWK-523: --- Status: Open (was: Patch Available) rowStyleClass does not resolve to an EL of var --

[jira] Commented: (TOMAHAWK-523) rowStyleClass does not resolve to an EL of var

2006-08-11 Thread Mike Kienenberger (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-523?page=comments#action_12427535 ] Mike Kienenberger commented on TOMAHAWK-523: Ronald, I appreciate the attempt, but there's more to fixing this issue than simply changing those

[jira] Commented: (TOMAHAWK-592) panelTabbedPane: Duplicate class attributes

2006-08-11 Thread Mike Kienenberger (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-592?page=comments#action_12427537 ] Mike Kienenberger commented on TOMAHAWK-592: John, Sounds like you've made good progress tracking this down. Can you submit a patch? Maybe remove

[jira] Commented: (TOMAHAWK-593) When i use StreamingAddResource and put calendar componente in tabbed panel, the css styles is not added

2006-08-11 Thread Mario Ivankovits (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-593?page=comments#action_12427554 ] Mario Ivankovits commented on TOMAHAWK-593: --- I'll have a look at it after my vacation (which ends soon), though, I can do it only in an JSP

[jira] Commented: (TOMAHAWK-579) java.lang.IllegalStateException: getOutputStream() has already been called for this response error using the RI 1.2_01 and Tomahawk 1.1.3

2006-08-11 Thread Veit Guna (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-579?page=comments#action_12427601 ] Veit Guna commented on TOMAHAWK-579: I've got the same problem. java.lang.IllegalStateException: getOutputStream() has already been called for this

[jira] Commented: (TOMAHAWK-579) java.lang.IllegalStateException: getOutputStream() has already been called for this response error using the RI 1.2_01 and Tomahawk 1.1.3

2006-08-11 Thread Mike Kienenberger (JIRA)
[ http://issues.apache.org/jira/browse/TOMAHAWK-579?page=comments#action_12427605 ] Mike Kienenberger commented on TOMAHAWK-579: Because Tomahawk is written against JSF 1.1, I'm not sure if anyone has tested this against 1.2. If

Fwd: Heads Up on Shale Test Framework API Change

2006-08-11 Thread Matthias Wessendorf
forward b/c of cross-posting ;) -- Forwarded message -- From: Matthias Wessendorf [EMAIL PROTECTED] Date: Aug 11, 2006 4:24 PM Subject: Re: Heads Up on Shale Test Framework API Change To: adffaces-dev@incubator.apache.org see inline On 8/11/06, Craig McClanahan [EMAIL

Re: Heads Up on Shale Test Framework API Change

2006-08-11 Thread Mike Kienenberger
Speaking of breakage, there's a Java 1.5 method dependency in the 1.0.3-snapshot, which is causing MyFaces to fail to build with testing enabled (the default) under Java 1.4. https://issues.apache.org/struts/browse/SHALE-251 It'd be great if we could get this fixed at the same time. It'd

Re: Heads Up on Shale Test Framework API Change

2006-08-11 Thread Dennis Byrne
Perhaps we can also get mvn to enforce this in local development as well? Mike, Did you mean 1.1.3 snap ? Dennis Byrne -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Friday, August 11, 2006 07:46 PM To: 'MyFaces Development' Cc: 'Craig McClanahan' Subject:

Re: Heads Up on Shale Test Framework API Change

2006-08-11 Thread Mike Kienenberger
No, it's a Java 1.5 method that snuck into Shale Test 1.0.3-snapshot. I should have been more clear about that. https://issues.apache.org/struts/browse/SHALE-251 But yeah, that would be good for us as well. On 8/11/06, Dennis Byrne [EMAIL PROTECTED] wrote: Perhaps we can also get mvn to

Re: Heads Up on Shale Test Framework API Change

2006-08-11 Thread Mike Kienenberger
And it's only failing for one of the Tomahawk tests, so it's not really a MyFaces core test that's failing (as far as I can tell). But still I checked out Shale Test, located all the dependencies, and created a patch. As far as I can tell, it's the only problem in the codebase. Eclipse

Heads Up on Shale Test Framework API Change

2006-08-11 Thread Craig McClanahan
We're looking at implementing a suggestion[1] to change the API on the setUp() and tearDown() methods of org.apache.shale.test.base.AbstractJsfTestCase, to add throws Exception to the method signatures. The primary goal is to be consistent with the underlying TestCase class from JUnit 3.8.1, and

Re: Heads Up on Shale Test Framework API Change

2006-08-11 Thread Mike Kienenberger
On 8/11/06, Craig McClanahan [EMAIL PROTECTED] wrote: We're looking at implementing a suggestion[1] to change the API on the setUp() and tearDown() methods of org.apache.shale.test.base.AbstractJsfTestCase, to add throws Exception to the method signatures. The primary goal is to be consistent