abandoned effort to have MultipartFile property for file upload rather
than just a request parameter because Spring binding and required field
validation was not working -- probably need a PropertyEditor but putting
that off for now
a shell of a strategy for demo purposes
initial revision
continued development
mappingFile.name column
configure import repository / strategy
configuration fixes for bugs with supporting multiple repositories
import lists
1) eagerly fetch the mappingFile
2) list query for definition names
mappingFile.name column
show current selected mappingFile name
1) switch from definitionName to definitionId so can use core method to
retrieve importDefinition
2) go back to using fileUpload tag instead of making data file a model
property because Spring not binding to MultipartFile without a
PropertyEditor (and no time for that now)
importSetup definitionName ==> definitionId
not setting repository on strategy because direction of relationship is
from repository to strategy and the same strategy could be used by
multiple repositories, so do not tie a strategy to a given repository
(note: this was not being set anyway, so got an error when tried to use
it in default handlesFile method in LocalFileSystemRepositoryStrategy
but decided did not need the repository for handlesFile implementations)
not setting repository on strategy because direction of relationship is
from repository to strategy and the same strategy could be used by
multiple repositories, so do not tie a strategy to a given repository
(note: this was not being set anyway, so got an error when tried to use
it in default handlesFile method in LocalFileSystemRepositoryStrategy
but decided did not need the repository for handlesFile implementations)
initial revision
1) changed handlesFiles so it does return true for every file so that
when iterating thru strategies it will not handle a file that it should
not (now only handles files in the default repository)
added explicit saveFile and deleteFile methods because if the LavaFile
is a property of the command object, rather than the command object
itself (as it is in BaseFileComponentHandler) then the afterCreate,
afterDelete and afterUpdate methods will not be called when the command
object is added/updated/deleted
lots of changes to get the mappingFile property working in terms of
writing the file to the repository
initial development continuing