December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3710) For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate

by Pete Muir (JIRA)

For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate ----------------------------------------------------------------------------------- Key: JBSEAM-3710 URL: https://jira.jboss.org/jira/browse/JBSEAM-3710 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Priority: Critical Fix For: 2.1.1.CR2 This is possible only in JavaBeans as the HttpSession is passed as an arguement to the sessionWillPassivate/sessionWillActivate call, and we can store the conversationId in @AroundInvoke method. In EJBs, the passivation/activation happens independently of the HttpSession. This should be a performance improvement, @PrePassivate (serialize out entities) will be called just as much, but @PostActivate will be called a lot less. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

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

14 years, 11 months

7
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3849) ClassLoader cannot find xhtml files when scanning page.xml files in an EAR with Multiple WARs

by Reind D (JIRA)

ClassLoader cannot find xhtml files when scanning page.xml files in an EAR with Multiple WARs --------------------------------------------------------------------------------------------- Key: JBSEAM-3849 URL: https://jira.jboss.org/jira/browse/JBSEAM-3849 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.CR2 Environment: JBoss AS 5.0.0.GA, JDK6, Seam 2.1.1.CR2 Reporter: Reind D I have an EAR that contains multiple WAR files. The ear deploys correctly, but on the first web request, during a scan of all *.page.xml files, I get the following output to the log for each page.xml file: WARN [VFSScanner] Error handling item 'login/index.page.xml': java.lang.NullPointerException: Cannot find URL from classLoader for login/index.page.xml, loading from org.jboss.web.tomcat.service.WebCtxLoader$ENCLoader@1ed964f The NPE occurs in this code: org.jboss.seam.deployment.FileDescriptor.java this.url = classLoader.getResource(name); if (this.url == null) { throw new NullPointerException("Cannot find URL from classLoader for " + name + ", loading from " + classLoader); } As a result, none of the page.xml files work. Note that the second WAR works as expected, with all the page.xml files loaded correctly. The same project worked in Seam 2.0.2.SP1 and JBoss AS 4.2.3.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3816) rules-agent should also work with dsl-based rules

by Joerg Viola (JIRA)

rules-agent should also work with dsl-based rules ------------------------------------------------- Key: JBSEAM-3816 URL: https://jira.jboss.org/jira/browse/JBSEAM-3816 Project: Seam Issue Type: Feature Request Components: Drools Affects Versions: 2.0.2.GA Reporter: Joerg Viola Usings the components.xml below, one should be able to dynamically deploy dsl-based rules. The DSL does not need to be dynamically changed, it may be loaded from the classpath. <drools:rule-base name="billingRules" dsl-file="/META-INF/billing.dsl"> <drools:rule-files> <value>/META-INF/billing.dslr</value> </drools:rule-files> </drools:rule-base> <drools:rule-agent startup="true" auto-create="true" name="billingRulebase" configurationFile="/billing.properties" /> <drools:managed-working-memory name="billingWorkingMemory" auto-create="true" scope="event" rule-base="#{billingRules}"> </drools:managed-working-memory> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3702) NotBoundException when undeploying Seam examples on AS5

by Jozef Hartinger (JIRA)

NotBoundException when undeploying Seam examples on AS5 ------------------------------------------------------- Key: JBSEAM-3702 URL: https://jira.jboss.org/jira/browse/JBSEAM-3702 Project: Seam Issue Type: Bug Components: EJB3, Examples Affects Versions: 2.1.0.SP1 Environment: JDK 6 AS 5 trunk Seam trunk r9564 Reporter: Jozef Hartinger I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

5
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3555) SeamMailAgain

by Markus Heidt (JIRA)

SeamMailAgain ------------- Key: JBSEAM-3555 URL: https://jira.jboss.org/jira/browse/JBSEAM-3555 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.CR1 Environment: JBoss AS 4.2.1.GA JBoss Seam 2.1.0-SNAPSHOT (10.10. HudsonNo330) Reporter: Markus Heidt Simple Mailing via Renderer doesn't work. 'Seam-gen'erated a new project and added a new action 'sendMail' Added the line to the action code: Renderer.instance().render("/simple.xhtml"); simple.xhtml is a modified version of the seam example (without #{person}) Error after executing the action: 2008-10-14 11:40:21,847 FATAL [javax.enterprise.resource.webcontainer.jsf.application] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory javax.faces.el.EvaluationException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.facesContextFactory at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) ... Caused by: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

18
55
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

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

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3737) Beta jsf-facelets.jar 1.1.15 causes crash with trees+outputlink, please go back to 1.1.14

by Francisco Jose Peredo Noguez (JIRA)

Beta jsf-facelets.jar 1.1.15 causes crash with trees+outputlink, please go back to 1.1.14 ----------------------------------------------------------------------------------------- Key: JBSEAM-3737 URL: https://jira.jboss.org/jira/browse/JBSEAM-3737 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Environment: Java 1.5, Tomcat 6.0.18, Windows Xp Sp3 Reporter: Francisco Jose Peredo Noguez I upgraded from Seam 2.0.2SP1 in to 2.1.0SP1 and now I am getting duplicate Id for a component errors (this works fine in 2.0.2SP1, I have 2 rich trees with outputlinks inside them): java.lang.IllegalStateException: duplicate Id for a component formMenuDinamico:menuDinamico:j_id13 Please see See Forum Reference for full stacktrace. I isolated the bad .jar: jsf-facelets.jar, if I use Seam 2.1.0SP1 but I use the file that came with 2.0.2SP1 everything works fine. The version of jsf-facelets.jar that works fine is 1.1.14, the one that fails is 1.1.15.B1. I think the B1 at the end means BETA1, I think Seam shouldn't be using unstable versions for its dependencies. I visited https://facelets.dev.java.net/servlets/ProjectDocumentList?folderID=3635&..., and it seems to confirm that 1.1.15.B1 is not an officially released (and stable) version -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2579) Messages.properties do not work as expected with multiple WARs inside multiple Seam EARs

by Reind D (JIRA)

Messages.properties do not work as expected with multiple WARs inside multiple Seam EARs ---------------------------------------------------------------------------------------- Key: JBSEAM-2579 URL: http://jira.jboss.com/jira/browse/JBSEAM-2579 Project: JBoss Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.1.GA Environment: JBoss 4.2.2 Reporter: Reind D When 2 Seam apps are deployed, both with multiple WARs each of which as a WEB-INF/classes/messages.properties file, the messages for one of the web contexts will not work. Instead, the messages for the other WAR in the same EAR will be displayed. I've attached a sample application that demonstrates this behavior. It is modified from the "Registration" example. Steps: 1) Untar the archive 2) Copy to the app server's deploy directory 3) Go to the following URLs: http://localhost:8080/a/register.seam http://localhost:8080/b/register.seam http://localhost:8080/c/register.seam http://localhost:8080/d/register.seam The 'expected' and 'actual' fields should always match, but they won't in 1 case. -- 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
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008