I finally found some time to actually look at
org.jboss.web.tomcat.service.WebAppClassLoader and see that the IIOP stub is now being
generated at the client (web app) side. Why can't a web client dynamically get (via
HTTP) IIOP stubs generated by the EJB container, like other clients do? This works fine
for plain application clients and for EJBs acting as clients, it should work also for web
clients.
The WebAppClassLoader dependency on the IIOPStubCompiler looks unnecessary (and bad) to
me. I understand that dependency was introduced to fix JBCTS-591 and JBCTS-609, but IMO
the right way of fixing those issues is to ensure that the webapp classloader sees the
auxiliary classes used by the container-generated stubs (i.e., jboss-iiop-client.jar).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108933#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...