June 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1373) QuartzDispatcher

by Gavin King (JIRA)

QuartzDispatcher ---------------- Key: JBSEAM-1373 URL: http://jira.jboss.com/jira/browse/JBSEAM-1373 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Gavin King People like Quartz. -- 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

17 years, 7 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1374) Document JBoss EL

by Gavin King (JIRA)

Document JBoss EL ----------------- Key: JBSEAM-1374 URL: http://jira.jboss.com/jira/browse/JBSEAM-1374 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Gavin King Assigned To: Norman Richards Priority: Critical Fix For: 1.3.0.ALPHA The whole "elenhancements" chapter needs a rewrite. -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1397) seam-gen: missing equal signs in messages_en.properties

by Pierre Raoul (JIRA)

seam-gen: missing equal signs in messages_en.properties ------------------------------------------------------- Key: JBSEAM-1397 URL: http://jira.jboss.com/jira/browse/JBSEAM-1397 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.3.0.ALPHA Reporter: Pierre Raoul In the seam-gen/resources/messages_en.properties file, equal sign is missing in many key/value -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1391) pages-1.3.xsd

by Gavin King (JIRA)

pages-1.3.xsd ------------- Key: JBSEAM-1391 URL: http://jira.jboss.com/jira/browse/JBSEAM-1391 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Norman Richards Fix For: 1.3.0.ALPHA Everything is in XSD except for pages.xml. -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1345) Update the docs for AS 4.2 / JSF 1.2

by Gavin King (JIRA)

Update the docs for AS 4.2 / JSF 1.2 ------------------------------------ Key: JBSEAM-1345 URL: http://jira.jboss.com/jira/browse/JBSEAM-1345 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Gavin King Assigned To: Norman Richards Fix For: 1.3.0.ALPHA -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1393) pages.xml parsing error in all examples

by Stuart Robertson (JIRA)

pages.xml parsing error in all examples --------------------------------------- Key: JBSEAM-1393 URL: http://jira.jboss.com/jira/browse/JBSEAM-1393 Project: JBoss Seam Issue Type: Bug Components: Core Environment: Seam from CVS, Jboss 4.2.0GA, OS X 10.4.9 Reporter: Stuart Robertson Fix For: 1.3.0.ALPHA I've just updated from CVS. Running each of the examples fails when I go to the landing page for each example. I've tried seamdiscs, dvdstore and booking, each with the same results. Here is the exception I'm seeing: 12:31:00,360 ERROR [SeamPhaseListener] uncaught exception java.lang.RuntimeException: org.dom4j.DocumentException: http://jboss.com/products/seam/pages-1.3.dtd Nested exception: http://jboss.com/products/seam/pages-1.3.dtd at org.jboss.seam.core.Pages.getDocumentRoot(Pages.java:836) at org.jboss.seam.core.Pages.parse(Pages.java:794) at org.jboss.seam.core.Pages.initialize(Pages.java:108) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:20) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123) at org.jboss.seam.Component.callComponentMethod(Component.java:1838) at org.jboss.seam.Component.callCreateMethod(Component.java:1761) at org.jboss.seam.Component.newInstance(Component.java:1750) at org.jboss.seam.Component.getInstance(Component.java:1647) at org.jboss.seam.Component.getInstance(Component.java:1626) at org.jboss.seam.Component.getInstance(Component.java:1603) at org.jboss.seam.Component.getInstance(Component.java:1598) at org.jboss.seam.core.Pages.instance(Pages.java:474) at org.jboss.seam.core.Manager.restoreConversation(Manager.java:439) at org.jboss.seam.jsf.AbstractSeamPhaseListener.afterRestoreView(AbstractSeamPhaseListener.java:53) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:95) 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.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:62) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:59) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:81) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:47) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:126) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:248) at org.jboss.seam.web.AbstractAjax4jsfFilter.doFilter(AbstractAjax4jsfFilter.java:35) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:126) 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.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:613) Caused by: org.dom4j.DocumentException: http://jboss.com/products/seam/pages-1.3.dtd Nested exception: http://jboss.com/products/seam/pages-1.3.dtd at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:343) at org.jboss.seam.util.XML.getRootElement(XML.java:16) at org.jboss.seam.core.Pages.getDocumentRoot(Pages.java:832) ... 56 more 12:31:00,495 ERROR [SeamPhaseListener] swallowing exception ... and further down: 12:31:00,517 ERROR [SeamPhaseListener] uncaught exception java.lang.IllegalStateException: No active conversation context at org.jboss.seam.core.FacesMessages.instance(FacesMessages.java:417) at org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:226) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:56) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) 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:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:62) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:59) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:81) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:47) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:126) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:248) at org.jboss.seam.web.AbstractAjax4jsfFilter.doFilter(AbstractAjax4jsfFilter.java:35) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:126) 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.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:613) 12:31:00,518 ERROR [SeamPhaseListener] swallowing exception java.lang.IllegalStateException: No active conversation context at org.jboss.seam.core.FacesMessages.instance(FacesMessages.java:417) at org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:226) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:56) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1360) s:fileupload not working

by Feivel Frey (JIRA)

