December 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] (SOLDER-310) Interceptor and @RequestParam: Unsatisfied dependencies.

by Vitaly Masterov (Created) (JIRA)

Interceptor and @RequestParam: Unsatisfied dependencies. -------------------------------------------------------- Key: SOLDER-310 URL: https://issues.jboss.org/browse/SOLDER-310 Project: Solder Issue Type: Bug Components: Build infrastructure, Core Affects Versions: 3.1.0.CR1 Environment: JBoss AS 7.0.2 SEAM-3.1.0-SNAPSHOT Reporter: Vitaly Masterov If the interceptor class uses injection with @RequestParam annotation, deployment returns the exception "Unsatisfied dependencies". {code:java} @Inject @RequestParam private String foo; {code} {code:none} Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [String] with qualifiers [@RequestParam] at injection point [[field] @Inject @RequestParam private ru.mugitus.ee.simpletester.SimpleInterceptor.foo] {code} The same injection in a simple bean works fine. -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMCONFIG-50) Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) for

by Geoffrey De Smet (JIRA)

Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) for ----------------------------------------------------------------------- Key: SEAMCONFIG-50 URL: https://issues.jboss.org/browse/SEAMCONFIG-50 Project: Seam Config Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Geoffrey De Smet Assignee: Stuart Douglas Priority: Critical at least when running from the IntelliJ tomcat 6 plugin. Occurs for both exploded war and not exploded war. Strangely enough, it doesn't ignore it for the root xml schema validation. The problem is probably in ClasspathResourceLoader.getResources(String name): when name = "WEB-INF/beans.xml", it returnts an empty Set, while it should contain something like: /.../guvnor/guvnor-webapp/target/guvnor-webapp-5.3.0-SNAPSHOT/WEB-INF/beans.xml Thread.currentThread().getContextClassLoader() returns an instance of org.apache.catalina.loader.WebappClassLoader When asking Thread.currentThread().getContextClassLoader().getResourceAsStream("WEB-INF/beans.xml") or Thread.currentThread().getContextClassLoader().getResourceAsStream("/WEB-INF/beans.xml") it returns null (so the catalina WebappClassLoader returns null for that). yet asking a resource, such as Thread.currentThread().getContextClassLoader().getResourceAsStream("/drools-asseteditors.xml") does not return null, but the correct resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

13
33
0 / 0

[JBoss JIRA] Created: (SEAMFACES-44) View scope problems

by Aleksandar Pejovic (JIRA)

View scope problems ------------------- Key: SEAMFACES-44 URL: https://jira.jboss.org/browse/SEAMFACES-44 Project: Seam Faces Issue Type: Bug Affects Versions: 3.0.0.Alpha3 Environment: glassfish v3.0.1 Reporter: Aleksandar Pejovic 1.View scope should behave like normal scope, but client proxies aren't being used. 2.View scoped beans should be passivation capable, but the container isn't enforcing that. 3.@ViewScoped annotation cannot be used on producer methods/fields. More detailed description is available on a forum: http://seamframework.org/Community/SeamfacesViewScopeProblems -- 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

14 years, 3 months

9
15
0 / 0

[JBoss JIRA] (SEAMTRANSACTION-10) Transaction Exception Handler swallows all exceptions

by Cody Lerum (Created) (JIRA)

Transaction Exception Handler swallows all exceptions ----------------------------------------------------- Key: SEAMTRANSACTION-10 URL: https://issues.jboss.org/browse/SEAMTRANSACTION-10 Project: Seam Transaction Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Cody Lerum Assignee: Stuart Douglas Priority: Blocker Fix For: 3.1.0.Final The SimpleTransactionExceptionHandler added in Seam Transaction rolls back transactions if there is an exception but does not rethrow. This cause JSF error pages to be blank rather than provide useful information about the error. -- 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

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (SEAMREPORTS-31) Failure to build documentation: Property ID "reports-quickstart" (found on "fo:block") previously used; ID values must be unique within a document!

by Marek Schmidt (Created) (JIRA)

