June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-969) EJB3Deployer locking jars in deploy dir

by Brian Stansberry (JIRA)

EJB3Deployer locking jars in deploy dir --------------------------------------- Key: EJBTHREE-969 URL: http://jira.jboss.com/jira/browse/EJBTHREE-969 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA Reporter: Brian Stansberry In chasing down JBPAPP-171 I found that JBoss' deployment process tends to lock files in the deploy dir on Windows. (The farm dir as well, which is just a specialized form of deploy dir.) Traced it down to the EJB3Deployer.accepts() functionality, particularly the hasEjbAnnotation() method. The first line in that method Iterator it = ArchiveBrowser.getBrowser(di.url, new ClassFileFilter()); is causing the original jar in deploy to be scanned for annotations, rather than the copy in the server/.../tmp dir. That scan results in Windows filesystem locks on the deploy dir jar. Not always but seems like roughly 1/2 the time. Changing that line to the following made the problem go away: Iterator it = ArchiveBrowser.getBrowser(di.localUrl, new ClassFileFilter()); di.localUrl points to the tmp dir copy of the deployment. -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-959) EJB 2.1 Stateful Session Beans don't deploy

by Carlo de Wolf (JIRA)

EJB 2.1 Stateful Session Beans don't deploy ------------------------------------------- Key: EJBTHREE-959 URL: http://jira.jboss.com/jira/browse/EJBTHREE-959 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Priority: Blocker Fix For: Branch_4_2, EJB 3.0 RC11 - FD Deploying an EJB 2.1 SFSB through the EJB3 deployer doesn't work. A lot of precondition checks will complain about the code. Any of the following exceptions will occur: java.lang.RuntimeException: @javax.annotation.PostActivate annotated method has the wrong signature ... (EJB3 12.4) java.lang.RuntimeException: @javax.annotation.PostConstruct annotated method has the wrong signature ... (EJB3 12.4) java.lang.RuntimeException: @javax.annotation.PrePassivate annotated method has the wrong signature ... (EJB3 12.4) java.lang.RuntimeException: Interceptors can only have one post-construct/@PostConstruct method - ... -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-958) @Resource annotation's element "name" does not default to field name.

by Jari Mustonen (JIRA)

@Resource annotation's element "name" does not default to field name. --------------------------------------------------------------------- Key: EJBTHREE-958 URL: http://jira.jboss.com/jira/browse/EJBTHREE-958 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 4.2.0 GA Environment: Windows XP, Java 1.5 Reporter: Jari Mustonen Priority: Minor The javadoc of @Resource#name states that "The JNDI name of the resource. For field annotations, the default is the field name. ..." The following version 1 of DaServiceBean don't work as it doesn't inject anything to "myVar". The version 2 injects the value 5 correctly. --- Version 1 --- @Stateless @Remote @RemoteBinding(jndiBinding="daService") public class DaServiceBean implements DaService { @Resource private int myVar; public void foo() { System.out.println("myVar: " + myVar); } } --- Version 2 --- @Stateless @Remote @RemoteBinding(jndiBinding="daService") public class DaServiceBean implements DaService { @Resource(name="myVar") private int myVar; public void foo() { System.out.println("myVar: " + myVar); } } --- ejb-jar.xml --- <enterprise-beans> <session> <ejb-name>DaServiceBean</ejb-name> <env-entry> <env-entry-name>myVar</env-entry-name> <env-entry-type>java.lang.Integer</env-entry-type> <env-entry-value>5</env-entry-value> </env-entry> </session> </enterprise-beans> -- 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, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-953) A method with transaction attribute NEVER should throw EJBException instead of IllegalStateException

by Carlo de Wolf (JIRA)

A method with transaction attribute NEVER should throw EJBException instead of IllegalStateException ---------------------------------------------------------------------------------------------------- Key: EJBTHREE-953 URL: http://jira.jboss.com/jira/browse/EJBTHREE-953 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf If a method of an EJB3 bean is called with transaction attribute never and there is a transaction active, it should throw an EJBException (not an IllegalStateException). EJB3 13.6.2.6 -- 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, 6 months

1
2
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, 6 months

1
3
0 / 0

[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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-931) ejb-link with relative path not working

by Carlo de Wolf (JIRA)

ejb-link with relative path not working --------------------------------------- Key: EJBTHREE-931 URL: http://jira.jboss.com/jira/browse/EJBTHREE-931 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD 12:44:55,904 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=ejb3_bb_stateful_basic.ear,jar=ejb3_bb_stateful_basic_ejb.jar,name=RemoteCalculatorBean,service=EJB3 with dependencies: 12:44:59,748 INFO [EJBContainer] STARTED EJB: com.sun.ts.tests.ejb30.bb.session.stateful.basic.RemoteCalculatorBean ejbName: RemoteCalculatorBean 12:44:59,995 WARN [DeploymentEjbResolver] can't find a deployment for path '' of ejb link '#RemoteCalculatorBean' 12:44:59,996 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface com.sun.ts.tests.ejb30.bb.session.stateful.basic.StatefulRemoteCalculator and ejbLink of ejb3_bb_stateful_basic_ejb.jar#RemoteCalculatorBean in application-client.xml of ejb3_bb_stateful_basic_client it might not be deployed yet12:45:00,022 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=ejb3_bb_stateful_basic.ear,jar=ejb3_bb_stateful_basic_client.jar,name=ejb3_bb_stateful_basic_client,service=EJB3 with dependencies: 12:45:00,256 WARN [DeploymentEjbResolver] can't find a deployment for path '' of ejb link '#RemoteCalculatorBean' 12:45:00,258 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:ear=ejb3_bb_stateful_basic.ear,jar=ejb3_bb_stateful_basic_client.jar,name=ejb3_bb_stateful_basic_client,service=EJB3 state=Create java.lang.RuntimeException: Failed to populate ENC: env/ejb/RemoteCalculatorBean global jndi name was null -- 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, 6 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, 6 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, 6 months

2
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, 6 months

1
3
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 June 2007