[jira] [Commented] (TRINIDAD-2527) Row selection retains with tr:table

[ramya (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463089#comment-16463089
 ] 

ramya commented on TRINIDAD-2527:
-

we are still facing this issue in JSF 2.2.0 .  Not only row selection we  are 
facing the radio selection also , Could you please provide either patch or 
solution

> Row selection retains with tr:table
> ---
>
> Key: TRINIDAD-2527
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2527
> Project: MyFaces Trinidad
>  Issue Type: Bug
>  Components: Archetype
>Affects Versions: 2.1.1-core
> Environment: Windows 7, Java 7
>Reporter: Deepan
>Priority: Major
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> A page contains  with rowSelection as "Single/Multiple" and the 
> beans are session scoped. 
> - Select a row using the radio or checkbox
> - Navigate to some other pages
> - Again come back to page 1. Now, previously selected radio or checkbox are 
> selected. 
> {code:title=Sample code|borderStyle=solid}
>  rowSelection="single"
> value="#{myBean.myList}"
> var="groups" varStatus="rowId" rowBandingInterval="1" 
> verticalGridVisible="true"
> selectionListener="#{myBackingBean.myRowSelectListener}">
> ...
> ...
> 
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

test has been moved to https://gitbox.apache.org/repos/asf/myfaces-test.git and 
https://github.com/apache/myfaces-test

[jira] [Deleted] (MFHTML5-21) I'm not sure if I can make it to the meeting tonight but I will be there in the morning to see how you are doing and if you want to come by and see you tomorrow at lefty

[Leonardo Uribe (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MFHTML5-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leonardo Uribe deleted MFHTML5-21:
--


> I'm not sure if I can make it to the meeting tonight but I will be there in 
> the morning to see how you are doing and if you want to come by and see you 
> tomorrow at lefty from perths pad and
> -
>
> Key: MFHTML5-21
> URL: https://issues.apache.org/jira/browse/MFHTML5-21
> Project: MyFaces HTML5 Component Library
>  Issue Type: New Feature
>Reporter: Andrew andalon
>Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MYFACES-4228) File Descriptor leak in DefaultFaceletFactory

[Peter Rainer (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462848#comment-16462848
 ] 

Peter Rainer commented on MYFACES-4228:
---

Just added a patch, hope that helps :) 

> File Descriptor leak in DefaultFaceletFactory
> -
>
> Key: MYFACES-4228
> URL: https://issues.apache.org/jira/browse/MYFACES-4228
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.12
> Environment: CentOS 7
>Reporter: Peter Rainer
>Priority: Major
> Fix For: 2.2.13, 2.3.2
>
> Attachments: 
> _MYFACES_4228__closing_URLConnection_in_needsToBeRefreshed__.patch
>
>
> URLConnection opened in line 346 of DefaultFaceletFactory.java is never closed
>  
>  
> {code:java}
> try
> {
> URLConnection conn = facelet.getSource().openConnection();
> long lastModified = ResourceLoaderUtils.getResourceLastModified(conn);
> return lastModified == 0 || lastModified > target;
> }
> catch (IOException e)
> {
> throw new FaceletException("Error Checking Last Modified for " + 
> facelet.getAlias(), e);
> }
> {code}
>  
> While this usually isn't an issue in most production environments, because 
> the javax.faces.FACELETS_REFRESH_PERIOD is set either -1 or a high value, 
> this can cause unexpected side effects in both test and hot-deploy production 
> environments.
>  
> The result of this issue is that every time the lastModified for a composite 
> component is checked, the composite component file descriptor does stay open 
> - on my test environment we did have 500k open file descriptors for composite 
> component xhtml files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MFHTML5-21) I'm not sure if I can make it to the meeting tonight but I will be there in the morning to see how you are doing and if you want to come by and see you tomorrow at lefty

[Andrew andalon (JIRA)]

Andrew andalon created MFHTML5-21:
-

 Summary: I'm not sure if I can make it to the meeting tonight but 
I will be there in the morning to see how you are doing and if you want to come 
by and see you tomorrow at lefty from perths pad and
 Key: MFHTML5-21
 URL: https://issues.apache.org/jira/browse/MFHTML5-21
 Project: MyFaces HTML5 Component Library
  Issue Type: New Feature
Reporter: Andrew andalon






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MYFACES-4228) File Descriptor leak in DefaultFaceletFactory

