I've run into this problem myself and traced it the absence of a client-config.wsdd file on the classpath of the invoking client code (running from an EAR deployed under JBoss) - the Axis engine was picking up the default client-config.wsdd supplied by JBoss which contained references to classes which were not available to my client code. The net result was that the ClassNotFoundException thrown during initialization resulted in a TypeMappingRegistry in the main engine configuration. Or something like that.
The moral is: make sure you have a usable client-config.wsdd on your client's classpath. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910529#3910529 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910529 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
