[jira] [Commented] (MYFACES-4171) Create a new web-facesconfig.xsd schema for JSF 2.3
[ https://issues.apache.org/jira/browse/MYFACES-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242877#comment-16242877 ] Eduardo Breijo commented on MYFACES-4171: - Yeah it's my bad, there is a spec issue opened for that: https://github.com/javaee/javaserverfaces-spec/issues/1457 > Create a new web-facesconfig.xsd schema for JSF 2.3 > --- > > Key: MYFACES-4171 > URL: https://issues.apache.org/jira/browse/MYFACES-4171 > Project: MyFaces Core > Issue Type: Task > Components: JSR-372 >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo > > I noticed that the schema file web-facesconfig.xsd has not been updated since > JSF 2.1. > The following spec issue was opened to add the element > /faces-config/factory/client-window-factory in the schema because it was > missing on JSF 2.2. > https://github.com/javaee/javaserverfaces-spec/issues/1241 > I also noticed that the following new elements need to be added to the JSF > 2.3 schema. > /faces-config/factory/search-expression-context-kit-factory > /faces-config/application/search-expression-handler > /faces-config/application/search-keyword-resolver > We need to create a new web-facesconfig.xsd schema for JSF 2.3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYFACES-4171) Create a new web-facesconfig.xsd schema for JSF 2.3
[ https://issues.apache.org/jira/browse/MYFACES-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242858#comment-16242858 ] Thomas Andraschko commented on MYFACES-4171: JFYI: search-expression-context-kit-factory doesn't exist, AFAIR it's without "kit" > Create a new web-facesconfig.xsd schema for JSF 2.3 > --- > > Key: MYFACES-4171 > URL: https://issues.apache.org/jira/browse/MYFACES-4171 > Project: MyFaces Core > Issue Type: Task > Components: JSR-372 >Affects Versions: 2.3.0-beta >Reporter: Eduardo Breijo > > I noticed that the schema file web-facesconfig.xsd has not been updated since > JSF 2.1. > The following spec issue was opened to add the element > /faces-config/factory/client-window-factory in the schema because it was > missing on JSF 2.2. > https://github.com/javaee/javaserverfaces-spec/issues/1241 > I also noticed that the following new elements need to be added to the JSF > 2.3 schema. > /faces-config/factory/search-expression-context-kit-factory > /faces-config/application/search-expression-handler > /faces-config/application/search-keyword-resolver > We need to create a new web-facesconfig.xsd schema for JSF 2.3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MYFACES-4171) Create a new web-facesconfig.xsd schema for JSF 2.3
Eduardo Breijo created MYFACES-4171: --- Summary: Create a new web-facesconfig.xsd schema for JSF 2.3 Key: MYFACES-4171 URL: https://issues.apache.org/jira/browse/MYFACES-4171 Project: MyFaces Core Issue Type: Task Components: JSR-372 Affects Versions: 2.3.0-beta Reporter: Eduardo Breijo I noticed that the schema file web-facesconfig.xsd has not been updated since JSF 2.1. The following spec issue was opened to add the element /faces-config/factory/client-window-factory in the schema because it was missing on JSF 2.2. https://github.com/javaee/javaserverfaces-spec/issues/1241 I also noticed that the following new elements need to be added to the JSF 2.3 schema. /faces-config/factory/search-expression-context-kit-factory /faces-config/application/search-expression-handler /faces-config/application/search-keyword-resolver We need to create a new web-facesconfig.xsd schema for JSF 2.3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (MYFACES-3250) [perf] Implement o.a.m.SUPPORT_MANAGED_BEANS
[ https://issues.apache.org/jira/browse/MYFACES-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152583#comment-16152583 ] Thomas Andraschko edited comment on MYFACES-3250 at 11/7/17 3:33 PM: - Introduced context param (org.apache.myfaces.SUPPORT_MANAGED_BEANS) + dynamically register the DestroyerListener. was (Author: tandraschko): Introduced context param + dynamically register the DestroyerListener. > [perf] Implement o.a.m.SUPPORT_MANAGED_BEANS > > > Key: MYFACES-3250 > URL: https://issues.apache.org/jira/browse/MYFACES-3250 > Project: MyFaces Core > Issue Type: Improvement > Environment: myfaces trunk, tomcat 6.0.26 >Reporter: Martin Kočí >Assignee: Thomas Andraschko >Priority: Minor > Fix For: 2.3.0 > > > When running stress test this is one of the most BLOCKED thread (blocked on > some ArrayList monitor in tomcat internals): > org.apache.catalina.core.ContainerBase.fireContainerEvent(String, Object) >org.apache.catalina.session.StandardSession.fireContainerEvent(Context, > String, Object) > org.apache.catalina.session.StandardSession.setAttribute(String, > Object, boolean) > org.apache.catalina.session.StandardSession.setAttribute(String, > Object) > > org.apache.catalina.session.StandardSessionFacade.setAttribute(String, > Object) > > org.apache.myfaces.context.servlet.SessionMap.setAttribute(String, Object) > > org.apache.myfaces.util.AbstractThreadSafeAttributeMap.put(String, Object) > > org.apache.myfaces.util.AbstractThreadSafeAttributeMap.put(Object, Object) > This happens when someone puts a attribute into httpSession: > org.apache.myfaces.util.AbstractThreadSafeAttributeMap.put(Object, Object) > > org.apache.myfaces.renderkit.ServerSideStateCacheImpl.nextViewSequence(FacesContext) > > org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.getResponseEncoding(FacesContext, > String) > > org.apache.myfaces.renderkit.ServerSideStateCacheImpl.saveSerializedViewInServletSession(FacesContext, > > then Servlet container delivers event HttpSessionBindingEvent. > in myfaces HttpSessionAttributeListener in implemented by > oam.StartupServletContextListener and handles some stuff for managed beans. > Review if this is needed - ideally remove it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1821) Update bootstrap datepicker library
[ https://issues.apache.org/jira/browse/TOBAGO-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241983#comment-16241983 ] Hudson commented on TOBAGO-1821: SUCCESS: Integrated in Jenkins build Tobago Trunk #1114 (See [https://builds.apache.org/job/Tobago%20Trunk/1114/]) TOBAGO-1821 Update bootstrap datepicker library * positioning for (hnoeth: rev 3d2436af1293c120ab1ff78f8bfb4aa0ddd9a6d1) * (edit) tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/js/tobago-layout.js * (edit) tobago-theme/tobago-theme-standard/src/main/resources/META-INF/resources/tobago/standard/tobago-bootstrap/_version/js/tobago-calendar.js > Update bootstrap datepicker library > --- > > Key: TOBAGO-1821 > URL: https://issues.apache.org/jira/browse/TOBAGO-1821 > Project: MyFaces Tobago > Issue Type: Improvement > Components: Themes >Affects Versions: 3.0.6 >Reporter: Henning Noeth >Assignee: Henning Noeth > > Current version: '4.17.37' can be updated to '4.17.45'. > The update fix the 'widgetParent positions the picker incorrectly' bug > (https://github.com/Eonasdan/bootstrap-datetimepicker/issues/790). > So we don't need to fix it in _tobago.scss. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TOBAGO-1821) Update bootstrap datepicker library
[ https://issues.apache.org/jira/browse/TOBAGO-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241666#comment-16241666 ] Hudson commented on TOBAGO-1821: SUCCESS: Integrated in Jenkins build Tobago Trunk #1113 (See [https://builds.apache.org/job/Tobago%20Trunk/1113/]) TOBAGO-1821 Update bootstrap datepicker library * update datepicker CSS (hnoeth: rev 9b35898590e1a38ae58804599a2e8f08579de3f3) * (edit) tobago-theme/tobago-theme-standard/src/main/resources/META-INF/tobago-config.xml > Update bootstrap datepicker library > --- > > Key: TOBAGO-1821 > URL: https://issues.apache.org/jira/browse/TOBAGO-1821 > Project: MyFaces Tobago > Issue Type: Improvement > Components: Themes >Affects Versions: 3.0.6 >Reporter: Henning Noeth >Assignee: Henning Noeth > > Current version: '4.17.37' can be updated to '4.17.45'. > The update fix the 'widgetParent positions the picker incorrectly' bug > (https://github.com/Eonasdan/bootstrap-datetimepicker/issues/790). > So we don't need to fix it in _tobago.scss. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
