January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-930) Simplify use of @CacheConfig

by Brian Stansberry (JIRA)

Simplify use of @CacheConfig ---------------------------- Key: EJBTHREE-930 URL: http://jira.jboss.com/jira/browse/EJBTHREE-930 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.0 CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry There are two separate @CacheConfig impls -- one for the simple cache and one for the clustered. We should support something like: @Stateful @org.jboss.annotation.ejb.cache.simple.CacheConfig(maxSize=200000, idleTimeoutSeconds=500) @Remote(Test.class) public class TestBean implements Test..... where clustering is enabled via <clustered>true</clustered> in jboss.xml. Similarly, @Stateful @org.jboss.annotation.ejb.cache.tree.CacheConfig(maxSize=200000, idleTimeoutSeconds=500, replicationIsPassivation=false) @Remote(Test.class) public class TestBean implements Test..... where clustering is disabled via <clustered>false</clustered> in jboss.xml. Basically, the StatefulCache impls should check for the existence of the other @CacheConfig if the standard one isn't present. Then use the common values between the two, and the default values for any missing configurations (e.g. replicationIsPassivation). Probably the @CacheConfig annotations themselves as well as the impls should be refactored into a type hierarchy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-947) Relaxed signature checking

by Carlo de Wolf (JIRA)

Relaxed signature checking -------------------------- Key: EJBTHREE-947 URL: http://jira.jboss.com/jira/browse/EJBTHREE-947 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD Allow RuntimeException throwing if relaxed signature checking is on for methods which should not throw any exception (EJB3 12.4). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-936) Allow jboss descriptor entries for unknown bean type

by Carlo de Wolf (JIRA)

Allow jboss descriptor entries for unknown bean type ---------------------------------------------------- Key: EJBTHREE-936 URL: http://jira.jboss.com/jira/browse/EJBTHREE-936 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC11 - FD Allow generic descriptor entries without knowing the bean type. The following could be specified in '<session>', but we don't want to know the actual annotation. So it should possible to use '<ejb>'. <jboss xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0"> <enterprise-beans> <ejb> <ejb-name>MyStatelessBean</ejb-name> <resource-ref> <res-ref-name>qFactory</res-ref-name> <jndi-name>ConnectionFactory</jndi-name> </resource-ref> </ejb> </enterprise-beans> </jboss> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-910) AllowedSuffixes in the deployer has inverted logic

by Carlo de Wolf (JIRA)

AllowedSuffixes in the deployer has inverted logic -------------------------------------------------- Key: EJBTHREE-910 URL: http://jira.jboss.com/jira/browse/EJBTHREE-910 Project: EJB 3.0 Issue Type: Bug Environment: trunk Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD Specifying AllowedSuffixes on the EJB3 deployer actually makes it ignore those and pick up the others. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-893) Set hibernate.session_factory_name to an appropriate default if the user don't

by Emmanuel Bernard (JIRA)

Set hibernate.session_factory_name to an appropriate default if the user don't ------------------------------------------------------------------------------ Key: EJBTHREE-893 URL: http://jira.jboss.com/jira/browse/EJBTHREE-893 Project: EJB 3.0 Issue Type: Feature Request Reporter: Emmanuel Bernard Fix For: EJB 3.0 RC11 - FD This is useful for clustering http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017398#4017398 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-861) Dependencies should be registered using a canonical name

by Carlo de Wolf (JIRA)

Dependencies should be registered using a canonical name -------------------------------------------------------- Key: EJBTHREE-861 URL: http://jira.jboss.com/jira/browse/EJBTHREE-861 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD Tip from Adrian: Why don't you just fix it like the ServiceMetaData does when it doesn't know whether it is dealing with a bean name or ObjectName? String dependency = ... try { ObjectName on = new ObjectName(dependency); dependency = on.getCanonicalName(); } catch (MalformedObjectName ignored) { // Not an object name } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-811) Create a new set of EJB3 deployers

by Carlo de Wolf (JIRA)

Create a new set of EJB3 deployers ---------------------------------- Key: EJBTHREE-811 URL: http://jira.jboss.com/jira/browse/EJBTHREE-811 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Priority: Critical The current EJB3 deployers need to be refactored to be more in line with the VDF. This should make it possible to augment metadata from other sources (EAR, Profile etc). - EJB3ParsingDeployer : parses the xml to create metadata - EJB3JBossParsingDeployer: parses the jboss-xml to augment the metadata - EJB3ScanningDeployer: scan annotations to augments the metadata -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-840) OutOfMemoryError: Java heap space

by Carlo de Wolf (JIRA)

OutOfMemoryError: Java heap space --------------------------------- Key: EJBTHREE-840 URL: http://jira.jboss.com/jira/browse/EJBTHREE-840 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: AS 4.2 (20070122) Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD OutOfMemoryError when running microbench -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
15
0 / 0

[JBoss JIRA] Created: (EJBTHREE-791) Deployment fail on non JTA persistence unit

by Emmanuel Bernard (JIRA)

Deployment fail on non JTA persistence unit ------------------------------------------- Key: EJBTHREE-791 URL: http://jira.jboss.com/jira/browse/EJBTHREE-791 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Emmanuel Bernard Fix For: EJB 3.0 RC10 - FD <persistence-unit>  </persistence-unt> and <persistence-unit transaction-type="RESOURCE_LOCAL">  </persistence-unt> Seems to fail with WARN [ServiceController] Problem starting service persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: jblog (2) should work (1) is very much expected from a usability POV. basically, if no jta-datasource is defined, we should expect a default transaction-type of RESOURCE_LOCAL Note that you might want to let the persistence provider test such compatibility issues, since it has more contextual information than the container (ie knows the meaning of the proprietary properties) Max can you confirm that my description match your bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

4
16
0 / 0

[JBoss JIRA] Created: (EJBTHREE-774) Please update the hibernate annotation documentation for @Version to indicate behaviour of null attribute

by Chris Hornsey (JIRA)

Please update the hibernate annotation documentation for @Version to indicate behaviour of null attribute --------------------------------------------------------------------------------------------------------- Key: EJBTHREE-774 URL: http://jira.jboss.com/jira/browse/EJBTHREE-774 Project: EJB 3.0 Issue Type: Task Components: Documentation Affects Versions: EJB 3.0 RC9 - FD Environment: all Reporter: Chris Hornsey Priority: Minor The hibernate annotation documentation has the following section: 2.2.1.2. Versioning for optimistic locking Please indicate in this documentation, that if an attribute that is versioned has a null value the entity will always be considered transient irregardless of other values typically analyzed to make the transient determination. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008