April 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3824) Chapter 29.10 should be updated being DeploymentHandler has been re-factored.

by Jay Balunas (JIRA)

Chapter 29.10 should be updated being DeploymentHandler has been re-factored. ----------------------------------------------------------------------------- Key: JBSEAM-3824 URL: https://jira.jboss.org/jira/browse/JBSEAM-3824 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.1.CR2 Reporter: Jay Balunas Fix For: 2.1.2.CR1 Since DeploymentHandler has been re-factored Chapter 29.10 should be updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4154) Remove core.init.userTransactionName

by Fusayuki Minamoto (JIRA)

Remove core.init.userTransactionName ------------------------------------ Key: JBSEAM-4154 URL: https://jira.jboss.org/jira/browse/JBSEAM-4154 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.2.CR1 Reporter: Fusayuki Minamoto JBSEAM-1144 removed the core.init.userTransactionName but the Seam reference doc wasn't updated. In the "31.10. Infrastructural components", following line should be removed. org.jboss.seam.core.init.userTransactionName — the JNDI name to use when looking up the JTA UserTransaction object. Besides, JBoss Developer Studio 2.0 has an input field for User-Transaction-Name of Init component on the Seam 2.0 component editor. How to reproduce ============== When you set the user-transaction-name attribute in the components.xml with JBDS 2.0, you will get an exception at deployment: Caused by: java.lang.IllegalArgumentException: no such field: org.jboss.seam.core.Init.userTransactionName at org.jboss.seam.util.Reflections.getField(Reflections.java:293) at org.jboss.seam.Component.initInitializers(Component.java:480) at org.jboss.seam.Component.<init>(Component.java:264) at org.jboss.seam.Component.<init>(Component.java:217) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1028) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3711) openid docs and example

by Norman Richards (JIRA)

openid docs and example ----------------------- Key: JBSEAM-3711 URL: https://jira.jboss.org/jira/browse/JBSEAM-3711 Project: Seam Issue Type: Sub-task Reporter: Norman Richards Assignee: Norman Richards Fix For: 2.1.1.CR2 Need to update docs and create a sample app -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4128) Regression: page parameters broken

by Sheng Gu (JIRA)

Regression: page parameters broken ---------------------------------- Key: JBSEAM-4128 URL: https://jira.jboss.org/jira/browse/JBSEAM-4128 Project: Seam Issue Type: Bug Components: EL Affects Versions: 2.1.2.CR1 Reporter: Sheng Gu Page parameters are lost/broken after upgrading to 2.1.2.CR1 from 2.1.1.GA. For example: page.xhtml has page parameters: param1, param2, param3, when click s:link view="page.xhtml" and pass a new value of param1 to the page, all other parameters param2 and param3 disappear from page.xhtml. In 2.1.1.GA, it doesn't happen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4159) The view-id attribute in pages.xml can be a pattern to match against multiple pages, it would be very useful to have a exclude-view-id attribute to exclude certain pages from being acted on.

by Arshad Mahmood (JIRA)

The view-id attribute in pages.xml can be a pattern to match against multiple pages, it would be very useful to have a exclude-view-id attribute to exclude certain pages from being acted on. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4159 URL: https://jira.jboss.org/jira/browse/JBSEAM-4159 Project: Seam Issue Type: Feature Request Reporter: Arshad Mahmood I have an application which required login-in for all pages except for the main login page itself. If I enter a generic <page view-id="/view/*.seam" login-required="true" /> then this causes problem with the login view itself (which is at /view/login.seam). It would be much easier if I could write a rule like <page view-id="/view/*.seam" exclude-view-id="/view/login.seam" login-required="true" />. Although, very useful in this scenario this enhacement I think would be worthwhile in other situations too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4130) NullPointerException is thrown after redirect from exception handler for ViewExpiredException to any view with a component with @In or @RequestParameter

by Bostjan Lah (JIRA)

