February 2008 - seam-issues - Jboss List Archives

[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, 11 months

3
5
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, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2688) Implement ETag/LastModified headers for Feed Servlet

by Christian Bauer (JIRA)

Implement ETag/LastModified headers for Feed Servlet ---------------------------------------------------- Key: JBSEAM-2688 URL: http://jira.jboss.com/jira/browse/JBSEAM-2688 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Critical We are wasting some bandwidth on the feeds, let's hope that feed readers understand caching and set the HTTP headers in the servlet correctly. We could also consider Cache-Control for the aggregated feeds, they are only updated every 10 minutes. Not sure that makes much sense, feed readers shouldn't poll in shorter intervals anyway. -- 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, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1769) Create DataModel from components.xml

by Felix Ho?feld (JIRA)

Create DataModel from components.xml ------------------------------------ Key: JBSEAM-1769 URL: http://jira.jboss.com/jira/browse/JBSEAM-1769 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.0.BETA1 Reporter: Felix Ho?feld Priority: Optional It would be nice if it were possible to create datamodels using something similiar to the <factory /> tag in components.xml, e.g.: <datamodel auto-create="true" name="dm_customerOrders" scope="EVENT" value="#{customer.orders}"/> This would simplify using tables on nested lists of entitiy especially removing etc. some of the nested enities. Regards Felix -- 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, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1739) EmptyStackException in Transaction.java

by Florian Bartels (JIRA)

EmptyStackException in Transaction.java --------------------------------------- Key: JBSEAM-1739 URL: http://jira.jboss.com/jira/browse/JBSEAM-1739 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: Seam CVS 2007 07 28 Reporter: Florian Bartels I still get the bug as in JBSEAM-1696. The recent changes do not seem to affect this problem. I was not able to identify another problem. Here is the stack trace: java.lang.IllegalStateException: Could not commit transaction at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:591) at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:325) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.renderCycle(ReceiveSendUpdates.java:57) at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.service(ReceiveSendUpdates.java:45) at com.icesoft.faces.webapp.http.core.IDVerifier.service(IDVerifier.java:25) at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16) at com.icesoft.faces.webapp.http.servlet.ViewBoundAdaptingServlet.service(ViewBoundAdaptingServlet.java:44) at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97) at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35) at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:469) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:364) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:54) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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:64) 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:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Caused by: java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at org.jboss.seam.transaction.SeSynchronizations.beforeTransactionCommit(SeSynchronizations.java:50) at org.jboss.seam.transaction.UTTransaction.commit(UTTransaction.java:49) at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:581) ... 62 more -- 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, 11 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1720) s:link doesnt work correctly in a portlet

by Chris Rudd (JIRA)

s:link doesnt work correctly in a portlet ----------------------------------------- Key: JBSEAM-1720 URL: http://jira.jboss.com/jira/browse/JBSEAM-1720 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd When using a s:link inside a portlet application the actionMethod/etc are not properly processed. Ive traced this down, the current SeamPhaseListener processes pageActions and the s:link/s:button as part of the beforeRender processing. The actionMethod/actionOutcome/etc parameters are only passed to the portlet during the processAction portlet request. The beforeRender is executed during the doView portlet request, which doesnt have access to those parameters. One possible solution is to pass those parameters as renderparameters via the SeamPhaseListener.setPortletRenderParameter so that they are accessible to the doView render process. I think the better solution is to have all that processing occur during the processAction phase instead of the doView phase. The following change seems to work : SeamPhaseListener.afterPortletPhase line 258 + // Use the getRenderResponse flag to indicate that we have hit the end of the last phase that will + // be processed before the render. Handle the beforeRender at this time, as the next phase to + // occur should be RENDER_RESPONSE + if( event.getPhaseId() != RENDER_RESPONSE && facesContext.getRenderResponse() ) + beforeRender(event); + FacesMessages.afterPhase(); After this change (and JBSEAM-1719) s:link/s:button works under jboss-portal 2.6 -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1649) Run Seam filter stack with SeamTest

by Christian Bauer (JIRA)

Run Seam filter stack with SeamTest ----------------------------------- Key: JBSEAM-1649 URL: http://jira.jboss.com/jira/browse/JBSEAM-1649 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Reporter: Christian Bauer Priority: Minor I'd like to test my servlet filter with SeamTest. I've wrapped it as a Seam component and it is part of the regular Seam filter stack (within A4JSF filter). I don't think this is currently supported at all, the Seam filter doesn't run for FacesRequest/NonFacesRequest. I guess this would also enable testing of exceptions. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1642) It is difficult to call method on "outer" instance of component

by Michael Youngstrom (JIRA)

It is difficult to call method on "outer" instance of component --------------------------------------------------------------- Key: JBSEAM-1642 URL: http://jira.jboss.com/jira/browse/JBSEAM-1642 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Michael Youngstrom There may be cases were you are executing method in a component and you wish to call another method in the same component that executes the interceptors of that component. This is currently not really possible unless you explicitly grab the current instance of the component out of the scope it resides in. It would be nice if there were an easier way to achieve this. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-571) Custom Exception Handler

by Jye Tucker (JIRA)

Custom Exception Handler ------------------------ Key: JBSEAM-571 URL: http://jira.jboss.com/jira/browse/JBSEAM-571 Project: JBoss Seam Issue Type: Feature Request Components: Framework Reporter: Jye Tucker Ability to specify custom exception handlers through the exceptions component of the framework. -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1033) Allow programmatic adding of exception handlers

by Mike Quilleash (JIRA)

Allow programmatic adding of exception handlers ----------------------------------------------- Key: JBSEAM-1033 URL: http://jira.jboss.com/jira/browse/JBSEAM-1033 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Allow something like: Exceptions.instance().addHandler( exceptionHandler ); -- 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, 11 months

4
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008