[convert] Use cases not currently covered

2004-03-22 Thread Legostaev, Andrei
Greetings All I have been corresponding with Stephen regarding some design decisions being made in [convert]. I'd like to make a couple of pugnacious declarations and hope that ensuing discussion generates good ideas and consensus. I'll first state my beliefs, then I'll try to justify them

Re: [convert] Use cases not currently covered

2004-03-22 Thread Matthew Sgarlata
of ConversionFactory and that the ConversionFactory interface should be simplified. I think this relates to point #2 of yours below... Matt - Original Message - From: Legostaev, Andrei [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 22, 2004 1:55 PM Subject: [convert] Use cases

Re: [convert] Use cases not currently covered

2004-03-22 Thread Ron Blaschke
LA 1) The actual conversion logic should be implemented in small chunks, LA inside the most primitive, bare code-container, interface : LA public interface Conversion { LA public Object convert(Object value) throws Exception; LA } I agree that the interface should be small, but I am not

RE: [convert] Use cases not currently covered

2004-03-22 Thread Legostaev, Andrei
LA public interface Conversion { LA public Object convert(Object value) throws Exception; LA } RB I am not too sure about the Exception. Throw-everything forces RB the caller to Catch-everything. Maybe a more specific Exception, RB like ConversionFailedException, is sufficient. Stephen