November 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4288) Seam-Wicket doesn't propagate to ResourceLinks

by Clint Popetz (JIRA)

Seam-Wicket doesn't propagate to ResourceLinks ---------------------------------------------- Key: JBSEAM-4288 URL: https://jira.jboss.org/jira/browse/JBSEAM-4288 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.2.0.CR1 Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.2.1.CR1 Need to override RequestCycle.encodeSharedResourceURL and propagate cid as request parameter, because there is no pagemap for SharedResources. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4282) Seam-Wicket conversation propagation doesn't respect endBeforeRedirect

by Clint Popetz (JIRA)

Seam-Wicket conversation propagation doesn't respect endBeforeRedirect ---------------------------------------------------------------------- Key: JBSEAM-4282 URL: https://jira.jboss.org/jira/browse/JBSEAM-4282 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.2.0.CR1 Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.2.1.CR1 SeamWebApplication and its inner classes use Manager.isLongRunningConversation to determine whether to propagate conversation ids across request targets, but if a user calls endBeforeRedirect and then redirects to a new page, that page will get the old conversation id. It should instead use the isReallyLongRunningConversation...a method whose very name suggests a design flaw :P -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4231) Invalid Content Id for email attchments

by Tom Goring (JIRA)

Invalid Content Id for email attchments --------------------------------------- Key: JBSEAM-4231 URL: https://jira.jboss.org/jira/browse/JBSEAM-4231 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: NA Reporter: Tom Goring Seam should not set the content id for attachments (e.g. in the case of a PDF). Some email clients don't like it and the attachments becomes hidden. I think this should be done in the case of disposition eq "attachment" and not for "inline" http://www.seamframework.org/Community/PDFAttachmentsAndLotusNotes65Outlo... -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4281) Conversations are not propagated to modal windows

by Clint Popetz (JIRA)

Conversations are not propagated to modal windows ------------------------------------------------- Key: JBSEAM-4281 URL: https://jira.jboss.org/jira/browse/JBSEAM-4281 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.2.0.CR1 Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.2.1.CR1 Wicket does not use its own RequestCycleProcessor.respond when showing a ModalWindow, so the seam/wicket integration mechanism that propagates conversations doesn't propagate them to modal windows. A workaround is to create the modal window with an anonymous subclass that puts the conversation id in the javascript that is appended for opening the window: add(modalWindow = new ModalWindow("yourModalTitle") { protected AppendingStringBuffer postProcessSettings(AppendingStringBuffer settings) { return settings.replace(0, Integer.MAX_VALUE, settings.toString().replaceFirst("(settings.src=\"[^\"]+)\"", "$1&cid=" + org.jboss.seam.core.Manager.instance().getCurrentConversationId()+'"')); } }); -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4105) NullPointer exception configuring a component using a qualified XML element

by Dan Allen (JIRA)

NullPointer exception configuring a component using a qualified XML element --------------------------------------------------------------------------- Key: JBSEAM-4105 URL: https://jira.jboss.org/jira/browse/JBSEAM-4105 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.CR1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.2.GA Consider the case where there is an existing component defined with the @Name annotation. Now, you want to be able to configure that component in XML. If the class name for the component cannot be derived from the name of the component, then Seam throws a NullPointerException. Case in point. Assume the following component package com.mydomain.project; @Name("com.mydomain.project.init") public class ProjectInit { ... } Now assume I am configuring it with: <project:init stage="test"/> Because the class of the component, com.mydomain.project.ProjectInit, cannot be derived form the component name, com.mydomain.project.init, Seam tries to do something with the class object that leads to a NullPointerException. What should happen is that Seam should recognize it is configuring an existing component and ignore that fact that it cannot resolve the class. That is the intended behavior. -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4060) back button in pageflow should work after a redirect

by Dan Allen (JIRA)

back button in pageflow should work after a redirect ---------------------------------------------------- Key: JBSEAM-4060 URL: https://jira.jboss.org/jira/browse/JBSEAM-4060 Project: Seam Issue Type: Feature Request Components: BPM Affects Versions: 2.1.1.GA Reporter: Dan Allen Fix For: 2.2.0.CR1 When the current page in a pageflow is validated, Seam is reference the page-scoped FacesPage. This component is only available on a faces request. Therefore, if a redirect is used in the pageflow, then it is no possible to use the back button, even if it is enabled in the pageflow definition, since the page-scope won't be available in that case. The validation should be changed to rely on information in the conversation rather than the page-scope. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3911) zipped ear files cause seam NullPointerException on deployment

