November 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-417) Make <s:validate> enter Process Validations phase

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-417?page=all ] Gavin King closed JBSEAM-417. ----------------------------- Resolution: Won't Fix I don't see anyway to improve the current situation here w/o hacking the JSF implementation. BTW, I think you have misunderstood the current behavior. Followup in IM/email, not JIRA. > Make <s:validate> enter Process Validations phase > ------------------------------------------------- > > Key: JBSEAM-417 > URL: http://jira.jboss.com/jira/browse/JBSEAM-417 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Christian Bauer > Priority: Minor > > Currently you can't completely rely on Hibernate Validator for input validation, at least one form field needs required="true". Otherwise the Process Validations phase is never reached, and <s:validate> doesn't run either. Basically, the @NotNull annotation on the domain model can't really be used in Seam. > Would be nice to have, because there is no way to easily customize the required="true" error message on a per-field basis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-384) Remove renderParameters component

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-384?page=all ] Gavin King closed JBSEAM-384. ----------------------------- Fix Version/s: 1.1.0.BETA2 Resolution: Done apparently I already did this :) > Remove renderParameters component > --------------------------------- > > Key: JBSEAM-384 > URL: http://jira.jboss.com/jira/browse/JBSEAM-384 > Project: JBoss Seam > Issue Type: Task > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1.0.BETA2 > > > This isn't needed anymore. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-95) Have Seam handle "concurrent access to stateful bean" exceptions elegantly.

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-95?page=all ] Gavin King closed JBSEAM-95. ---------------------------- Fix Version/s: 1.1.0.BETA2 Resolution: Done Assignee: Gavin King Can do it using exceptions.xml, > Have Seam handle "concurrent access to stateful bean" exceptions elegantly. > --------------------------------------------------------------------------- > > Key: JBSEAM-95 > URL: http://jira.jboss.com/jira/browse/JBSEAM-95 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Affects Versions: 1.0 beta 1 > Reporter: Ryan Dewell > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1.0.BETA2 > > > See the rejected issue: EJBTHREE-313 > This can be duplicated in the demo app (or any other app), by simply double clicking a commandLink/commandButton. If Seam could detect the double postback, and just ignore one of them, that would be ideal. Perhaps JSF 1.2 provides better postback detection handling? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-406) debug.seam causes exception

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-406?page=all ] Gavin King closed JBSEAM-406. ----------------------------- Fix Version/s: 1.1.0.BETA2 Resolution: Done this was already fixed > debug.seam causes exception > --------------------------- > > Key: JBSEAM-406 > URL: http://jira.jboss.com/jira/browse/JBSEAM-406 > Project: JBoss Seam > Issue Type: Bug > Components: Tools > Affects Versions: 1.1.0.BETA1 > Environment: jboss 4.0.5CR1 with Seam CVS and RC9 of EJB3 > Reporter: jarkko Lietolahti > Fix For: 1.1.0.BETA2 > > > Accessing http://localhost:8080/seamApp/debug.seam causes the following exception in log (and 404 on the brorwser). > 150438 16:57:07,871 ERROR [PhaseListenerManager] Exception in PhaseListener RENDER_RESPONSE(6) beforePhase. > javax.faces.el.PropertyNotFoundException: /file:/home/jarkko/seam-workspace/tear/src/tc3.ear/tc3Web.war/WEB-INF/lib/jboss-seam-debug.jar!/META-INF/debug.xhtml @63,90 rendered="#{empty org$jboss$seam$debug$contexts.conversationEntries}": Bean: org.jboss.seam.debug.Contexts$$EnhancerByCGLIB$$fb7d5aec, property: conversationEntries > at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:58) > at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:1076) > at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:231) > at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239) > at org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:50) > at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70) > at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:33) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:153) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-446) s:link linkStyle="button" not rendering all attributes

by Bradley Smith (JIRA)

s:link linkStyle="button" not rendering all attributes ------------------------------------------------------ Key: JBSEAM-446 URL: http://jira.jboss.com/jira/browse/JBSEAM-446 Project: JBoss Seam Issue Type: Bug Components: Core, JSF Affects Versions: 1.1.0.BETA1 Reporter: Bradley Smith The s:link tag is not rendering javascript event-handler attributes correctly: Example: <s:link action="/index.xhtml" propagation="end" linkStyle="button" value=" Home " buttonClass="xsmallButton" onmouseover="this.className='xsmallButton2'" onmouseout="this.className='xsmallButton'"/> Produces: <input type="button" id="_id20" onclick="location.href='/access/WEB-INF/views/error_template.seam?actionOutcome=%2Findex.xhtml&conversationPropagation=end'" value=" Home " class="xsmallButton" /> notice the onmouseover and onmouseout event-handler attributes are missing in the rendered markup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-161) Calendaring/scheduling

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-161?page=all ] Gavin King updated JBSEAM-161: ------------------------------ Fix Version/s: 1.2.0.BETA1 > Calendaring/scheduling > ---------------------- > > Key: JBSEAM-161 > URL: http://jira.jboss.com/jira/browse/JBSEAM-161 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.2.0.BETA1 > > > We need calendared events to be processed in the scope of a Seam context. > We need to investigate what timer solutions make sense: jBPM, Quartz, EJB timers? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-186) Exception event listeners.

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-186?page=all ] Gavin King closed JBSEAM-186. ----------------------------- Fix Version/s: 1.1.0.BETA2 Resolution: Done Already done. > Exception event listeners. > -------------------------- > > Key: JBSEAM-186 > URL: http://jira.jboss.com/jira/browse/JBSEAM-186 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.BETA2 > > > Add an exceptions.xml file in WEB-INF that provides mappings to actions: > <exceptions> > <exception class="java.lang.IllegalStateException" action="#{exceptions.handleIllegalState}"/> > <exception class="java.lang.Throwable" view-id="/error.jsp"/> > ... > </exceptions> > Only the most-specific action for an exception type would be invoked. > Not sure how easy it is to implement this right now, since apparently JSF nastily swallows/wraps some exceptions. Need to investigate. (Perhaps what the action around the EJBs, not the JSF lifecycle.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-330) currentDate, currentTime, currentTimestamp components

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-330?page=all ] Gavin King closed JBSEAM-330. ----------------------------- Fix Version/s: 1.1.0.BETA1 Resolution: Done This was done already. > currentDate, currentTime, currentTimestamp components > ----------------------------------------------------- > > Key: JBSEAM-330 > URL: http://jira.jboss.com/jira/browse/JBSEAM-330 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.BETA1 > > > Its useful to do: #{currentDate} and #{currentTime} in EL > Its also useful to be able to do CurrentTimestamp.instance() in business code working with entities. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-80) Allow @In("#{jstl expression}")

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-80?page=all ] Gavin King updated JBSEAM-80: ----------------------------- Fix Version/s: 1.0 beta 2 > Allow @In("#{jstl expression}") > ------------------------------- > > Key: JBSEAM-80 > URL: http://jira.jboss.com/jira/browse/JBSEAM-80 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.0 beta 2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-261) Use an EJB3 interceptor stack instead of a single SeamInterceptor

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-261?page=all ] Gavin King closed JBSEAM-261. ----------------------------- Resolution: Rejected No, for various reasons :) > Use an EJB3 interceptor stack instead of a single SeamInterceptor > ----------------------------------------------------------------- > > Key: JBSEAM-261 > URL: http://jira.jboss.com/jira/browse/JBSEAM-261 > Project: JBoss Seam > Issue Type: Feature Request > Components: EJB3 > Reporter: Gavin King > Assigned To: Gavin King > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2006