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