Hi,
Have you managed to integrate the client-config.wsdd directly in the
applet ? Or are you relying on the client having this file on his
computer?
Regards
Igor
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of J Seo
Sent: martes, 21 de octubre de 2008 18:43
To: #PAN KE#
Cc: Rachana Ananthakrishnan; gt-user@globus.org
Subject: Re: [gt-user] about Java WS core client-side library
Hi Pan Ke
I experimentally found the necessary jar files for a client side.
I developed an applet UI and tried to find out jar files one by one for
client side.
Our applet UI is working on a tomcat server with 22 jar files from the
gt4 core library and is therefore running on the client web browser
without GT4.
The problem is WS-notification because the gt4 client should use the
embedded container for receiving notifications, creating EPRs.
Therefore, I realized it is very difficult to separate the client side
from the server side because the client side should run a notification
service as servers do.
Anyway, jar files in my case are:
axis.jar,
addressing-1.0.jar,
jaxrpc.jar,
commons-discovery.jar,
wsdl4j.jar,
wsrf_common.jar,
wsrf_core.jar,
wsrf_tools.jar,
wsrf_core_stubs.jar,
cog-jglobus.jar,
cog-axis.jar,
wss4j.jar,
xalan.jar,
axis.jar,
axis-url.jar,
commons-digester.jar,
commons-collections-3.2.jar,
commons-beanutils.jar,
commons-cli-2.0.jar,
naming-common.jar,
naming-java.jar,
naming-resources,jar
Hopefully, it will help you.
Jung
#PAN KE# wrote:
It is a common usage that GT4 services are defined and deployed at the
server side while clients on other machines invoke the services
without installation of GT4 or the java WS core. Why the client-side
library is not abstracted out from the collection of Java WS core
libraries? The whole collection of the Java WS core libraries is not
small-sized, this may prevent GT4 clients from running on
resource-limited platforms. Thanks for your attention.
Regards,
Pan Ke
------------------------------------------------------------------------
*From:* Rachana Ananthakrishnan [mailto:[EMAIL PROTECTED]
*Sent:* Mon 10/20/2008 9:39 PM
*To:* #PAN KE#; gt-user@globus.org
*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:* gt-user@globus.org
*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.
------------------------------------------------------------------
