[jboss-dev-forums] [Design of EJB 3.0] - Re: Empty @Remote on bean class

[ALRubinger]

I'll need some more background on how the CTS test deployments differ from those in the EJB3 testsuite.

"Metadata trunk, RemoteProcessor Line 71" wrote : if(remote.value() == null || remote.value().length == 0)
  |             throw new IllegalArgumentException("Empty @Remote on bean class " + type.getName() + " is not allowed");

...seems to violate EJB3 4.6.6 Bullet 5.6; this doesn't make for an invalid annotation if one business interface is defined by the bean class.

However, when I make the same case in EJB3 (Empty @Remote with one business interface implemented by the bean class), deployment succeeds; the above code is not even hit.

Why does the CTS code run through the RemoteProcessor where the EJB3 testsuite does not?

S,
ALR



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110362#4110362

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110362