July 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMCATCH-41) Provide SPI for registering HandlerMethod programatically

by Jozef Hartinger (JIRA)

Provide SPI for registering HandlerMethod programatically --------------------------------------------------------- Key: SEAMCATCH-41 URL: https://issues.jboss.org/browse/SEAMCATCH-41 Project: Seam Catch Issue Type: Feature Request Components: Framework Integration Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Assignee: Jason Porter It would be nice to offer registerHandlerMethod(HandlerMethod<?> method) for other modules to be able to register handler methods. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-57) Seam persistence fails in AS7 looking up the transaction manager from jndi

by Jason Porter (JIRA)

Seam persistence fails in AS7 looking up the transaction manager from jndi -------------------------------------------------------------------------- Key: SEAMPERSIST-57 URL: https://issues.jboss.org/browse/SEAMPERSIST-57 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Final Environment: AS7 Reporter: Jason Porter Assignee: Stuart Douglas The TransactionManager is no longer available via JNDI in AS7 whenever a transaction is started via Seam Persistence it fails when it tries to find the transaction manager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAM-93) Seam3 Booking example NPE in bookHotel on AS7

by Marek Schmidt (JIRA)

Seam3 Booking example NPE in bookHotel on AS7 --------------------------------------------- Key: SEAM-93 URL: https://issues.jboss.org/browse/SEAM-93 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.0.0.Final Environment: jboss-7.0.0.Beta4-SNAPSHOT, build #1194, standalone Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: Future Clicking "Book Hotel" on a Hotel Details page leads to javax.ejb.EJBTransactionRolledbackException {quote} ... #{bookingAgent.bookHotel}: javax.ejb.EJBTransactionRolledbackException: javax.faces.FacesException: #{bookingAgent.bookHotel}: javax.ejb.EJBTransactionRolledbackException ... Caused by: java.lang.NullPointerException at org.jboss.seam.examples.booking.booking.BookingAgent.bookHotel(BookingAgent.java:108) [classes:] ... {quote} Seems like bookHotel not run in the same conversation scope for some reason (pretty faces issue, maybe?) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (SEAMINTL-49) Add GeoIP support

by Shane Bryzak (JIRA)

Add GeoIP support ----------------- Key: SEAMINTL-49 URL: https://issues.jboss.org/browse/SEAMINTL-49 Project: Seam International Issue Type: Feature Request Reporter: Shane Bryzak Assignee: Ken Finnigan Priority: Minor It would be nice to have GeoIP support in Seam International, perhaps based on this: http://www.maxmind.com/app/java I'd say that being able to inject the country/city of the user would be the minimum functionality required, although there may also be some more useful goodies provided by the above library. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4824) When resteasy jars is present in ear dependencies are not injected in session bean

by Sverker Abrahamsson (JIRA)

When resteasy jars is present in ear dependencies are not injected in session bean ---------------------------------------------------------------------------------- Key: JBSEAM-4824 URL: https://issues.jboss.org/browse/JBSEAM-4824 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.2.2.Final Environment: Jboss 5.1.0.GA, jdk 6, Resteasy 2.2.1.GA Reporter: Sverker Abrahamsson When resteasy jars are present in ear then seam does not inject dependencies into session beans. If the resteasy jars are removed then the dependencies are injected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMJMS-50) QueueBuilder and TopicBuilder should support Destination objects

by John Ament (JIRA)

QueueBuilder and TopicBuilder should support Destination objects ---------------------------------------------------------------- Key: SEAMJMS-50 URL: https://issues.jboss.org/browse/SEAMJMS-50 Project: Seam JMS Issue Type: Feature Request Components: Injection Affects Versions: 3.0.0.CR1 Reporter: Marek Schmidt Assignee: John Ament Priority: Minor Fix For: 3.0.0.CR2 These interfaces support JNDI lookup for destinations but did not have have methods added to support concrete destinattions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMVALIDATE-18) ValidationExtension conflicts with Weld build-in Validator

by Jan Groth (JIRA)

ValidationExtension conflicts with Weld build-in Validator ---------------------------------------------------------- Key: SEAMVALIDATE-18 URL: https://issues.jboss.org/browse/SEAMVALIDATE-18 Project: Seam Validation Issue Type: Bug Reporter: Jan Groth Assignee: Gunnar Morling I'm on a project with the full Seam 3 stack, and using @Inject private Validator validator; results in a deployment exception: WELD-001318 Cannot resolve an ambiguous dependency between [ org.jboss.seam.validation.ValidationExtension$2@38f8cf74, Built-in Bean [javax.validator.Validator] with qualifiers [@Default] ] I suspect the following code from ValidationException.java to be unaware of the Weld built-in component "javax.validator.Validator": // do nothing, if Validator already exists if (!bm.getBeans(Validator.class).isEmpty()) { return; } If the code gets executed, it works fine, but it seems as if the Weld-Component gets installed _after ValidationExtension registers its validator... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
9
0 / 0

[JBoss JIRA] Created: (SEAMCRON-33) Implement concurrency control for @Scheduled and @Asynchronous methods

by Dave Oxley (JIRA)

Implement concurrency control for @Scheduled and @Asynchronous methods ---------------------------------------------------------------------- Key: SEAMCRON-33 URL: https://issues.jboss.org/browse/SEAMCRON-33 Project: Seam Cron Issue Type: Feature Request Reporter: Dave Oxley Assignee: Peter Royle QueuJ provides a QueueRestriction which allows concurrency restrictions based on the state of other jobs in queue. Seam Cron would benefit from API's for this using QueuJ as the provider. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-53) Injected EntityManager can not be invoked in java se

by Liu Jianhong (JIRA)

