[jira] Created: (TOMAHAWK-1174) broken pipe message when ExtensionsFilter is serving resources to Internet Explorer

broken pipe message when ExtensionsFilter is serving resources to Internet Explorer --- Key: TOMAHAWK-1174 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1174

Re: svn commit: r610323 - in /myfaces/tomahawk/trunk/core/src/main/java/org/apache/myfaces/renderkit/html/util: DefaultAddResource.java MyFacesResourceLoader.java ResourceLoader.java

Hi Simon! public void serveResource(ServletContext context, HttpServletRequest request, -HttpServletResponse response, String resourceUri) throws IOException; +HttpServletResponse response, String resourceUri) +throws IOException, ClosedSocketException;

Re: [Vote] MyFaces site design

Hello It appears the the 4 sample is more appreciated than others. So we will try to put the 4 layout on the Maven :) We will also modify the Apache banner accordingly. Thanks for your help :) Have a nice day ! Adonis On 1/9/08, Matthias Wessendorf [EMAIL PROTECTED] wrote: yah, that will be

[jira] Created: (TOBAGO-586) tc:panel, tc:box, and maybe tc:sheet change attribute or facet

tc:panel, tc:box, and maybe tc:sheet change attribute or facet -- Key: TOBAGO-586 URL: https://issues.apache.org/jira/browse/TOBAGO-586 Project: MyFaces Tobago Issue Type: New

[jira] Created: (TRINIDAD-889) inputDate day light saving bug

inputDate day light saving bug -- Key: TRINIDAD-889 URL: https://issues.apache.org/jira/browse/TRINIDAD-889 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions:

jira: resolved versus closed status

Hi All, I see that there are quite a few issues in JIRA marked as resolved. The status of resolved means that the developer thinks it is now fixed, and is waiting for either the person who raised the request or the QA department to check it and then close the issue. If you fix an issue, and

Re: jira: resolved versus closed status

Common practice in the past was that the release manager sets all resolved issues to closed after the release is out. --Manfred On 1/9/08, Simon Kitching [EMAIL PROTECTED] wrote: Hi All, I see that there are quite a few issues in JIRA marked as resolved. The status of resolved means that

[jira] Commented: (TRINIDAD-768) improved support for sortable properties

