March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2705) RichFaces stylesheets return empty when page security is set

by cbonami (JIRA)

RichFaces stylesheets return empty when page security is set ------------------------------------------------------------ Key: JBSEAM-2705 URL: http://jira.jboss.com/jira/browse/JBSEAM-2705 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.0.GA Environment: JBoss 4.2.2.GA; Leopard OS X 10.5.2; SEAM 2.0.0.GA Reporter: cbonami Priority: Critical Please look at this issue: http://jira.jboss.com/jira/browse/RF-2316 There's an incompatibility between RichFaces and SEAM. The guys from RichFaces tell me it's a SEAM bug. Basically, in order to avoid the bug, you have to switch off security (pages.xml: ... login-required="false") in order to get the RichFaces stylesheets rendered by your browser. If security is set on, the generated richfaces stylesheets return blank, and the page doesn't get rendered well. Switching off page security is not a long-term solution. -- 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

16 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1735) Pages.getStringValuesFromModel throws ConcurrentModificationException

by Darryl Smith (JIRA)

Pages.getStringValuesFromModel throws ConcurrentModificationException --------------------------------------------------------------------- Key: JBSEAM-1735 URL: http://jira.jboss.com/jira/browse/JBSEAM-1735 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Darryl Smith I don't see how this is happening from looking at the code, but occasionally I get a ConcurrentModificationException from Pages.getStringValuesFromModel. I can not reproduce it on demand. Only place that access this collection is Pages:971 page.getParameters().add( parseParam(param) ); but this shouldn't be called after init from what I can see. Jul 27, 2007 2:44:09 PM com.sun.facelets.FaceletViewHandler handleRenderException SEVERE: Error Rendering View[/secure/viewVacancy.xhtml] java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.jboss.seam.navigation.Pages.getStringValuesFromModel(Pages.java:651) at org.jboss.seam.ui.component.UISeamCommandBase.getUrl(UISeamCommandBase.java:50) at org.jboss.seam.ui.renderkit.LinkRendererBase.doEncodeBegin(LinkRendererBase.java:26) at org.jboss.seam.ui.util.cdk.RendererBase.encodeBegin(RendererBase.java:79) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:785) at org.ajax4jsf.framework.renderer.RendererBase.renderChild(RendererBase.java:280) at org.richfaces.renderkit.html.ToolBarGroupRenderer.encodeChildren(ToolBarGroupRenderer.java:68) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:809) at org.ajax4jsf.framework.renderer.RendererBase.renderChild(RendererBase.java:282) at org.richfaces.renderkit.html.ToolBarRendererBase.encodeChildren(ToolBarRendererBase.java:81) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:809) at org.ajax4jsf.framework.renderer.RendererBase.renderChild(RendererBase.java:282) at org.ajax4jsf.framework.renderer.RendererBase.renderChildren(RendererBase.java:262) at org.richfaces.renderkit.html.PanelRenderer.doEncodeChildren(PanelRenderer.java:189) at org.richfaces.renderkit.html.PanelRenderer.doEncodeChildren(PanelRenderer.java:184) at org.ajax4jsf.framework.renderer.RendererBase.encodeChildren(RendererBase.java:121) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:809) at org.jboss.seam.ui.util.cdk.RendererBase.renderChild(RendererBase.java:186) at org.jboss.seam.ui.util.cdk.RendererBase.renderChildren(RendererBase.java:166) at org.jboss.seam.ui.renderkit.DecorateRendererBase.doEncodeChildren(DecorateRendererBase.java:94) at org.jboss.seam.ui.util.cdk.RendererBase.encodeChildren(RendererBase.java:92) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:809) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:886) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:233) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:82) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:61) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:149) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:595) -- 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

16 years, 2 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2447) Premature requests causes pages actions problem

by Samuel Mendenhall (JIRA)

Premature requests causes pages actions problem ----------------------------------------------- Key: JBSEAM-2447 URL: http://jira.jboss.com/jira/browse/JBSEAM-2447 Project: JBoss Seam Issue Type: Bug Reporter: Samuel Mendenhall Sending multiple requests to an app while it is starting up causes page actions to not get correctly set up. Fix is to add @Startup to src/main/org/jboss/seam/core/Pages.java -- 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

16 years, 2 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2693) Little documentation error

by Sebastian Hennebrueder (JIRA)

