I haven't written something for a long time. I have been busy in this time. I have a big pile of experience, it is more scattered, so the whole experience is still over time.
However, this small problem is still independent.
If you have a grind, you have to mention it again, GT3 realizes the Thought of Grid Service is a stateful service, while GT4 is a stateful service stateful resource. This seems not large in the Client side, but there is a problem. In the GT3, the client end accesses service through service; in GT4, in GT4 is an object with EndPointReferenceType (usually I defined this variable name EPR, after which EPR, "means ENDPOINTREFERENCETYPE objects to access service and resource; EndpointReference is a type of WS-Addressing standard definition, which contains information about Service's Handle and Resource authentication.
Handle is a string type, which is easy to output and save. EndPointReference is a complex type. After you create a resource, the server returns an EPR to read, modify the Resource by this EPR. However, if the Client end programs exit, if you don't want to destroy Resource (later in the future), EPR will be lost, and the loss of EPR will result in the loss of Resource. So you must save EPR, save method? This problem did not consider this problem in all published Globus documents and sample code (it was used in this program in this program). I asked globus.org, thanks to Ben Clifford and Jarek. In order to ensure the versatility of the saved EPR, it is best to output the EndPointReferenceType Object to the language-independent XML document. In the future, they will explain this standard to save EPR, maybe just a suggestion.
Perhaps it is a tool.
Specific practice, I will explain first.
.
When ePR is output, use org.globus.wsrf.Encoding.ObjectSerializer,
When reading EPR, use org.globus.wsrf.Encoding.ObjectDeselIz.
If you want to see the code, you can visit SourceForge.net, read the latest QueuingServiceClient.java of the GCSF project, Test Platform: Redhat 9, Globus Toolkit 3.9.3
