I might have not stressed that enough in the previous posts, but I meant the
methods to be conceptually abstract, not formally, e.g.:
@Name("a")
public class ComponentA
{
@In("b")
protected IComponentB getB()
{
throw new UnsupportedOperationException();
}
public void doStuff()
{
getB().doSomeOtherStuff();
// more stuff
}
}
Note that both class ComponentA and method getB should be abstract, but are not.
Is it against the EJB spec to have such SFSB?
Also, I do not see how this class is difficult to test.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947179#3947179
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947179
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