[Peter Rainer (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462805#comment-16462805
 ] 

Peter Rainer commented on MYFACES-4228:
---

I will create one later today

> File Descriptor leak in DefaultFaceletFactory
> -
>
> Key: MYFACES-4228
> URL: https://issues.apache.org/jira/browse/MYFACES-4228
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.12
> Environment: CentOS 7
>Reporter: Peter Rainer
>Priority: Major
> Fix For: 2.2.13, 2.3.2
>
>
> URLConnection opened in line 346 of DefaultFaceletFactory.java is never closed
>  
>  
> {code:java}
> try
> {
> URLConnection conn = facelet.getSource().openConnection();
> long lastModified = ResourceLoaderUtils.getResourceLastModified(conn);
> return lastModified == 0 || lastModified > target;
> }
> catch (IOException e)
> {
> throw new FaceletException("Error Checking Last Modified for " + 
> facelet.getAlias(), e);
> }
> {code}
>  
> While this usually isn't an issue in most production environments, because 
> the javax.faces.FACELETS_REFRESH_PERIOD is set either -1 or a high value, 
> this can cause unexpected side effects in both test and hot-deploy production 
> environments.
>  
> The result of this issue is that every time the lastModified for a composite 
> component is checked, the composite component file descriptor does stay open 
> - on my test environment we did have 500k open file descriptors for composite 
> component xhtml files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MYFACES-4228) File Descriptor leak in DefaultFaceletFactory

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462804#comment-16462804
 ] 

Thomas Andraschko commented on MYFACES-4228:


A patch would be great!

> File Descriptor leak in DefaultFaceletFactory
> -
>
> Key: MYFACES-4228
> URL: https://issues.apache.org/jira/browse/MYFACES-4228
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.12
> Environment: CentOS 7
>Reporter: Peter Rainer
>Priority: Major
> Fix For: 2.2.13, 2.3.2
>
>
> URLConnection opened in line 346 of DefaultFaceletFactory.java is never closed
>  
>  
> {code:java}
> try
> {
> URLConnection conn = facelet.getSource().openConnection();
> long lastModified = ResourceLoaderUtils.getResourceLastModified(conn);
> return lastModified == 0 || lastModified > target;
> }
> catch (IOException e)
> {
> throw new FaceletException("Error Checking Last Modified for " + 
> facelet.getAlias(), e);
> }
> {code}
>  
> While this usually isn't an issue in most production environments, because 
> the javax.faces.FACELETS_REFRESH_PERIOD is set either -1 or a high value, 
> this can cause unexpected side effects in both test and hot-deploy production 
> environments.
>  
> The result of this issue is that every time the lastModified for a composite 
> component is checked, the composite component file descriptor does stay open 
> - on my test environment we did have 500k open file descriptors for composite 
> component xhtml files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MYFACES-4228) File Descriptor leak in DefaultFaceletFactory

[Peter Rainer (JIRA)]

Peter Rainer created MYFACES-4228:
-

 Summary: File Descriptor leak in DefaultFaceletFactory
 Key: MYFACES-4228
 URL: https://issues.apache.org/jira/browse/MYFACES-4228
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.2.12
 Environment: CentOS 7
Reporter: Peter Rainer


URLConnection opened in line 346 of DefaultFaceletFactory.java is never closed

 

 
{code:java}
try
{
URLConnection conn = facelet.getSource().openConnection();
long lastModified = ResourceLoaderUtils.getResourceLastModified(conn);

return lastModified == 0 || lastModified > target;
}
catch (IOException e)
{
throw new FaceletException("Error Checking Last Modified for " + 
facelet.getAlias(), e);
}

{code}
 

While this usually isn't an issue in most production environments, because the 
javax.faces.FACELETS_REFRESH_PERIOD is set either -1 or a high value, this can 
cause unexpected side effects in both test and hot-deploy production 
environments.

 

The result of this issue is that every time the lastModified for a composite 
component is checked, the composite component file descriptor does stay open - 
on my test environment we did have 500k open file descriptors for composite 
component xhtml files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [ANNOUNCE] MyFaces Core v2.3.1 Release

[Mike Kienenberger]

For future announcements we should consider adding a one-line
description of JSF.  For example:

   The Apache MyFaces team is pleased to announce the release of
MyFaces Core 2.3.1.

   MyFaces Core is a JavaServer(tm) Faces 2.3 implementation as
specified by JSR-372.

+ JavaServer Faces (JSF) is a Java specification for building
component-based user interfaces for web applications.

   MyFaces Core 2.3.1 is available in both binary and source distributions.

On Thu, May 3, 2018 at 9:57 AM, Eduardo B  wrote:
> The Apache MyFaces team is pleased to announce the release of MyFaces Core
> 2.3.1.
>
> MyFaces Core is a JavaServer(tm) Faces 2.3 implementation as specified by
> JSR-372.
>
> MyFaces Core 2.3.1 is available in both binary and source distributions.
>
> * http://myfaces.apache.org/download.html
>
> MyFaces Core is also available in the central Maven repository under Group
> ID "org.apache.myfaces.core".
>
> Release Notes - MyFaces Core - Version 2.3.1 can be found in the following
> link:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12342790
>
> Regards,
> Eduardo M. Breijo

