May 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2991) Controller does not inject the log correctly

by Betto McRose Gamarra (JIRA)

Controller does not inject the log correctly -------------------------------------------- Key: JBSEAM-2991 URL: http://jira.jboss.com/jira/browse/JBSEAM-2991 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.1.GA Reporter: Betto McRose Gamarra Priority: Blocker When I try to persist an EntityHome derived class I have a null pointer in the Controller class at the point of debug method the log is not injected properly so I have a null pointer execption error -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2515) Abstraction of FacesMessages

by Pete Muir (JIRA)

Abstraction of FacesMessages ---------------------------- Key: JBSEAM-2515 URL: http://jira.jboss.com/jira/browse/JBSEAM-2515 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.GA Needed for support other view layers -- 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, 8 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2988) some chinese charactor(only a few) can not write in the seam config xml files

by Tony Lee (JIRA)

some chinese charactor(only a few) can not write in the seam config xml files ----------------------------------------------------------------------------- Key: JBSEAM-2988 URL: http://jira.jboss.com/jira/browse/JBSEAM-2988 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1 Environment: windows 2003 chinese, jboss 4.2.2, jbosstools ide 2.1.0cr1 Reporter: Tony Lee Priority: Minor some chinese charactor can not write in the seam config xml files till now I found only two charactors:层在 and any other chinese charactors is ok I write the two chinese charactors in these config xml files:components.xml & page.xml and in  & <message></message> I think if any other chinese charactors can be used in the xml files, but only the two charactors will cause the exception, it would be a bug. I'm not sure if the bug is about seam. But I haven't met this problem in other places. at the end, I am sorry for my poor english. error log is: java.lang.RuntimeException: org.dom4j.DocumentException: Error on line 32 of document : Invalid byte 3 of 3-byte UTF-8 sequence. Nested exception: Invalid byte 3 of 3-byte UTF-8 sequence. at org.jboss.seam.navigation.Pages.getDocumentRoot(Pages.java:950) at org.jboss.seam.navigation.Pages.parse(Pages.java:908) at org.jboss.seam.navigation.Pages.initialize(Pages.java:108) at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2084) at org.jboss.seam.Component.callCreateMethod(Component.java:2007) at org.jboss.seam.Component.newInstance(Component.java:1978) at org.jboss.seam.Component.getInstance(Component.java:1873) at org.jboss.seam.Component.getInstance(Component.java:1852) at org.jboss.seam.Component.getInstance(Component.java:1829) at org.jboss.seam.Component.getInstance(Component.java:1824) at org.jboss.seam.navigation.Pages.instance(Pages.java:604) at org.jboss.seam.core.ConversationPropagation.restoreNaturalConversationId(ConversationPropagation.java:107) at org.jboss.seam.core.ConversationPropagation.restoreConversationId(ConversationPropagation.java:55) 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) 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:83) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) 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.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) 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.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) 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:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) 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(Unknown Source) Caused by: org.dom4j.DocumentException: Error on line 32 of document : Invalid byte 3 of 3-byte UTF-8 sequence. Nested exception: Invalid byte 3 of 3-byte UTF-8 sequence. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:343) at org.jboss.seam.util.XML.getRootElement(XML.java:24) at org.jboss.seam.navigation.Pages.getDocumentRoot(Pages.java:946) ... 60 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, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2981) java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)

by Pete Muir (JIRA)

java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml) --------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2981 URL: http://jira.jboss.com/jira/browse/JBSEAM-2981 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1 Reporter: Pete Muir Assigned To: Norman Richards Priority: Blocker Fix For: 2.1.0.BETA1 java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml) at org.jboss.seam.core.Init.checkDuplicateFactoryExpressions(Init.java:189) at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:182) at org.jboss.seam.core.Init.addFactoryValueExpression(Init.java:245) at org.jboss.seam.init.Initialization.installComponents(Initialization.java:964) at org.jboss.seam.init.Initialization.init(Initialization.java:609) at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915) at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58) ... Removed 15 stack frames -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-274) More flexible mapping of URLs to view ids

by Norman Richards (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=comments#action_12412534 ] Norman Richards commented on JBSEAM-274: ---------------------------------------- This code has already been completed and integrated. The only remaining step is to add scanning/preloading of pages.xml files. (currently we lazy load files, which is insufficient since we need to know about all the pages and page patterns before the page has been first accessed) > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: Seam > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assigned To: Norman Richards > Fix For: 2.1.0.GA > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF implementation. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2971) initial property value does not work if setter is missing (doesn't fall back to field)

by Dan Allen (JIRA)

initial property value does not work if setter is missing (doesn't fall back to field) -------------------------------------------------------------------------------------- Key: JBSEAM-2971 URL: http://jira.jboss.com/jira/browse/JBSEAM-2971 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.2.GA The check for the setter method when preparing the initial property value is not wrapped in a catch block, so the logic never makes it to the field check. If the setter is missing, the proper behavior is that it moves on to looking for a field. -- 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, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-274) More flexible mapping of URLs to view ids

by Przemyslaw Jaskierski (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=comments#action_12412530 ] Przemyslaw Jaskierski commented on JBSEAM-274: ---------------------------------------------- Please make it possible to disable this filter if you really-really plan to add it to the Seam filter chain. > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: Seam > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assigned To: Norman Richards > Fix For: 2.1.0.GA > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF implementation. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-274) More flexible mapping of URLs to view ids

by Dan Allen (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=comments#action_12412503 ] Dan Allen commented on JBSEAM-274: ---------------------------------- After some research, we have determined that the UrlRewriteFilter is compatible with Seam as it is released under the new BSD license. I don't see any reason why we cannot move forward with this initiative and bundle the urlrewritefilter.jar with both Seam and seam-gen. First and foremost we should create a filter and put it in the Seam filter chain so that it doesn't not have to be added to web.xml. > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: Seam > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assigned To: Norman Richards > Fix For: 2.1.0.GA > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF implementation. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2819) Improve the seamspace example adding a dynamic menu from a database using richfaces according to the roles that were implemented by the identity management

by nelson fernandez (JIRA)

Improve the seamspace example adding a dynamic menu from a database using richfaces according to the roles that were implemented by the identity management ----------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2819 URL: http://jira.jboss.com/jira/browse/JBSEAM-2819 Project: JBoss Seam Issue Type: Task Reporter: nelson fernandez This example will be helpful for beginners developments. -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2957) seambay example - all web services on test page return error code 404

by Jay Balunas (JIRA)

seambay example - all web services on test page return error code 404 --------------------------------------------------------------------- Key: JBSEAM-2957 URL: http://jira.jboss.com/jira/browse/JBSEAM-2957 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas On the front page of the seambay example is a link to a test page containing links that should launch and display various web service calls. All of the web service calls return a javascript message box with error code 404 from localhost:8080. No errors are seen in the logs. -- 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, 8 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2008