March 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-863) Replication of EJB Session Beans does not work in cluster

by Martin Gencur (JIRA)

Replication of EJB Session Beans does not work in cluster --------------------------------------------------------- Key: WELD-863 URL: https://issues.jboss.org/browse/WELD-863 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Final Environment: JBossAS 6 SNAPSHOT (from 2011-03-02) - built in hudson Reporter: Martin Gencur Assignee: Ales Justin Fix For: TBC Attachments: weld-translator.ear I tested this feature with JSF/Translator example and I needed to do a few changes to test this feature. My fork of weld-core with the changes can be found at: https://github.com/mgencur/core/tree/cluster-test. I'll also attach a packaged ear of the app which I used. Steps to reproduce the bug: 1) deploy the attached weld-translator.ear file or checkout my changes from github and build the application 2) start first and second instance of the JBossAS to create a cluster (can be found at https://github.com/weld/core/blob/master/examples/README.md) 3) deploy the app 4) go to your web browser and disable cookies 5) go to http://localhost:8080/weld-translator, enter some text and click "Translate" 6) now change the port number in the address to 8180 and refresh (note that there should be also jsessionid included in the URL) 7) now the text you entered into the text area should be still there (since the value is stored in a field of SFSB which is clustered, but instead, you get the following exception at the slave JBossAS instance: 12:00:16,662 WARN [org.jboss.web.tomcat.service.session.distributedcache.ispn.DistributedCacheManager] Problem accessing session [hz****59+A__]: org.jboss.weld.exceptions.WeldException: WELD-001500 Failed to deserialize proxy object Note that if you then go to the first address (with port 8080) and then again to 8180 - from now the replication works fine. But IMHO this is not desired behaviour, the second (backup) JBoss instance should be ready immediately The question is if the changes of the application are the right ones. There is nobody here who could confirm this. Please pay attention to it and comment this issue if it's not correct. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
13
0 / 0

[JBoss JIRA] Created: (WELD-439) conversation example

by Dan Allen (JIRA)

conversation example -------------------- Key: WELD-439 URL: https://jira.jboss.org/jira/browse/WELD-439 Project: Weld Issue Type: Feature Request Components: Examples Affects Versions: 1.0.1.CR2 Reporter: Dan Allen There should be an example that demonstrates the minimal use of conversations, perhaps using the example from the spec or reference guide. The example should include a scenario where the conversation is propagated on a postback, both with and without <f:ajax>. -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (WELD-494) Add Arquillian test to the dist examples

by Aslak Knutsen (JIRA)

Add Arquillian test to the dist examples ---------------------------------------- Key: WELD-494 URL: https://jira.jboss.org/jira/browse/WELD-494 Project: Weld Issue Type: Task Components: Examples Reporter: Aslak Knutsen The Weld/CDI examples that are included in the Weld dist should come complete with Arquillian test suites showing how to test. Both embedded/container. -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-848) @Inject ignores activation of passivated stateful session beans

by Juergen Zimmermann (JIRA)

@Inject ignores activation of passivated stateful session beans --------------------------------------------------------------- Key: WELD-848 URL: https://issues.jboss.org/browse/WELD-848 Project: Weld Issue Type: Bug Reporter: Juergen Zimmermann If a stateful session bean gets passivated and later on activated, then the @Inject'ed fields are null. The only workaround I found is: provide a method annotated with @PostConstruct and make a JNDI lookup for "java:comp/BeanManager". -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (WELD-498) A better way to specify the version than using the manifest

by Pete Muir (JIRA)

A better way to specify the version than using the manifest ----------------------------------------------------------- Key: WELD-498 URL: https://jira.jboss.org/jira/browse/WELD-498 Project: Weld Issue Type: Feature Request Components: Infrastructure Reporter: Pete Muir This is flaky as the manifest gets rewritten. Steve Ebersole did something where he wrote it to a class as part of the build -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-38) ConversationScoped not working on Tomcat

by Fabio Wang (JIRA)

ConversationScoped not working on Tomcat ---------------------------------------- Key: WELDX-38 URL: https://jira.jboss.org/jira/browse/WELDX-38 Project: Weld Extensions Issue Type: Bug Components: Servlet Containers Affects Versions: Servlet Containers 1.0.0.CR1 Environment: Apache Tomcat 6.0.20 Reporter: Fabio Wang Trying to mark a conversation as long-running causes an exception (java.lang.NoClassDefFoundError: javassist/util/proxy/ProxyObject) when the ServletConversationManager tries to get a proxy for the httpSession. The ProxyFactory.classLoaderProvider ends up resolving the classloader to an instance of org.apache.catalina.loader.StandardClassLoader (which doesn't know the javassist lib, since it's only in the app classloader). -- 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, 10 months

5
24
0 / 0

[JBoss JIRA] Created: (WELD-446) Improve startup times

by Shane Bryzak (JIRA)

Improve startup times --------------------- Key: WELD-446 URL: https://jira.jboss.org/jira/browse/WELD-446 Project: Weld Issue Type: Task Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.CR2 Reporter: Shane Bryzak Assignee: Pete Muir We need to improve startup times for environments such as Google App Engine, which are currently in the range of 4-6 seconds. -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-840) Weld 1.1 breaks compatibility with groovy objects

by Jeff Howard (JIRA)

Weld 1.1 breaks compatibility with groovy objects ------------------------------------------------- Key: WELD-840 URL: https://issues.jboss.org/browse/WELD-840 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.Final Environment: Groovy 1.7.6, tomcat 6, weld 1.1, JSF 2 (mojarra 2.0.3) Reporter: Jeff Howard Weld created proxies need to know how to work with groovy objects. Currently, weld is attempting to proxy the methods from the groovy.lang.GroovyObject interface which is confusing the groovy runtime. Groovy objects have a per-class metaclass that is getting used with the wrong class instances. Also, weld is using hyphen characters in the generated proxy class names, which breaks groovy's dynamic invoke mechanism. The referenced forum thread contains a patch that addresses the groovy incompatabilities in weld's ProxyFactory.java -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (WELD-817) Wrap Contexutal impls passed to Contexts in a serializable wrapper if the context is passivation capable

by Pete Muir (JIRA)

Wrap Contexutal impls passed to Contexts in a serializable wrapper if the context is passivation capable -------------------------------------------------------------------------------------------------------- Key: WELD-817 URL: https://issues.jboss.org/browse/WELD-817 Project: Weld Issue Type: Feature Request Reporter: Pete Muir Fix For: 1.2.0.Beta1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-765) Simplify access to a deployment's BeanManager, when its id (or the BDA id) is known

by Marius Bogoevici (JIRA)

Simplify access to a deployment's BeanManager, when its id (or the BDA id) is known ----------------------------------------------------------------------------------- Key: WELD-765 URL: https://jira.jboss.org/browse/WELD-765 Project: Weld Issue Type: Feature Request Components: Weld SPI Affects Versions: 1.1.0.Beta2 Reporter: Marius Bogoevici Fix For: 1.1.0.Beta3 Currently, the BM id and BDA ID are practically equivalent. Retrieving the BeanManager if said ID is known requires iterating Deployment.getBeanDeploymentArchives() until the BDA is found and then retrieving the BeanManager from the deployment by using Bootstrap.getManager(BeanDeploymentArchive beanDeploymentArchive). This can be simplified by introducing Deployment.getBeanDeploymentArchive(String BDAid). Another possibility is to provide Bootstrap.getManager(String bdaID). Both variants would simplify the access code and make it work faster. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2011