October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1526) Support selective validation with a:region

by Christian Bauer (JIRA)

Support selective validation with a:region ------------------------------------------ Key: JBSEAM-1526 URL: http://jira.jboss.com/jira/browse/JBSEAM-1526 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer In complex forms I'd like to be able to customize validation per region: <h:form> <a:region> <h:inputText value="#{foo.bar}"/> <a:region> <h:inputText value="#{bar.foo}"/> <a:commandButton action="#{bar.baz}"/> </a> <a:commandButton action="#{foo.baz}"/> </a> </h:form> If the nested button is pressed, I only want #{bar.foo} validated (there is an <s:validateAll> around it). If the outer button is pressed, I want both properties validated. I realize that this is a major issue regarding model updates, however, I don't need to update the model for any non-validated property because a) it is not decoded on the server anyway (? I don't understand the a:region docs) b) i don't need an updated model because my action doesn't expect it c) i don't need an updated model because i am re-rendering an area that doesn't expect it -- 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

15 years, 11 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2062) Consider changing s:link default to propagation=none

by Stuart Douglas (JIRA)

Consider changing s:link default to propagation=none ---------------------------------------------------- Key: JBSEAM-2062 URL: http://jira.jboss.com/jira/browse/JBSEAM-2062 Project: JBoss Seam Issue Type: Feature Request Reporter: Stuart Douglas Priority: Minor the reason to consider this change is that foo?cid=123 links are confusing for search engine crawlers. -- 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

15 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1052) seam-dev.properties, seam-prod.properties

by Pete Muir (JIRA)

seam-dev.properties, seam-prod.properties ----------------------------------------- Key: JBSEAM-1052 URL: http://jira.jboss.com/jira/browse/JBSEAM-1052 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.2.0.GA Reporter: Pete Muir Priority: Optional In the same way you have persistence-dev.xml, there should be seam-dev.properties to allow you to configure your application differently when in dev/prod (e.g. disable random password generation). AFAICS seam.properties must be in WEB-INF/classes/seam.properties for it to be read (it isn't read in ejb-jar/seam.properties as it's not in the classloader) -- 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

15 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1844) @Raise event does not work with @Observer in the same bean

by Ilya Doe (JIRA)

@Raise event does not work with @Observer in the same bean ---------------------------------------------------------- Key: JBSEAM-1844 URL: http://jira.jboss.com/jira/browse/JBSEAM-1844 Project: JBoss Seam Issue Type: Bug Reporter: Ilya Doe If the method that is annotated with @RaiseEvent is in the same stateful bean (conversation scoped) with the method annotated @Observer; when the observer method is called all to-be injected fields are null. See details in the forum post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074789 -- 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

15 years, 12 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2148) Support for SelectItemGroup

by Pete Muir (JIRA)

Support for SelectItemGroup --------------------------- Key: JBSEAM-2148 URL: http://jira.jboss.com/jira/browse/JBSEAM-2148 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.2.GA We can do something like <s:selectItemGroup label="#{foo.bar}"> <s:selectItems .../> <s:selectItems .../> </s:selectItemGroup> and, as a shorthand to put each list in a distinct group <s:selectItems group="Foo"/> I don't understand why this isn't in JSF core. -- 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

3
16
0 / 0

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

by Matt Drees (JIRA)

EmptyStackException in Transaction.java --------------------------------------- Key: JBSEAM-1696 URL: http://jira.jboss.com/jira/browse/JBSEAM-1696 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: Seam cvs 20070717.1711 Reporter: Matt Drees Priority: Minor I occasionally get the following stacktrace. I believe it happens when the SeamPhaseListener tries to begin a transaction, but an exception is thrown, so the stack is never pushed. Later, when it tries to commitOrRollback, the following happens. 2007-07-18 15:29:55,229 ERROR () SeamPhaseListener: uncaught exception java.lang.IllegalStateException: Could not commit transaction at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:589) 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 javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 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:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) 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.Transaction.beforeCommit(Transaction.java:64) at org.jboss.seam.transaction.UTTransaction.commit(UTTransaction.java:44) at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:579) You'd probably just need a simple "if (!synchronizations.isEmpty())" check before peek()ing or pop()ing. -- 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

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2079) CLONE -Remember-Me automatic authentication

by Eugene Kisly (JIRA)

CLONE -Remember-Me automatic authentication ------------------------------------------- Key: JBSEAM-2079 URL: http://jira.jboss.com/jira/browse/JBSEAM-2079 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Eugene Kisly Fix For: 1.1.7.CR1 Extend the behaviour of Remember-Me to automatically authenticate the user after they have selected the "Remember Me" service rather than have him or her re-enter their password each time. -- 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

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-979) Seam scan's for pageflows on startup

by Pete Muir (JIRA)

Seam scan's for pageflows on startup ------------------------------------ Key: JBSEAM-979 URL: http://jira.jboss.com/jira/browse/JBSEAM-979 Project: JBoss Seam Issue Type: Feature Request Components: BPM, Core Affects Versions: 1.2.0.GA Reporter: Pete Muir -- 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

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1946) seam 2.0's persistence:managed-persistence-context not support openjpa

by clf clf (JIRA)

