May 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-146) Support multiple enums in the @Viewconfig interface

by Brian Leathem (JIRA)

Support multiple enums in the @Viewconfig interface --------------------------------------------------- Key: SEAMFACES-146 URL: https://issues.jboss.org/browse/SEAMFACES-146 Project: Seam Faces Issue Type: Feature Request Components: View Configuration Reporter: Brian Leathem Fix For: 3.0.2 Consider putting the @ViewConfig "child" annotations on an enum itself, and have it apply to all contained views. One could then have multiple enums as a way of sharing annotation configuration amongst multiple views that don't necessarily share a common view pattern. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFACES-161) UIInputContainer causes warning when project stage is set to "Development"

by Alt Avatar (JIRA)

UIInputContainer causes warning when project stage is set to "Development" -------------------------------------------------------------------------- Key: SEAMFACES-161 URL: https://issues.jboss.org/browse/SEAMFACES-161 Project: Seam Faces Issue Type: Bug Components: UI Components Affects Versions: 3.0.1 Reporter: Alt Avatar If "Development" javax.faces.PROJECT_STAGE is configured in web.xml, then using a component based on UIInputContainer results in this error message being displayed: "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>" This occurs, for example, when using the composite component definition from the input.xhtml file in the Seam-Booking example, and the following View template: <x:input label="Email"> <h:inputText value="#{login.email}" required="true" /> </x:input> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBSEAM-4808) Wicket integration - Conversation lifecycle is broken when onPageAttached() is overridden.

by Rob Shepherd (JIRA)

Wicket integration - Conversation lifecycle is broken when onPageAttached() is overridden. ------------------------------------------------------------------------------------------ Key: JBSEAM-4808 URL: https://issues.jboss.org/browse/JBSEAM-4808 Project: Seam 2 Issue Type: Bug Components: Wicket Affects Versions: 2.2.2.Final Environment: MAC OS X Java 1.6.0_24 JBoss AS 5.1.0.GA JBoss SEAM 2.2.2.FINAL Reporter: Rob Shepherd Primarily - see the seam framework forum post. Under the hood of course, onPageAttached() will have been instrumented to: onPageAttached100() and the original method name then providing a SEAM request lifecycle wrapper, to perform injection and other interceptor functions around the original method content. It looks like the seam manager has not yet begun delivering the request and retrieved the conversation ID from the previously rendered page's page map and switched the conversation. In the failure mode - I'm unclear how a conversationally scoped re-injected instance can exist when the current conversation ID is seen to change. The original use-case for overriding the onPageAttached() was - when re-rendering page instances from the page map - to detect changes in other injected session-scoped context variables and mark a page as expired if changes have occurred - or proceed if no changes have occurred. Any @In-jected conversational bean is replaced by a new instance - even if (later in the request) the conversation ID seems to revert back to the proper ID. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMREPORTS-12) Split impl into different modules

by George Gastaldi (JIRA)

Split impl into different modules --------------------------------- Key: SEAMREPORTS-12 URL: https://issues.jboss.org/browse/SEAMREPORTS-12 Project: Seam Reports Issue Type: Task Affects Versions: 3.0.0.Alpha1 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: The Future The impl module should be split into different submodules, so that would fit the reporting implementations into their own submodules, e.g. seam-reports-pentaho, seam-reports-jasperreports -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMCRON-13) Try workaround for WELD-862 using deep copy

by Peter Royle (JIRA)

Try workaround for WELD-862 using deep copy ------------------------------------------- Key: SEAMCRON-13 URL: https://issues.jboss.org/browse/SEAMCRON-13 Project: Seam Cron Issue Type: Task Reporter: Peter Royle Assignee: Peter Royle As suggested on WELD-862, possible workaround is to deep copy the InvocationContext. Marius Bogoevici has suggested that this can be done using stuff from JBoss Interceptor so I should try that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMCRON-21) Add SPI documentation

by Peter Royle (JIRA)

Add SPI documentation --------------------- Key: SEAMCRON-21 URL: https://issues.jboss.org/browse/SEAMCRON-21 Project: Seam Cron Issue Type: Task Reporter: Peter Royle Assignee: Peter Royle Fix For: 3.0.0.Alpha2 Cover: # SPI # adding an asynch provider (show Threads as exmaple?) # adding scheduling provider # lifecycle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMCRON-17) Create documentation

