September 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMREST-44) Deployment fails on JBoss AS 7

by Jozef Hartinger (JIRA)

Deployment fails on JBoss AS 7 ------------------------------ Key: SEAMREST-44 URL: https://issues.jboss.org/browse/SEAMREST-44 Project: Seam REST Issue Type: Bug Components: Client Affects Versions: 3.0.0.Final Environment: JBoss AS 7.0.0.Beta4-SNAPSHOT Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Blocker Fix For: 3.1.0.Alpha1 08:16:49,123 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."rest-exceptions.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."rest-exceptions.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ClientExecutor] with qualifiers [@Default] at injection point [[parameter 2] of [method] @Produces @RestClient public org.jboss.seam.rest.client.RestClientProducer.produceClientRequest(InjectionPoint, ClientExecutor)] at org.jboss.as.weld.services.WeldService.start(WeldService.java:96) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ClientExecutor] with qualifiers [@Default] at injection point [[parameter 2] of [method] @Produces @RestClient public org.jboss.seam.rest.client.RestClientProducer.produceClientRequest(InjectionPoint, ClientExecutor)] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:270) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:129) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:351) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:336) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:396) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) ... 4 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-47) remoting examples - CNFE: TransactionInterceptor

by Jozef Hartinger (JIRA)

remoting examples - CNFE: TransactionInterceptor ------------------------------------------------ Key: SEAMREMOTING-47 URL: https://issues.jboss.org/browse/SEAMREMOTING-47 Project: Seam Remoting Issue Type: Bug Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 3.1.0.CR1 Both remoting-model and remoting-validation examples fail to deploy to AS 7 with the following exception: {noformat} 14:48:20,152 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."remoting-validation.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."remoting-validation.war".WeldService: org.jboss.weld.resources.spi.ResourceLoadingException: java.lang.ClassNotFoundException: org.jboss.seam.transaction.TransactionInterceptor from [Module "deployment.remoting-validation.war:main" from Service Module Loader]; location: <class>org.jboss.seam.transaction.TransactionInterceptor</class> in vfs:/content/remoting-validation.war/WEB-INF/beans.xml@14 at org.jboss.as.weld.services.WeldService.start(WeldService.java:96) 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_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] Caused by: org.jboss.weld.resources.spi.ResourceLoadingException: java.lang.ClassNotFoundException: org.jboss.seam.transaction.TransactionInterceptor from [Module "deployment.remoting-validation.war:main" from Service Module Loader]; location: <class>org.jboss.seam.transaction.TransactionInterceptor</class> in vfs:/content/remoting-validation.war/WEB-INF/beans.xml@14 at org.jboss.weld.manager.Enabled$ClassLoader.apply(Enabled.java:75) at org.jboss.weld.manager.Enabled$ClassLoader.apply(Enabled.java:56) at com.google.common.collect.Lists$TransformingRandomAccessList.get(Lists.java:435) at java.util.AbstractList$Itr.next(AbstractList.java:345) [:1.6.0_24] at org.jboss.weld.manager.Enabled.createMetadataMap(Enabled.java:143) at org.jboss.weld.manager.Enabled.<init>(Enabled.java:113) at org.jboss.weld.manager.Enabled.of(Enabled.java:95) at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:104) at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185) at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:197) at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:156) at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:293) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:79) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) ... 5 more Caused by: java.lang.ClassNotFoundException: org.jboss.seam.transaction.TransactionInterceptor from [Module "deployment.remoting-validation.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101) at org.jboss.as.weld.WeldModuleResourceLoader.classForName(WeldModuleResourceLoader.java:68) at org.jboss.weld.manager.Enabled$ClassLoader.apply(Enabled.java:71) ... 18 more {noformat} This is caused by missing seam-transaction dependency. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-23) Support global exception handler

by Jozef Hartinger (JIRA)

Support global exception handler -------------------------------- Key: SEAMREMOTING-23 URL: https://issues.jboss.org/browse/SEAMREMOTING-23 Project: Seam Remoting Issue Type: Feature Request Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Fix For: 3.0.0.CR1 Besides allowing a specific exception handler to be associated with every method invocation, it would be nice to provide a way of registering a global exception handler i.e. Seam.globalExceptionHandler = function() { ... } This would most often be used to inform an end user that an unexpected exception occured. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-48) Functional test failures after migration to Ajocado

by Jozef Hartinger (JIRA)

Functional test failures after migration to Ajocado --------------------------------------------------- Key: SEAMREMOTING-48 URL: https://issues.jboss.org/browse/SEAMREMOTING-48 Project: Seam Remoting Issue Type: Bug Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Minor Fix For: 3.1.0.CR1 All the test failures are caused by weird behavior of the selenium.getAlert() method, which does not detect the alert after a remoting call. Alerts produced directly seem to be detected as expected. remoting/helloworld: {noformat} Tests in error: testCasualEnglish(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts testCasualRussian(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts testFormalEnglish(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts testFormalRussian(org.jboss.seam.remoting.examples.helloworld.ftest.HelloworldTest): ERROR: There were no alerts Tests run: 4, Failures: 0, Errors: 4, Skipped: 0 remoting/validation Tests in error: testCorrectValues(org.jboss.seam.remoting.examples.validation.ftest.ValidationTest): ERROR: There were no alerts Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-40) Model example broken on AS7: Could not find TransactionManager in JNDI

by Marek Schmidt (JIRA)