[ANNOUNCE] MyFaces Core v2.3.1 Release

[Eduardo B]

The Apache MyFaces team is pleased to announce the release of MyFaces Core
2.3.1.

MyFaces Core is a JavaServer(tm) Faces 2.3 implementation as specified by
JSR-372.

MyFaces Core 2.3.1 is available in both binary and source distributions.

* http://myfaces.apache.org/download.html

MyFaces Core is also available in the central Maven repository under Group
ID "org.apache.myfaces.core".

Release Notes - MyFaces Core - Version 2.3.1 can be found in the following
link:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600=12342790

Regards,
Eduardo M. Breijo

[jira] [Commented] (TOBAGO-1896) 2nd AJAX will fail with JSF 2.3: IllegalArgumentException: Illegal base64 character a

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462427#comment-16462427
 ] 

Hudson commented on TOBAGO-1896:


SUCCESS: Integrated in Jenkins build Tobago Trunk #1416 (See 
[https://builds.apache.org/job/Tobago%20Trunk/1416/])
TOBAGO-1896: 2nd AJAX will fail with JSF 2.3: IllegalArgumentException: 
(lofwyr: rev 08826a2e52634293e02cde668324016fcad3862e)
* (edit) 
tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/js/tobago-jsf.js


> 2nd AJAX will fail with JSF 2.3: IllegalArgumentException: Illegal base64 
> character a
> -
>
> Key: TOBAGO-1896
> URL: https://issues.apache.org/jira/browse/TOBAGO-1896
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Themes
>Affects Versions: 4.2.0
> Environment: JSF 2.3
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Major
> Fix For: 4.2.1
>
>
> The "a" in the exception message is a hex value from a "LINE FEED" inserted 
> from an additional #text node  from the AJAX response since TOBAGO-1887



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (MYFACES-4223) FacesContext ViewRoot is Null - in JSF1.1.9

[Thomas Andraschko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYFACES-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko resolved MYFACES-4223.

Resolution: Incomplete

> FacesContext ViewRoot is Null - in JSF1.1.9
> ---
>
> Key: MYFACES-4223
> URL: https://issues.apache.org/jira/browse/MYFACES-4223
> Project: MyFaces Core
>  Issue Type: Bug
> Environment: Production
>Reporter: Venkatesh
>Priority: Critical
> Attachments: faces-config-bean.xml, faces-config.xml, web.xml
>
>
> Dear All,
> I have JSF1.1 application which runs on Java 6/WAS7 as of now. We are 
> currently doing Java 8 Migration with WAS 8.5.5.11. Installed WAS8.5.5.11 & 
> Java 8 and Configured workspace and changed the Compiler & Project Facelets 
> to Java 1. 8 & WAS8.5 and restarted the servers without any issues. 
> But when login getting View CertificateException for ViewID with Restore_View 
> :1 error and when I debugged I am seeing viewroot is empty in facescontext 
> and I do the same in Jav6/WAS7 I am able to see the values for viewroot in 
> facecontext. I did only Java 8/WAS5.5.11 install and started the servers 
> without any changes but it is not working in new environment.
> Could you please help me to find the root cause and solution to resolve the 
> issue.
> Using myfaces-api-1.1.9 & jsf-facelets-1.1.14
> Thanks,
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MYFACES-4223) FacesContext ViewRoot is Null - in JSF1.1.9

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462379#comment-16462379
 ] 

Thomas Andraschko commented on MYFACES-4223:


Will close it for now.

Please use the mailing list for such "questions" next time.

> FacesContext ViewRoot is Null - in JSF1.1.9
> ---
>
> Key: MYFACES-4223
> URL: https://issues.apache.org/jira/browse/MYFACES-4223
> Project: MyFaces Core
>  Issue Type: Bug
> Environment: Production
>Reporter: Venkatesh
>Priority: Critical
> Attachments: faces-config-bean.xml, faces-config.xml, web.xml
>
>
> Dear All,
> I have JSF1.1 application which runs on Java 6/WAS7 as of now. We are 
> currently doing Java 8 Migration with WAS 8.5.5.11. Installed WAS8.5.5.11 & 
> Java 8 and Configured workspace and changed the Compiler & Project Facelets 
> to Java 1. 8 & WAS8.5 and restarted the servers without any issues. 
> But when login getting View CertificateException for ViewID with Restore_View 
> :1 error and when I debugged I am seeing viewroot is empty in facescontext 
> and I do the same in Jav6/WAS7 I am able to see the values for viewroot in 
> facecontext. I did only Java 8/WAS5.5.11 install and started the servers 
> without any changes but it is not working in new environment.
> Could you please help me to find the root cause and solution to resolve the 
> issue.
> Using myfaces-api-1.1.9 & jsf-facelets-1.1.14
> Thanks,
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MYFACES-4227) Dynamic Resource Loading doesn't work

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462371#comment-16462371
 ] 

