May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1344) Projects created with seam-gen run out of memory on redeployment

by Austin Kotlus (JIRA)

Projects created with seam-gen run out of memory on redeployment ---------------------------------------------------------------- Key: JBSEAM-1344 URL: http://jira.jboss.com/jira/browse/JBSEAM-1344 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Windows XP SP2, seam-gen, JBoss AS 4.0.5GA (with portal 1.2.0) installed with the JEMS Middleware Installer - BETA 3 Reporter: Austin Kotlus If you create a project through seam-gen with the default settings and: 1) deploy to jboss 2) view the home page 3) go to step 1 After about 4 iterations JBoss runs out of memory. On all successful deployments/views of the home page, memory usage stays constant. On the final deployment/view, all memory gets consumed. NOTE: I tried this same thing with the booking example and it does not have this issue. -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [jboss-user] [JBoss Seam] Seam calling from servlet filter..

by rishi

I am very new to jboss Seam and hence a simple query. I want to call up a seam component from inside a servlet filter as below: AuthorizerActionLocal authLocal = (AuthorizerActionLocal)Seam.componentForName("packageCreationAction") .getInstance( AuthorizerActionImpl.class); UserVO userVO = authLocal.login(userName); I get an error saying: java.lang.IllegalStateException: No application context active at org.jboss.seam.Component.forName(Component.java:1603) What is going wrong? Is it possible to call a seam component from inside a servlet filter as above? If not then is there any other way Regards, Rishi

17 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-842) s:hasRole() in jBPM EL.

by Gavin King (JIRA)

s:hasRole() in jBPM EL. ----------------------- Key: JBSEAM-842 URL: http://jira.jboss.com/jira/browse/JBSEAM-842 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Shane Bryzak Priority: Critical Currently, jBPM uses its own forked EL (which is a problem to begin with....). This means that it can't see the s: functions. We need to fix this problem ASAP. -- 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

17 years, 7 months

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1338) Unifying Start-page & Start-state pageflows

by Andy Gibson (JIRA)

Unifying Start-page & Start-state pageflows ------------------------------------------- Key: JBSEAM-1338 URL: http://jira.jboss.com/jira/browse/JBSEAM-1338 Project: JBoss Seam Issue Type: Feature Request Components: BPM Affects Versions: 1.2.1.GA Environment: Seam Reporter: Andy Gibson Do we really need two different types of page flows? Pageflows started in pages.xml requires a <start-page> as the start of the pageflow. Pageflows started on @Begin annotated methods need a <start-state>. The problem is that you could easily want to start pageflows from either location, and would then need to write two identical pageflows to accomodate this. i.e. A page for editing a widget is RESTful, and bookmarkable with the id in the URL, elsewhere, you may want to edit the same widget in a nested conversation. as part of another process. For the RESTFul URL, you need to use pages.xml to define the conversation start and the pageflow. For the other edit, you need a @begin annotated method (possibly with passing the widget instance in) and it requires a different pageflow, even though it is identical to the first. This annotation is also required to identify the need for a nested conversation. There is a real need for initiating pageflows from two separate places, and a need for them to use the same page flow. It is possible to work around this and go back to the @Create @Begin(pageflow="editwidget:") annotations on a method for RESTful urls. Given the number of times the problem appears in the forums, it appears to be an inobvious stumbling block without a real purpose as to its existence. It just seems messy to have two identical flows, when in 99% of cases the start page/state can be derived from one unified pageflow. In the other 1%, it is still possible to write a separate pageflow, but having two incompatible but almost identical flows appears clumsy. -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1339) EntityQuery: sorting support

by Hung Tang (JIRA)

EntityQuery: sorting support ---------------------------- Key: JBSEAM-1339 URL: http://jira.jboss.com/jira/browse/JBSEAM-1339 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.3.0.BETA1 Reporter: Hung Tang Would be nice to have EntityQuery support column sorting, possibly by changing the "order" value, but it also needs to keep track of whether a particular column is ascending or descending. Currently contactlist example doesn't support column sorting, but maybe this is planned for later. -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1162) propagation none with s:link

by Daniel Wiell (JIRA)

propagation none with s:link ---------------------------- Key: JBSEAM-1162 URL: http://jira.jboss.com/jira/browse/JBSEAM-1162 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: Seam 1.2.1.GA, MyFaces 1.1.6 nighly from march, Facelets 1.1.11 Reporter: Daniel Wiell <s:link action="/test.xhtml" propagate="none"/> behaves diffrently from <h:commandLink action="/test.xhtml"> <f:param name="conversationPropagation" value="none"/> </h:commandLink> The s:link propagates the conversation to the next view, while the h:commandLink doesn't. Here are some code to replicate this behavior: ----------------------- test1.xhtml <?xml version='1.0' encoding='UTF-8'?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:s="http://jboss.com/products/seam/taglib"> <head></head> <body> <h:form> <h:commandLink value="Refresh" action="/test1.xhtml"/> <br/><br/>  <s:link value="To test 2 (s:link)" action="/test2.xhtml" propagation="none"/> <br/>  <h:commandLink value="To test 2 (h:commandLink no propagate)" action="/test2.xhtml"> <f:param name="conversationPropagation" value="none"/> </h:commandLink> <br/>  <h:commandLink value="To test 2 (h:commandLink propagates)" action="/test2.xhtml"/> </h:form> </body> </html> ----------------------- test2.xhtml <?xml version='1.0' encoding='UTF-8'?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:s="http://jboss.com/products/seam/taglib"> <head></head> <body> <h:form> <s:link value="To test 1" action="toTest1"/> </h:form> </body> </html> ----------------------- The relevant parts from pages.xml <page view-id="/test1.xhtml" > <begin-conversation join="true"/> </page> <page view-id="/test2.xhtml"> <navigation> <rule if-outcome="toTest1"> <begin-conversation/> <redirect view-id="/test1.xhtml"/> </rule> </navigation> </page> -- 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

17 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1114) EntitySecurityListener problem in unit tests

by Artur Chyzy (JIRA)

EntitySecurityListener problem in unit tests -------------------------------------------- Key: JBSEAM-1114 URL: http://jira.jboss.com/jira/browse/JBSEAM-1114 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.0.GA Environment: Windows XP SP2, JBoss AS EJB3 profile 4.0.5.GA Reporter: Artur Chyzy When putting to orm.xml config for EntitySecurityListener <persistence-unit-metadata> <persistence-unit-defaults> <entity-listeners> <entity-listener class="org.jboss.seam.security.EntitySecurityListener"/> </entity-listeners> </persistence-unit-defaults> </persistence-unit-metadata> and trying to run unit tests the following exception is thrown java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.hibernate.ejb.event.ListenerCallback.invoke(ListenerCallback.java:33) at org.hibernate.ejb.event.EntityCallbackHandler.callback(EntityCallbackHandler.java:78) at org.hibernate.ejb.event.EntityCallbackHandler.postLoad(EntityCallbackHandler.java:71) at org.hibernate.ejb.event.EJB3PostLoadEventListener.onPostLoad(EJB3PostLoadEventListener.java:35) at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:201) at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842) at org.hibernate.loader.Loader.doQuery(Loader.java:717) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2821) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.jav a:370) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:351) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:122) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:808) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:801) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:155) at pl.alternativ.med.pacjent.DeklaracjaPOZUnitTest.utworz(DeklaracjaPOZUnitTest.java:78) at org.hibernate.ejb.event.ListenerCallback.invoke(ListenerCallback.java:30) ... 42 more Caused by: java.lang.IllegalStateException: No active session context at org.jboss.seam.security.Identity.instance(Identity.java:108) at org.jboss.seam.security.EntitySecurityListener.postLoad(EntitySecurityListener.java:24) ... 47 more ... Removed 26 stack frames Without EntitySecurityListener config in orm.xml tests runs fine. -- 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

17 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1337) Add generated sources to .cvsignore

by Stephan Heffner (JIRA)

Add generated sources to .cvsignore ----------------------------------- Key: JBSEAM-1337 URL: http://jira.jboss.com/jira/browse/JBSEAM-1337 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.2.1.GA Reporter: Stephan Heffner Priority: Minor Attachments: seam-cvs-ignore-patch.txt Add generated sources to .cvsignore. Created by 'ant build' in the top level jboss-seam project dir. -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1115) Conversation propagation problem in integration tests

by Artur Chyzy (JIRA)

Conversation propagation problem in integration tests ----------------------------------------------------- Key: JBSEAM-1115 URL: http://jira.jboss.com/jira/browse/JBSEAM-1115 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.0.GA Environment: Windows XP SP2, JBoss 4.0.5GA Reporter: Artur Chyzy When trying to run integration test with following config in edit.page.xml <navigation from-action="#{someBean.select}"> <begin-conversation nested="true"/> <redirect view-id="/edit.jspx" /> </navigation> after invoking of select method the conversation is not long running (the object added using Contexts.getConversationContext().set() is not put to the conversation) and Manager.instance().isLongRunningConversation() return false Using @Begin on select method works fine. -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-668) method bindings with a parameter don't work in facelets tag source files

by Guy Veraghtert (JIRA)

method bindings with a parameter don't work in facelets tag source files ------------------------------------------------------------------------ Key: JBSEAM-668 URL: http://jira.jboss.com/jira/browse/JBSEAM-668 Project: JBoss Seam Issue Type: Bug Reporter: Guy Veraghtert Attachments: seam-bug-method-parameter.zip Method bindings with a parameter on a parameterized target bean don't work in a facelets tag source file. java.lang.NullPointerException at org.jboss.seam.ui.facelet.MethodExpressionHelper.findParamTypes(MethodExpressionHelper.java:146) at org.jboss.seam.ui.facelet.MethodExpressionHelper.invokeTheExpression(MethodExpressionHelper.java:98) at org.jboss.seam.ui.facelet.ParamMethodExpression.invoke(ParamMethodExpression.java:62) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96) -- 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

17 years, 7 months

5
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2007