Injected EntityManager can not be invoked in java se ----------------------------------------------------- Key: SEAMPERSIST-53 URL: https://issues.jboss.org/browse/SEAMPERSIST-53 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Final Environment: weld-se-1.1.1,seam-persistence 3.0.0 and 3.0.1-SNAPSHOT Reporter: Liu Jianhong When call entityManager.toString(), entityManager.persist() addn so on ,it produces WELD-001303 error: Exception in thread "main" org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:664) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:77) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:87) at org.jboss.seam.transaction.org$jboss$weld$bean-classpath-ManagedBean-org$jboss$seam$transaction$EntityTransaction$@javax$enterprise$context$RequestScoped()@org$jboss$seam$config$xml$core$XmlConfiguredBean()@org$jboss$seam$transaction$DefaultTransaction()${org$jboss$seam$transaction$EntityTransaction$entityManager$@javax$inject$Inject()$$org$jboss$seam$transaction$EntityTransaction$persistenceProvider$@javax$inject$Inject()$$org$jboss$seam$transaction$EntityTransaction$init$@javax$inject$Inject()$(org$jboss$seam$transaction$Synchronizations)$}_$$_WeldClientProxy.isActive(org$jboss$weld$bean-classpath-ManagedBean-org$jboss$seam$transaction$EntityTransaction$@javax$enterprise$context$RequestScoped()@org$jboss$seam$config$xml$core$XmlConfiguredBean()@org$jboss$seam$transaction$DefaultTransaction()${org$jboss$seam$transaction$EntityTransaction$entityManager$@javax$inject$Inject()$$org$jboss$seam$transaction$EntityTransaction$persistenceProvider$@javax$inject$Inject()$$org$jboss$seam$transaction$EntityTransaction$init$@javax$inject$Inject()$(org$jboss$seam$transaction$Synchronizations)$}_$$_WeldClientProxy.java) at org.jboss.seam.persistence.ManagedPersistenceContextProxyHandler.joinTransaction(ManagedPersistenceContextProxyHandler.java:126) at org.jboss.seam.persistence.ManagedPersistenceContextProxyHandler.invoke(ManagedPersistenceContextProxyHandler.java:114) at $Proxy36.toString(Unknown Source) at java.lang.String.valueOf(String.java:2826) at java.io.PrintStream.println(PrintStream.java:771) at test.UserFacet.save(UserFacet.java:27) at test.Main.main(Main.java:17) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
8
0 / 0

[JBoss JIRA] Created: (SOLDER-106) Seam transaction potential memory leaks if there is nested @TransactionAttritue

by yangju (JIRA)

Seam transaction potential memory leaks if there is nested @TransactionAttritue ------------------------------------------------------------------------------- Key: SOLDER-106 URL: https://issues.jboss.org/browse/SOLDER-106 Project: Seam Solder Issue Type: Bug Affects Versions: 3.0.0.Final Environment: Windows, Eclipse, jboss AS 6 Final Reporter: yangju I have been doing some performance testing on cdi beans with @TransactionAttribute in jboss AS 6 final. After my application runs non-stop for a while (I have created 10 threads constantly invoking the ApplicaitonScoped bean to get data from database and then update those data), I got got exception:: java.lang.OutOfMemoryError: GC overhead limit exceeded. This happened when I have Bean A injects Bean B and both A and B are annotated with @TransactionAttribute. These two beans looks up (instead of injecting) entity manager from an entity manager factory (jndi lookup emf first, then emf.createEntityManager()). These beans are not declared as session bean and no SMPC is used. I thought transaction will be propagated from one bean to another, or it only does that for stateful session beans or SMPC? If I remove one of the TransactionAttribute annotation from B then the OOM problem does not occur. This OOM problem also occurs after my application runs for a while in this scenario: Bean A injects Bean B and Bean C; Bean C injects Bean B. I analyzed the heap dump with eclipse memory analyzer and it suspects that the seam 3 transaction interceptor might have memory leaks. I used Eclipse Memory Analyzer to analyze the heap dump when OOM occurred. It says: One instance of "org.jboss.weld.context.CreationalContextImpl" loaded by "org.jboss.classloader.spi.base.BaseClassLoader @ 0xd2b85a08" occupies 387,677,848 (40.99%) bytes. The memory is accumulated in one instance of "java.lang.Object[]" loaded by "<system class loader>". Keywords java.lang.Object[] org.jboss.classloader.spi.base.BaseClassLoader @ 0xd2b85a08 org.jboss.weld.context.CreationalContextImpl Shortest Paths To the Accumulation Point Class Name Shallow Heap Retained Heap java.lang.Object[198578] @ 0xf2c419b8 1,588,648 387,677,288 elementData java.util.ArrayList @ 0xde867580 40 387,677,328 list, c java.util.Collections$SynchronizedRandomAccessList @ 0xde867568 40 387,677,368 dependentInstances org.jboss.weld.context.CreationalContextImpl @ 0xde867418 48 387,677,848 creationalContext org.jboss.weld.bean.builtin.InstanceImpl @ 0xde8673e0 56 88 transaction org.jboss.seam.transaction.TransactionInterceptor @ 0xde867330 40 584 instance org.jboss.interceptor.proxy.InterceptorInvocation$InterceptorMethodInvocation @ 0xfc2cf5a8 40 80 [0] java.lang.Object[10] @ 0xfc2cf570 104 184 elementData java.util.ArrayList @ 0xfc2cf558 40 224 interceptorMethodInvocations org.jboss.interceptor.proxy.SimpleInterceptionChain @ 0xfc2cf530 64 984 <Java Local> java.lang.Thread @ 0xdef53810 pool-109-thread-2 Thread 176 44,120 value java.util.HashMap$Entry @ 0xde867310 » 48 48 Total: 2 entries -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2011