Thomas Andraschko commented on MYFACES-4227:


HtmlStylesheetRenderer and HtmlScriptRenderer#processEvent are also not called.

Not sure how it was designed
[~lu4242] Do you have some minutes to explain how it should be implemented (how 
the diff is calculcated) or can check the bug itself?

> Dynamic Resource Loading doesn't work
> -
>
> Key: MYFACES-4227
> URL: https://issues.apache.org/jira/browse/MYFACES-4227
> Project: MyFaces Core
>  Issue Type: Improvement
>  Components: JSR-372
>Affects Versions: 2.3.0, 2.3.1
>Reporter: Thomas Andraschko
>Priority: Major
> Fix For: 2.3.2
>
>
> [https://github.com/martin654/primefaces-test]
> Just run the example via jetty:run
> For MyFaces, you need to exchange Mojarra with MyFaces.
> It works fine in Mojarra but in MyFaces, the "javax.faces.Resource" update is 
> never rendered.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MYFACES-4227) Dynamic Resource Loading doesn't work

[Thomas Andraschko (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462369#comment-16462369
 ] 

Thomas Andraschko commented on MYFACES-4227:


PartialViewContextImpl#processRenderResource is called for head but 
isRenderTarget returns false and getRenderTargetComponentList is empty, too.

> Dynamic Resource Loading doesn't work
> -
>
> Key: MYFACES-4227
> URL: https://issues.apache.org/jira/browse/MYFACES-4227
> Project: MyFaces Core
>  Issue Type: Improvement
>  Components: JSR-372
>Affects Versions: 2.3.0, 2.3.1
>Reporter: Thomas Andraschko
>Priority: Major
> Fix For: 2.3.2
>
>
> [https://github.com/martin654/primefaces-test]
> Just run the example via jetty:run
> For MyFaces, you need to exchange Mojarra with MyFaces.
> It works fine in Mojarra but in MyFaces, the "javax.faces.Resource" update is 
> never rendered.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MYFACES-4227) Dynamic Resource Loading doesn't work

[Thomas Andraschko (JIRA)]

Thomas Andraschko created MYFACES-4227:
--

 Summary: Dynamic Resource Loading doesn't work
 Key: MYFACES-4227
 URL: https://issues.apache.org/jira/browse/MYFACES-4227
 Project: MyFaces Core
  Issue Type: Improvement
Affects Versions: 2.3.0, 2.3.1
Reporter: Thomas Andraschko


[https://github.com/martin654/primefaces-test]

Just run the example via jetty:run

For MyFaces, you need to exchange Mojarra with MyFaces.

It works fine in Mojarra but in MyFaces, the "javax.faces.Resource" update is 
never rendered.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (TOBAGO-1896) 2nd AJAX will fail with JSF 2.3: IllegalArgumentException: Illegal base64 character a

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462319#comment-16462319
 ] 

Hudson commented on TOBAGO-1896:


SUCCESS: Integrated in Jenkins build Tobago Trunk #1415 (See 
[https://builds.apache.org/job/Tobago%20Trunk/1415/])
TOBAGO-1896: 2nd AJAX will fail with JSF 2.3: IllegalArgumentException: 
(lofwyr: rev b6d0c8bc648f652d653361411fd0de8ae10f2d35)
* (edit) 
tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/js/tobago-jsf.js


> 2nd AJAX will fail with JSF 2.3: IllegalArgumentException: Illegal base64 
> character a
> -
>
> Key: TOBAGO-1896
> URL: https://issues.apache.org/jira/browse/TOBAGO-1896
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Themes
>Affects Versions: 4.2.0
> Environment: JSF 2.3
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
>Priority: Major
> Fix For: 4.2.1
>
>
> The "a" in the exception message is a hex value from a "LINE FEED" inserted 
> from an additional #text node  from the AJAX response since TOBAGO-1887



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[Tobago] Preparation for the 4.2.1 release

[Udo Schnurpfeil]

Hi, folks,

we plan to build version 4.2.1 of Tobago soon.

If you know any blocking problems with the current SNAPSHOT, give me a
hint.

Regards,
Udo