Jaikiran, thanks again for taking a look at this but for this instance, I think I figured it out (after much debuging). I ASSUMED that my client JBoss will automatically have access to jbossall-client.jar. That as I know now was a silly assumption, like most assumptions. For what it is worth, I debuged my standalone code and my JBoss code. They followed the same path until NamingManager, line 303, at which time the JBoss client tried to load ObjectFactory from reference and bombed since it couldn't load the class. On the standalone side, I had included it in the classpath. My solution - add jbossall-client.jar to my "jboss client" 's lib directory. It works now. Obviously, if this is not the way to solve it, please correct me, but I think this was a classpath issue. Commets/corrections will be greatly appreciated View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174878#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...