November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2153) ConversationEntry.redirect applies page parameters

by Pete Muir (JIRA)

ConversationEntry.redirect applies page parameters -------------------------------------------------- Key: JBSEAM-2153 URL: http://jira.jboss.com/jira/browse/JBSEAM-2153 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Fix For: 2.0.1.GA ConversationEntry.redirect applies page parameters to the redirect. Thus state in the redirected-to conversation is overwritten by state in the redirected-from conversation when: 1) The page parameter's value exists in the redirected-from conversation 2) The redirected-to conversation's view applies a page parameter with the same name If (2) doesn't happen it doesn't cause the state to be overwritten but we still end up with an incorrect url. -- 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
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1103) Deploying Seam example app into /trunk causes ZipException

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-1103?page=comments#action_12387892 ] Pete Muir commented on JBSEAM-1103: ----------------------------------- We should wait for Beta3 of AS 5 to be released before working further on this IMO. > Deploying Seam example app into /trunk causes ZipException > ---------------------------------------------------------- > > Key: JBSEAM-1103 > URL: http://jira.jboss.com/jira/browse/JBSEAM-1103 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Environment: r61655 of /trunk and jboss-seam-1.2.0.PATCH1 > Reporter: Charles Crouch > Fix For: 2.0.1.GA > > Attachments: cglib-nodep-2.1_3.jar, el-api.jar, el-ri.jar, jboss-seam-numberguess.ear > > > Deploying a modified version of jboss-seam-numberguess.ear into the current Beta2 server causes ZipException's to be thrown during startup and trying to hit http://localhost:8080/seam-numberguess produces 500's. Deploying the same app into Beta1 works fine. > Steps to reproduce: > 1) Copy > jboss-seam-1.2.0.PATCH1\lib\el-api.jar > and > jboss-seam-1.2.0.PATCH1\lib\el-ri.jar > to > build\output\jboss-5.0.0.Beta2\server\default\deployers\jbossweb.deployer\jsf-libs > 2) Copy > cglib-nodep-2.1_3.jar (version probably doesn't matter) > to > build\output\jboss-5.0.0.Beta2\server\default\lib > 3) Copy modified jboss-seam-numberguess.ear > to > build\output\jboss-5.0.0.Beta2\server\default\deploy > 4) Start the server and you get several exceptions like the following... > 12:09:11,896 INFO [Catalina] Server startup in 190 ms > 12:09:20,769 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=Dispatcher,service=EJB3 with dependencies: > 12:09:24,244 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.Dispatcher ejbName: Dispatcher > 12:09:24,484 WARN [JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED > 12:09:24,484 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TransactionListener,service=EJB3 with dependencies: > 12:09:26,216 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.TransactionListener ejbName: TransactionListener > 12:09:29,441 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war > 12:09:35,319 INFO [TomcatDeployment] deploy, ctxPath=/seam-numberguess, vfsUrl=jboss-seam-numberguess.ear/jboss-seam-numberguess.war > 12:09:38,895 INFO [ServletContextListener] Welcome to Seam 1.2.0.PATCH1 > 12:09:38,995 INFO [Scanner] scanning: vfsfile:/C:/usr/projects/current/jboss/trunk/build/output/jboss-5.0.0.Beta2/server/default/deploy/jboss-seam-numberguess.ear/jboss-seam.jar > 12:09:38,995 WARN [Scanner] could not read entries > java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:203) > at java.util.zip.ZipFile.<init>(ZipFile.java:234) > at org.jboss.seam.deployment.Scanner.handleArchive(Scanner.java:110) > at org.jboss.seam.deployment.Scanner.scan(Scanner.java:96) > at org.jboss.seam.deployment.NamespaceScanner.getPackages(NamespaceScanner.java:34) > at org.jboss.seam.init.Initialization.addNamespaces(Initialization.java:590) > at org.jboss.seam.init.Initialization.<init>(Initialization.java:80) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) -- 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-2182) Add support for Seam component support for InitializingBean in the Spring integration

by Michael Youngstrom (JIRA)

