Chapter 10: Resource Properties

In the previous chapters we have seen how state information in the service is stored inside a resource and, more specifically, in resource properties. However, our interaction with resource properties was very limited: our service could modify their values, and we could only access one particular resource property ( Value) using the GetValueRP operation. In this chapter we will see all the tools that will allow us to work with resource properties. We will also see how we can declare resource properties more complex than the ones seen in the previous examples.

10.1 A Closer Look at Resource Properties

Before we begin, we need to take a closer look at how resource properties are represented and handled internally in our service. First of all, let's recall how our resource properties are declared in all the examples we've seen so far:

                            <a name="328"></a><a name="page138"></a>

Notice how we're using XML Schema to declare an element named MathResource- Properties that must contain a Value element and a LastOp element. The Value element, in turn, is declared to contain an integer ( xsd:int) and the LastOp element, a string ( xsd:string).

Remember

Remember that the individual resource properties (such as Value and LastOp must be declared as global elements. This was explained in Section 6.1.2, "WSRF and Globus-specific features of WSDL".

In the previous examples, we have simply interpreted this as meaning "Our service has two resource properties, Value of type...

< Previous Excerpt Next Excerpt >

Purchase This Book

Globus Toolkit 4: Programming Java Services

TABLE OF CONTENTS

Chapter 10: Resource Properties

10.1 A Closer Look at Resource Properties

Contact Preferences

This is embarrasing...

Customize Your GlobalSpec Experience

Select Your Free Newsletters

Industry Newsletters

Select Your Free Product Alerts

This is embarrasing...