Model example broken on AS7: Could not find TransactionManager in JNDI ---------------------------------------------------------------------- Key: SEAMREMOTING-40 URL: https://issues.jboss.org/browse/SEAMREMOTING-40 Project: Seam Remoting Issue Type: Bug Environment: Seam Remoting 3.0.1-SNAPSHOT JBoss AS 7.1.0-Alpha Firefox 3.6.18 Reporter: Marek Schmidt Assignee: Shane Bryzak Fix For: 3.1.0.Final Seam Remoting Model example is broken on AS7, cannot modify any values nor create new persons: The following log from attempting to create a new person, notice the "RuntimeException: Could not find TransactionManager in JNDI" {quote} Fri Jul 15 2011 15:37:37 GMT+0200 (CET): Request packet: <envelope><header><context><callId>1</callId></context></header><body><model operation="fetch"><action><target>org.jboss.seam.remoting.examples.model.PersonAction</target><method>createPerson</method></action><bean alias="person"><name>org.jboss.seam.remoting.examples.model.PersonAction</name><property>person</property></bean></model></body></envelope> Fri Jul 15 2011 15:37:37 GMT+0200 (CET): Response packet: <envelope><header><context><conversationId>1</conversationId><callId>1</callId></context></header><body><model id="3fbca98e-a040-48c4-8d21-74caef019093"><value alias="person"><ref id="0"/></value><refs><ref id="0"><bean type="org.jboss.seam.remoting.examples.model.Person"><member name="dateOfBirth"><null/></member><member name="lastName"><null/></member><member name="personId"><null/></member><member name="addresses"><bag></bag></member><member name="firstName"><null/></member></bean></ref></refs></model></body></envelope> Fri Jul 15 2011 15:37:46 GMT+0200 (CET): Request packet: <envelope><header><context><callId>2</callId><conversationId>1</conversationId></context></header><body><model id="3fbca98e-a040-48c4-8d21-74caef019093" operation="apply"><action><target>org.jboss.seam.remoting.examples.model.PersonAction</target><method>savePerson</method></action><delta><changeset refid="0"><member name="dateOfBirth"><date>19840101000000000</date></member><member name="lastName"><str>Doe</str></member><member name="firstName"><str>John</str></member></changeset></delta></model></body></envelope> Fri Jul 15 2011 15:37:46 GMT+0200 (CET): Response packet: <envelope><body><exception><message><str>java.lang.RuntimeException%3A%20java.lang.RuntimeException%3A%20Could%20not%20find%20TransactionManager%20in%20JNDI</str></message></exception></body></envelope> {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-5) Add messages support for Remoting

by Shane Bryzak (JIRA)

Add messages support for Remoting --------------------------------- Key: SEAMREMOTING-5 URL: https://jira.jboss.org/browse/SEAMREMOTING-5 Project: Seam Remoting Issue Type: Feature Request Reporter: Shane Bryzak We need to add support for adding status messages. Any messages generated during a request will need to go into the context of the response packet, where they can then be accessed by the client. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-46) remote.js contains syntax error

by Jozef Hartinger (JIRA)

remote.js contains syntax error ------------------------------- Key: SEAMREMOTING-46 URL: https://issues.jboss.org/browse/SEAMREMOTING-46 Project: Seam Remoting Issue Type: Bug Environment: Seam Remoting SNAPSHOT (8e1103d533b783231efa376daa52d44eb95d1d9b) Reporter: Jozef Hartinger Priority: Blocker Fix For: 3.1.0.CR1 Reproduced on remoting-helloworld application: *8e1103d533b783231efa376daa52d44eb95d1d9b (current develop HEAD)* - on the initial page load the firebug plugin reports: {noformat} missing ; before statement [Break On This Error] var Seam = { beans: {}, debug: false, ...pattern.test(this.currentValue);}) ); remote.js (line 1) Seam is not defined [Break On This Error] Seam.debug = true; helloworld.html (line 41) Seam is not defined [Break On This Error] Seam.debug = true; helloworld.html (line 41) {noformat} *cb242114143ecaa94235ec9083ef20db1f4b16c7* - the remoting.js error does not happen -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMFACES-204) Non-BeanManaged converter warning is too verbose

by Cody Lerum (JIRA)

Non-BeanManaged converter warning is too verbose ------------------------------------------------ Key: SEAMFACES-204 URL: https://issues.jboss.org/browse/SEAMFACES-204 Project: Seam Faces Issue Type: Bug Affects Versions: 3.1.0.Beta2 Reporter: Cody Lerum Adding this to a page - <f:converter converterId="com.ocpsoft.PrettyTimeConverter"/> will throw a WARN message in the logs on every invoke 15:05:05,454 WARN [org.jboss.seam.faces.environment.SeamApplicationWrapper] Using JSF provided instance, unable to find a BeanManaged instance for class com.ocpsoft.pretty.time.web.jsf.PrettyTimeConverter This was suppressed for standard javax.* converters here https://github.com/seam/faces/commit/5e1d8ed972fcc9074210b1e214e355352ac0... but should probably move to DEBUG level as some converters like PrettyTime will never be beanmanaged. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
7
0 / 0

[JBoss JIRA] Created: (SEAM-61) Update the PrettyFaces version to 3.2.0

by Brian Leathem (JIRA)

Update the PrettyFaces version to 3.2.0 --------------------------------------- Key: SEAM-61 URL: https://issues.jboss.org/browse/SEAM-61 Project: Seam 3 Distribution Issue Type: Library Upgrade Components: Common Dependencies Reporter: Brian Leathem Fix For: 3.0.0.Final SEAMFACES-101 requires the pretty faces version to be bumped to version 3.2.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
4
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-15) Add varargs contact methods

by Cody Lerum (JIRA)

Add varargs contact methods --------------------------- Key: SEAMMAIL-15 URL: https://issues.jboss.org/browse/SEAMMAIL-15 Project: Seam Mail Issue Type: Enhancement Affects Versions: 3.0.0.Alpha1 Reporter: Cody Lerum Assignee: Cody Lerum Fix For: 3.0.0.Alpha1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2011