Add support for Seam component support for InitializingBean in the Spring integration ------------------------------------------------------------------------------------- Key: JBSEAM-2182 URL: http://jira.jboss.com/jira/browse/JBSEAM-2182 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 2.0.0.CR3 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.0.1.GA Spring provides integrations with lots of 3rd party tools. It would be nice if Seam could take better advantage of these integrations without having to embed a Spring container. One way Seam can do this is provide an interceptor that looks for beans that implemented InitialziingBean and calls afterPropertiesSet(). -- 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-2150) JSF can try to access it's messages bundle before Seam starts

by Pete Muir (JIRA)

JSF can try to access it's messages bundle before Seam starts ------------------------------------------------------------- Key: JBSEAM-2150 URL: http://jira.jboss.com/jira/browse/JBSEAM-2150 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Minor Fix For: 2.0.1.GA This causes an IllegalStateException as the contexts aren't active. We should deal with this case by just returning the key or using the delegate or something. -- 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-2055) NPE in UIComponent when ViewRoot not available

by Matt Drees (JIRA)

NPE in UIComponent when ViewRoot not available ---------------------------------------------- Key: JBSEAM-2055 URL: http://jira.jboss.com/jira/browse/JBSEAM-2055 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR1 Reporter: Matt Drees Priority: Minor I have an @Observer("org.jboss.seam.beforePhase") in a component that injects a UIComponent via #{uicomponent[...]} java.lang.NullPointerException at org.jboss.seam.faces.UiComponent$1.get(UiComponent.java:56) at org.jboss.seam.faces.UiComponent$1.get(UiComponent.java:45) at javax.el.MapELResolver.getValue(MapELResolver.java:51) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64) at org.jboss.el.parser.AstBracketSuffix.getValue(AstBracketSuffix.java:59) at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112) at org.jboss.seam.Component.getValueToInject(Component.java:2126) at org.jboss.seam.Component.injectAttributes(Component.java:1599) at org.jboss.seam.Component.inject(Component.java:1417) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) ... at org.jboss.seam.Component.callComponentMethod(Component.java:2087) at org.jboss.seam.core.Events.raiseEvent(Events.java:83) at org.jboss.seam.jsf.SeamPhaseListener.raiseEventsBeforePhase(SeamPhaseListener.java:381) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:118) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) ... -- 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-2229) Upgrade to JBPM-jPDL 3.2.2

by Matthew Lieder (JIRA)

Upgrade to JBPM-jPDL 3.2.2 -------------------------- Key: JBSEAM-2229 URL: http://jira.jboss.com/jira/browse/JBSEAM-2229 Project: JBoss Seam Issue Type: Task Components: BPM Affects Versions: 2.0.0.GA Reporter: Matthew Lieder Fix For: 2.0.1.GA Not sure why this hasn't happened yet, but Seam's currently using jBPM-jPDL 3.2.1 when 3.2.2 has been out since late September. At the very least, it'd be extremely nice if it was added to the repository.jboss.org/maven2 repo... -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-340) Streamline use of i18n validation error messages

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-340?page=comments#action_12387553 ] Pete Muir commented on JBSEAM-340: ---------------------------------- Isn't this issue out of date. No, we don't need a dependency on commons-xxx > Streamline use of i18n validation error messages > ------------------------------------------------- > > Key: JBSEAM-340 > URL: http://jira.jboss.com/jira/browse/JBSEAM-340 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.0.1 > Environment: Seam 1.0.1.GA > Reporter: Manfred Moser > Assigned To: Emmanuel Bernard > > As described in the forum post referenced introducing i18n error message from validation of an entity bean does not have an example anywhere and actually only works nicely with a bit of a work around. The situation is that the hibernate validation needs the error message in ValidatorMessages_*.properties and Seam has its properties in messages_*.properties. For the entity bean to work without Seam (e.g. in a unit test that verifies the validation settings) the messages have to exist in the hibnerate resource bundle. For usage in Seam they have to exist in the Seam bundle. For a Seam app to actually start up all properties related to exist in the Hibnerate and the Seam bundles .. which leads to ugly duplication. A fix is to keep all properties in the seam bundles and copy them into the hibernate bundle at build time. The forum post has a ant task. It would however be better if Seam could somehow manage to pass the resources to hibernate or otherwise just automatically include the hibernate bundle. An example of the i18n of the validation message and other annotation based messages should be included in the examples. -- 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] Commented: (JBSEAM-340) Streamline use of i18n validation error messages

