Carlos, As James is pointing out, you can register your own Callback class for persisting the data if you write a class which implements either SetResourcePropertyCallback or just ResourcePropertyCallback (depending on what "hooks" you would like).
In you implementation of the Callback you would need to persist the value however you see fit. -Sal -----Original Message----- From: James Lorenzen [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 19, 2005 10:17 AM To: [email protected]; [email protected] Subject: RE: about set requests and values kept in memory Here is a SOAP Set Request I have used previously. This one sets the OperationalStatus property to Unavailable. ** Note: you might need to change the ResourceID tag in the Header element. I think currently the name should be ResourceIdentifier as defined in your jndi-config.xml file. Hope this helps. Simpliest way to store this value would be: Create a Property Callback, set the callback in your XXXXXResource.java class. In the Callback store the value in a file. Then each time the Callback is called, the new value will be stored to the file. When you initialize the value in your XXXXXResource.java init() method, you can retrieve the value from the file. Hope that makes sense. <s12:Envelope xmlns:s12= "http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsa= "http://schemas.xmlsoap.org/ws/2004/03/addressing"; xmlns:wsrp="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"; xmlns:muws-xs1 ="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part1.xsd"; xmlns:muws-xs2 ="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.xsd"; xmlns:tns= "urn://com.gestalt.dmit.xswtp/wsdl"> <s12:Header> <wsa:To> http://localhost:7070/muse/services/TargetNominationService </wsa:To> <wsa:Action> http://gestalt.com/tacf/systeminfo/SetResourceProperties </wsa:Action> <tns:ResourceID>bob</tns:ResourceID> </s12:Header> <s12:Body> <wsrp:SetResourceProperties xmlns:wsrp="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"; xmlns:tns= "urn://com.gestalt.dmit.xswtp/wsdl"> <wsrp:Update> <muws-xs2:OperationalStatus>Unavailable</muws-xs2:OperationalStatus> </wsrp:Update> </wsrp:SetResourceProperties> </s12:Body> </s12:Envelope> ________________________________ From: Lombrera Lombrera [mailto:[EMAIL PROTECTED] Sent: Mon 7/18/2005 10:08 PM To: [email protected] Subject: about set requests and values kept in memory Hi all I have deployed Muse and I am very happy to see it working I would like to ask you two things: a - if there is a sample of a set request, for example, to change the value of a propertie like CpuUsage from the Host Service. I have been using the requests in the requests dir, but there is not a example of a set request to change the value of some propertie. Existing this, could you share it with me? b - I have perceived also, that when I will change the value of some propertie, this value will be kept in memory. This means that if the machine is rebooted it will loose the new values. Is this right ? What could be the best way to make this new values be mantained? Thank you in advance Excuse me for my poor english Carlos ________________________________ Yahoo! Acesso Grátis <http://us.rd.yahoo.com/mail/br/taglines/*http://br.acesso.yahoo.com/> : Internet rápida e grátis. Instale o discador agora! <http://us.rd.yahoo.com/mail/br/taglines/*http://br.acesso.yahoo.com/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