Little documentation error -------------------------- Key: JBSEAM-2693 URL: http://jira.jboss.com/jira/browse/JBSEAM-2693 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.0.1.GA Environment: any Reporter: Sebastian Hennebrueder Fix For: 2.0.2.GA documentation seems to have a little bug. > > 25.3.1. Boostrapping Hibernate in Seam > > <persistence:managed-hibernate-session name="hibernateSessionFactory" > session-factory="#{hibernateSessionFactory}"/> > > should be > > <persistence:managed-hibernate-session name="hibernateSession" > session-factory="#{hibernateSessionFactory}"/> > > Correct? > > Best Regards > > Sebastian -- 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

16 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2605) Allow to specify filename for attachment

by Terry (JIRA)

Allow to specify filename for attachment ---------------------------------------- Key: JBSEAM-2605 URL: http://jira.jboss.com/jira/browse/JBSEAM-2605 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.1.GA Reporter: Terry Priority: Minor Fix For: 2.1.x For disposition=attachment, allow to specify a filename. Currenly Seam uses name of the viewid with documentType extension. -- 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

16 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2661) Upgrade to latest jfreechart

by Pete Muir (JIRA)

Upgrade to latest jfreechart ---------------------------- Key: JBSEAM-2661 URL: http://jira.jboss.com/jira/browse/JBSEAM-2661 Project: JBoss Seam Issue Type: Task Components: PDF Reporter: Pete Muir Assigned To: Norman Richards Fix For: 2.0.2.GA, 2.1.0.GA -- 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

16 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2441) Deployment fails with unhelpful errors if DTD can't be found

by Eric H (JIRA)

Deployment fails with unhelpful errors if DTD can't be found ------------------------------------------------------------ Key: JBSEAM-2441 URL: http://jira.jboss.com/jira/browse/JBSEAM-2441 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Linux, Java 6 Reporter: Eric H If there is an incorrect DTD URL in files parsed by dom4j, dom4j attempts to fetch the DTD over the net. This is inherently bad because unknown, non-secure resources (DTD files) are being silently added to the application classpath. What is worse, if the file is not found it fails with an unhelpful error, which is dependent on the specific network problem. For example, if name resolution does work, but routing does not work, the application fails (after a delay) with a no route to host error and no indication of which file failed. Really, the XML parser should never attempt to get a resource over the net, unless it has been explicitly configured to do so. See: [url]http://chiralsoftware.com/blog/No-route-to-host-while-parsing-b6b5f0c...] -- 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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] How translate default validation error messages?

by Christian Bonami

Consider this: <h:inputText value="#{editPipeline.pipeline.nscId}" id="nscid" redisplay="true" required="true"/> When the field is not filled in, I get a validation error in English stating me that this field is required. But how can I translate this error to eg. Dutch? I googled around but found nothing... What/where should I specify so that this messages gets translated in the current locale (I belief this is the locale of the browser, or isn't it?) Kind regards, -- Christian Bonami EDONIS bvba +32474494608

16 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2703) Avoid exceptions for invalid system request parameters

by Christian Bauer (JIRA)

Avoid exceptions for invalid system request parameters ------------------------------------------------------ Key: JBSEAM-2703 URL: http://jira.jboss.com/jira/browse/JBSEAM-2703 Project: JBoss Seam Issue Type: Task Components: JSF Integration Reporter: Christian Bauer Priority: Minor Some of Seams JSF integration code takes request parameters but doesn't check them properly for valid values. Usually that ends with an exception of some doofus tries to manipulate URIs: java.lang.IllegalArgumentException: No enum const class org.jboss.seam.core.PropagationType.HTTP://WWW.ELECTROFED.COM/_APP/EFC/OD... at java.lang.Enum.valueOf(Enum.java:192) at org.jboss.seam.core.PropagationType.valueOf(PropagationType.java:8) at org.jboss.seam.core.ConversationPropagation.getPropagationFromRequestParameter(ConversationPropagation.java:163) at org.jboss.seam.core.ConversationPropagation.restoreConversationId(ConversationPropagation.java:58) at org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:389) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:228) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:194) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) We might want to look at these cases and see if can avoid exceptions and just ignore invalid input. -- 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

16 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2612) Drop dtds

by Pete Muir (JIRA)

Drop dtds --------- Key: JBSEAM-2612 URL: http://jira.jboss.com/jira/browse/JBSEAM-2612 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Pete Muir Assigned To: Norman Richards Fix For: 2.1.0.GA Remove remaining dtds for pages.xml etc. -- 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

16 years, 2 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2008