Community
Participate
Working Groups
Add action to generate deployment descriptor from Annotations for Java EE 5 projects (example: for EJB 3 projects to generate ejb-jar.xml) Use case: It's easier for developers to use annotations during the Java EE 5 projects development but annotations are "hard-coded" in the code. The Application Assembler, The EJB Deployer, The System Administrator needs the deployment descriptor. So, when the developer finishes the projects he/she must write the xml deployment descriptor manually. From my point of view the following possible scenarios must be handled: 1. the xml descriptor does not exist - just generated. 2. the xml descriptor exists. A dialog must appear with possible solutions: - the xml properties takes precedence; - the annotations takes precedence; - manual (something similar to manual resolving of conflicts). I don't know if the opposite is useful - to generate annotations from xml descriptor.
Moving these enhancements to 301 for now
This is probably something we should wait until 3.1 to do.
Functionality for processing Java EE models is provided with bug 198815. I could enhance the current implementation of the Java EE model providers so that one can get the xml model, the annotation model, and the merge model using IModelProvider.getModelObject(path). Depending on the "path" value we can return xml, annotation or merged model. This way it would be easy to generate xml dd from annotation.
This bug looks very similar to bug 236621. I think they are not duplicated, since bug 236621 suggests also an option in the wizard while this bug suggests an action for generating deployment descriptor from annotation. But there is for sure a connection between both bugs. At least the functionality will be the same. I am currently not sure about the dependencies between both bugs :)