by simon lebettre (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-340?page=comments#action_12387530 ] simon lebettre commented on JBSEAM-340: --------------------------------------- What about using something like common-configuration's property includes ? #inside messages_en.properties include ValidatorMessages_en.properties http://commons.apache.org/configuration/userguide/howto_properties.html#I... > Streamline use of i18n validation error messages > ------------------------------------------------- > > Key: JBSEAM-340 > URL: http://jira.jboss.com/jira/browse/JBSEAM-340 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.0.1 > Environment: Seam 1.0.1.GA > Reporter: Manfred Moser > Assigned To: Emmanuel Bernard > > As described in the forum post referenced introducing i18n error message from validation of an entity bean does not have an example anywhere and actually only works nicely with a bit of a work around. The situation is that the hibernate validation needs the error message in ValidatorMessages_*.properties and Seam has its properties in messages_*.properties. For the entity bean to work without Seam (e.g. in a unit test that verifies the validation settings) the messages have to exist in the hibnerate resource bundle. For usage in Seam they have to exist in the Seam bundle. For a Seam app to actually start up all properties related to exist in the Hibnerate and the Seam bundles .. which leads to ugly duplication. A fix is to keep all properties in the seam bundles and copy them into the hibernate bundle at build time. The forum post has a ant task. It would however be better if Seam could somehow manage to pass the resources to hibernate or otherwise just automatically include the hibernate bundle. An example of the i18n of the validation message and other annotation based messages should be included in the examples. -- 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-1421) Example of how to extend Identity with configuration

by Pete Muir (JIRA)

Example of how to extend Identity with configuration ---------------------------------------------------- Key: JBSEAM-1421 URL: http://jira.jboss.com/jira/browse/JBSEAM-1421 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.2.1.GA Reporter: Pete Muir Assigned To: Shane Bryzak Priority: Minor This seems to come up a lot on the forum -- 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-1901) ConversationEntry.isDisplayable should also check that its not isRemoveAfterRedirect

by Chris Rudd (JIRA)

ConversationEntry.isDisplayable should also check that its not isRemoveAfterRedirect ------------------------------------------------------------------------------------ Key: JBSEAM-1901 URL: http://jira.jboss.com/jira/browse/JBSEAM-1901 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd I have a situation where temporary conversations that are promoted to long running (due to a redirect) for views with a valid description show up in the conversationList. If ConversationEntry.isDisplayable adds the contraint !isRemoveAfterRedirect() , then the issue does not appear. public boolean isDisplayable() { return !isEnded() && !isRemoveAfterRedirect() && getDescription()!=null; } NOTE: The particular instance this occurs in for me is due to a current limitation in seam. Currently there is no way to end the current conversation and start a new one (under a new conversation context) in the same request. For instance : Im in conversation id 5, I hit the "done" button, which I want to end the current conversation (and destroy that context), then redirect me toto the same view starting a new conversation. There use to be a "new" propagation mode, but that seems to be missing now. If you simply start a new conversation after the redirect, the current conversation (the one promoted due to the redirect, the same one you wanted to end) is just propagated along and contains all same state as before. This is not the desired affect, I want a NEW conversation that contains only new items So my "workaround" is to have the "done" out come end the conversation, redirect me to another action, that then redirects me to my final view with a propagation none. The "problem" is that the first conversation, is still out there waiting to be "continued" so that it can convert it back into a temporary (as its marked removeAfterRedirect). Since is a long running conv, it shows up in the conv list (which it should not as its not really a long running conversation). The conv is eventually pruned (due to conv timeout). <rule if-outcome="done"> <end-conversation/> <redirect>  <param name="actionOutcome" value="#{'edit'}"/> <param name="conversationPropagation" value="none"/> </redirect> </rule> <rule if-outcome="edit"> <begin-conversation join="true"/> </rule> -- 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
4
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