[ https://issues.apache.org/jira/browse/TRINIDAD-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12557281#action_12557281 ] Luka Surija commented on TRINIDAD-768: -- still doesn't work in this case :

Re: jira: resolved versus closed status

+1 I do the same for Trinidad On Jan 9, 2008 5:54 AM, Manfred Geiler [EMAIL PROTECTED] wrote: Common practice in the past was that the release manager sets all resolved issues to closed after the release is out. --Manfred On 1/9/08, Simon Kitching [EMAIL PROTECTED] wrote: Hi All, I

[jira] Created: (TOBAGO-587) Suggest on tc:in has wrong postion if used in tc:sheet that is rendered with scrollbar

Suggest on tc:in has wrong postion if used in tc:sheet that is rendered with scrollbar Key: TOBAGO-587 URL: https://issues.apache.org/jira/browse/TOBAGO-587

[jira] Created: (TOBAGO-588) Ajax timeout is hardcoded

Ajax timeout is hardcoded - Key: TOBAGO-588 URL: https://issues.apache.org/jira/browse/TOBAGO-588 Project: MyFaces Tobago Issue Type: Bug Affects Versions: 1.0.12 Reporter: Benjamin Jacob Ajax

Re: jira: resolved versus closed status

This seems to be a fairly large task for the release manager to do - or is there an easy way to do a bulk change of jira statuses? And what exactly is the benefit? Isn't it just as easy to get a list of closed issues with fix-version=x.y.z as it is to get a list of resolved issues? Cheers,

[jira] Commented: (TOBAGO-587) Suggest on tc:in has wrong postion if used in tc:sheet that is rendered with scrollbar

[ https://issues.apache.org/jira/browse/TOBAGO-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12557295#action_12557295 ] Volker Weber commented on TOBAGO-587: - which version of tobago? the underlying

[jira] Created: (TOBAGO-589) Print pages

Print pages --- Key: TOBAGO-589 URL: https://issues.apache.org/jira/browse/TOBAGO-589 Project: MyFaces Tobago Issue Type: New Feature Reporter: Benjamin Jacob We need a possibility to print displayed Data in an easy

Re: jira: resolved versus closed status

2008/1/9, Simon Kitching [EMAIL PROTECTED]: This seems to be a fairly large task for the release manager to do - or is there an easy way to do a bulk change of jira statuses? Yep: Select all the issues that have been resolved with the desired Fix version, Bulk change, transition through

Re: [Vote] MyFaces site design

I like the rounded corners and separation of #4. +1 for #4 Paul Spencer Catalin Kormos wrote: Hi, The latest designs provided by Adonis are available now at [1]; we think it would be better to do a voting on these, as there are several versions that he came up with, all quite great. Please

Taglibdoc documentation is missing for Core 1.1 and Core 1.2 projects

The Taglibdoc documentation report is missing the API and Impl subprojects of the Core 1.1 and Core 1.2 projects. The documentation may be missing from other subprojects, I have not checked :( Paul Spencer

Re: [Vote] MyFaces site design

+1 for #4 But why #1 has a search on the top and #2, #3 and #4 do not? This button works? Leonardo Uribe

Re: Taglibdoc documentation is missing for Core 1.1 and Core 1.2 projects

Hi Paul, Paul Spencer [EMAIL PROTECTED] schrieb: The Taglibdoc documentation report is missing the API and Impl subprojects of the Core 1.1 and Core 1.2 projects. The documentation may be missing from other subprojects, I have not checked :( What Taglibdoc report do you mean? I

Re: jira: resolved versus closed status

On Jan 9, 2008 7:40 AM, Simon Kitching [EMAIL PROTECTED] wrote: This seems to be a fairly large task for the release manager to do - or is there an easy way to do a bulk change of jira statuses? there is a bulk task, yes. And what exactly is the benefit? Isn't it just as easy to get a list

[jira] Created: (TRINIDAD-890) trinidad-demo fails to run in jetty

trinidad-demo fails to run in jetty --- Key: TRINIDAD-890 URL: https://issues.apache.org/jira/browse/TRINIDAD-890 Project: MyFaces Trinidad Issue Type: Bug Components: Build Affects Versions:

[jira] Commented: (TOBAGO-587) Suggest on tc:in has wrong postion if used in tc:sheet that is rendered with scrollbar

[ https://issues.apache.org/jira/browse/TOBAGO-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12557328#action_12557328 ] Benjamin Jacob commented on TOBAGO-587: --- 1.0.11 and 1.0.12 didn't already tested with

Re: Taglibdoc documentation is missing for Core 1.1 and Core 1.2 projects

Simon, I was looking for the tlddocs in Project Reports, which is where they have been in the past. Tomahawk still has them in Project Reports [1]. Paul Spencer [1] http://myfaces.apache.org/tomahawk/project-reports.html Simon Kitching wrote: Hi Paul, Paul Spencer [EMAIL PROTECTED]

Re: svn commit: r610323 - in /myfaces/tomahawk/trunk/core/src/main/java/org/apache/myfaces/renderkit/html/util: DefaultAddResource.java MyFacesResourceLoader.java ResourceLoader.java

On Wed, 2008-01-09 at 10:56 +0100, Mario Ivankovits wrote: Hi Simon! public void serveResource(ServletContext context, HttpServletRequest request, -HttpServletResponse response, String resourceUri) throws IOException; +HttpServletResponse response, String

[jira] Commented: (TRINIDAD-890) trinidad-demo fails to run in jetty

[ https://issues.apache.org/jira/browse/TRINIDAD-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12557382#action_12557382 ] Matthias Weßendorf commented on TRINIDAD-890: - looks like only true with

[jira] Created: (TRINIDAD-891) Locking issues coming from restore state

Locking issues coming from restore state - Key: TRINIDAD-891 URL: https://issues.apache.org/jira/browse/TRINIDAD-891 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.4-core

[jira] Resolved: (TRINIDAD-854) Double check for isListKey in org.apache.myfaces.trinidad.bean.FacesBeanImpl

[ https://issues.apache.org/jira/browse/TRINIDAD-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-854. - Resolution: Fixed Fix Version/s: 1.2.5-core

[Trinidad] trunk and release

Hi, as I am about to prepare the bits for the 1.x.5 releases of Trinidad, I updated already the trunks to say 1.x.6-SNAPSHOT. I also added a new version to JIRA. Are there any open bugs, you want in the release ? Tonight, I'll run the build-scripts to provide the bits for the vote. Thx,

[core] TestCase: LifecycleImplCactus

Hi, does one know how-to execute this test-class LifecycleImplCactus. I thought that cargo etc. were able to run those kind of container-based tests during the regular build. thx, Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions:

[testing] cargo / cactus ...

Hi, someone wrote a (JUnit/TestNG) for a PhaseListener ? Shale's MockLifecycle.execute/render aren't doing anything, for some reasons. So I just wonder what folks do for testing PhaseListeners. -M -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions:

[jira] Commented: (TRINIDAD-888) Add support for tabindex to focusable components

[ https://issues.apache.org/jira/browse/TRINIDAD-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12557544#action_12557544 ] Sandeep Manepalli Gururaj commented on TRINIDAD-888: I guess the code