[jira] Commented: (TOMAHAWK-1560) Tomahawk 1.1.10 for JSF 1.2 fails to deploy on JBoss AS 6 because of TLD errors
[ https://issues.apache.org/jira/browse/TOMAHAWK-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980379#action_12980379 ] Stan Silvert commented on TOMAHAWK-1560: I'd be interested to know if this workaround fixes the problem. Go to server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml. Set one or both of the validation properties to false: 2002 false false > Tomahawk 1.1.10 for JSF 1.2 fails to deploy on JBoss AS 6 because of TLD > errors > --- > > Key: TOMAHAWK-1560 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1560 > Project: MyFaces Tomahawk > Issue Type: Bug >Affects Versions: 1.1.10 >Reporter: Kennard Consulting >Priority: Critical > Attachments: TOMAHAWK-1560.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Tomahawk 1.1.10 for JSF 1.2 fails to deploy on the recently released JBoss AS > 6. This appears to be because of errors in tomahawk.tld. I managed to resolve > it by taking the following steps (any of which may be sub-optimal): > 1. Changed > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd"; > to xsi:schemaLocation="http://java.sun.com/xml/ns/javaee > http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd"; (i.e. the first > half of the schemaLocation was missing) > 2. Removed tag (is a bad element name?) > 3. Removed all tags (they contain invalid markup?) > Regards, > Richard. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2860) Provide AnnotationScanner interface
[ https://issues.apache.org/jira/browse/MYFACES-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896990#action_12896990 ] Stan Silvert commented on MYFACES-2860: --- The point of this interface is that we don't want MyFaces to do any scanning at all. MyFaces should contain a default scanner in case the container doesn't provide one. But if I implement this interfaces I expect that MyFaces will not scan at all. It will only load the classes where I found JSF annotations. So MyFaces doesn't worry about metadata-complete. The scanner implementation does that. Since MyFaces isn't doing the scanning, it also doesn't have to worry about file type vs. jar file. JBoss has its own protocols for its virtual file system. So you'd have more trouble navigating that anyway. I'd rather see something like: public Collection> getAnnotatedClasses(Class annotation, ExternalContext extCtx); I see your point about ExternalContext and portlets. But like you, I'm not sure if it's really needed. We need to think about that one some more. > Provide AnnotationScanner interface > --- > > Key: MYFACES-2860 > URL: https://issues.apache.org/jira/browse/MYFACES-2860 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-314 >Affects Versions: 2.0.1 >Reporter: Leonardo Uribe >Assignee: Leonardo Uribe > Attachments: jboss-myfaces.zip, Myfaces-2.0-jsf.deployer.zip, > MYFACES-2860-1.patch > > > Looking integration of myfaces with JBoss AS6, it was notice myfaces does not > have a way to override the annotation configurator. > Ri has a class called AnnotationProvider with this methods: > public AnnotationProvider(ServletContext sc) > abstract public Map getAnnotatedClasses(Set urls) > the documentation says it is possible to override using this type of > constructor. > public AnnotationProvider(ServletContext sc, AnnotationProvider parent) > We should provide something similar (let's call it AnnotationScanner because > its objective is scan for annotations). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2860) Provide AnnotationScanner interface
[ https://issues.apache.org/jira/browse/MYFACES-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896877#action_12896877 ] Stan Silvert commented on MYFACES-2860: --- Leonardo, I don't see how it makes a difference where the classes came from. Did you find something in the spec that says an annotation is treated differently based on whether it is in WEB-INF, META-INF, or JSF impl? Perhaps ordering is a concern? What you have would be an improvement, but you are still scanning twice. If I just provide you with a collection of classes then you have to scan the classes for the annotations you are interested in. But on my end I already know which annotations are in each class. If you give me an annotation, I can tell you which classes in a deployment contain that annotation. Also, I don't need the ExternalContext if you give me the ServletContext in the constructor. > Provide AnnotationScanner interface > --- > > Key: MYFACES-2860 > URL: https://issues.apache.org/jira/browse/MYFACES-2860 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-314 >Affects Versions: 2.0.1 >Reporter: Leonardo Uribe >Assignee: Leonardo Uribe > Attachments: jboss-myfaces.zip, Myfaces-2.0-jsf.deployer.zip, > MYFACES-2860-1.patch > > > Looking integration of myfaces with JBoss AS6, it was notice myfaces does not > have a way to override the annotation configurator. > Ri has a class called AnnotationProvider with this methods: > public AnnotationProvider(ServletContext sc) > abstract public Map getAnnotatedClasses(Set urls) > the documentation says it is possible to override using this type of > constructor. > public AnnotationProvider(ServletContext sc, AnnotationProvider parent) > We should provide something similar (let's call it AnnotationScanner because > its objective is scan for annotations). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (JSR301-1) Bad init param causes infinite loop
Bad init param causes infinite loop --- Key: JSR301-1 URL: https://issues.apache.org/jira/browse/JSR301-1 Project: MyFaces Portlet Bridge Issue Type: Bug Components: General Affects Versions: 1.0.0-SNAPSHOT Reporter: Stan Silvert If the default view for a portlet mode is not specified, you will get an infinite loop. In GenericFacesPortlet, the doDispatchInternal() method will call super.doDispatch(request, response) if a default view is not specified in portlet.xml. GenericPortlet.doDispatch() calls back into GenericFacesPortlet, creating an infinite loop. It should throw a PortletException instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1481) MyFacesGenericPortlet does not work in a cluster
[ https://issues.apache.org/jira/browse/MYFACES-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472949 ] Stan Silvert commented on MYFACES-1481: --- Yes, it's fixed in 1.1.5. Though I doubt that this is the last of the clustering issues with JSF portlets. More research is needed. > MyFacesGenericPortlet does not work in a cluster > > > Key: MYFACES-1481 > URL: https://issues.apache.org/jira/browse/MYFACES-1481 > Project: MyFaces Core > Issue Type: Bug > Components: Portlet_Support >Affects Versions: 1.1.4 >Reporter: John Gilbert > Assigned To: Stan Silvert > Fix For: 1.1.5 > > > The problem is that ServletFacesContextImpl is not serializable and > processAction places one in the session. > Here is a link to a discussion on the JBoss Forum. > http://jboss.org/index.html?module=bb&op=viewtopic&p=3981103#3981103 > Here is a link to the workaround I created. > http://taylor.cvs.sourceforge.net/taylor/taylor/commons/src/main/java/net/taylor/portlet/MyFacesGenericPortlet.java?view=markup -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1518) Redirect in portlet does not work because of Render Parameter
[ https://issues.apache.org/jira/browse/MYFACES-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462630 ] Stan Silvert commented on MYFACES-1518: --- Yes, redirects to absolute URLs should be OK. My bad, I thought you were talking about using in JSF navigation. If you do a redirect to an absolute URL then you should call FacesContext.responseComplete(). Then setRenderParameter() will not be called. > Redirect in portlet does not work because of Render Parameter > - > > Key: MYFACES-1518 > URL: https://issues.apache.org/jira/browse/MYFACES-1518 > Project: MyFaces Core > Issue Type: New Feature > Components: Portlet_Support > Environment: Windows, Linux >Reporter: Ryan Wynn > > At the end of the portlet action phase the MyFacesGenericPortlet sets a > render parameter. > response.setRenderParameter(VIEW_ID, facesContext.getViewRoot().getViewId()); > This is not allowed if redirect has already been called on the external > context during the action phase of the jsf lifecycle. I believe for redirect > case a flag should be used to indicate the the render parameter should not be > set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1518) Redirect in portlet does not work because of Render Parameter
[ https://issues.apache.org/jira/browse/MYFACES-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462610 ] Stan Silvert commented on MYFACES-1518: --- In general, redirects are not supported in JSF portlets. This is a topic being discussed as part of the JSR-301 (JSF Portlet Bridge) expert group. While it may be possible, nobody is really sure how to do it at this point. > Redirect in portlet does not work because of Render Parameter > - > > Key: MYFACES-1518 > URL: https://issues.apache.org/jira/browse/MYFACES-1518 > Project: MyFaces Core > Issue Type: Bug > Components: Portlet_Support > Environment: Windows, Linux >Reporter: Ryan Wynn > > At the end of the portlet action phase the MyFacesGenericPortlet sets a > render parameter. > response.setRenderParameter(VIEW_ID, facesContext.getViewRoot().getViewId()); > This is not allowed if redirect has already been called on the external > context during the action phase of the jsf lifecycle. I believe for redirect > case a flag should be used to indicate the the render parameter should not be > set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1481) MyFacesGenericPortlet does not work in a cluster
[ http://issues.apache.org/jira/browse/MYFACES-1481?page=comments#action_12457479 ] Stan Silvert commented on MYFACES-1481: --- I occurs to me that the FacesContext also needs to be removed from the session at the end of processAction. I have learned that some Portal containers actually do a redirect after processAction instead of calling render() directly. The redirect means that the request is ended and replication could happen. However, I'm not sure if things will still work if I remove FacesContext from the session and immediately rebuild it during render(). BTW, as part of the cleanup I've now added FacesContext.release() at the end of the render() phase. > MyFacesGenericPortlet does not work in a cluster > > > Key: MYFACES-1481 > URL: http://issues.apache.org/jira/browse/MYFACES-1481 > Project: MyFaces Core > Issue Type: Bug >Reporter: John Gilbert > Assigned To: Stan Silvert > > The problem is that ServletFacesContextImpl is not serializable and > processAction places one in the session. > Here is a link to a discussion on the JBoss Forum. > http://jboss.org/index.html?module=bb&op=viewtopic&p=3981103#3981103 > Here is a link to the workaround I created. > http://taylor.cvs.sourceforge.net/taylor/taylor/commons/src/main/java/net/taylor/portlet/MyFacesGenericPortlet.java?view=markup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-660) (Patch provided) "request scoping" from Portlet Action- to RenderRequest should not occur via Attribute Request Map
[ http://issues.apache.org/jira/browse/MYFACES-660?page=comments#action_12451434 ] Stan Silvert commented on MYFACES-660: -- After attending the JSR-301 meeting and talking this issue over with some portlet experts, I think I know what needs to be done. The only thing that needs to be fixed is propagation of request attributes from processAction to facesRender. Attributes are saved at the end of processAction. The saved attributes are kept until the next processAction or until the session times out/invalidates. On each facesRender, request attributes set during processAction are restored just before lifecycle.render(). In short, managed beans with request scope should now work across all portlet containers. It's only taken 13 months to get this resolved. Better late than never! > (Patch provided) "request scoping" from Portlet Action- to RenderRequest > should not occur via Attribute Request Map > --- > > Key: MYFACES-660 > URL: http://issues.apache.org/jira/browse/MYFACES-660 > Project: MyFaces Core > Issue Type: Bug > Components: Portlet_Support >Affects Versions: 1.1.2-SNAPSHOT > Environment: myfaces-api + myfaces-impl (rev. 292564) , > pluto-1.0.1-rc4 (binary bundle), Liferay 3.6.1 Enterprise, jdk1.5.0_03-b07 >Reporter: Tanju Erinmez > Assigned To: Stan Silvert > Fix For: 1.1.5-SNAPSHOT > > Attachments: myfaces-impl-src-java.diff, navdemo2.war > > > Hi, > After pulling my hair out (and getting a transplant :) I think there is a > refined spec vs. current implementation clash [1]. I have looked into this > and come up with a possible solution [2]. After having also discussed > MYFACES-549 with Brian Chan from Liferay [3] I think you can hit two birds > with one stone with the provided patch and get Liferay & BEA platform support > for free ;-)). > Cheers, > Tanju > 1. Details > -- > There has been a refinement to the JSR 168 Spec PLT.11.1.3 recently which now > clearly indicates that it cannot be assumed that attributes from an > ActionRequest will be available in a RenderRequest (see > http://jcp.org/aboutJava/communityprocess/maintenance/jsr168/Portlet1.0-ERRATA.html#issue10). > On the other hand, it is a legitimate need for JSF to carry over results > (e.g. Request scoped managed beans) from the lifecycle execution part > (ActionRequest) over to the render part (RenderRequest). > AFAIK, there is no special treatment of this case, which means JSF just > populates and fetches from the attribute map assuming a standard servlet > request behavior. > Instead of interfering with this already for servlet mode working behavior I > have come up with a special Request Map treatment approach. However, I'm not > sure which of the following processing model the design of the portlet > integration follows and would be glad if some light could be shed on this: > 1. Portlet X receives an ActionRequest and later a RenderRequest this two > Requests make up the entire faces lifecycle. Portlet Y from the same > PortletContext just receives an ordinary RenderRequest without knowing of any > previous ActionRequests > 2. Same as above but Portlet Y is "aware" of the ActionRequest e.g. somehow > Interportlet communication shall be achieved in the future > 2. Solution > - > After rolling the dice, I have decided to go with the first approach. The > idea is to use a separate map stored in the PortletSession to mimic a request > map which spans over two requests (Action & RenderRequest). This map is > removed from the PortletSession after the render cycle is concluded. > I have tested this approach with two simple portlets each containing 3 jsp > pages embedding a t:saveState binding to the same managed request scoped > bean. I could verify on pluto as well as Liferay that this bean was created > only once and its value is preserved despite changing pages in the same > portlet. (I merely used saveState as a lazy way to check for request > leaking -> it will not work for multiple portlet with the intention to have > several "conversations" in parallel). > However, what puzzles me right now is that without the patch the "standard" > behavior on pluto is that the bean is created everytime. This indicates that > the ActionRequest attribute map is not inherited to the RenderRequest (is ok > according to PLT.11.1.3) which would actually mean that request scoped beans > haven' worked up to now which I cannot believe. So this is speculative as I > have not verified this yet. > 3. Liferay et al. > > MYFACES-549 is somewhat different to the case above because it revolves > around the problem that the attribute map from one RenderRequests is visible > to
[jira] Commented: (MYFACES-1481) MyFacesGenericPortlet does not work in a cluster
[ http://issues.apache.org/jira/browse/MYFACES-1481?page=comments#action_12448884 ] Stan Silvert commented on MYFACES-1481: --- John, I just committed some changes to MyFacesGenericPortlet. FacesContext will be removed from the session after each render(). I don't have a cluster set up so I can't test it out. Can you test it for me to see if replication works? Thanks, Stan > MyFacesGenericPortlet does not work in a cluster > > > Key: MYFACES-1481 > URL: http://issues.apache.org/jira/browse/MYFACES-1481 > Project: MyFaces Core > Issue Type: Bug >Reporter: John Gilbert > Assigned To: Stan Silvert > > The problem is that ServletFacesContextImpl is not serializable and > processAction places one in the session. > Here is a link to a discussion on the JBoss Forum. > http://jboss.org/index.html?module=bb&op=viewtopic&p=3981103#3981103 > Here is a link to the workaround I created. > http://taylor.cvs.sourceforge.net/taylor/taylor/commons/src/main/java/net/taylor/portlet/MyFacesGenericPortlet.java?view=markup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1481) MyFacesGenericPortlet does not work in a cluster
[ http://issues.apache.org/jira/browse/MYFACES-1481?page=comments#action_12448529 ] Stan Silvert commented on MYFACES-1481: --- Thanks for researching this. It is something I hadn't considered. However, I don't think that your workaround is the best approach. The FacesContext should be removed from the session at the end of the request. Since session replication should not happen in the middle of the request, the problem would be solved. I have to figure out how to make this all work properly though. render() can be called without a processAction(). In that case we need to create a new FacesContext instead of using the one in the session. Stan > MyFacesGenericPortlet does not work in a cluster > > > Key: MYFACES-1481 > URL: http://issues.apache.org/jira/browse/MYFACES-1481 > Project: MyFaces Core > Issue Type: Bug >Reporter: John Gilbert > Assigned To: Stan Silvert > > The problem is that ServletFacesContextImpl is not serializable and > processAction places one in the session. > Here is a link to a discussion on the JBoss Forum. > http://jboss.org/index.html?module=bb&op=viewtopic&p=3981103#3981103 > Here is a link to the workaround I created. > http://taylor.cvs.sourceforge.net/taylor/taylor/commons/src/main/java/net/taylor/portlet/MyFacesGenericPortlet.java?view=markup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1070) NullPointerException in MyFacesGenericPortlet.facesRender method
[ http://issues.apache.org/jira/browse/MYFACES-1070?page=all ] Stan Silvert resolved MYFACES-1070: --- Fix Version: 1.1.4-SNAPSHOT Resolution: Fixed Fixed > NullPointerException in MyFacesGenericPortlet.facesRender method > > > Key: MYFACES-1070 > URL: http://issues.apache.org/jira/browse/MYFACES-1070 > Project: MyFaces Core > Type: Bug > Components: Portlet_Support > Versions: 1.1.1 > Environment: JDK 1.5.0 on Mac OS X 10.4 (Tiger); JBoss AS 4.0.3.SP1; JBoss > Portal 2.2.0-FINAL > Reporter: Max Rudman > Assignee: Stan Silvert > Fix For: 1.1.4-SNAPSHOT > > Here are the steps to reproduce: > 1) Submit a form inside of JSF-based portlet (in other words generate a Faces > request) > 2) Hit JBoss Portal URL page URL (I believe this causes the page and portlets > to re-render) > 3) Hot-redeploy WAR file containg the portlet. > You no can't get to the page because the portlet throws a NPE. Here is > partial stack trace: > java.lang.NullPointerException > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:393) > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266) > at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:154) > at javax.portlet.GenericPortlet.render(GenericPortlet.java:394) > at > org.jboss.portal.portlet.PortletContainer.invokeRender(PortletContainer.java:499) > at > org.jboss.portal.portlet.PortletContainer.dispatch(PortletContainer.java:416) > The problem seems to be that FacesContextImpl object is no longer in > PortletSession even though the PortletSession itself is present. This is > probably a bug in JBoss Portal. However, facesRender method should check for > null FacesContextImpl and treat it as a non-Faces request (just like when > PortletSession times out). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1274) JSR-252 Unified EL: Implement sections 5.5, 5.6, 5.7, and 5.8 of the JSF 1.2 spec
[ http://issues.apache.org/jira/browse/MYFACES-1274?page=all ] Stan Silvert resolved MYFACES-1274: --- Fix Version: 1.2.0-SNAPSHOT Resolution: Fixed A big DONE for this one. > JSR-252 Unified EL: Implement sections 5.5, 5.6, 5.7, and 5.8 of the JSF 1.2 > spec > - > > Key: MYFACES-1274 > URL: http://issues.apache.org/jira/browse/MYFACES-1274 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.2.0-SNAPSHOT > > There was no specific EG issue number for this, so this Jira task will serve > as a catch-all for integration with the new Unified EL provided in JSP 2.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1207) JSR-252 Issue #15: Enhanced the usage of the "Decorator Pattern" for ViewHandler, StateManager and ResponseWriter
[ http://issues.apache.org/jira/browse/MYFACES-1207?page=all ] Stan Silvert resolved MYFACES-1207: --- Fix Version: 1.2.0-SNAPSHOT Resolution: Fixed > JSR-252 Issue #15: Enhanced the usage of the "Decorator Pattern" for > ViewHandler, StateManager and ResponseWriter > - > > Key: MYFACES-1207 > URL: http://issues.apache.org/jira/browse/MYFACES-1207 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.2.0-SNAPSHOT > > Enhanced the usage of the "Decorator Pattern" for ViewHandler, StateManager > and ResponseWriter classes by providing abstract wrapper classes to make it > easier to override a subset of the total methods for those classes. Please > see Section 8.5 "Standard HTML RenderKit Implementation" for descriptions of > those components. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=15 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1210) JSR-252 Issue #18: behavior clarifications
[ http://issues.apache.org/jira/browse/MYFACES-1210?page=all ] Stan Silvert resolved MYFACES-1210: --- Fix Version: 1.2.0-SNAPSHOT Resolution: Fixed > JSR-252 Issue #18: behavior clarifications > - > > Key: MYFACES-1210 > URL: http://issues.apache.org/jira/browse/MYFACES-1210 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.2.0-SNAPSHOT > > When a resource lookup is done on the java.util.Map (loaded from > ) using a key, and the key is not found in the Map, return the > literal string ???KEY??? where KEY is the key being looked up in the Map > (instead of throwing a MissingResourceException). Throw a JspException if > the named bundle identified by does not exist. Please see > Section 9.4.7 "". > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=18 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1211) JSR-252 Issue #20: Specify that the event queue should be cleared after each phase (except for RestoreViewPhase and RenderResponse) if responseComplete or renderRespons
[ http://issues.apache.org/jira/browse/MYFACES-1211?page=all ] Stan Silvert resolved MYFACES-1211: --- Resolution: Fixed > JSR-252 Issue #20: Specify that the event queue should be cleared after each > phase (except for RestoreViewPhase and RenderResponse) if responseComplete or > renderResponse has been set > -- > > Key: MYFACES-1211 > URL: http://issues.apache.org/jira/browse/MYFACES-1211 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Specify that the event queue should be cleared after each phase (except for > RestoreViewPhase and RenderResponse) if responseComplete or renderResponse > has been set on FacesContext. > See > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=20 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1242) JSR-252 Issue #75: Added "getRequestContentType" and "getResponseContentType" to ExternalContext.
[ http://issues.apache.org/jira/browse/MYFACES-1242?page=all ] Stan Silvert resolved MYFACES-1242: --- Fix Version: 1.2.0-SNAPSHOT Resolution: Fixed Done. > JSR-252 Issue #75: Added "getRequestContentType" and "getResponseContentType" > to ExternalContext. > - > > Key: MYFACES-1242 > URL: http://issues.apache.org/jira/browse/MYFACES-1242 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.2.0-SNAPSHOT > > Added "getRequestContentType" and "getResponseContentType" to ExternalContext. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=75 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1252) JSR-252 Issue #135: Support Java EE 5 enums as valid types
[ http://issues.apache.org/jira/browse/MYFACES-1252?page=all ] Stan Silvert resolved MYFACES-1252: --- Fix Version: 1.2.0-SNAPSHOT Resolution: Fixed This is done except that Tomcat 6 coercion doesn't yet support enums as required by the spec. This has been reported to the Tomcat team. > JSR-252 Issue #135: Support Java EE 5 enums as valid types > -- > > Key: MYFACES-1252 > URL: http://issues.apache.org/jira/browse/MYFACES-1252 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.2.0-SNAPSHOT > > Support Java EE 5 enums as valid types > See > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=135 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1254) JSR-252 Issue #151: Specified standard converter for Enums
[ http://issues.apache.org/jira/browse/MYFACES-1254?page=all ] Stan Silvert resolved MYFACES-1254: --- Fix Version: 1.2.0-SNAPSHOT Resolution: Fixed Converter done. > JSR-252 Issue #151: Specified standard converter for Enums > -- > > Key: MYFACES-1254 > URL: http://issues.apache.org/jira/browse/MYFACES-1254 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.2.0-SNAPSHOT > > Specified standard converter for Enums > See > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=151 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1266) JSR-252 Issue #118: Specified that an implementation of Map returned from ExternalContext.getSessionMap implement a "clear" method that calls "removeAttribute" on each
[ http://issues.apache.org/jira/browse/MYFACES-1266?page=all ] Stan Silvert resolved MYFACES-1266: --- Fix Version: 1.2.0-SNAPSHOT Resolution: Fixed > JSR-252 Issue #118: Specified that an implementation of Map returned from > ExternalContext.getSessionMap implement a "clear" method that calls > "removeAttribute" on each attribute in the Servlet or Portlet Session. > > > Key: MYFACES-1266 > URL: http://issues.apache.org/jira/browse/MYFACES-1266 > Project: MyFaces Core > Type: Improvement > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.2.0-SNAPSHOT > > Specified that an implementation of Map returned from > ExternalContext.getSessionMap implement a "clear" method that calls > "removeAttribute" on each attribute in the Servlet or Portlet Session. > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1204) JSR-252 Issue #8: Made UIViewRoot a source of PhaseEvent(s) for all phases of the request processing lifecycle except RestoreView.
[ http://issues.apache.org/jira/browse/MYFACES-1204?page=comments#action_12376318 ] Stan Silvert commented on MYFACES-1204: --- The code is done and tested. I just need to be able to check it in to svn. I tested it by updating the JSF 1.1 TLD. It needs to be retested once the JSF 1.2 TLD is created. > JSR-252 Issue #8: Made UIViewRoot a source of PhaseEvent(s) for all phases of > the request processing lifecycle except RestoreView. > -- > > Key: MYFACES-1204 > URL: http://issues.apache.org/jira/browse/MYFACES-1204 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Made UIViewRoot a source of PhaseEvent(s) for all phases of the request > processing lifecycle except RestoreView. Provided additional "before" and > "after" phase listener attributes for the tag. Please see Section > 4.1.17 "UIViewRoot" for more details. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MYFACES-549) faces navigation rules not working for two portlets on portal page
[ http://issues.apache.org/jira/browse/MYFACES-549?page=all ] Stan Silvert closed MYFACES-549: Resolution: Won't Fix The latest version of LifeRay has a fix for this. > faces navigation rules not working for two portlets on portal page > -- > > Key: MYFACES-549 > URL: http://issues.apache.org/jira/browse/MYFACES-549 > Project: MyFaces Core > Type: Bug > Components: General > Versions: 1.1.1 > Environment: Linux 2.6.12, Java 1.5.0_04, Liferay Pro 3.6.1 (portla), > nightly build (20050909) > Reporter: zeroconf > Priority: Minor > Attachments: cardemo.war.zip > > I'm trying to write some JSF portlets within one portlet application > but encountered some problems concerning navigation rules when I > put more than one JSF portlet per portal page. > When I put just one portlet on my page everything concerning the > navigation rules (with /> stuff) works fine and I get to the next view. > But when I put a second faces portlet on the page navigation and invoking > actions on backing beans in the second portlet just doesn't work at all. > If I remove both portlets and put the second portlet on the page again (so > that > I'm having just one portlet again) this portlet works fine as well. So I > assume > that navigation settings in faces-config.xml must be correct. It has > something to do > with the arrangement of two faces portlets on the portal page so that > the second one > stops working as expected. > I also tried to use distinct IDs for all ui-components and also > distinct -values but that doesn't help > Thanks > zeroconf > Attached are the important parts of my web.xml, faces-config.xml and > portlet.xml > web.xml > > > Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";> > >PROJECT_NAME > >company_id >liferay.com > > >javax.faces.STATE_SAVING_METHOD >client > > >javax.faces.application.CONFIG_FILES >/WEB-INF/faces-config.xml > > > com.liferay.portal.servlet.PortletContextListener > > > org.apache.myfaces.webapp.StartupServletContextListener > > >PROJECT_NAME > com.liferay.portal.servlet.PortletServlet > >portlet-class > org.apache.myfaces.portlet.MyFacesGenericPortlet > >0 > > >FacesServlet >javax.faces.webapp.FacesServlet >1 > > >PROJECT_NAME >/PROJECT_NAME/* > > >http://java.sun.com/portlet > /WEB-INF/tld/liferay-portlet.tld > > > faces-config.xml: > == > > JavaServer Faces Config 1.1//EN" > "http://java.sun.com/dtd/web-facesconfig_1_1.dtd";> > http://java.sun.com/JSF/Configuration";> > > org.apache.myfaces.context.MyFacesContextFactoryImpl > > > >/jsp/jsf1/index.jsp > >p1next >/jsp/jsf1/n1.jsp > > > >/jsp/jsf1/n1.jsp > >p1back >/jsp/jsf1/index.jsp > > > > >/jsp/jsf2/index.jsp > >p2next >/jsp/jsf2/n1.jsp > > > >/jsp/jsf2/n1.jsp > >p2back >/jsp/jsf2/index.jsp > > > > portlet.xml > = > >jsf2 >jsf2 > org.apache.myfaces.portlet.MyFacesGenericPortlet > >default-view >/jsp/jsf2/index.jsp > > >text/html > > >jsf2 >jsf2 >jsf2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MYFACES-821) Usage of request attributes for caching
[ http://issues.apache.org/jira/browse/MYFACES-821?page=all ] Stan Silvert closed MYFACES-821: Resolution: Won't Fix This is a problem in LifeRay. The latest version has a fix. > Usage of request attributes for caching > --- > > Key: MYFACES-821 > URL: http://issues.apache.org/jira/browse/MYFACES-821 > Project: MyFaces Core > Type: Bug > Versions: 1.1.0 > Environment: liferay 3.6.1 > Reporter: Michael Lipp > Assignee: Stan Silvert > > JspStateManagerImpl (and maybe other classes) uses request attributes for > caching state. This causes a wrong view to be used if there is more than one > JSF-based portlet on a single page. MyFaces saves the serialized view of the > first portlet on the page as a request attribute. To avoid re-serialization, > MyFaces subsequently checks if there already is a request attribute with a > serialized view. As request attributes are not scoped to a single portlet > (the portlet specification does not require this), the serialized view of the > first portlet will be found and used by the second portlet. > This usage of request attributes may also be the cause of MYFACES-549. > As JSF, of course, does not need to know about the portlet environment, it > cannot be required that MyFaces saves such information "per view", e.g. by > prepending the viewId to the key for the request attribute (although this > would solve the problem). IMHO any request attributes added during > lifecycle.render() should be removed after lifecycle() render by the portlet > bridge. (The same applies to request attributes added during > lifecycle.execute(), but these should also be re-added before > lifecycle.render().) I have implemented this in my portlet bridge as a > workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-470) validator messages do not appear in portlets
[
http://issues.apache.org/jira/browse/MYFACES-470?page=comments#action_12374014
]
Stan Silvert commented on MYFACES-470:
--
Marcus,
Can you attach a simple test portlet for this?
Stan
> validator messages do not appear in portlets
>
>
> Key: MYFACES-470
> URL: http://issues.apache.org/jira/browse/MYFACES-470
> Project: MyFaces Core
> Type: Bug
> Versions: 1.1.0
> Environment: tomcat 5.5.9, uPortal 2.5.0
> Reporter: Dave Brondsema
> Assignee: Stan Silvert
>
> When in servlet mode, validation error messages do appear. When in portlet
> mode, it seems that validation occurs but the messages are not shown. Here
> is a snippet of the JSP:
>
>type="time" value="#{menubean.menu.dinnerStart}">
>validatorId="cu.DateRangeValidator" />
>
>value="10:00 PM" />
>
>/>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1274) JSR-252 Unified EL: Implement sections 5.5, 5.6, 5.7, and 5.8 of the JSF 1.2 spec
JSR-252 Unified EL: Implement sections 5.5, 5.6, 5.7, and 5.8 of the JSF 1.2 spec - Key: MYFACES-1274 URL: http://issues.apache.org/jira/browse/MYFACES-1274 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert There was no specific EG issue number for this, so this Jira task will serve as a catch-all for integration with the new Unified EL provided in JSP 2.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1266) JSR-252 Issue #118: Specified that an implementation of Map returned from ExternalContext.getSessionMap implement a "clear" method that calls "removeAttribute" on each
[ http://issues.apache.org/jira/browse/MYFACES-1266?page=comments#action_12373518 ] Stan Silvert commented on MYFACES-1266: --- Code is done for this. I just need to wait on our JSF 1.2 branch to open. This can't be done in MyFaces 1.1.2 because the JSF 1.1 TCK expects an exception when you call SessionMap.clear(). > JSR-252 Issue #118: Specified that an implementation of Map returned from > ExternalContext.getSessionMap implement a "clear" method that calls > "removeAttribute" on each attribute in the Servlet or Portlet Session. > > > Key: MYFACES-1266 > URL: http://issues.apache.org/jira/browse/MYFACES-1266 > Project: MyFaces Core > Type: Improvement > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Specified that an implementation of Map returned from > ExternalContext.getSessionMap implement a "clear" method that calls > "removeAttribute" on each attribute in the Servlet or Portlet Session. > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1269) JSR-252 Issue #145: Define new method on UIComponent, invokeOnComponent().
JSR-252 Issue #145: Define new method on UIComponent, invokeOnComponent(). -- Key: MYFACES-1269 URL: http://issues.apache.org/jira/browse/MYFACES-1269 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Define new method on UIComponent, invokeOnComponent(). This will find a component in the tree by clientId and invoke a user specified callback on it. Please see Section 3.1.8 "Component Tree Navigation" and Section 4.1.1.3 "Methods" [of UIData] for more details. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=145 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1268) JSR-252 Issue #138: Change the required return type for action methods to be Object instead of String.
JSR-252 Issue #138: Change the required return type for action methods to be Object instead of String. -- Key: MYFACES-1268 URL: http://issues.apache.org/jira/browse/MYFACES-1268 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Change the required return type for action methods to be Object instead of String. This allows the usage of Enums for the return type of action methods, as long as the toString() method of the enum matches the expected value in the application configuration resources. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=138 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1267) JSR-252 Issue #122: Clarified renderkit docs with respect to what gets rendered for disabled command link attributes.
JSR-252 Issue #122: Clarified renderkit docs with respect to what gets rendered for disabled command link attributes. - Key: MYFACES-1267 URL: http://issues.apache.org/jira/browse/MYFACES-1267 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Clarified renderkit docs with respect to what gets rendered for disabled command link attributes. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=122 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1266) JSR-252 Issue #118: Specified that an implementation of Map returned from ExternalContext.getSessionMap implement a "clear" method that calls "removeAttribute" on each a
JSR-252 Issue #118: Specified that an implementation of Map returned from ExternalContext.getSessionMap implement a "clear" method that calls "removeAttribute" on each attribute in the Servlet or Portlet Session. Key: MYFACES-1266 URL: http://issues.apache.org/jira/browse/MYFACES-1266 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Specified that an implementation of Map returned from ExternalContext.getSessionMap implement a "clear" method that calls "removeAttribute" on each attribute in the Servlet or Portlet Session. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1265) JSR-252 Issue #111: Specified that a component must allow child components to be added to and removed from the child list of the currrent component, even though the chil
JSR-252 Issue #111: Specified that a component must allow child components to be added to and removed from the child list of the currrent component, even though the child component returns null from getParent() -- Key: MYFACES-1265 URL: http://issues.apache.org/jira/browse/MYFACES-1265 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified that a component must allow child components to be added to and removed from the child list of the currrent component, even though the child component returns null from getParent(). See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=111 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1264) JSR-252 Issue #108: JSF in Java EE containers must validate the application resource file against the XML schema.
JSR-252 Issue #108: JSF in Java EE containers must validate the application resource file against the XML schema. - Key: MYFACES-1264 URL: http://issues.apache.org/jira/browse/MYFACES-1264 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified that JSF implementations that are not part of a Java EE technology-compliant implementation are required to validate the application resource file against the XML schema for structural correctness. Also specified that validation is recommended, but not required for JSF implementations that are not part of a Java EE technology compliant implementation. Please refer to Section 10.4.2 "Application Startup Behavior" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=108 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1263) JSR-252 Issue #105: Specified that for commandButton rendering, the "image" attribute value must not be escaped.
JSR-252 Issue #105: Specified that for commandButton rendering, the "image" attribute value must not be escaped. Key: MYFACES-1263 URL: http://issues.apache.org/jira/browse/MYFACES-1263 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specified that for commandButton rendering, the "image" attribute value must not be escaped. Specified that for graphicImage rendering, the "src" attribute must not be escaped. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=105 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1262) JSR-252 Issue #99: Specified Java EE 5 Generics usage where applicable.
JSR-252 Issue #99: Specified Java EE 5 Generics usage where applicable. --- Key: MYFACES-1262 URL: http://issues.apache.org/jira/browse/MYFACES-1262 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified Java EE 5 Generics usage where applicable. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=99 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1261) JSR-252 Issue #93: Added "escape" flag indicating the text of UISelectItem should be escaped when rendering.
JSR-252 Issue #93: Added "escape" flag indicating the text of UISelectItem should be escaped when rendering. Key: MYFACES-1261 URL: http://issues.apache.org/jira/browse/MYFACES-1261 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added "escape" flag indicating the text of UISelectItem should be escaped when rendering. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1260) JSR-252 Issue #13: Specified "by type" converter registration for BigDecimal and BigInteger
JSR-252 Issue #13: Specified "by type" converter registration for BigDecimal and BigInteger --- Key: MYFACES-1260 URL: http://issues.apache.org/jira/browse/MYFACES-1260 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified "by type" converter registration for BigDecimal and BigInteger https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=13 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MYFACES-1205) JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: must guarantee that if beforePhase() is called the afterPhase() must also be called.
[ http://issues.apache.org/jira/browse/MYFACES-1205?page=all ] Stan Silvert resolved MYFACES-1205: --- Fix Version: 1.1.2 Resolution: Fixed > JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: > must guarantee that if beforePhase() is called the afterPhase() must also be > called. > --- > > Key: MYFACES-1205 > URL: http://issues.apache.org/jira/browse/MYFACES-1205 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.1.2 > > Clarified the behavior of PhaseListener implementations in the following way: > they must guarantee that if "beforePhase()" is called, then "afterPhase()" > must also be called, regardless of any thrown exceptions. Please see Section > 11.3 "PhaseListener" for more specifics. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1205) JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: must guarantee that if beforePhase() is called the afterPhase() must also be called.
[ http://issues.apache.org/jira/browse/MYFACES-1205?page=comments#action_12373219 ] Stan Silvert commented on MYFACES-1205: --- Fixed in the 1.1 branch. This impl also fixes a problem I found with listeners in afterPhase being called in the wrong order. It should be a little faster because I was able to eliminate some synchronization. We now only have to get the list of listeners once during execute and once during render. > JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: > must guarantee that if beforePhase() is called the afterPhase() must also be > called. > --- > > Key: MYFACES-1205 > URL: http://issues.apache.org/jira/browse/MYFACES-1205 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Clarified the behavior of PhaseListener implementations in the following way: > they must guarantee that if "beforePhase()" is called, then "afterPhase()" > must also be called, regardless of any thrown exceptions. Please see Section > 11.3 "PhaseListener" for more specifics. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1258) JSR-252 Issue #160: Added and specified ResponseWriter.writeText method that takes a UIComponent argument.
JSR-252 Issue #160: Added and specified ResponseWriter.writeText method that takes a UIComponent argument. -- Key: MYFACES-1258 URL: http://issues.apache.org/jira/browse/MYFACES-1258 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added and specified ResponseWriter.writeText method that takes a UIComponent argument. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=160 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1257) JSR-252 Issue #155: Specified "columnClasses", "rowClasses" descriptions for panelGrid in renderkit docs.
JSR-252 Issue #155: Specified "columnClasses", "rowClasses" descriptions for panelGrid in renderkit docs. - Key: MYFACES-1257 URL: http://issues.apache.org/jira/browse/MYFACES-1257 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified "columnClasses", "rowClasses" descriptions for panelGrid in renderkit docs. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=155 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1256) JSR-252 Issue #154: Fixed FacesTag "name" attribute discrepency - made it a String (was ValueExpression).
JSR-252 Issue #154: Fixed FacesTag "name" attribute discrepency - made it a String (was ValueExpression). - Key: MYFACES-1256 URL: http://issues.apache.org/jira/browse/MYFACES-1256 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Fixed FacesTag "name" attribute discrepency - made it a String (was ValueExpression). See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=154 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1255) JSR-252 Issue #152: Specified EL coercion usage in API javadocs UISelectOne/UISelectMany (when items are compared in validation) and standard html renderkit docs during
JSR-252 Issue #152: Specified EL coercion usage in API javadocs UISelectOne/UISelectMany (when items are compared in validation) and standard html renderkit docs during encoding of select components. --- Key: MYFACES-1255 URL: http://issues.apache.org/jira/browse/MYFACES-1255 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified EL coercion usage in API javadocs UISelectOne/UISelectMany (when items are compared in validation) and standard html renderkit docs during encoding of select components. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=152 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1254) JSR-252 Issue #151: Specified standard converter for Enums
JSR-252 Issue #151: Specified standard converter for Enums -- Key: MYFACES-1254 URL: http://issues.apache.org/jira/browse/MYFACES-1254 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Specified standard converter for Enums See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=151 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1253) JSR-252 Issue #147: Clarified grammer with respect to component id.
JSR-252 Issue #147: Clarified grammer with respect to component id. --- Key: MYFACES-1253 URL: http://issues.apache.org/jira/browse/MYFACES-1253 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Clarified grammer with respect to component id. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=147 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1252) JSR-252 Issue #135: Support Java EE 5 enums as valid types
JSR-252 Issue #135: Support Java EE 5 enums as valid types -- Key: MYFACES-1252 URL: http://issues.apache.org/jira/browse/MYFACES-1252 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Support Java EE 5 enums as valid types See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=135 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1251) JSR-252 Issue #134: Backward compatability issues
JSR-252 Issue #134: Backward compatability issues - Key: MYFACES-1251 URL: http://issues.apache.org/jira/browse/MYFACES-1251 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=134 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1250) JSR-252 Issue #131: Specified that a compliant implementation must allow the registration of a converter for class java.lang.String and java.lang.String.TYPE that will b
JSR-252 Issue #131: Specified that a compliant implementation must allow the registration of a converter for class java.lang.String and java.lang.String.TYPE that will be used to convert values for these types. -- Key: MYFACES-1250 URL: http://issues.apache.org/jira/browse/MYFACES-1250 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specified that a compliant implementation must allow the registration of a converter for class java.lang.String and java.lang.String.TYPE that will be used to convert values for these types. See See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=131 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1249) JSR-252 Issue #124: Clarified renderkit docs with repsect to graphicImage "alt" attribute.
JSR-252 Issue #124: Clarified renderkit docs with repsect to graphicImage "alt" attribute. -- Key: MYFACES-1249 URL: http://issues.apache.org/jira/browse/MYFACES-1249 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Clarified renderkit docs with repsect to graphicImage "alt" attribute. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=124 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1248) JSR-252 Issue #123: Clarified renderkit docs with respect to dataTable attribute rendering
JSR-252 Issue #123: Clarified renderkit docs with respect to dataTable attribute rendering -- Key: MYFACES-1248 URL: http://issues.apache.org/jira/browse/MYFACES-1248 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Clarified renderkit docs with respect to dataTable attribute rendering See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=123 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1247) JSR-252 Issue #120: Specified in the renderkit docs that commandButton rendering can generate javascript for "onclick" attribute.
JSR-252 Issue #120: Specified in the renderkit docs that commandButton rendering can generate javascript for "onclick" attribute. - Key: MYFACES-1247 URL: http://issues.apache.org/jira/browse/MYFACES-1247 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified in the renderkit docs that commandButton rendering can generate javascript for "onclick" attribute. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=120 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1246) JSR-252 Issue #119: implementations running in a JSR-250 container have their managed bean methods annotated with @PostConstruct be called after the object is instantiat
JSR-252 Issue #119: implementations running in a JSR-250 container have their managed bean methods annotated with @PostConstruct be called after the object is instantiated, and after injection is performed, but before the bean is placed into scope. Key: MYFACES-1246 URL: http://issues.apache.org/jira/browse/MYFACES-1246 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specified that implementations running in a JSR-250 compliant container have their managed bean methods annotated with @PostConstruct be called after the object is instantiated, and after injection is performed, but before the bean is placed into scope. Specified that methods annotated with @PreDestroy be called when the scope for the bean is ending. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=252 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1245) JSR-252 Issue #98: Specified that "SelectManyCheckboxListRenderer" and "RadioRenderer" must render the "label" element after the "input" element for each "SelectItem".
JSR-252 Issue #98: Specified that "SelectManyCheckboxListRenderer" and "RadioRenderer" must render the "label" element after the "input" element for each "SelectItem". --- Key: MYFACES-1245 URL: http://issues.apache.org/jira/browse/MYFACES-1245 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specified that "SelectManyCheckboxListRenderer" and "RadioRenderer" must render the "label" element after the "input" element for each "SelectItem". Specified that the "label" element must refer to the "input" element using the "for" attribute. Please see Section 8.5 "Standard HTML RenderKit Implementation" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=98 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1244) JSR-252 Issue #95: Allow multiple instances of FacesServlet in a single webapp, mapped with different URI mappings, to use different implementations of Lifecycle
JSR-252 Issue #95: Allow multiple instances of FacesServlet in a single webapp, mapped with different URI mappings, to use different implementations of Lifecycle - Key: MYFACES-1244 URL: http://issues.apache.org/jira/browse/MYFACES-1244 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Allow multiple instances of FacesServlet in a single webapp, mapped with different URI mappings, to use different implementations of Lifecycle by allowing the lifecycle-id to be specified as an init-param in addition to the existing way of specifying it as a context-param. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=95 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1243) JSR-252 Issue #87: Modified specification for the setVariableResolver() and setPropertyResolver() methods on Application to state that they may not be called after the a
JSR-252 Issue #87: Modified specification for the setVariableResolver() and setPropertyResolver() methods on Application to state that they may not be called after the app has served any requests. Key: MYFACES-1243 URL: http://issues.apache.org/jira/browse/MYFACES-1243 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Modified specification for the setVariableResolver() and setPropertyResolver() methods on Application to state that they may not be called after the app has served any requests. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=87 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1242) JSR-252 Issue #75: Added "getRequestContentType" and "getResponseContentType" to ExternalContext.
[ http://issues.apache.org/jira/browse/MYFACES-1242?page=comments#action_12373208 ] Stan Silvert commented on MYFACES-1242: --- I have the code for this. I'm just waiting for the new branch. > JSR-252 Issue #75: Added "getRequestContentType" and "getResponseContentType" > to ExternalContext. > - > > Key: MYFACES-1242 > URL: http://issues.apache.org/jira/browse/MYFACES-1242 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Added "getRequestContentType" and "getResponseContentType" to ExternalContext. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1242) JSR-252 Issue #75: Added "getRequestContentType" and "getResponseContentType" to ExternalContext.
JSR-252 Issue #75: Added "getRequestContentType" and "getResponseContentType" to ExternalContext. - Key: MYFACES-1242 URL: http://issues.apache.org/jira/browse/MYFACES-1242 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Added "getRequestContentType" and "getResponseContentType" to ExternalContext. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1241) JSR-252 Issue #86: Specified that "OutputLinkRenderer" must render the "name" attribute with the same value as the "id" attribute.
JSR-252 Issue #86: Specified that "OutputLinkRenderer" must render the "name" attribute with the same value as the "id" attribute. -- Key: MYFACES-1241 URL: http://issues.apache.org/jira/browse/MYFACES-1241 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specified that "OutputLinkRenderer" must render the "name" attribute with the same value as the "id" attribute. Please see Section 8.5 "Standard HTML RenderKit Imiplementation" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=86 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1240) JSR-252 Issue #85: Add new tag: f:setPropertyActionListener. Useful for pushing values into managed beans without allowing modification of the value.
JSR-252 Issue #85: Add new tag: f:setPropertyActionListener. Useful for pushing values into managed beans without allowing modification of the value. -- Key: MYFACES-1240 URL: http://issues.apache.org/jira/browse/MYFACES-1240 Project: MyFaces Core Type: New Feature Reporter: Stan Silvert Add new tag: f:setPropertyActionListener. Useful for pushing values into managed beans without allowing modification of the value. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=85 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1239) JSR-252 Issue #84: Added rendered attribute to the core f:verbatim tag.
JSR-252 Issue #84: Added rendered attribute to the core f:verbatim tag. --- Key: MYFACES-1239 URL: http://issues.apache.org/jira/browse/MYFACES-1239 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added rendered attribute to the core f:verbatim tag. Please see Section 9.4 "JSF Core Tag Library" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=84 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1238) JSR-252 Issue #82: Added new feature, the ability to resolve ResourceBundles via the EL without the use of the tag.
JSR-252 Issue #82: Added new feature, the ability to resolve ResourceBundles via the EL without the use of the tag. -- Key: MYFACES-1238 URL: http://issues.apache.org/jira/browse/MYFACES-1238 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added new feature, the ability to resolve ResourceBundles via the EL without the use of the tag. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=82 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1237) JSR-252 Issue #81: Enable the message displayed for "required" validation, conversion, and validation to be overridden by the page author (JSP or non-JSP).
JSR-252 Issue #81: Enable the message displayed for "required" validation, conversion, and validation to be overridden by the page author (JSP or non-JSP). --- Key: MYFACES-1237 URL: http://issues.apache.org/jira/browse/MYFACES-1237 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Enable the message displayed for "required" validation, conversion, and validation to be overridden by the page author (JSP or non-JSP). See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=81 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1236) JSR-252 Issue #80: Specify that the JSF Core Tag Library must not contain any tags that cause JavaScript to be rendered to the client.
JSR-252 Issue #80: Specify that the JSF Core Tag Library must not contain any tags that cause JavaScript to be rendered to the client. -- Key: MYFACES-1236 URL: http://issues.apache.org/jira/browse/MYFACES-1236 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specify that the JSF Core Tag Library must not contain any tags that cause JavaScript to be rendered to the client. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=80 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1235) JSR-252 Issue #78: Added a more "user-friendly" default error message for UIInput "update model".
JSR-252 Issue #78: Added a more "user-friendly" default error message for UIInput "update model". - Key: MYFACES-1235 URL: http://issues.apache.org/jira/browse/MYFACES-1235 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Added a more "user-friendly" default error message for UIInput "update model". Please see Section 2.5.2.4 "Localized Application Messages" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=78 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1234) JSR-252 Issue #74: Added "disabled" property to "outputLink" and "commandLink".
JSR-252 Issue #74: Added "disabled" property to "outputLink" and "commandLink". --- Key: MYFACES-1234 URL: http://issues.apache.org/jira/browse/MYFACES-1234 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added "disabled" property to "outputLink" and "commandLink". Please see Section 8.5 "Standard HTML RenderKit Implementation" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=74 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1233) JSR-252 Issue #73: Added a new FacesException - "javax.faces.application.ViewExpiredException"
JSR-252 Issue #73: Added a new FacesException - "javax.faces.application.ViewExpiredException" -- Key: MYFACES-1233 URL: http://issues.apache.org/jira/browse/MYFACES-1233 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added a new FacesException - "javax.faces.application.ViewExpiredException". Specified that the implementation must throw this exception when an attempt to restore a view results in failure on postback. Please see Section 2.2.1 "Restore View" for more details. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=73 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1232) JSR-252 Issue #72: Improve XHTML compliance by rendering both "lang" and "xml:lang" attributes.
JSR-252 Issue #72: Improve XHTML compliance by rendering both "lang" and "xml:lang" attributes. --- Key: MYFACES-1232 URL: http://issues.apache.org/jira/browse/MYFACES-1232 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Improve XHTML compliance by rendering both "lang" and "xml:lang" attributes. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=72 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1231) JSR-252 Issue #69: Permit the passing of a null value to SelectItem.setValue().
JSR-252 Issue #69: Permit the passing of a null value to SelectItem.setValue(). --- Key: MYFACES-1231 URL: http://issues.apache.org/jira/browse/MYFACES-1231 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Permit the passing of a null value to SelectItem.setValue(). See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=69 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1230) JSR-252 Issue #68: Specify that the component tree may be manipulated throughout the request processing lifecycle, except during render.
JSR-252 Issue #68: Specify that the component tree may be manipulated throughout the request processing lifecycle, except during render. Key: MYFACES-1230 URL: http://issues.apache.org/jira/browse/MYFACES-1230 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specify that the component tree may be manipulated throughout the request processing lifecycle, except during render. Please see Section 2.2.6 "Render Response" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=68 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1229) JSR-252 Issue #67: Allow the resetting of an input component's value by introducing a resetValue() method on UIInput
JSR-252 Issue #67: Allow the resetting of an input component's value by introducing a resetValue() method on UIInput Key: MYFACES-1229 URL: http://issues.apache.org/jira/browse/MYFACES-1229 Project: MyFaces Core Type: New Feature Reporter: Stan Silvert Allow the resetting of an input component's value by introducing a resetValue() method on UIInput See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=67 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1228) JSR-252 Issue #66: Specified that "FormRenderer" must render the "name" attribute with the same value as the "id" attribute.
JSR-252 Issue #66: Specified that "FormRenderer" must render the "name" attribute with the same value as the "id" attribute. -- Key: MYFACES-1228 URL: http://issues.apache.org/jira/browse/MYFACES-1228 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Specified that "FormRenderer" must render the "name" attribute with the same value as the "id" attribute. Please see Section 8.5 "Standard HTML RenderKit Implementation" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=66 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1227) JSR-252 Issue #65: Added standard converter messages. Please see Section 2.5.2.4 "Localized Application Messages" for more details.
JSR-252 Issue #65: Added standard converter messages. Please see Section 2.5.2.4 "Localized Application Messages" for more details. Key: MYFACES-1227 URL: http://issues.apache.org/jira/browse/MYFACES-1227 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added standard converter messages. Please see Section 2.5.2.4 "Localized Application Messages" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=65 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1226) JSR-252 Issue #59: Avoid EL expression evaluation for "value" attribute on "AttributeTag". "AttributeTag" now passes the expression to UIComponent for evaluation.
JSR-252 Issue #59: Avoid EL expression evaluation for "value" attribute on "AttributeTag". "AttributeTag" now passes the expression to UIComponent for evaluation. --- Key: MYFACES-1226 URL: http://issues.apache.org/jira/browse/MYFACES-1226 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Avoid EL expression evaluation for "value" attribute on "AttributeTag". "AttributeTag" now passes the expression to UIComponent for evaluation. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=59 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1225) JSR-252 Issue #58: Enabled "protected" access to internal "DataModel" in UIData
JSR-252 Issue #58: Enabled "protected" access to internal "DataModel" in UIData --- Key: MYFACES-1225 URL: http://issues.apache.org/jira/browse/MYFACES-1225 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Enabled "protected" access to internal "DataModel" in UIData See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=58 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1224) JSR-252 Issue #55: For postback requests, in the "RestoreViewPhase", during ValueExpression examination for each component, specify that calling setValue() on each Value
JSR-252 Issue #55: For postback requests, in the "RestoreViewPhase", during ValueExpression examination for each component, specify that calling setValue() on each ValueExpression should be done "parent-first" - Key: MYFACES-1224 URL: http://issues.apache.org/jira/browse/MYFACES-1224 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert For postback requests, in the "RestoreViewPhase", during ValueExpression examination for each component in the component tree, specify that calling the setValue() method on each ValueExpression, should be done in a "parent-first" fashion, calling the setValue() method and then traversing the children. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=55 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1223) JSR-252 Issue #54: Added new extension elements to the Faces XML schema.
JSR-252 Issue #54: Added new extension elements to the Faces XML schema. Key: MYFACES-1223 URL: http://issues.apache.org/jira/browse/MYFACES-1223 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Added new extension elements to the Faces XML schema. Please see Section 1.1 "XML Schema Definition". Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=54 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1222) JSR-252 Issue #51: Allow implementations to check for the presence of a servlet-class definition in a web app deployment descriptor as a means to abort the configuration
JSR-252 Issue #51: Allow implementations to check for the presence of a servlet-class definition in a web app deployment descriptor as a means to abort the configuration and save startup time. Key: MYFACES-1222 URL: http://issues.apache.org/jira/browse/MYFACES-1222 Project: MyFaces Core Type: Improvement Components: JSR-252 Reporter: Stan Silvert Clarify the specification with respect to "Application Startup Behavior". Allow implementations to check for the presence of a servlet-class definition in a web app deployment descriptor as a means to abort the configuration and save startup time. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=51 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1221) JSR-252 Issue #50: Allow an application to specify multiple render kits by introducing an optional "renderKitId" attribute on "".
JSR-252 Issue #50: Allow an application to specify multiple render kits by introducing an optional "renderKitId" attribute on "". - Key: MYFACES-1221 URL: http://issues.apache.org/jira/browse/MYFACES-1221 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Allow an application to specify multiple render kits by introducing an optional "renderKitId" attribute on "". It is no longer required to write a customer ViewHandler to incorporate a different render kit. Please refer to Section 8.3 "ResponseStateManager" and Section 9.4.20 "" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=50 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1220) JSR-252 Issue # 48: Specify the algorithm used for client id generation as well as provide a way to allow the page author to specify exactly what the client id should be
JSR-252 Issue # 48: Specify the algorithm used for client id generation as well as provide a way to allow the page author to specify exactly what the client id should be, and preventing Faces from altering it. - Key: MYFACES-1220 URL: http://issues.apache.org/jira/browse/MYFACES-1220 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Specify the algorithm used for client id generation as well as provide a way to allow the page author to specify exactly what the client id should be, and preventing Faces from altering it. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=48 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1219) JSR-252 Issue # 47: Introduced a mechanism to detect if a request is a postback.
JSR-252 Issue # 47: Introduced a mechanism to detect if a request is a postback. Key: MYFACES-1219 URL: http://issues.apache.org/jira/browse/MYFACES-1219 Project: MyFaces Core Type: New Feature Reporter: Stan Silvert Introduced a mechanism to detect if a request is a postback. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=47 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1218) JSR-252 Issue #45: Avoided concurrent read issues by using a java.util.HashMap instead of java.util.WeakHashMap for a component's Property Descriptor Map
JSR-252 Issue #45: Avoided concurrent read issues by using a java.util.HashMap instead of java.util.WeakHashMap for a component's Property Descriptor Map - Key: MYFACES-1218 URL: http://issues.apache.org/jira/browse/MYFACES-1218 Project: MyFaces Core Type: Bug Components: JSR-252 Reporter: Stan Silvert Avoided concurrent read issues by using a java.util.HashMap instead of java.util.WeakHashMap for a component's Property Descriptor Map. This also fixes the performance problem as identified in the forum. Please refer the the Property Descriptor methods and the constructor in javax.faces.component.UIComponentBase. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=45 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1217) JSR-252 Issue #43: Migrated over to using XML Schema (from DTD) for configuration file validation.
JSR-252 Issue #43: Migrated over to using XML Schema (from DTD) for configuration file validation. -- Key: MYFACES-1217 URL: http://issues.apache.org/jira/browse/MYFACES-1217 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Migrated over to using XML Schema (from DTD) for configuration file validation. Please see Section 1.1 "XML Schema Definition". Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=43 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1216) JSR-252 Issue #35: Provided a new facet for DataTable Renderer that allows the rendering of a table "caption" element immediately following the "table" element.
JSR-252 Issue #35: Provided a new facet for DataTable Renderer that allows the rendering of a table "caption" element immediately following the "table" element. Key: MYFACES-1216 URL: http://issues.apache.org/jira/browse/MYFACES-1216 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Provided a new facet for DataTable Renderer that allows the rendering of a table "caption" element immediately following the "table" element. Also provided style sheet attributes for this new element. Please see Section 8.5 "Standard HTML RenderKit Implementation" for a description of this component. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=35 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1215) JSR-252 Issue #30: Make the "commandButton" "image" attribute render the same as the "graphicImage" "img" attribute for consistency.
JSR-252 Issue #30: Make the "commandButton" "image" attribute render the same as the "graphicImage" "img" attribute for consistency. Key: MYFACES-1215 URL: http://issues.apache.org/jira/browse/MYFACES-1215 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Make the "commandButton" "image" attribute render the same as the "graphicImage" "img" attribute for consistency. Please see Section 8.5 "Standard HTML RenderKit Implementation" for more information. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=30 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1214) JSR-252 Issue #29: Allow the use of user-defined "onclick" Javascript on CommandLink
JSR-252 Issue #29: Allow the use of user-defined "onclick" Javascript on CommandLink Key: MYFACES-1214 URL: http://issues.apache.org/jira/browse/MYFACES-1214 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Allow the use of user-defined "onclick" Javascript on CommandLink See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=29 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1213) JSR-252 Issue #27: ", "") if the "layout" attribute is "list" or the "layout" attribute is not specified.
JSR-252 Issue #27: ", "") if the "layout" attribute is "list" or the "layout" attribute is not specified. -- Key: MYFACES-1213 URL: http://issues.apache.org/jira/browse/MYFACES-1213 Project: MyFaces Core Type: Bug Components: JSR-252 Reporter: Stan Silvert ", "") if the "layout" attribute is "list" or the "layout" attribute is not specified. If the "layout" is "table" HTML "table" element is rendered instead of an outer "span". Please see Section 8.5 "Standard HTML RenderKit Implementation" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=27 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1212) JSR-252 Issue #21: Provide additional "binding" attribute for the core Converter, Listener, and Validator tags that would be used as a ValueExpression to alternatively c
JSR-252 Issue #21: Provide additional "binding" attribute for the core Converter, Listener, and Validator tags that would be used as a ValueExpression to alternatively create the instance --- Key: MYFACES-1212 URL: http://issues.apache.org/jira/browse/MYFACES-1212 Project: MyFaces Core Type: Bug Components: JSR-252 Reporter: Stan Silvert Provide additional "binding" attribute for the core Converter, Listener, and Validator tags that would be used as a ValueExpression to alternatively create the Converter, Listener, or Validator instance. Please see Section 9.4 "JSF Core Tag Library" for more details. Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=21 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1205) JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: must guarantee that if beforePhase() is called the afterPhase() must also be called.
[ http://issues.apache.org/jira/browse/MYFACES-1205?page=comments#action_12373174 ] Stan Silvert commented on MYFACES-1205: --- Sounds good. I'll commit after I do a little more testing. > JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: > must guarantee that if beforePhase() is called the afterPhase() must also be > called. > --- > > Key: MYFACES-1205 > URL: http://issues.apache.org/jira/browse/MYFACES-1205 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Clarified the behavior of PhaseListener implementations in the following way: > they must guarantee that if "beforePhase()" is called, then "afterPhase()" > must also be called, regardless of any thrown exceptions. Please see Section > 11.3 "PhaseListener" for more specifics. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1211) JSR-252 Issue #20: Specify that the event queue should be cleared after each phase (except for RestoreViewPhase and RenderResponse) if responseComplete or renderRespon
[ http://issues.apache.org/jira/browse/MYFACES-1211?page=comments#action_12373158 ] Stan Silvert commented on MYFACES-1211: --- It looks like MyFaces is already doing this. > JSR-252 Issue #20: Specify that the event queue should be cleared after each > phase (except for RestoreViewPhase and RenderResponse) if responseComplete or > renderResponse has been set > -- > > Key: MYFACES-1211 > URL: http://issues.apache.org/jira/browse/MYFACES-1211 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Specify that the event queue should be cleared after each phase (except for > RestoreViewPhase and RenderResponse) if responseComplete or renderResponse > has been set on FacesContext. > See > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=20 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1211) JSR-252 Issue #20: Specify that the event queue should be cleared after each phase (except for RestoreViewPhase and RenderResponse) if responseComplete or renderResponse
JSR-252 Issue #20: Specify that the event queue should be cleared after each phase (except for RestoreViewPhase and RenderResponse) if responseComplete or renderResponse has been set -- Key: MYFACES-1211 URL: http://issues.apache.org/jira/browse/MYFACES-1211 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Specify that the event queue should be cleared after each phase (except for RestoreViewPhase and RenderResponse) if responseComplete or renderResponse has been set on FacesContext. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=20 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1210) JSR-252 Issue #18: behavior clarifications
[ http://issues.apache.org/jira/browse/MYFACES-1210?page=comments#action_12373156 ] Stan Silvert commented on MYFACES-1210: --- I have the code for this. I'm just waiting for the new branch to open. > JSR-252 Issue #18: behavior clarifications > - > > Key: MYFACES-1210 > URL: http://issues.apache.org/jira/browse/MYFACES-1210 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > When a resource lookup is done on the java.util.Map (loaded from > ) using a key, and the key is not found in the Map, return the > literal string ???KEY??? where KEY is the key being looked up in the Map > (instead of throwing a MissingResourceException). Throw a JspException if > the named bundle identified by does not exist. Please see > Section 9.4.7 "". > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=18 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1210) JSR-252 Issue #18: behavior clarifications
JSR-252 Issue #18: behavior clarifications - Key: MYFACES-1210 URL: http://issues.apache.org/jira/browse/MYFACES-1210 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert When a resource lookup is done on the java.util.Map (loaded from ) using a key, and the key is not found in the Map, return the literal string ???KEY??? where KEY is the key being looked up in the Map (instead of throwing a MissingResourceException). Throw a JspException if the named bundle identified by does not exist. Please see Section 9.4.7 "". Also see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=18 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1209) JSR-252 Issue #17: Introduced a new optional "layout" attribute on the "PanelGroup" component that controls the rendering of either a "div" or "span" HTML element.
JSR-252 Issue #17: Introduced a new optional "layout" attribute on the "PanelGroup" component that controls the rendering of either a "div" or "span" HTML element. --- Key: MYFACES-1209 URL: http://issues.apache.org/jira/browse/MYFACES-1209 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Introduced a new optional "layout" attribute on the "PanelGroup" component that controls the rendering of either a "div" or "span" HTML element. Please see Section 8.5 "Standard HTML RenderKit Implementation" for more details. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=17 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1208) JSR-252 Issue #16: Provided additional I18n attributes "dir" and "land" for the tags , , , and .
JSR-252 Issue #16: Provided additional I18n attributes "dir" and "land" for the tags , , , and . - Key: MYFACES-1208 URL: http://issues.apache.org/jira/browse/MYFACES-1208 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Provided additional I18n attributes "dir" and "land" for the tags , , , and . Please see Section 8.5 "Standard HTML RenderKit Implementation" for descriptions of these components. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=16 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1207) JSR-252 Issue #15: Enhanced the usage of the "Decorator Pattern" for ViewHandler, StateManager and ResponseWriter
[ http://issues.apache.org/jira/browse/MYFACES-1207?page=comments#action_12373154 ] Stan Silvert commented on MYFACES-1207: --- I have the code for this. I'm just waiting for the new branch to open. > JSR-252 Issue #15: Enhanced the usage of the "Decorator Pattern" for > ViewHandler, StateManager and ResponseWriter > - > > Key: MYFACES-1207 > URL: http://issues.apache.org/jira/browse/MYFACES-1207 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Enhanced the usage of the "Decorator Pattern" for ViewHandler, StateManager > and ResponseWriter classes by providing abstract wrapper classes to make it > easier to override a subset of the total methods for those classes. Please > see Section 8.5 "Standard HTML RenderKit Implementation" for descriptions of > those components. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=15 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1207) JSR-252 Issue #15: Enhanced the usage of the "Decorator Pattern" for ViewHandler, StateManager and ResponseWriter
JSR-252 Issue #15: Enhanced the usage of the "Decorator Pattern" for ViewHandler, StateManager and ResponseWriter - Key: MYFACES-1207 URL: http://issues.apache.org/jira/browse/MYFACES-1207 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Enhanced the usage of the "Decorator Pattern" for ViewHandler, StateManager and ResponseWriter classes by providing abstract wrapper classes to make it easier to override a subset of the total methods for those classes. Please see Section 8.5 "Standard HTML RenderKit Implementation" for descriptions of those components. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=15 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1206) JSR-252 Issue #11: Provide a unique window identifier to accomodate applications that have multiple instances of the same view, but perhaps in different browser windows
JSR-252 Issue #11: Provide a unique window identifier to accomodate applications that have multiple instances of the same view, but perhaps in different browser windows or frames. --- Key: MYFACES-1206 URL: http://issues.apache.org/jira/browse/MYFACES-1206 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Provide a unique window identifier (in addition to "viewid") to accomodate applications that have multiple instances of the same view, but perhaps in different browser windows or frames. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=11 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-1205) JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: must guarantee that if beforePhase() is called the afterPhase() must also be called.
[ http://issues.apache.org/jira/browse/MYFACES-1205?page=comments#action_12373152 ] Stan Silvert commented on MYFACES-1205: --- I finished the code for this. I'm just waiting for the branch to open up. > JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: > must guarantee that if beforePhase() is called the afterPhase() must also be > called. > --- > > Key: MYFACES-1205 > URL: http://issues.apache.org/jira/browse/MYFACES-1205 > Project: MyFaces Core > Type: New Feature > Components: JSR-252 > Reporter: Stan Silvert > Assignee: Stan Silvert > > Clarified the behavior of PhaseListener implementations in the following way: > they must guarantee that if "beforePhase()" is called, then "afterPhase()" > must also be called, regardless of any thrown exceptions. Please see Section > 11.3 "PhaseListener" for more specifics. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1205) JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: must guarantee that if beforePhase() is called the afterPhase() must also be called.
JSR-252 Issue #9: Clarified the behavior of PhaseListener implementations: must guarantee that if beforePhase() is called the afterPhase() must also be called. --- Key: MYFACES-1205 URL: http://issues.apache.org/jira/browse/MYFACES-1205 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Assigned to: Stan Silvert Clarified the behavior of PhaseListener implementations in the following way: they must guarantee that if "beforePhase()" is called, then "afterPhase()" must also be called, regardless of any thrown exceptions. Please see Section 11.3 "PhaseListener" for more specifics. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1204) JSR-252 Issue #8: Made UIViewRoot a source of PhaseEvent(s) for all phases of the request processing lifecycle except RestoreView.
JSR-252 Issue #8: Made UIViewRoot a source of PhaseEvent(s) for all phases of the request processing lifecycle except RestoreView. Key: MYFACES-1204 URL: http://issues.apache.org/jira/browse/MYFACES-1204 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Made UIViewRoot a source of PhaseEvent(s) for all phases of the request processing lifecycle except RestoreView. Provided additional "before" and "after" phase listener attributes for the tag. Please see Section 4.1.17 "UIViewRoot" for more details. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-1203) JSR-252 Issue #6: Introduced a new optional "label" attribute for input components that will provide an association between a component, and the message that the compone
JSR-252 Issue #6: Introduced a new optional "label" attribute for input components that will provide an association between a component, and the message that the component (indirectly) produced. -- Key: MYFACES-1203 URL: http://issues.apache.org/jira/browse/MYFACES-1203 Project: MyFaces Core Type: New Feature Components: JSR-252 Reporter: Stan Silvert Introduced a new optional "label" attribute for input components that will provide an association between a component, and the message that the component (indirectly) produced. Please refer to Section 8.5 "Standard HTML RenderKit Implementation" and Section 2.5.2.4 "Localized Application Messages" for more details. See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