Failure to build documentation: Property ID "reports-quickstart" (found on "fo:block") previously used; ID values must be unique within a document! --------------------------------------------------------------------------------------------------------------------------------------------------- Key: SEAMREPORTS-31 URL: https://issues.jboss.org/browse/SEAMREPORTS-31 Project: Seam Reports Issue Type: Bug Components: docs Affects Versions: 3.1.0.CR1 Reporter: Marek Schmidt Fix For: 3.1.0.Final [ERROR] Failed to execute goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.3.5:generate (default-generate) on project seam-reports-reference-guide: XSLT problem: error rendering [org.apache.fop.fo.ValidationException: Property ID "reports-quickstart" (found on "fo:block") previously used; ID values must be unique within a document! (See position -1:-1); SystemID: jar:file:/home/hudson/.m2/repository/net/sf/docbook/docbook/1.74.0/docbook-1.74.0.jar!/fo/titlepage.templates.xsl; Line#: 2305; Column#: -1] on master.xml -> [Help 1] [maschmid@dhcp-26-127 en-US]$ grep -R reports-quickstart * reports-extension.xml: <section id="reports-quickstart"> reports-usage.xml: <section id="reports-quickstart"> section ids have to be unique -- 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

14 years, 3 months

6
5
0 / 0

[JBoss JIRA] Created: (SEAM-88) Solder Property couldn't get property value if the property type is primitive.

by Miyazawa Yasushi (JIRA)

Solder Property couldn't get property value if the property type is primitive. ------------------------------------------------------------------------------ Key: SEAM-88 URL: https://issues.jboss.org/browse/SEAM-88 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Miyazawa Yasushi Property couldn't get property value if the property type is primitive. Simplest Test =================================================================================================== package org.miyazyss; import org.jboss.seam.solder.properties.Property; import org.jboss.seam.solder.properties.query.NamedPropertyCriteria; import org.jboss.seam.solder.properties.query.PropertyQueries; import org.jboss.seam.solder.properties.query.PropertyQuery; import org.junit.Assert; import org.junit.Test; /** * */ public class SolderMethodTest { public static class Bean { public long longValue = 1; public Long longClassValue = 3L; public long getLongValueMethod(){ return(2); } } private Bean bean = new Bean(); @Test public void testPrimitiveField(){ PropertyQuery<Bean> query = PropertyQueries.createQuery(Bean.class); Property<Bean> prop = query.addCriteria(new NamedPropertyCriteria("longValue")).getFirstResult(); Assert.assertEquals(1, prop.getValue(this.bean)); } @Test public void testPrimitiveReturnTypeMethod(){ PropertyQuery<Bean> query = PropertyQueries.createQuery(Bean.class); Property<Bean> propValue = query.addCriteria(new NamedPropertyCriteria("longValueMethod")).getFirstResult(); Assert.assertEquals(2, propValue.getValue(this.bean)); } @Test public void testClassField(){ PropertyQuery<Bean> query = PropertyQueries.createQuery(Bean.class); Property<Bean> propValue = query.addCriteria(new NamedPropertyCriteria("longClassValue")).getFirstResult(); Assert.assertEquals(3L, propValue.getValue(this.bean)); } } Result ========================================================================================================= SolderMethodTest org.miyazyss.SolderMethodTest testPrimitiveField(org.miyazyss.SolderMethodTest) java.lang.ClassCastException at java.lang.Class.cast(Unknown Source) at org.jboss.seam.solder.reflection.Reflections.getFieldValue(Reflections.java:682) at org.jboss.seam.solder.properties.FieldPropertyImpl.getValue(FieldPropertyImpl.java:75) at org.miyazyss.SolderMethodTest.testPrimitiveField(SolderMethodTest.java:37) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) testPrimitiveReturnTypeMethod(org.miyazyss.SolderMethodTest) java.lang.ClassCastException at java.lang.Class.cast(Unknown Source) at org.jboss.seam.solder.properties.MethodPropertyImpl.getValue(MethodPropertyImpl.java:136) at org.miyazyss.SolderMethodTest.testPrimitiveReturnTypeMethod(SolderMethodTest.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
6
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-38) ServletContextAttributeProvider uses wrong servlet ctx. attribute name to lookup the bean manager