by Peter Royle (JIRA)

Create documentation -------------------- Key: SEAMCRON-17 URL: https://issues.jboss.org/browse/SEAMCRON-17 Project: Seam Cron Issue Type: Task Reporter: Peter Royle Assignee: Peter Royle Fix For: 3.0.0.Alpha1 Be sure to include: - building from source - adding as dependency/explanation of different jars - general usage - scheduling - asynchronous - SPI - adding an asynch provider (show Threads as exmaple?) - adding scheduling provider - lifecycle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (SEAMCRON-19) Provide durable @Asynchronous provider using application-linked queue

by Dan Allen (JIRA)

Provide durable @Asynchronous provider using application-linked queue --------------------------------------------------------------------- Key: SEAMCRON-19 URL: https://issues.jboss.org/browse/SEAMCRON-19 Project: Seam Cron Issue Type: Feature Request Reporter: Dan Allen Assignee: Peter Royle TorqueBox uses an application-linked queue (in other words, a queue local to the application) to execute asynchronous methods. It uses this strategy to allow for asynchronous invocations to be durable. Seam Cron should offer a "durable = true" flag on @Asynchronous that, when set to true, will switch to the queue-based invocation provider. An override queue could be provided using another annotation and configured in seam-beans.xml. See http://torquebox.org/documentation/1.0.1/messaging.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-37) Exception when deploying with Seam Config (bad beans.xml file?)

by Lincoln Baxter III (JIRA)

Exception when deploying with Seam Config (bad beans.xml file?) --------------------------------------------------------------- Key: SEAMREMOTING-37 URL: https://issues.jboss.org/browse/SEAMREMOTING-37 Project: Seam Remoting Issue Type: Bug Affects Versions: 3.0.0.Final Environment: JBoss AS6 Final Reporter: Lincoln Baxter III <dependency> <groupId>org.jboss.seam.remoting</groupId> <artifactId>seam-remoting</artifactId> <version>3.0.1-SNAPSHOT</version> </dependency> <dependency> <groupId>org.jboss.seam.config</groupId> <artifactId>seam-config-xml</artifactId> <version>3.0.0.Final</version> </dependency> Exception 0 : org.jboss.seam.config.xml.util.XmlConfigurationException: Wrong root namespace for XML config file, expected:urn:java:ee or http://java.sun.com/xml/ns/javaee found: at vfs:/Users/lbaxter/Projects/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6/deploy/twitterstream.war/WEB-INF/lib/seam-conversation-spi-3.0.0.CR1.jar/META-INF/beans.xml:19 at org.jboss.seam.config.xml.model.ModelBuilder.build(ModelBuilder.java:77) at org.jboss.seam.config.xml.bootstrap.XmlConfigExtension.beforeBeanDiscovery(XmlConfigExtension.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:88) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:52) at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:48) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:344) at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.boot(BootstrapBean.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) , **ERROR** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:82) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.checkComplete(ProfileControllerContext.java:138) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:246) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_24] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_24] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-68) DialogueFilter breaks character encoding

by Stefano Travelli (JIRA)

DialogueFilter breaks character encoding ---------------------------------------- Key: SEAMSECURITY-68 URL: https://issues.jboss.org/browse/SEAMSECURITY-68 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Final Environment: JBoss 6 Final, JSF 2 Reporter: Stefano Travelli Including seam-security-external among the dependencies causes the application to use the default iso-8851-1 character encoding for parsing form parameters. After digging into the code I found that character encoding would be set to the correct value by the FacesServlet that calls request.setCharacterEncoding(). This method must be called before any attempts to get a parameter from the request, since at the very first getParameter() the request parses all parameters with the specified encoding. However seam-security-external introduces a DialogueFilter that look for a dialogId parameter too early (see: https://github.com/seam/security/blob/master/external/src/main/java/org/j...) causing all the parameters to be parsed as iso-8859-1 and the subsequent encoding set by the FacesServlet to be ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2011