I think only an EJB can specialize an EJB - writing it from memory so take it as it please. This is actually nice cause it enforces the exception model and avoid to miss cases in tests. But yes @Specializes is a quick and efficient mocking solution.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-11-03 10:08 GMT-08:00 hwaastad <[email protected]>: > OK, > cool and I'll check out tomorrow. > > So, If I can try to summarize what I can do: > > - For CDI beans I only need @specializes when extending implementation. > > - For EJB's I need either a @Local or @Local(iface) and @specializes. > > No need for specific beans.xml config. > > Actually, just using @specializes fits my need in this pratially mocking > scenario.. > > Made a use.local-interface branch just to state the, after some > consideration, the obvious :-) > > br hw > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/ApplicationComposer-alternative-stereotype-mocking-tp4676678p4676714.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
