I am leaning towards the java-add-annotation approach as it seems more intuitive and could solve other use cases that may arise.When I create an EJB with Forge with the following command :ejb-new-bean --named MyServiceI get the following :@Stateless@LocalBeanpublic class MyService implements SerializableIn some cases, I would need to add an extra @Named annotation. Several ways to do it. On the EJB command itself, we could add a parameter :ejb-new-bean --named MyService --addNamedBut I think it would be good to have something more generic that could be used anywhere. We could use the same logic as constraint-add (that adds any kind of constraint on any Entity) and have something likecdi-add-qualifier --qualifier Named --target org.app.service.MyService// or on a property, which could be usefulcdi-add-qualifier --qualifier Named --onProperty myPropcdi-add-qualifier --qualifier Named --onMethod myMethodOr something even more generic would be to use the Java commandjava-add-annotation --annotation javax.inject.Named --target org.app.service.MyService
java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onProperty myPropjava-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onMethod myMethodjava-add-annotation --annotation javax.inject.Named --onProperty myPropjava-add-annotation --annotation javax.inject.Named --onMethod myMethodAny thoughts ?Antonio_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev