Hi Dies, Thanks for your reply :)
Dies wrote: > > I believe there are no major updates to the manual since the 1.2. The > version number is not even updated. > Regarding detailed documentation, also check out the Wiki, and this > mailing list. > http://wiki.apache.org/ws/FrontPage/Axis > I've checked out the wiki also, but again it only seems to deal with the Web service is all in one package deployment. Dies wrote: > >> But when I try and load the actual implemntation class in the helper >> using >> class.newInstance() I get an exception (one that will not get caught >> despite >> surrounding it in a try/catch block) thrown back to the client. So I >> assume >> I haven't set things out correctly. > > I assume so, I think you put your classes in the right place (provided > the directory names match your package name). > Yes, the folders correspond to the package names. I am able to reference the business logic statically, but can't do it dynamically. For example if in my Web service *Impl class I write: businesslogic bl = new businesslogic(); bl.doSomething(); it works. However if I try to do the following: class c = Thread.currentThread().getContextClassLoader().loadClass(className); businesslogic bl = (businesslogic) c.getInstance(); I get an exception. Any ideas why? Also any ideas why the exception refuses to be caught even though I wrap it in a try/catch(Exception e) block? The error on the client side is java.lang.reflect.InvocationTargetException Dies wrote: > >> Also when using a resource bundle with a properties file, the properties >> file needs to be in \Tomcat\webapps\axis\WEB-INF\classes\ to be found. >> Does >> this mean that all services on the server need to have differently named > > Yes. It is usual to put your property files in packages like your > classes, so this should not be a problem? > Sorry, I'm not 100% sure what you mean here, are you saying that it is usual to store the properties files in a jar (in which case can you alter them?) or just that you should have separate names for them? I am slightly confused at the way that you would have a common package that needs a different configuration for each service it is used in. It seems to me that this is not possible unless you pass the properties to the common package when you instantiate it? Thanks for all your help, and any further help you can provide :) - Michael -- View this message in context: http://www.nabble.com/Deploying+Web+services+with+Axis+1.3-t1672497.html#a4534851 Sent from the Axis - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
