Concerning the client-config.wsdd... Is the client always expected to have this file in his HOME folder, or is there a tricky way to include it in some jars?
I've never managed the latter solution, and the former is not realistic for a transparent user application Regards Igor From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rachana Ananthakrishnan Sent: lunes, 20 de octubre de 2008 15:39 To: '#PAN KE#'; [email protected] Subject: RE: [gt-user] about Java WS core client-side library I don't have a list of dependencies that are needed just for the client side. But you will need at least all of the security libraries, the client-config.wsdd file and the jars for classes in that file (which would be wsrf core, common and so on). For most part, the Java WS core libraries and the stubs for your library should definitely work. Rachana ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of #PAN KE# Sent: Monday, October 20, 2008 4:37 AM To: [email protected] Subject: [gt-user] about Java WS core client-side library Dear folks, Suppose I have written a GT4 web service and deployed in a GT4 Java WS core container. I want to invoke this service from a machine which does not have GT4 installation. What client-side library does the machine need except the stubs for the invoked web service? i.e. what globus-specific client-side library does the machine need? Thanks. Regards, Pan Ke ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------
