perfsonar development work

[Herbert Souza <>]

Maciej,
 
 In the class "LSRegisterAction.java" in the check metadata part exists a test: "if(checkIfKeyIsRegistered (keyValue))". If this test return "true" the Key is registered and this service must be updated rigth? If yes, why in test when the result is "true" you consider that the Key was not found? 
 
 The correct would be: if(!checkIfKeyIsRegistered (keyValue))?
 
 Regards!
 
 The correct one would not be if (! Che) 
 
 
 

Maciej Glowiak <> escreveu:
>  Loukik,
>
> Just some additional thoughts.
>
> Loukik Kudarimoti napisał(a):
> > Hi Roman and Maciej,
> > 
> >  From SQL MA, I found out that the following properties are being used 
> > in order to determine the type of access to xmldb and also the access 
> > related parameters.
> > 
> >
>  component.ma.xmldb.db_uri
> > component.ma.xmldb.db_username
> > component.ma.xmldb.db_password
> > component.ma.xmldb.db_status
> > component.ma.xmldb.db_access
> > component.ma.xmldb.db_uri.xmlrpc
> > 
> > Can you please help me in understanding the purpose and the way to use 
> > the following properties
> > 
> > component.ma.xmldb.db_uri.xmlrpc and component.ma.xmldb.db_uri
> > -> do we need both of them?
> > 
> > component.ma.xmldb.db_status
> > -> what does this mean? If its off, does the storage manager 
> > automatically read from an xml file instead?
> > 
> > I would like to make use of the existDb but I see that I need to pass 
> > the names of these properties. I suggest we fix the name of these 
> > properties and read them directly in the factory so that
> > * Each service doesn't need to pass them. Invocation becomes simpler.
>
> First I created Storage Manager in
>  Components architecture because of 
> performance. But as I tested later, the performance was exactly the 
> same, so using component is unnecessary complication.
>
> The simplest way of using Storage Manager is the way I followed in the 
> LS. (XmlLsTypeServiceEngine.java).
>
> I left old functionality to avoid crash of other services that used this 
>   Storage Manager. But I think we should migrate towards using Storage 
> Manager directly
>
> > * We have the same property names for all the services. That way we 
> > avoid duplicate entries and its easier to manage and understand.
>
> I agree, that properties names should be unified, but it may be not so 
> simple, especially if you need to use different Storage Managers 
> (probably there would be a need for using it in LS when we had AA)
>
> But,as I told you by phone: I agree it could be done better. I'll talk 
> to Roman about it and we'll find a consensus :)
>
> Maciej
>
>
> --
>  
>
>   --------------------------------------------------------------------
> | Maciej Glowiak        Network Research and Development            ||
> |      Poznan Supercomputing and Networking Center ||
> | (+48 61) 858 2024     http://monstera.man.poznan.pl/              ||
>   ====================================================================

Herbert Monteiro Souza

NUPERC - UNIFACS

E-mail alternativo:

Cel.: 55 (71) 88029549

Tel. Com.: 55 (71)3300179

---

O Yahoo! está de cara nova. Venha conferir!