November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2185) s:selectItems performance issue with many combo-box items

by Stephan Bublava (JIRA)

s:selectItems performance issue with many combo-box items --------------------------------------------------------- Key: JBSEAM-2185 URL: http://jira.jboss.com/jira/browse/JBSEAM-2185 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR3 Reporter: Stephan Bublava Priority: Minor UISelectItems.asSelectItems() iterates over all combo box items and calls getLabel() and getDisabled() (usually value expressions) twice per entry: for (Object o : iterable) { initVar(o); selectItems.add(new javax.faces.model.SelectItem(o, getLabel() == null ? null : getLabel(), "", getDisabled() == null ? false : getDisabled())); destroyVar(); } Using local variables can make a noticeable difference, if there are many combo box items. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2212) framework objects do not work with entities mapped in *.hbm.xml

by daniel varga (JIRA)

framework objects do not work with entities mapped in *.hbm.xml --------------------------------------------------------------- Key: JBSEAM-2212 URL: http://jira.jboss.com/jira/browse/JBSEAM-2212 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.0.CR3 Reporter: daniel varga I develop a web app which has it model classes in a separate jar that also contains the hbm.xml files for mapping the entities. The entities are accessed through standard JPA EntityManager. There are both query and home components declared in components.xml: <framework:entity-query name="subsystemList" ejbql="select s from CaasSubsystem s" max-results="1000" /> <framework:entity-home name="subsystemHome" entity-class="com.comptel.cs.caas.pojo.CaasSubsystem" /> Everything goes fine until I delete an entity with the home component. Then Seam.getEntityClass gets invoked and returns null, which in turn causes the following: Caused by: java.lang.IllegalArgumentException: Not an entity class: com.comptel.cs.caas.pojo.CaasSubsystem at org.jboss.seam.Entity.forClass(Entity.java:208) at org.jboss.seam.persistence.PersistenceProvider.getName(PersistenceProvider.java:75) at org.jboss.seam.persistence.HibernatePersistenceProvider.getName(HibernatePersistenceProvider.java:246) at org.jboss.seam.framework.EntityHome.getEntityName(EntityHome.java:123) at org.jboss.seam.framework.Home.getSimpleEntityName(Home.java:255) at org.jboss.seam.framework.Home.raiseAfterTransactionSuccessEvent(Home.java:250) at org.jboss.seam.framework.EntityHome.remove(EntityHome.java:64) This is because the Seam.getEntityClass checks for @javax.persisence.Entity annotation or ejb3 xml mapping, but it does not take into account that entities can mapped by hbm.xml files too. I tried using hibernate-entity-home and hibernate-entity-query components , but it did not help and the exception occurred more often, not only after invoking remove on the entity home component. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-326) Dynamic view-id in Pageflow

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-326?page=all ] Pete Muir closed JBSEAM-326. ---------------------------- Resolution: Done Fixed - please test for me! > Dynamic view-id in Pageflow > --------------------------- > > Key: JBSEAM-326 > URL: http://jira.jboss.com/jira/browse/JBSEAM-326 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Affects Versions: 1.1.0.BETA1 > Environment: seam cvs as of 8/2/2006 > Reporter: John Conner > Assigned To: Pete Muir > Fix For: 2.0.1.GA > > Attachments: jbseam-326.diff, pageflow-dynamic-view-id, pageflow-dynamic-view-id > > > I have a need where I would like to have an el expression in the view-id of a pageflow. I've looked a bit at themes; and while I might be able to do what I want by replacing the template.xhtml dynamically, I don't (at least initial) like indirection. > I believe the patch for this functionality is reletively trivial. Altough, I very well could have missed something. Basically, I modified the Page.getViewId() method to evaulate the value returned and replace any el expressions. > I also modified the Number Guess example to use this feature. > I have attached an initial patch as a proof of concept if it is of any interest to the Seam developers. > -- JC -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2191) Include latest stable Drools realease with Seam2.0

by Juraj Holtak (JIRA)

Include latest stable Drools realease with Seam2.0 -------------------------------------------------- Key: JBSEAM-2191 URL: http://jira.jboss.com/jira/browse/JBSEAM-2191 Project: JBoss Seam Issue Type: Task Components: Drools Affects Versions: 2.0.0.CR3 Reporter: Juraj Holtak Please bundle the latest Drools binaries with Seam2.0 as they fix serious bugs. -- 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-2188) Imports are broken

by Matt Drees (JIRA)

Imports are broken ------------------ Key: JBSEAM-2188 URL: http://jira.jboss.com/jira/browse/JBSEAM-2188 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR3 Reporter: Matt Drees @Import doesn't work. I think the fix to http://jira.jboss.com/jira/browse/JBSEAM-2076 broke this. Init.initNamespaceForName(String name, boolean isComponent) always returns the root namespace when isComponent is false (which happens when initializing the namespace for @Imports). This isn't what Component.getInstanceInAllNamespaces is expecting. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2239) After a logout, roles are not cleared

by Adam Warski (JIRA)

After a logout, roles are not cleared ------------------------------------- Key: JBSEAM-2239 URL: http://jira.jboss.com/jira/browse/JBSEAM-2239 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Adam Warski After logging out, using a link: <s:link action="#{identity.logout}" value="Logout" rendered="#{identity.loggedIn}" /> the roles are not cleared, that is, when the response page is rednered, #{s:hasRole('admin')} is still true (assuming the user that was logged in had the role :) ). Everything is ok if you add a view="xxx.xhtml" parameter to s:link, however I think it should work without it, too, so that users can logout and stay on the page they were last viewing, if authorization permits them to. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2204) Potential XSS issue in seam text with allowed href attribute

by Christian Bauer (JIRA)

Potential XSS issue in seam text with allowed href attribute ------------------------------------------------------------ Key: JBSEAM-2204 URL: http://jira.jboss.com/jira/browse/JBSEAM-2204 Project: JBoss Seam Issue Type: Bug Components: Wiki Affects Versions: 2.0.0.GA Reporter: Christian Bauer Assigned To: Christian Bauer We allow <a href="foo"/> in Seam Text, which can potentially be abused to inject Javascript executed in the context of the page. Need to evaluate impact of leaving or removing. -- 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

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2238) SecurityInterceptor not invoked for Web Service requests

by Shane Bryzak (JIRA)

SecurityInterceptor not invoked for Web Service requests -------------------------------------------------------- Key: JBSEAM-2238 URL: http://jira.jboss.com/jira/browse/JBSEAM-2238 Project: JBoss Seam Issue Type: Bug Components: WS Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 2.0.1.GA As the SecurityInterceptor has a type of InterceptorType.CLIENT, it is not included in the interceptor stack for the invocation context of web service requests. We need to somehow include the SecurityInterceptor in the interceptor stack for these requests. -- 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

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2237) Namespace or alias of messages' key

by Pierre Raoul (JIRA)

Namespace or alias of messages' key ----------------------------------- Key: JBSEAM-2237 URL: http://jira.jboss.com/jira/browse/JBSEAM-2237 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Pierre Raoul To be able to defined messages alias in components.xml: | <component name="org.jboss.seam.international.messages"> | <property name="abbrs"> | <value>*:btn=lacewiki.button</value> | <value>*:lb=lacewiki.label</value> | <value>/admin.xhtml:_=lacewiki.button.adminHome.</value> | <value>/login.xhtml:ur.=lacewiki.button.userRegister.</value> | </property> | </component> | | Now in /admin.xhtml instead of writing something like #{"messages['lacewiki.button.adminHome.Remove']"} it's possible to write #{"msg._Remove"} And in /login.xhtml: #{msg['ur.Register]} -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2236) Add the possibility to deploy process definition never/ifNotExists/always in components.xml

by Alexandre Russel (JIRA)

Add the possibility to deploy process definition never/ifNotExists/always in components.xml ------------------------------------------------------------------------------------------- Key: JBSEAM-2236 URL: http://jira.jboss.com/jira/browse/JBSEAM-2236 Project: JBoss Seam Issue Type: Patch Components: BPM Reporter: Alexandre Russel Priority: Optional Process definition are always deployed atm. The patch allows to set deployement to: always (a process definition will always be deployed even if it already exists in the db at startup time, this is the default) never (never deployed, would be the responsability of the code to do so) ifNotExists (if a processDefinition of the same name already exists in the database, do nothing, otherwise deploy). I added a separate folder for test (I'll start a thread in the forum about it). related thread/jira: http://jira.jboss.org/jira/browse/JBSEAM-198 http://jira.jboss.org/jira/browse/JBSEAM-1034 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103819 -- 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

1
2
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