The more we discuss about this the more convinced I become that we should just include the
stubs in the war deployments.
First because if you want your component to be a client of an IIOP application you should
provide the stubs that will allow your component to make the IIOP calls. I don't see
why you would rely on the app server runtime to provide those for you.
Second because of the possibility of abuse that you have just described. I don't think
we should include a hack to allow the generation of stubs when someone forgets to add
those stubs to the deployments.
When we act as a client, stubs should either be pre-compiled and inserted in the
deployment war file or downloaded from a location specified in the IOR (when the server
makes such mechanism available). As the RI doesn't make stubs available for download,
the only other way left for us is to include the pre-compiled stubs in the vehicles war
files. At least this is what I think.
If this makes sense, we should review the way stubs are generated in the ejb container.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157084#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...