s:fileupload not working ------------------------ Key: JBSEAM-1360 URL: http://jira.jboss.com/jira/browse/JBSEAM-1360 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Windows XP, JBoss-4-0.5.GA Reporter: Feivel Frey <s:fileUpload id="fileupload" data="#{specialreleaseeditor.file}" accept="*/*" fileName="#{specialreleaseeditor.fileName}" contentType="#{specialreleaseeditor.fileContentType}"/> getter and setter for file, filename and fileContentType not called, only I comment s:fileupload. -- 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

17 years, 7 months

3
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1060) Documentation enhancement for themes (add JSF requestContextPath to example)

by Arjan van Bentem (JIRA)

Documentation enhancement for themes (add JSF requestContextPath to example) ---------------------------------------------------------------------------- Key: JBSEAM-1060 URL: http://jira.jboss.com/jira/browse/JBSEAM-1060 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Optional I know the following is actually JSF related: http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... shows the following example: <link href="#{theme.css}" rel="stylesheet" type="text/css" /> Maybe the following text can be added right below it: Or, when the page definition resides in some subdirectory: <link href="#{facesContext.externalContext.requestContextPath}/#{theme.css}" rel="stylesheet" type="text/css" /> So: <para> Or, when the page definition resides in some subdirectory: </para> <programlisting><![CDATA[ <link href="#{facesContext.externalContext.requestContextPath}/#{theme.css}" rel="stylesheet" type="text/css" /> ]]></programlisting> Furthermore, http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... shows css ../screen.css template template.xhtml while http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... refers to that last line using <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" template="#{theme.template}"> When this ui:composition is used in a page file that resides in a subdirectory (such as /admin) then the last line needs a leading slash. One could also add that leading slash to the property file. Again, this is a JSF issue. But when the template is not found then (in my world) one does not get any meaningful error message other than a Tomcat "The requested resource (xxx.seam) is not available" when JSF cannot find the template file (while the logs show that Seam is not having any trouble setting up the components as used in that page). This might be avoided by using the leading slash in the example: css ../screen.css template /template.xhtml So: <programlisting><![CDATA[css ../screen.css template /template.xhtml]]></programlisting> (I actually also wonder why the css refers to some relative path in this example, but an erroneous value would only yield a broken layout when the stylesheet is not found, and is much easier solved -- especially when knowing about facesContext.externalContext.requestContextPath). -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1048) Documentation enhancement for injecting TaskInstance and ProcessInstance (add full package name)

by Arjan van Bentem (JIRA)

Documentation enhancement for injecting TaskInstance and ProcessInstance (add full package name) ------------------------------------------------------------------------------------------------ Key: JBSEAM-1048 URL: http://jira.jboss.com/jira/browse/JBSEAM-1048 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Optional This may be too obvious for some, but maybe, just maybe, the following needs some enhancements: http://fisheye.jboss.com/browse/JBoss/jboss-seam/doc/reference/en/modules... reads: @StartTask [...] The jBPM TaskInstance will be available in a request context variable named taskInstance. The jPBM ProcessInstance will be available in a request context variable named processInstance. (Of course, these objects are available for injection via @In.) Built-in Seam components TaskInstance and ProcessInstance exist, but in fact are not used here. Due to the @Unwrap in org.jboss.seam.core.TaskInstance and ProcessInstance one actually gets an org.jbpm.taskmgmt.exe.TaskInstance and an org.jbpm.graph.exe.ProcessInstance injected. The exception when the Java code expects a Seam component is in fact clear: java.lang.IllegalArgumentException: Could not set field value by reflection: TodoList.processInstance on: org.jboss.seam.example.todo.TodoList with value: class org.jbpm.graph.exe.ProcessInstance However, this error might be embedded in a long list of other exceptions. For example, when adding the injection to the TodoList example it will be the 5th embedded exception in a message that starts with "javax.servlet.ServletException: Cannot get value for expression '#{todoList.description}'". Fix: Maybe the text above could be changed to include the full package name (hoping that it will not change in the near future): The jBPM org.jbpm.taskmgmt.exe.TaskInstance will be available in a request context variable named taskInstance. The jBPM org.jbpm.graph.exe.ProcessInstance will be available in a request context variable named processInstance. (Of course, these objects are available for injection via @In.) The very same text applies to @BeginTask. When not changing the documentation then, as of now, at least JIRA will show a hit when searching for "injection AND ProcessInstance" ;-) -- 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

17 years, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-301) request for Seam tag description chapter in reference

by Shane Bryzak (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-301?page=all ] Shane Bryzak closed JBSEAM-301. ------------------------------- Resolution: Out of Date The updated controls chapter of the documentation should address this issue to a satisfactory level. Any specific documentation issues from now on should be directed toward the control in question. > request for Seam tag description chapter in reference > ----------------------------------------------------- > > Key: JBSEAM-301 > URL: http://jira.jboss.com/jira/browse/JBSEAM-301 > Project: JBoss Seam > Issue Type: Feature Request > Components: Documentation > Affects Versions: 1.0.1, 1.0 beta 2, 1.0, 1.0 beta 1 > Environment: all > Reporter: David Bernstein > Assigned To: Shane Bryzak > Priority: Optional > > Trying to get a good understanding of what's possible with Seam tags involves a bit of scanning of the reference manual as well as the source code Java and taglib.tld. It would be easier if there were a chapter in the reference manual all about Seam's tags like there is about its annotations. Perhaps Jakarta Taglibs at http://jakarta.apache.org/taglibs/index.html could help in making this easily automatable? A little custom XSL should do the trick also. -- 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

17 years, 7 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 June 2007