November 2007 - seam-issues - Jboss List Archives

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

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, 6 months

4
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2319) searchparents="true" required to properly detect Groovy in build

by Dan Allen (JIRA)

searchparents="true" required to properly detect Groovy in build ---------------------------------------------------------------- Key: JBSEAM-2319 URL: http://jira.jboss.com/jira/browse/JBSEAM-2319 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.0.x Attachments: JBSEAM-2319-v1.txt If you are using Ant >= 1.7.0, the check to determine if there are Groovy files present on the classpath will not work unless the attribute searchparents="true" is added to the <available> element that performs the check. This is an API change in Ant. Unfortunately, this attribute is not present in earlier versions of Ant and therefore throws an error. Can we just require Ant 1.7.0 or is there some way to work around an attribute that an older version of Ant does not recognize? Here is the check:  <available property="groovy.present" value="true" file="" searchparents="true"> <filepath> <fileset dir="${src.action.dir}"> <include name="**/*.groovy"/> </fileset> </filepath> </available> -- 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 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2266) WLS doesn't support Servlet 2.5

by Pete Muir (JIRA)

WLS doesn't support Servlet 2.5 ------------------------------- Key: JBSEAM-2266 URL: http://jira.jboss.com/jira/browse/JBSEAM-2266 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.GA Reporter: Pete Muir Priority: Minor Fix For: 2.0.2.GA web.xml references 2.5, but WLS only supports servlet 2.4 (but examples still seem to work...) -- 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 months

2
4
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, 6 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1296) Add <propagation type="?"/> as a child to <rule> or <redirect/> / <render/> in pages.xml

by Chris Rudd (JIRA)

Add <propagation type="?"/> as a child to <rule> or <redirect/> / <render/> in pages.xml ---------------------------------------------------------------------------------------- Key: JBSEAM-1296 URL: http://jira.jboss.com/jira/browse/JBSEAM-1296 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA, 1.2.0.GA Reporter: Chris Rudd While you can add a the propagation via a parameter its a bit verbose and cluttered (due to the value binding string literal) <page view-id="/editDocument.xhtml"> <navigation from-action="#{documentEditor.update}"> <rule if="#{documentEditor.errors.empty}"> <end-conversation/> <redirect view-id="/viewDocument.xhtml"> <param name="conversationPropagation" value="#{'none'}"/> </redirect> </rule> </navigation> </page> Adding a <propagation type="?"/> would be much cleaer. <page view-id="/editDocument.xhtml"> <navigation> <rule if-outcome="done"> <end-conversation/> <redirect view-id="/viewDocument.xhtml"> <propagation type="none"/> </redirect> </rule> </navigation> </page> Side note : The reason for needing to control the propagation in the circumstance above is so that the target view (/viewDocument.xhtml) can start with a new clean conversation. The redirect mechanism delays the end of the conversation untill it gets to the redirected to view, but I dont want that conv to be used. The before-redirect attribute doesnt work in this case as the redirect url needs to include data from the existing conversation (page parameters). I use the same scenario in other places via s:link/s:button but I cannot do this here as its dependent on the outcome not what link/button I pressed -- 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, 7 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1304) OC4J showing a blank page when deploying Glassfish example

by Richard Hoffman (JIRA)

OC4J showing a blank page when deploying Glassfish example ---------------------------------------------------------- Key: JBSEAM-1304 URL: http://jira.jboss.com/jira/browse/JBSEAM-1304 Project: JBoss Seam Issue Type: Feature Request Reporter: Richard Hoffman We are trying to get a Seam project deployed to OC4J. So far, the recommendation is to use the Glassfish example and deploy that to OC4J, but there are no instructions as to how to do this...so far, myself and a few others on the forums have only managed to get OC4J to show a blank screen. (I'm personally deploying via JDeveloper.) See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=100418 for petemuir's request to make this a Jira ticket. On a personal note, I don't have a preference as to who's EJB3 implementation to use (if any...Hibernate is fine, too). I just need to prove Seam works on OC4J...my client is making me use OC4J, despite my insistence that it's crap. :-/ -- 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, 7 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1530) Seam-gen: @Length in char(1) property

by Luiz Augusto Ruiz (JIRA)

Seam-gen: @Length in char(1) property ------------------------------------- Key: JBSEAM-1530 URL: http://jira.jboss.com/jira/browse/JBSEAM-1530 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.3.0.ALPHA Reporter: Luiz Augusto Ruiz Seam-gen put a @Length Hibernate validator in char property. When a field of a table is CHAR(1) Hibernate generates a char property and seam-gen put a @Length(size=1). This can be fixed updating the template pojo/GetPropertyAnnotation.ftl: <#include "Ejb3PropertyGetAnnotation.ftl"/> <#if !property.optional> @${pojo.importType("org.hibernate.validator.NotNull")} </#if> <#if property.columnSpan==1> <#assign column = property.getColumnIterator().next()/> <#if !c2h.isManyToOne(property) && !c2h.isTemporalValue(property) && column.length!=255 && column.length!=1> @${pojo.importType("org.hibernate.validator.Length")}(max=${column.length?c}) </#if> </#if> " && column.length!=1" fix the bug. -- 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, 7 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2158) Can't inject a org.hibernate.classic.Session

by Clint Popetz (JIRA)

Can't inject a org.hibernate.classic.Session -------------------------------------------- Key: JBSEAM-2158 URL: http://jira.jboss.com/jira/browse/JBSEAM-2158 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR3 Reporter: Clint Popetz If one does import org.hibernate.classic.Session; @In Session session; the injection throws an IllegalArgumentException, because HibernateSessionProxy doesn't implement the classic Session interface. It seems harmless to do this, and would allow for easier migration of large source bases from loyal hibernate early adoptees that are now transitioning to the next-big-thing. If making HibernateSessionProxy implement the classic interface would be acceptable, please make note of it here and I'll create a patch to that effect. -- 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, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2187) E-mail attachment <cid:xxxxxx> problem

by Stefano Zaccaria (JIRA)

E-mail attachment <cid:xxxxxx> problem -------------------------------------- Key: JBSEAM-2187 URL: http://jira.jboss.com/jira/browse/JBSEAM-2187 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.0.CR3 Reporter: Stefano Zaccaria Assigned To: Pete Muir Priority: Minor Fix For: 2.0.0.GA When use the cid: tag with seam like the document read <m:attachment value="#{person.photo}" contentType="image/jpeg" fileName="#{person.firstname}_#{person.lastname}.jpg" status="personPhoto" disposition="inline" /> <img src="cid:#{personPhoto.contentId}" /> In my email client (Thunderbird) the image is attachment and not place inline -- 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, 7 months

5
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007