Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Namespaces and LS installation

Subject: perfsonar development work

List archive

Re: [pS-dev] Namespaces and LS installation


Chronological Thread 
  • From: Michael Michalis <>
  • To: Prodromos Gerakios <>
  • Cc: "" <>, Loukik Kudarimoti <>, Ilias Tsompanidis <>, Michael Michalis <>, Athanassios Liakopoulos <>, Luis Marta <>, Maciej Glowiak <>
  • Subject: Re: [pS-dev] Namespaces and LS installation
  • Date: Fri, 16 Nov 2007 08:16:27 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Prodromos Gerakios wrote:
> Hi all,
>
> Namespaces:
> I have attempted to use trang so as to automatically generate the
> xsd files. trang ran successfully *but* the files produced by trang
> use the same namespace. For instance, in LSRegister there exist two
> messages: a request and response message, which have some element
> names in common but *just the names* not the *definitions*. I
> noticed that the rnc files do indeed use the same namespaces. It is
> therefore, impossible to write a single WSDL file for the entire web
> service. In fact, it is necessary to provide a different WSDL file
> for each operation. I noticed that other tests on soapUI (clmp and
> rrdMA) use multiple WSDL files as a result of this issue. I am not
> sure how Relax-NG works but it should be possible to generate a
> *single* and *complete* WSDL file. As things stand, it is
> impossible to validate request and response messages: current WSDL
> files (of clmp and rrdma) import both request and response xsds but
> really only use the response definitions for soapUI validation.
> Additionally, if the LS (or some other) service is contacted by an
> external (in respect to perfSONAR) service/client then it must use a
> single WSDL to contact it, right ?
>
Prodromos,
This is a long standing issue for perfSONAR and it has been raised a
lot times in the past. But to be honest I'm not sure this will change
soon.
> LS installation:
>
> I think that the LS installation assumes that eXist listens on port
> 8086. It also did not create a new account in eXist as a result of
> this problem. I imagine that the installation script does attempt to
> generate a new account. There is a relatively easy workaround
> (modify the properties file in the deployment directory and create
> the eXist account manually) but I think the installation should be
> automated.
>
The process should be automated, I think it is required by the Release
Management Team, and in any case the script should have asked for
eXist location. It's been a while since I have installed LS and I'm
not sure what the installation script asks the user. I think the
script also asks for the user to choose between exsit standalone and
embedded in Tomcat. From your commends I suppose you chose standalone.
I think it would be easier for you, since your a new comer to use
embedded exist, and don't worry about ports and so on and also it
will save you some time. In any case you should report any bugs or
insufficiencies in the installation procedure(and off course for the
service in general) to the developer of the service, which is Maciej
Glowiak -on the cc list-(Its my mistake I haven't told you the name of
the person responsible for the service), so you can get some
assistance and also report any bugs in Bugzilla
http://wiki.perfsonar.net/jra1-wiki/index.php/Bugzilla_details .

You can find contact information for any one in the project in
http://wiki.perfsonar.net/jra1-wiki/index.php/PerfSONAR_Contacts (You
should also add your won contact information :-) ).

Michalis
>
> Please let me know what you think. We could discuss these issues in
> tomorrow's meeting.
>
> Kind regards,
> Prodromos.
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHPTW7oEWq51/Q/40RAnAKAKCLKJIKDcdF9YbBHlHoeOnsfSP/sgCgnK1h
bT+VYaNy3wpvqb5ZgGO+dPo=
=A+7G
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.16.

Top of Page