I am leaning towards the java-add-annotation approach as it seems more intuitive and could
solve other use cases that may arise.
Em 13/06/2014, às 04:19, Antonio Goncalves
<antonio.mailing(a)gmail.com> escreveu:
When I create an EJB with Forge with the following command :
ejb-new-bean --named MyService
I get the following :
@Stateless
@LocalBean
public class MyService implements Serializable
In 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 --addNamed
But 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 like
cdi-add-qualifier --qualifier Named --target org.app.service.MyService
// or on a property, which could be useful
cdi-add-qualifier --qualifier Named --onProperty myProp
cdi-add-qualifier --qualifier Named --onMethod myMethod
Or something even more generic would be to use the Java command
java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService
java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService
--onProperty myProp
java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService
--onMethod myMethod
java-add-annotation --annotation javax.inject.Named --onProperty myProp
java-add-annotation --annotation javax.inject.Named --onMethod myMethod
Any thoughts ?
Antonio
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev