November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly

by Andy Bosch (JIRA)

FacesMessages.instance().addToControl and Datatable do not work properly ------------------------------------------------------------------------ Key: JBSEAM-1855 URL: http://jira.jboss.com/jira/browse/JBSEAM-1855 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.0.GA Reporter: Andy Bosch It is possible do add FacesMessages via the Seam functionality with FacesMessages.instance().addToControl. In the parameters you have to pass the component id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In the JSF-way you have to pass the client-id. With normal input components you can use both ways. But when you work with datatables, you MUST work with the client-id, the Seam-way with using only the component-id does NOT work. Explanation: When using a datatable-tag, you only have one component. The renderer generates the various rows. In the component-tree there is yet only one component! If you want to add a FacesMessage to one row, you can only work with client-ids (because you have to include the row-index). My wish: Please change FacesMessages.instance().addToControl. for using with client-ids. -- 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, 3 months

10
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1572) Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly)

by Alex Savitsky (JIRA)

Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly) --------------------------------------------------------------------------- Key: JBSEAM-1572 URL: http://jira.jboss.com/jira/browse/JBSEAM-1572 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Alex Savitsky Priority: Minor ui:decorate preserves its children, while s:decorate groups them as one instead. This makes s:decorate unusable for form fields laid out using h:panelGrid, as there's no way to separate the field label from the field itself (they are grouped together). -- 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, 4 months

9
23
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2093) Optimize getting Id in Seam code for better performance

by Mikhail Grushinskiy (JIRA)

Optimize getting Id in Seam code for better performance ------------------------------------------------------- Key: JBSEAM-2093 URL: http://jira.jboss.com/jira/browse/JBSEAM-2093 Project: JBoss Seam Issue Type: Feature Request Reporter: Mikhail Grushinskiy This sequence of calls (used in PersistenceProvider) is quite slow Entity.forClass(bean.getClass()).getIdentifier(bean); 1) Entity.forClass() is reading annotations using JDK 5 methods (JDK 5 annotation reading is not that fast). Can it be cached? 2) JDK 5 reflection is used to get bean id (which is slower than optmized reflection with cglib) 3) There could be other reasons as well. I think repetitive calling of this sequence under profiler will give better picture. from PersistenceProvider.java /** * Get the value of the entity identifier attribute. * * @param bean a managed entity instance */ public Object getId(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getIdentifier(bean); } /** * Get the name of the entity * * @param bean * @param entityManager */ public String getName(Object bean, EntityManager entityManager) { return Entity.forClass(bean.getClass()).getName(); } /** * Get the value of the entity version attribute. * * @param bean a managed entity instance */ public Object getVersion(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getVersion(bean); } -- 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, 4 months

7
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2255) Undeploying multiple wars inside an ear causes IllegalStateException.

by Richard Teviotdale (JIRA)

Undeploying multiple wars inside an ear causes IllegalStateException. --------------------------------------------------------------------- Key: JBSEAM-2255 URL: http://jira.jboss.com/jira/browse/JBSEAM-2255 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Debian GNU/Linux x86_64 2.6.18-4 SMP, Java 1.5.0_12, JBoss 4.2.1.GA, Seam 2.0.0.GA. Reporter: Richard Teviotdale When undeploying an ear that contains two wars an IllegalStateException is generated. I have not checked for more than two wars but I suspect an exception would be generated for each undeploying war after the first. This exception does not prevent the server from undeploying and redeploying the ear, it just produces an error and stacktrace in the server log. Here's how to duplicate. - make a generic seam-gen project called test deployed as an ear - ant explode - go to $JBOSS_HOME/default/deploy/test.ear - recursive copy test.war directory to test2.war - edit META-INF/application.xml and create deploy entry for test2.war - run server - touch META-INF/application.xml see server log for following stack trace: 15:05:11,798 INFO [TomcatDeployer] undeploy, ctxPath=/test2, warUrl=.../deploy/test.ear/test2.war/ 15:05:12,067 INFO [TomcatDeployer] undeploy, ctxPath=/test, warUrl=.../deploy/test.ear/test.war/ 15:05:12,068 ERROR [[/test]] Session event listener threw exception java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36) at org.jboss.seam.contexts.Lifecycle.endSession(Lifecycle.java:220) at org.jboss.seam.contexts.ServletLifecycle.endSession(ServletLifecycle.java:129) at org.jboss.seam.servlet.SeamListener.sessionDestroyed(SeamListener.java:49) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:702) at org.apache.catalina.session.StandardSession.expire(StandardSession.java:660) snip... 15:05:12,276 ERROR [[/test]] Exception sending context destroyed event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36) at org.jboss.seam.contexts.Lifecycle.endApplication(Lifecycle.java:50) at org.jboss.seam.contexts.ServletLifecycle.endApplication(ServletLifecycle.java:118) at org.jboss.seam.servlet.SeamListener.contextDestroyed(SeamListener.java:39) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3893) -- 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, 5 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1486) Posibility to configure session scope type when in portlet environment

by ivica c (JIRA)

Posibility to configure session scope type when in portlet environment ---------------------------------------------------------------------- Key: JBSEAM-1486 URL: http://jira.jboss.com/jira/browse/JBSEAM-1486 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA Reporter: ivica c Fix For: 1.3.0.GA It would be nice to have a possibility to define the session scope type in the portlet environment: portlet scope or application scope. It affects not only seam session scope but also the conversation scope because the conversation scope internally uses the session scope. Now, seam components can be saved only in the portlet session scope so it is not possible to share data between portlets. If there is possibility to set components can be saved in the application scope, then data will be able to be shared between portlets in the same war. -- 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, 5 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1913) EL with parameters not work in a <ui:composition> facelet component

by Gilliard Cordeiro (JIRA)

EL with parameters not work in a <ui:composition> facelet component ------------------------------------------------------------------- Key: JBSEAM-1913 URL: http://jira.jboss.com/jira/browse/JBSEAM-1913 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 1.2.1.GA Environment: Windows or Linux, Java 6, Tomcat 6.0.14 Reporter: Gilliard Cordeiro EL with parameters not work in a <ui:composition> facelet component. The value of parameters is available in a <h:outputText>, for instance, but is null when executing a Java action methods. -- 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, 6 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-967) JBoss Seam - Support authentication from a realm (on Tomcat)

by Bradley Smith (JIRA)

JBoss Seam - Support authentication from a realm (on Tomcat) ------------------------------------------------------------ Key: JBSEAM-967 URL: http://jira.jboss.com/jira/browse/JBSEAM-967 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Bradley Smith Please see discussion in the JBoss forum reference. The idea is to allow the Seam Identity (security) component to get the Principal from the HttpServletRequest and to delegate the hasRole() calls to the HttpServletRequest as well. This is because, in my case, Tomcat has already forced the user to authenticate if necessary and the authentication, authorization information is available in the container's HttpServletRequest impl. Principal userPrincipal = httpServletRequest.getUserPrincipal(); boolean hasRole(String roleName) { return httpServletRequest.isUserInRole(roleName); } public String getUsername() { return httpServletRequest.getRemoteUser(); } public boolean isLoggedIn() { return httpServletRequest.getUserPrincipal() != null; } -- 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, 6 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1587) page parameters: option to bypass model-based validations

by Hung Tang (JIRA)

page parameters: option to bypass model-based validations --------------------------------------------------------- Key: JBSEAM-1587 URL: http://jira.jboss.com/jira/browse/JBSEAM-1587 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Hung Tang -- 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, 6 months

7
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2232) Reduce debug log level for events

by Christian Bauer (JIRA)

Reduce debug log level for events --------------------------------- Key: JBSEAM-2232 URL: http://jira.jboss.com/jira/browse/JBSEAM-2232 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Christian Bauer Priority: Critical Debug logging with Seam 2.x is completely useless. The most critical information in the debug log is the instantiation and lookup of components, however, if you enable DEBUG for org.jboss.seam.Component, you get thousands of these: 12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events We need to exclude the event firing from debug logging, even if we hardcode it. And, are these events really useful? I have no idea why and when I'd want to listen to "context variable initialized" events. -- 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, 7 months

9
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2026) Maven archetypes

by Pete Muir (JIRA)

Maven archetypes ---------------- Key: JBSEAM-2026 URL: http://jira.jboss.com/jira/browse/JBSEAM-2026 Project: JBoss Seam Issue Type: Feature Request Reporter: Pete Muir Assigned To: Dan Allen Fix For: 2.0.x Create some maven archetypes to compliment seam-gen. -- 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, 8 months

9
20
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