Commit Log
From VCGR Wiki
Krasimira Kapitanova (25 June, 2008, 6:56 PM Eastern)
I have just added the new genesis_dai and genesis_dair services. Most of the java files are just skeletons of the services. The service which is currently operational is the genesis_dair SQLAccessCombined. It can be used to send SQL queries to existing database tables. For every result of a query it creates an SQLDataResource which stores the result, has an EPR, a properties document and some additional data.
There is a new tool (dair-query) which can be used to send SQL queries to the SQLAccessCombined service.
Mark Morgan (9 June 2008, 4:45 PM Eastern)
I'm adding notes on some things that I have checked in recently and forgot to mention.
- Reworked the deployment stuff that we had. Now, there is a central place to go through in the code (called Deployment) which keeps track of deployment directories and sub directories under it. This is cleaner and more consistent and will help us do better installers.
- Moved some of the properties out of client-config.xml and server-config.xml and into web-container.properties and security.properties files. The reason for this was to seperate certain types of properties from others -- namely, to make it much easier to programmatically change and acquire certain high level properties like port number, and certificate files which will help in making better installers.
- Added a user-preferences database with the system. Users can set whether they prefer stack traces, or summaries printed when something goes bad. They can also indicate whether they generally prefer GUIs when available, or text based dialogs.
- I also created a complete widget system for doing dialogs that supports both text and windowing based dialog boxes. I retrofitted most of our tools to use this system.
- Finally, I completely re-worked the RNS code so that it was more consistent with the usages that users are expecting. This was also part of the effort to shrink our CallingContext information by taking out intermediate EPRs in calling context path. The biggest changes that programmers will see are:
- RNSPath now by default looks for exact string matches rather than pattern matches. However, there is an additional mechanism for doing either Regex, or file pattern matching.
- RNSPath now interacts with the RNS server by acquiring an exact item that a user wants to lookup, or the entire list.
Duane Merrill (18 December 2007, 9:40 AM Eastern)
Checked in changes to login command-line syntax. Here are the four ways that you'll generally be using the login command:
For obtaining a credential delegated from an identity within the Windows keystore
login --storetype=WIN [--validMillis=<valid milliseconds>]
For obtaining a credential delegated from an identity within a keystore file (where the URL protocol is empty or "file:" for a local keystore file or "rns:" for a keystore file in the grid directory service)
login [--storetype=<PKCS12|JKS>] [--password=<keystore-password>] [--alias] [--pattern=<certificate/token pattern>] [--validMillis=<valid milliseconds>] [<keystore URL>]
For obtaining a credential delegated from a WS-Trust identity provider in the grid directory service
login [--validMillis=<valid milliseconds>] [--username=<username> [--password=<password>] ] rns:<identity provider path>
For obtaining a username-token credential
login --username=<username> [--password=<password>]
Checked in changes to allow the creation of "identity provider resource". The root identity provider service for a given container is "/containers/<container>/Services/X509AuthnPortType". Like exports, you have to create your identity resources using such an identity provider service. There are two ways you'll generally be using the "idp" identity resource creation tool:
For creating a "MyProxy"-like service that is given a delegated token (e.g., for 180 days) from which you can retrieve further "cranked-down" delegations using the "issue" method
idp --storetype=<PKCS12|JKS|WIN> [--password=<keystore-password>] [--alias] [--pattern=<certificate/token pattern>] [--validMillis=<valid milliseconds>] [<keystore path>] <IDP service path> <new IDP name>
For creating new identity resources that can be logged-into using the "issue" method
idp <IDP service path> <new IDP name>
After using the IDP tool to create your new identity resource, you can use the chmod tool to add it into other acls
chmod / +w "/containers/<container>/Services/X509AuthnPortType/grads"
or to add permissions for its "issue" method (an X-execute operation)
chmod "/containers/<container>/Services/X509AuthnPortType/grads" +x --username=dgm4d --password=helloworld
Mark Morgan (8 November 2007, 9:40 AM Eastern)
I also checked in a change yesterday (forgot to note it) whereby an operation was added to the BESActivity port type. The inclusion of this operation makes it possible now to retrieve error information from activities that fail to run for some reason (failures in data staging, etc.). This change will require a complete rebuild of the system including re-genning the port types from the WSDL.
Krasimira Kapitanova (7 November 2007, 4:20 PM Eastern)
I added my Information Service to the SVN repository.
Files that were added: - a wsdl folder - a src/container folder named InformationService - a new tool named InfoSQueryTool
Files that were modified: - the configuration files in the deployments for both the client and the server - the classpath file - the build.xml file - the mappings.properties file
Mark Morgan (6 November 2007, 3:30 PM Eastern, Revision 190)
This is another commit. Notice that I have added the new commit (the later one chronographically) to the head of the list. Let's keep that order. Also, notice that I added the SVN revision number to the log. This is very useful when someone may need to look at SVN logs and what not. This number is printed out on the console every time you do an svn commit so it's easy to get. If you do the commit from eclipse, you simply have to bring up the console and switch to the SVN tab of it (contact me if you don't know how to do that). If you forgot to look when you committed, you can also get the revision number by issuing the svn info command. For example, I did just that and got the following output.
Path: . URL: svn://mamba.cs.virginia.edu:9002/GenesisII/trunk Repository Root: svn://mamba.cs.virginia.edu:9002 Repository UUID: 31b5fc62-7e36-0410-b1c6-c26cd53d3853 Revision: 186 Node Kind: directory Schedule: normal Last Changed Author: mmm2a Last Changed Rev: 186 Last Changed Date: 2007-11-02 16:44:13 -0400 (Fri, 02 Nov 2007)
From eclipse, this can be done by issuing the Show History command from the Team menu.
Mark Morgan (6 November 2007, 3:25 PM Eastern)
This isn't a true commit, but it shows an example of the format that I would like us to use for commits. Obviously the content will be different, but it would be nice if each commit had a header with the user and the date and time when the commit happened. Under that, it could have any information that seems necessary.