by Adam Montague (JIRA)

zipped ear files cause seam NullPointerException on deployment -------------------------------------------------------------- Key: JBSEAM-3911 URL: https://jira.jboss.org/jira/browse/JBSEAM-3911 Project: Seam Issue Type: Bug Environment: Jboss 5.0.0-GA, jdk 1.6.0_07 Reporter: Adam Montague A webapp using seam that is deployed as a zipped ear fails to deploy. First you get an exception like this for each war that uses seam: 15:55:08,634 WARN [URLScanner] could not read entries java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:114) at java.util.zip.ZipFile.<init>(ZipFile.java:131) at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:111) at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:98) at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:81) at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrateg y.java:67) at org.jboss.seam.init.Initialization.create(Initialization.java:102) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca tDeployment.java:367) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym ent.java:146) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 5) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy36.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi on(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon trollerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr ollerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC ontext.java:286) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe ployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 71) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 9) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 ) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 ) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS erviceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService Bootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) Then you get the following exception for the first war, causing deployment to fail: 15:16:26,981 ERROR [[/merlin/affiliate]] Exception sending context initialized event to listen er instance of class org.jboss.seam.servlet.SeamListener java.lang.NullPointerException at org.jboss.seam.init.Initialization.installComponents(Initialization.java:958) at org.jboss.seam.init.Initialization.init(Initialization.java:589) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(Tomca tDeployment.java:367) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeploym ent.java:146) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2 5) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy36.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLif ecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallActi on(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessCon trollerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractContr ollerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerC ontext.java:286) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy( AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDe ployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:1 71) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:143 9) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersI mpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098 ) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerCo ntext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:159 8) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.j ava:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController. java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545 ) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileS erviceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileService Bootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) If you unzip the ear, then you still get the zipexceptions for each war in the ear, but the final exception does not happen and the deployment succeeds. -- 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

8
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3853) seam-gen unexplode on windows while server is running does not remove all artifacts

by Jay Balunas (JIRA)

seam-gen unexplode on windows while server is running does not remove all artifacts ------------------------------------------------------------------------------------ Key: JBSEAM-3853 URL: https://jira.jboss.org/jira/browse/JBSEAM-3853 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: windows XP Reporter: Jay Balunas Priority: Minor Fix For: 2.1.2.CR1 This only appears to be an issue on windows machine - most likely because of the way it holds onto file handles. While the jboss AS server is running attempt to "seam unexplode" a previously exploded project and a subset of directories will remain and cause random exceptions. In order to remove correctly you must stop the app server, then run "seam unexplode" -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3870) SeamFactoryBean.getObjectType() throws an IllegalStateException when referencing a factory method

by Michael Youngstrom (JIRA)

SeamFactoryBean.getObjectType() throws an IllegalStateException when referencing a factory method ------------------------------------------------------------------------------------------------- Key: JBSEAM-3870 URL: https://jira.jboss.org/jira/browse/JBSEAM-3870 Project: Seam Issue Type: Bug Components: Spring Affects Versions: 2.1.1.GA, 2.0.3.CR1 Reporter: Michael Youngstrom Assignee: Michael Youngstrom Fix For: 2.0.3.CR2, 2.1.2.CR1 SeamFactoryBean.getObjectType() throws an IllegalStateException when referencing named entities that are not components like a factory method. When it should return null. -- 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

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3783) add farm targets to seam-gen build

by Dan Allen (JIRA)

add farm targets to seam-gen build ---------------------------------- Key: JBSEAM-3783 URL: https://jira.jboss.org/jira/browse/JBSEAM-3783 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.1.CR1 Reporter: Dan Allen Assignee: Dan Allen Priority: Minor Fix For: 2.1.2.CR1 Migrate the farm targets from the booking example to the seam-gen build so that it is possible to deploy new apps to a JBoss AS cluster w/o any manual configuration (from the application side of things). -- 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

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2009