January 2008 - seam-issues - Jboss List Archives

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

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

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2491) Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released

by Marcus Adair (JIRA)

Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released ----------------------------------------------------------------- Key: JBSEAM-2491 URL: http://jira.jboss.com/jira/browse/JBSEAM-2491 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.0.1.CR1 Reporter: Marcus Adair According to the groovy-all.jar/META-INF/MANIFEST.MF file, Groovy 1.1 beta is still be used. 1.5 was released in 12/2007 and appears to solve some gotchas related to its use with Seam. See: http://docs.codehaus.org/display/GROOVY/2007/12/07/Groovy+1.5+released -- 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
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2482) Possible work around for Weblogic "varargs" EJB issue

by Jay Balunas (JIRA)

Possible work around for Weblogic "varargs" EJB issue ----------------------------------------------------- Key: JBSEAM-2482 URL: http://jira.jboss.com/jira/browse/JBSEAM-2482 Project: JBoss Seam Issue Type: Task Components: Documentation, Examples Affects Versions: 2.0.1.CR1 Reporter: Jay Balunas Priority: Minor Attachments: full-stack-of-ejb-transient-error.txt There is a know issue with weblogic and support for EJBs that use variable arguments. This is documented in the reference guide for more details. I've attached the full stack trace from the console. The main errors revolve around EJB3 timers - there may be a way to disable timers through the weblogic.xml deployment descriptor, or perhaps a different file. There are other warnings around EJB synchronization, but they may still function. If solved the reference docs should be updated. -- 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
14
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, 7 months

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

3
4
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, 7 months

4
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2408) Icefases inputFile breaks seam application, EJB's will remain associated with another transaction and cannot be reloaded from backupstore

by Indrek Altpere (JIRA)

Icefases inputFile breaks seam application, EJB's will remain associated with another transaction and cannot be reloaded from backupstore ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2408 URL: http://jira.jboss.com/jira/browse/JBSEAM-2408 Project: JBoss Seam Issue Type: Bug Components: EJB3, ICE Faces Integration Affects Versions: 2.0.0.GA Environment: on Glassfish server Reporter: Indrek Altpere Priority: Blocker When turning on seams's ejb transaction with <transaction:ejb-transaction /> icefaces file upload fails. When I try to render the outputprogress in upload's progress listeners, I get exception right away NRU-org.jboss.seam.transaction.EjbSynchronizations: Cannot load from BACKUPSTORE FOR Key: <3e90c03b00a81f-ffffffffd01e540c-1> EJB5018: An exception was thrown during an ejb invocation on [EjbSynchronizations] javax.ejb.NoSuchObjectLocalException: The EJB does not exist. session-key: 3e90c03b00a81f-ffffffffd01e540c-1 and in the end there is exception: Caused by: javax.el.ELException: /inputfile.xhtml @22,93 value="File Name: #{inputFileBackerBean.fileName}": javax.ejb.EJBException: nested exception is: java.lang.IllegalStateException: EJB is already associated with an incomplete transaction at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:76) at javax.faces.component.UIOutput.getValue(UIOutput.java:173) ... 82 more When I turn off the progress thing for icefaces file upload and only set actionlistener (is called when file upload completes), then after first upload, whole application becomes unusable (clicking on any seam link or trying another uploads ends up at debug page with same exceptions in server log as shown before). It seems that EJB is not stored to because some transaction is still going on, and since it is not stored, it cannot be restored from storage and the above exceptions occur. I have posted full stacktraces to icefaces forums at http://www.icefaces.org/JForum/posts/list/6613.page Icefaces used is 1.7DR#3, seam used is Seam 2.0.0GA, Glassfish is v2 (v2ur1 does not make any difference) Example ear for glassfish deployment http://www.flamebox.org/fserver/soov.ear Source http://www.flamebox.org/fserver/soovexample.rar -- 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
6
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, 7 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2517) Id Attribute does not render on s:graphicImage

by nathan dennis (JIRA)

Id Attribute does not render on s:graphicImage ---------------------------------------------- Key: JBSEAM-2517 URL: http://jira.jboss.com/jira/browse/JBSEAM-2517 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.1.CR1 Environment: jboss 4.2.1 Reporter: nathan dennis id attribute will not render on a s:graphicImage. Code: <s:graphicImage id="phototoedit" value="#{modeditAction.outpic}" style="border:0px;" rendered="#{modeditAction.outpic != null}"/> renders as Code: <img src="/picture/seam/resource/graphicImage/org.jboss.seam.ui.GraphicImageStore.-4aa1b80-11799ac64d4--7fee.p ng" style="border:0px;" /> -- 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
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008