NullPointerException is thrown after redirect from exception handler for ViewExpiredException to any view with a component with @In or @RequestParameter -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4130 URL: https://jira.jboss.org/jira/browse/JBSEAM-4130 Project: Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.1.1.GA Environment: Seam 2.1.1.GA, Jboss As 4.2.3, Java 1.6 Reporter: Bostjan Lah I have the following in my pages.xml: <exception class="javax.faces.application.ViewExpiredException"> <end-conversation/> <redirect view-id="/content.xhtml"> <message>Your session has expired.</message> </redirect> </exception> However content.xhtml uses a component ContentHome which has several @RequestParameter annotations. Here is stacktrace: java.lang.NullPointerException at org.jboss.seam.navigation.Pages.getStringValuesFromModel(Pages.java:758) at org.jboss.seam.navigation.Pages.encodePageParameters(Pages.java:937) at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:176) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:55) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:42) at org.jboss.seam.exception.RedirectHandler.handle(RedirectHandler.java:51) at org.jboss.seam.exception.Exceptions.handle(Exceptions.java:76) at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) 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:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) It seems this is caused by trying to retrieve page parameter from page context which doesn't exist at that point. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3412) .page.xml are only loaded for pages with .xhtml extesnion.

by Prashant Kadam (JIRA)

.page.xml are only loaded for pages with .xhtml extesnion. ---------------------------------------------------------- Key: JBSEAM-3412 URL: https://jira.jboss.org/jira/browse/JBSEAM-3412 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1 Environment: JBoss Reporter: Prashant Kadam I have a facelete pages with '.jspx' extension. It seems that pages with only .xhtml extensions are mapped for page orchestration. Here's the code from org.jboss.seam.navigation.Pages.java file : private void parsePages(Set<String> ...fileNames) { Set<String> mergedFileNames = new HashSet<String>(); for (Set<String> f : fileNames) { mergedFileNames.addAll(f); } for (String fileName: mergedFileNames) { String viewId = "/" + fileName.substring(0,fileName.length()-".page.xml".length()) + ".xhtml"; // needs more here InputStream stream = ResourceLoader.instance().getResourceAsStream(fileName); if (stream==null) { log.info("no pages.xml file found: " + fileName); } else { log.debug("reading pages.xml file: " + fileName); parse(stream,viewId); } } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4156) Typo in sample code in documentation, chapter 18.1.3. Use tag<p:facet> instead of <f:facet>

by Denis Forveille (JIRA)

Typo in sample code in documentation, chapter 18.1.3. Use tag<p:facet> instead of <f:facet> ------------------------------------------------------------------------------------------- Key: JBSEAM-4156 URL: https://jira.jboss.org/jira/browse/JBSEAM-4156 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.2.CR1 Reporter: Denis Forveille Assignee: Denis Forveille Priority: Trivial Fix For: 2.1.2.CR2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4155) Reference doc typos

by Fusayuki Minamoto (JIRA)

Reference doc typos ------------------- Key: JBSEAM-4155 URL: https://jira.jboss.org/jira/browse/JBSEAM-4155 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.2.CR1 Reporter: Fusayuki Minamoto Priority: Minor Two spelling misstakes are found in the Seam reference doc. 13.2. Home objects If we only want to refresh certain queries when a particular entity is persited, updated or removed => "persited" should be "persisted". 13.3. Query objects Unfortunately Query objects don't work well with join fetch queries - the use of pagination with these queries is not recomended, => "recomended" should be "recommended". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4050) Improve handling of bad exception handling config

by Matthew Lieder (JIRA)

Improve handling of bad exception handling config ------------------------------------------------- Key: JBSEAM-4050 URL: https://jira.jboss.org/jira/browse/JBSEAM-4050 Project: Seam Issue Type: Task Components: Core Affects Versions: 2.1.1.GA Reporter: Matthew Lieder If you have the following in pages.xml and throw that exception, Seam throws an NPE at org.jboss.seam.exception.Exceptions.parse(Exceptions.java:195): <exception class="com.example.helloworld.BadParameterException" log="false"> </exception> The cause is that while Exceptions.createHandler(...) can return null, Exceptions.parse(...) assumes that it can't. It appears that having an <exception> element without a <redirect> or <http-error> child is invalid (which definitely makes sense, since otherwise Seam would have no idea what to do when the exception happens), but given that it isn't enforced in the XSD and that I could definitely see others making this same mistake I definitely believe that this NPE should be avoided and a more informative error message should be shown (or even an exception upon Seam startup, while parsing pages.xml). In a Seam vs. Spring Web Flow comparison one of the big knocks against Seam was its cryptic error messages; by filing tickets like this I'm trying to do my part to remedy that :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2009