Luciano Resende wrote:
While reviewing contribution code and thinking about some test
scenarios, I
have the following questions and would like to get some thoughts.
1.What should be the default behavior when i re-deploy a contribution
to the
repository ? Should it replace the existing application, or an exception
should be thrown ?
To start simple, I think we could replace the existing contribution for now.
2.When you re-deploy a contribution, should it get a new
contributionId ? or
continue to use the same ?
Not sure... I noticed this ContributionID in the code but I'm not sure
what it represents and how it is used. Could you help us understand what
it is?
3.When deploying a folder contribution, should we support store this
contribution into the repository ?
Maybe, but working off the folder passed to the contribution service
seems more important to me initially. This is the typical scenario where
a developer works in a folder and wants to run off the artifacts
developed in that folder, without any heavy copying taking place.
4.In contributionService, do we really need to pass the InputStream
for the
contribution service ? would we have scenarios where we will not be
able to
access the contribution via it's url / uri ? I'd like to leave to the
contribution to decide really when it would be necessary to open the
streams
to probably have a better performance and use less resources.
An InputStream may be needed at some point, or may not :) I suggest to
add this variation when a concrete scenario that requires it comes up.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