by Daniel Kvasnička (JIRA)

ServletContextAttributeProvider uses wrong servlet ctx. attribute name to lookup the bean manager ------------------------------------------------------------------------------------------------- Key: SEAMSERVLET-38 URL: https://issues.jboss.org/browse/SEAMSERVLET-38 Project: Seam Servlet Issue Type: Bug Components: Event Bridge, Producers Affects Versions: 3.0.0.Final Environment: JDK6, Tomcat 6, weld-servlet 1.1.1.Final, seam-solder 3.0.0.Final, seam-servlet 3.0.0.Final Reporter: Daniel Kvasnička Priority: Critical org.jboss.seam.servlet.beanManager.ServletContextAttributeProvider uses BeanManager.class.getName() to lookup the bean manager in servlet context, but the name of the attribute used in sub-servlet3.0 containers is now org.jboss.weld.environment.servlet.Listener.BEAN_MANAGER_ATTRIBUTE_NAME -- AFAIK (see https://issues.jboss.org/browse/RESTEASY-471). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (SOLDER-99) javax.el.ExpressionFactory can not be injected because it has final methods

by Denis Forveille (JIRA)

javax.el.ExpressionFactory can not be injected because it has final methods --------------------------------------------------------------------------- Key: SOLDER-99 URL: https://issues.jboss.org/browse/SOLDER-99 Project: Seam Solder Issue Type: Bug Components: Compliance Affects Versions: 3.0.0.CR3 Environment: WebSphere 8 beta Reporter: Denis Forveille seam-booking can not start in WebSphere v8 beta because of the following exception I think this is class org.jboss.seam.solder.el.Expressions that causes this (WAS v8 uses openwebbeans and not weld..) {noformat} Caused by: javax.enterprise.inject.UnproxyableResolutionException: WebBeans with api type with normal scope must be proxiable to inject. javax.el.ExpressionFactory has final methods! CDI doesn't allow that. at org.apache.webbeans.util.InjectionExceptionUtils.throwUnproxyableResolutionException(InjectionExceptionUtils.java:39) at org.apache.webbeans.util.WebBeansUtil.checkUnproxiableApiType(WebBeansUtil.java:2084) {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
6
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-44) Remoting Model API lazy fields initialized automatically on Glassfish and AS7

by Marek Schmidt (JIRA)

Remoting Model API lazy fields initialized automatically on Glassfish and AS7 ----------------------------------------------------------------------------- Key: SEAMREMOTING-44 URL: https://issues.jboss.org/browse/SEAMREMOTING-44 Project: Seam Remoting Issue Type: Bug Affects Versions: 3.0.0.Final Environment: seam remoting 3.0.1-SNAPSHOT, glassfish 3.1.1.b12 with default persistence provider (eclipselink) || jboss-as-7.1.0.Alpha1-SNAPSHOT with default persistence provider (hibernate 4) Reporter: Marek Schmidt Lazy fields, such as {noformat} @OneToMany(fetch = FetchType.LAZY, mappedBy = "person", cascade = CascadeType.ALL, orphanRemoval = true) public Collection<Address> getAddresses() { return addresses; } {noformat} are loaded automatically in the model on AS7 and Glassfish. On JBoss AS 6, the field is works correctly and is undefined unless explicitly expanded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
7
0 / 0

[JBoss JIRA] (SEAMREMOTING-53) Model example not working on glassfish

by Tomas Remes (Created) (JIRA)

Model example not working on glassfish -------------------------------------- Key: SEAMREMOTING-53 URL: https://issues.jboss.org/browse/SEAMREMOTING-53 Project: Seam Remoting Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: glassfish3.1, seam-3.1.0.CR1 Reporter: Tomas Remes Fix For: 3.1.0.Final There is no way how to add or update person attributes running model example on glassfish. Use case of creating new person is processed with no errors/exceptions, but the new person is not added. Same problem is updating addresses or any other attributes of already created persons. Everything process fine, but the change is not applied. -- 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

14 years, 3 months

4
3
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 December 2011