[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-342) Unify configuration file names and bootstrap
[
https://jira.jboss.org/browse/EJBTHREE-342?page=com.atlassian.jira.plugin...
]
Carlo de Wolf resolved EJBTHREE-342.
------------------------------------
Resolution: Out of Date
This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.
If you can reproduce this bug against a currently maintained version of
JBoss EJB 3 please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
Unify configuration file names and bootstrap
--------------------------------------------
Key: EJBTHREE-342
URL: https://jira.jboss.org/browse/EJBTHREE-342
Project: EJB 3.0
Issue Type: Bug
Reporter: Christian Bauer
Assignee: Bill Burke
Fix For: Branch_4_2
The microcontainer can be booted with StandaloneBootstrap, and it searches for
jboss-beans.xml in / and META-INF.
The E-EJB3 container is booted with EJB3StandaloneBootstrap, which searches for
embedded-jboss-beans.xml in / and supports a "basepath" argument.
Unify these two bootstrap classes. Wishlist:
- sensible default name for the configuration file ("jboss-beans.xml" sounds
good)
- searches in default locations (/ and META-INF)
- supports parameters to completely override not only the "basepath", but the
full location of the configuration file
The EJB3StandaloneBootstrap should _extend_ the StandaloneBootstrap, not reimplement it.
The current situation makes documentation and explanation unecessarily difficult.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira