On Wed, 29 Dec 2004 08:51:54 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote: > [snip] > * Now that we're moving around all these catalog/command pairs, I'm > starting to wonder if we wouldn't like to have a standard > representation of the pair in a single string. This may even belong > in the chain-package proper, but it seems so fundamental that it > would be very useful. I'm thinking split a command on ":" and if > there is text preceding the colon, treat that as a catalog name. We > could discuss whether we want to continue to truck around with double > parameters where we have them now (the controller config) or will > soon (ActionConfig, maybe ForwardConfig.) These parameters are also > some place where we might like to use the wildcard substitution > values, which is something I'll have to look at more closely, as I > haven't really started using that yet.
This is definitely an interesting notion, and probably does belong in Commons Chain itself. To avoid any backwards compatibility issues, it might be easiest to add a getCommand() method to CatalogFactory that does this lookup (that kind of method doesn't really fit into a class named CatalogFactory very well ... but its at the correct architectural level). Regarding syntax, I like the ':' idea, but have only one reservation -- what if we later on wanted to implement some sort of URL-ish interpretation where the prefix was treated as an access scheme of some sort (like "http:" or "ftp:" in a typical URL), and a string like "foo:bar:baz" would mean "use access method 'foo' to access catalog 'bar', then load command 'baz'. Perhaps we should reserve for future use any string that has more than one ':' in it. > Joe Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
