[ http://jira.codehaus.org/browse/MEJB-6?page=comments#action_64753 ]
Wayne Fay commented on MEJB-6: ------------------------------ The EJB3 "final draft" was voted on and accepted by the JCP Executive Committee recently. Among the details is a confirmation that ejb-jar.xml is now optional, and ejb3 containers will now rely on metadata and automatic configurations of beans rather than requiring the deployment descriptor. So I believe Dan's patch should be accepted and applied to the maven-ejb-plugin, and a new release (or at least an official snapshot) produced asap. Relevant links: http://www.theserverside.com/news/thread.tss?thread_id=40199 http://jcp.org/en/jsr/detail?id=220 Copied from the EJB 3.0 final draft PDF document: 1.2 What is New in EJB 3.0 The Enterprise JavaBeans 3.0 architecture presented in this document extends Enterprise JavaBeans to include the following new functionality and simplifications to the earlier EJB APIs: Definition of the Java language metadata annotations that can be used to annotate EJB applications. These metadata annotations are targeted at simplifying the developer's task, at reducing the number of program classes and interfaces the developer is required to implement, and at eliminating the need for the developer to provide an EJB deployment descriptor. Specification of programmatic defaults, including for metadata, to reduce the need for the developer to specify common, expected behaviors and requirements on the EJB container. A "configuration by exception" approach is taken whenever possible. > Make the ejb-jar.xml deployment descriptor optional > --------------------------------------------------- > > Key: MEJB-6 > URL: http://jira.codehaus.org/browse/MEJB-6 > Project: Maven 2.x Ejb Plugin > Type: Improvement > Reporter: Tim Kettler > Priority: Trivial > Attachments: MEJB-4-maven-ejb-plugin.patch, MEJB-6-maven-ejb-plugin.patch > > > In the now near final EJB3 specification the use of deployment descripors is > optional. It would be nice if the maven-ejb-plugin wouldn't bump out with an > error if no descriptor is present. > The attached patch introduces a new boolean configuration option > 'enforceDeploymentDescriptor' which defaults to true so that the default > behavior is not changed. Feel free to change the name of the property if > appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
