The sar contains the class files for the MBean interface and implementation, it
also contains a jar file that has the stateless bean interfaces and the
implementations with @Stateless annotation.
I do realize that I could produce 2 separate jars, one with interfaces only and
one with
Falcor1 wrote :
|
| I do realize that I could produce 2 separate jars, one with interfaces only
and one with implementation.
|
| That seems like a bit of a maintenance hassle though and complicates the
build process.
|
|
It's not about a maintenance hassle, it's actually the
anonymous wrote : So is there a way to tell JBoss not to deploy the stateless
session beans that it is finding in the sar?
Are you even packaging the bean implementation classes (which have the
@Stateless annotation) in the .sar? If you are packaging only the interfaces
(which is the right
