July 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-4939) pages.xml does not support "virtual" view-id without file on disk

by Andrea Martino (JIRA)

Andrea Martino created JBSEAM-4939: -------------------------------------- Summary: pages.xml does not support "virtual" view-id without file on disk Key: JBSEAM-4939 URL: https://issues.jboss.org/browse/JBSEAM-4939 Project: Seam 2 Issue Type: Bug Components: Core, Framework Affects Versions: 2.3.0.BETA1 Environment: JBOSS 7.1 AS + JSF2.1 + Richfaces 4.2.0.Final Reporter: Andrea Martino In Seam 2.2.x, it is possible to define a "virtual" view in pages.xml without any related file on disk. For example, in Seam 2.2.x it is possible to define a redirect as following without having any "home.xhtml" file on disk: <page view-id="/home.xhtml"> <navigation> <redirect view-id="/welcome.xhtml"/> </navigation> </page> In Seam 2.2.x, when entering "/myapp/home.seam" the browser is correctly redirected to "/myapp/welcome.seam". In Seam 2.3.0.Beta1 in JBOSS 7.1 AS, a FacesFileNotFoundException is thrown. This issue is similar to JBSEAM-4926. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

6
19
0 / 0

[JBoss JIRA] (JBSEAM-4856) AS7 Multi-war ear Seam 2.2.2.Final fails deployment (race condition?)

by Todd Sproule (Created) (JIRA)

AS7 Multi-war ear Seam 2.2.2.Final fails deployment (race condition?) --------------------------------------------------------------------- Key: JBSEAM-4856 URL: https://issues.jboss.org/browse/JBSEAM-4856 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.2.2.Final Environment: Ubuntu 11.10, Sun Java 1.6.0_26-b03, JBoss AS7 7.0.1.Final Reporter: Todd Sproule Deployment of a multi-war Seam ear into AS7 causes a deployment exception with duplicate component exception. This is easy to reproduce with any AS7 Seam ear and two wars. 16:19:13,605 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/seam-hello1]] (MSC service thread 1-3) Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml) at org.jboss.seam.core.Init.checkDuplicateFactoryExpressions(Init.java:227) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:220) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.core.Init.addFactoryValueExpression(Init.java:283) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.init.Initialization.installComponents(Initialization.java:1152) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.init.Initialization.init(Initialization.java:737) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam-2.2.2.Final.jar:] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
22
0 / 0

[JBoss JIRA] (JBSEAM-4962) Generation of Seam Reference Guide sometime throws ConcurrentModificationException

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4962: ------------------------------------- Summary: Generation of Seam Reference Guide sometime throws ConcurrentModificationException Key: JBSEAM-4962 URL: https://issues.jboss.org/browse/JBSEAM-4962 Project: Seam 2 Issue Type: Bug Components: Build Affects Versions: 2.3.0.BETA2, 2.3.0.BETA1 Reporter: Marek Novotny Fix For: 2.3.0.CR1 That happens more frequently on Jenkins than on my local build. {noformat} [ERROR] Failed to execute goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.2.0:generate (jdocbook:generate) on project seam-reference-guide: Execution jdocbook:generate of goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.2.0:generate failed. ConcurrentModificationException -> [Help 1] {noformat} We probably need to upgrade to the latest maven-jdocbook-plugin from 2.2.0 to 2.3.x? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
5
0 / 0

[JBoss JIRA] (JBSEAM-4980) Use registration to javax.faces.event.PostConstructApplicationEvent instead of relying on ServletContextListener

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4980: ------------------------------------- Summary: Use registration to javax.faces.event.PostConstructApplicationEvent instead of relying on ServletContextListener Key: JBSEAM-4980 URL: https://issues.jboss.org/browse/JBSEAM-4980 Project: Seam 2 Issue Type: Bug Components: JSF Integration Affects Versions: 2.3.0.BETA2, 2.3.0.BETA1 Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.CR1 Use registration to javax.faces.event.PostConstructApplicationEvent instead of relying on ServletContextListener for initializing of JSF 2 integration. JSF2 specifically addresses this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBSEAM-4998) Drools does not work with Java7

by Ramkumar Pillai (JIRA)

Ramkumar Pillai created JBSEAM-4998: --------------------------------------- Summary: Drools does not work with Java7 Key: JBSEAM-4998 URL: https://issues.jboss.org/browse/JBSEAM-4998 Project: Seam 2 Issue Type: Bug Components: Drools Environment: Jboss AS7 Reporter: Ramkumar Pillai https://issues.jboss.org/browse/JBRULES-3163 Drool 5.1.1 has a Defect whicis is not working on JVM 1.7, the same issue is closed in Rools not yet Fixed in Seam BOM file -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4512) BPM task does not rollback

by Jason E (JIRA)

BPM task does not rollback -------------------------- Key: JBSEAM-4512 URL: https://jira.jboss.org/jira/browse/JBSEAM-4512 Project: Seam Issue Type: Bug Components: BPM Affects Versions: 2.2.0.GA Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2 Reporter: Jason E I have made a simple change to the ShipAction.java class in the dvdstore example that ships with Seam. Here is the change //@EndTask public String ship() { order.ship(track); TaskInstance ti = ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId()); taskInstance.end(); if(true) throw new RuntimeException("TESTING"); return "admin"; } I commented out the end task annotation and I am ending the task via the TaskInstance API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e. updating the tracking number) rolls back. The problem is that the task instance change (i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in another db transaction. This seems like a bug since I would expect the ending of my task to also rollback. This seems like the desired behavior. This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so it should be easy to reproduce. Thanks! Jason -- 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

12 years, 4 months

7
18
0 / 0

[JBoss JIRA] (JBSEAM-4933) Create war and ear maven archetype to simulate generate general seam2 project

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4933: ------------------------------------- Summary: Create war and ear maven archetype to simulate generate general seam2 project Key: JBSEAM-4933 URL: https://issues.jboss.org/browse/JBSEAM-4933 Project: Seam 2 Issue Type: Task Components: Tools Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.BETA2 We need quick Seam 2 project template creation for Web and Enterprise Applications. This would be achieved by creating EAR and WAR Seam2 archetype. They should be based on previous generated project templates from Seam Generator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-86) Scheme setting for pages in @ViewConfig

by Bill Elliot (JIRA)

Scheme setting for pages in @ViewConfig --------------------------------------- Key: SEAMSECURITY-86 URL: https://issues.jboss.org/browse/SEAMSECURITY-86 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Bill Elliot Is there a way in Seam 3 to do like in the Page definitions of Seam 2 to specify the Scheme (HTTP/HTTPS) to use for a specific page? I need to be able to place the login and password changing screens into HTTPS for increased security and best practices. This could likely be done in the Pages definition under a @ViewConfig. Possibly adding a new annotation @Scheme("HTTPS"). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
5
0 / 0

[JBoss JIRA] (JBSEAM-5005) Seam core unit tests failed on openjdk 6 - IAE URI is not hierarchical

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5005: ------------------------------------- Summary: Seam core unit tests failed on openjdk 6 - IAE URI is not hierarchical Key: JBSEAM-5005 URL: https://issues.jboss.org/browse/JBSEAM-5005 Project: Seam 2 Issue Type: Bug Components: Test Harness Affects Versions: 2.3.0.BETA2 Reporter: Marek Novotny {noformat} java.lang.IllegalArgumentException: URI is not hierarchical at java.io.File.<init>(File.java:380) at org.jboss.seam.mock.MockServletContext.<init>(MockServletContext.java:67) at org.jboss.seam.test.unit.CoreTest.triggerComponentScan(CoreTest.java:22) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:122) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:101) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) ... Removed 19 stack frames Click to hide stack frames java.lang.IllegalArgumentException: URI is not hierarchical at java.io.File.<init>(File.java:380) at org.jboss.seam.mock.MockServletContext.<init>(MockServletContext.java:67) at org.jboss.seam.test.unit.CoreTest.triggerComponentScan(CoreTest.java:22) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:260) at org.testng.SuiteRunner.run(SuiteRunner.java:223) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1039) at org.testng.TestNG.runSuitesLocally(TestNG.java:964) at org.testng.TestNG.run(TestNG.java:900) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:122) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

[JBoss JIRA] (SEAMINTL-70) Document usage of BundleTemplateMessage/TemplateMessage

by Gerald Turner (Created) (JIRA)

Document usage of BundleTemplateMessage/TemplateMessage ------------------------------------------------------- Key: SEAMINTL-70 URL: https://issues.jboss.org/browse/SEAMINTL-70 Project: Seam International Issue Type: Feature Request Components: Messages Affects Versions: 3.1.0.Beta3 Reporter: Gerald Turner Assignee: Ken Finnigan Priority: Optional As a user, the current documentation is sufficient for severity+text messages, however on closer inspection of the Message class, I see that detail and targets properties are available, much like FacesMessage. I dug around the seam-international source and experimented with a bean having fields/method like the following: @Inject private Messages messages; @Inject private transient TemplateMessage message; public void doSometing() { messages.add(message.level(Level.WARN).text("Text {0}, {1}, {2}").textParams('a', 'b', 'c').detail("Detail {0}, {1}, {2}").detailParams(1, 2, 3).targets("message").build()); messages.add(message.level(Level.FATAL).text("Fatality!").targets("message").build()); } This works. A few caveats: * TemplateMessage field has to be marked transient, otherwise get WELD error during deployment about Serializable bean having non-Serializable field. * Make sure to call add(Message) signature (invoke build()) instead of add(MessageBuilder), otherwise only the most recent message is added. * doSomething method is not reentrant/thread-safe because of the builder. I'd prefer to use Messages instead of the builders, perhaps have a methods like info(String text, String details, String targets, Object... args), however that gets ugly with the varargs, having to cast Object[], etc. Perhaps I should stick with FacesMessages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2012