[
https://issues.apache.org/jira/browse/CHAIN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedikt Ritter updated CHAIN-17:
---------------------------------
Summary: Consider making lookup commands default to same chain (was:
[chain] Consider making lookup commands default to same chain)
> Consider making lookup commands default to same chain
> -----------------------------------------------------
>
> Key: CHAIN-17
> URL: https://issues.apache.org/jira/browse/CHAIN-17
> Project: Commons Chain
> Issue Type: Improvement
> Environment: Operating System: All
> Platform: All
> Reporter: Joe Germuska
> Priority: Minor
>
> I've just now started looking at some of the changes related to the
> CatalogFactory implementations. I find the need to specify a catalog in the
> lookup commands clumsy and counter-intuitive. It seems to me one should be
> able
> to assume that lookups would be relative to other commands -- specifically for
> the LookupCommand, but in struts-chain the ExceptionCatcher command would also
> benefit.
> Yes, you have the issue then of how one specifies that the command to be
> looked
> up is in the "default" catalog, but I suspect that in reality the annoyance of
> someone forgetting to specify the catalogName until there's an error will
> happen
> much more than the need to specify "look this up in an entirely different
> catalog and specifically the one-which-has-no-name" Perhaps a boolean
> property
> "defaultCatalog" or a reserved catalog name like DEFAULT_CATALOG ?
> I'd be happy to provide a patch, but first -- will people support this change
> or
> veto it?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