seam 2.0's persistence:managed-persistence-context not support openjpa ---------------------------------------------------------------------- Key: JBSEAM-1946 URL: http://jira.jboss.com/jira/browse/JBSEAM-1946 Project: JBoss Seam Issue Type: Bug Components: Core Environment: tomacat 6+ myfaces 1.2.0 + seam 2.0 ga+ spring 2.0.6 + openjpa 0.9.7 Reporter: clf clf I try to test the Seam's compatibility with openjpa. The web project is tomacat + myfaces + seam + spring jpa + openjpa. I define entityManagerFactory in the application.xml [code]  <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> <property name="dataSource" ref="dataSource"/> <property name="loadTimeWeaver"> <bean class="org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver"/> </property> <property name="jpaVendorAdapter">   <bean id="jpaAdapter" class="org.springframework.orm.jpa.vendor.OpenJpaVendorAdapter"> <property name="database" value="HSQL"/> <property name="showSql" value="true"/> </bean> </property> </bean> [/code] And Define managed-persistence-context in component.xml [code] <persistence:managed-persistence-context name="courseEntityManager" entity-manager-factory="#{entityManagerFactory}" auto-create="true" /> [/code] The Web Project reports Error [code] 2007-09-21 09:21:09,981 ERROR [org.jboss.seam.jsf.SeamPhaseListener] - <uncaught exception> java.lang.RuntimeException: could not proxy delegate at org.jboss.seam.persistence.HibernatePersistenceProvider.proxyDelegate(HibernatePersistenceProvider.java:102) Caused by: java.lang.ClassCastException: org.apache.openjpa.persistence.EntityManagerImpl at org.jboss.seam.persistence.HibernatePersistenceProvider.proxyDelegate(HibernatePersistenceProvider.java:98) [/code] I also test seam with toplink and hibernate,and find toplink fail,hibernate success It seems to me that seam's persistence:managed-persistence-context only supports hibernate as entity-manager-factory and not supports other jpa 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, 1 month

4
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-829) ICEfaces Tree Component needs reworking

by Gregory Dick (JIRA)

ICEfaces Tree Component needs reworking --------------------------------------- Key: JBSEAM-829 URL: http://jira.jboss.com/jira/browse/JBSEAM-829 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Reporter: Gregory Dick Assigned To: Gregory Dick Some comments Plain tree component with label: <ice:tree value="#{nodeTree.model}" var="item"> <ice:treeNode> <f:facet name="content"> <ice:commandLink actionListener="# {item.userObject.nodeClicked}"> <ice:outputText value="# {item.userObject.text}"/> </ice:commandLink> </f:facet> </ice:treeNode> </ice:tree> Renders HTML with whitespace between <img> and <a> tags, resulting in broken <div> padding and unwanted spaces: <div class="iceTreeRow" id="_id21:_id22-div-2" name="treeNodeDiv"><img alt="" border="0" src="./xmlhttp/css/xp/css- images/tree_line_blank.gif"></img> <img alt="" border="0" src="./xmlhttp/css/xp/css-images/ tree_line_last_node.gif"></img> Should be: <div class="iceTreeRow" id="_id21:_id22-div-2" name="treeNodeDiv"><img alt="" border="0" src="./xmlhttp/css/xp/css- images/tree_line_blank.gif"></img><img alt="" border="0" src="./ xmlhttp/css/xp/css-images/tree_line_last_node.gif"></img> and so on... the only whitespaces should (could) be between </ div><div> tags, nowhere else. The trick with whitespace:nowrap in the CSS is not going to cut it, there are still spaces left that I don't want. --------------------------------------------------- The xp/tree_nav_top_close_no_siblings.gif GIF is broken, it is not transparent and the icon is not centered on the canvas. --------------------------------------------------- After clicking on the tree and playing with the XHTML a little, I got this: 03:36:56,599 ERROR [[Blocking Servlet]] Servlet.service() for servlet Blocking Servlet threw exception java.lang.RuntimeException: viewNumber 1 update queue exceeded 26 at com.icesoft.faces.webapp.xmlhttp.BlockingResponseState.writeElement (BlockingResponseState.java:183) at com.icesoft.faces.context.DOMResponseWriter.writeDOM (DOMResponseWriter.java:375) at com.icesoft.faces.application.D2DViewHandler.renderView (D2DViewHandler.java :161) Had to restart the server. --------------------------------------------------- To collapse a node I can click on the [-] icon of the node. Expanding with the then displayed [+] icon does not work, although I see a submit on the server log. If I click on the commandLink (the label) instead, the node expands but I also get the select event for that node. This is either a simple copy/paste bug or inconsistent UI behavior. --------------------------------------------------- Did not find a way (documentation doesn't mention it) to customize the images that are rendered by components without CSS, for example, the expand/collapse icons of a tree. After reading the source and API doc of the Tree component, I found the setImageDir() method, this should be documented better in the reference. --------------------------------------------------- The data binding for the tree is questionable. First, the idea of using the Swing datamodels is good, in fact, JSF should not have its own UI datamodels at all and every UI component should be able to use the Swing datamodels. This allows us to expose a UI datamodel on backing beans (EJBs in Seam) without requiring extension or inclusion of any vendor-specific API or JAR in the EJB deployment module. Most JSF component providers do not realize this and require custom datamodels. I can't list everything that is wrong with the tree databinding, short list: - Finally, the UI component does no longer require DefaultTreeModel but the TreeModel interface (good) - Every object in the TreeModel is cast to a DefaultMutableTreeNode, this is not an interface! I want to use my own TreeNode implementation! - Every DefaultMutableTreeNode needs a wrapped IceUserObject, this is completely unecessary if I'd be able to use my own TreeNode implementation (maybe I can also implement an IceTreeNode interface for some UI binding). - This would also solve the lazy loading FAQs on the Icefaces forum, the approach with event listeners in the IceUserObject is a non- starter, my TreeModel/TreeNode implementation could do that just fine - There are unused classes such as TreeDataModel hanging around the icefaces package, these only add to the confusion Summary: This needs a serious redesign before it is usable. --------------------------------------------------- -- 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, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2007