January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1014) Deployment dependencies in new VDF

by Carlo de Wolf (JIRA)

Deployment dependencies in new VDF ---------------------------------- Key: EJBTHREE-1014 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1014 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC11 - FD Containers are started in the wrong order. This needs a proper supply / demand chain. -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-993) Error message for not specifying a non-jta-data-source for RESOURCE_LOCAL should reference spec

by Carlo de Wolf (JIRA)

Error message for not specifying a non-jta-data-source for RESOURCE_LOCAL should reference spec ----------------------------------------------------------------------------------------------- Key: EJBTHREE-993 URL: http://jira.jboss.com/jira/browse/EJBTHREE-993 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf The following error message should make a reference to spec EJB3 JPA 6.2.1.2: 20:39:08,015 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:ear=jemos-ejb3-ear-1.0.0.ear,jar=jemos-ejb3-ejb-1.0.0.jar,unitName=jemos-ejb3-test-junit 20:39:08,031 WARN [ServiceController] Problem starting service persistence.units:ear=jemos-ejb3-ear-1.0.0.ear,jar=jemos-ejb3-ejb-1.0.0.jar,unitName=jemos-ejb3-test-junit java.lang.RuntimeException: You have not defined a non-jta-data-source for a RESOURCE_LOCAL enabled persistence context named: jemos-ejb3-test-junit -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-996) Unit test for EJBTHREE-751

by Carlo de Wolf (JIRA)

Unit test for EJBTHREE-751 -------------------------- Key: EJBTHREE-996 URL: http://jira.jboss.com/jira/browse/EJBTHREE-996 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

16 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1000) Service bean is uninstalled without using canonical name

by Carlo de Wolf (JIRA)

Service bean is uninstalled without using canonical name -------------------------------------------------------- Key: EJBTHREE-1000 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1000 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD java.lang.IllegalStateException: Not installed: jboss.ejb3:management=interface,with=customName,is=serviceThree at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:449) at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:389) at org.jboss.ejb3.MCKernelAbstraction.uninstallMBean(MCKernelAbstraction.java:188) -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-974) Temporarly have the SecurityDeployer ignore all EJB3 deployments

by Carlo de Wolf (JIRA)

Temporarly have the SecurityDeployer ignore all EJB3 deployments ---------------------------------------------------------------- Key: EJBTHREE-974 URL: http://jira.jboss.com/jira/browse/EJBTHREE-974 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-985) env-entry-value is optional (16.4.1.3 last paragraph)

by Carlo de Wolf (JIRA)

env-entry-value is optional (16.4.1.3 last paragraph) ----------------------------------------------------- Key: EJBTHREE-985 URL: http://jira.jboss.com/jira/browse/EJBTHREE-985 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf -- 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

16 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-971) Allow injection of EJBContext into java:comp/env via Resource annotation

by Carlo de Wolf (JIRA)

Allow injection of EJBContext into java:comp/env via Resource annotation ------------------------------------------------------------------------ Key: EJBTHREE-971 URL: http://jira.jboss.com/jira/browse/EJBTHREE-971 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-973) Allow a @SecurityDomain with only unauthenticatedPrincipal

by Carlo de Wolf (JIRA)

Allow a @SecurityDomain with only unauthenticatedPrincipal ---------------------------------------------------------- Key: EJBTHREE-973 URL: http://jira.jboss.com/jira/browse/EJBTHREE-973 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal doesn't throw an IllegalStateException. Effectively the bean would run without security, because principals can't be validated. Note that in time the server itself will have an unauthenticatedPrincipal default which comes from the security deployer. (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751) -- 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

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-972) sessionContext.getBusinessObject(null) should throw IllegalStateException

by Carlo de Wolf (JIRA)

sessionContext.getBusinessObject(null) should throw IllegalStateException ------------------------------------------------------------------------- Key: EJBTHREE-972 URL: http://jira.jboss.com/jira/browse/EJBTHREE-972 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

16 years, 11 months

1
3
0 / 0

[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

16 years, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008