[04:43:36 EDT(-0400)] * Tuomaz (n=fredrik@kaffe.umdc.umu.se) has joined ##uportal
[09:41:24 EDT(-0400)] * jayshao (n=jayshao@jshao.rutgers.edu) has joined ##uportal
[09:46:15 EDT(-0400)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined ##uportal
[10:21:29 EDT(-0400)] * EricDalquist (n=EricDalq@dyn-0-104.uwnet.wisc.edu) has joined ##uportal
[10:40:26 EDT(-0400)] * EricDalquist (n=EricDalq@dyn-0-104.uwnet.wisc.edu) has joined ##uportal
[15:10:51 EDT(-0400)] <EricDalquist> hrm
[15:11:27 EDT(-0400)] <EricDalquist> so ... class A is responsible for crud type methods dealing with interface I
[15:12:00 EDT(-0400)] <EricDalquist> is it OK for class A to assume the impl of interface I on methods that pass I in as an argument?
[16:00:13 EDT(-0400)] <apetro_andreasde> of course not
[16:00:39 EDT(-0400)] <apetro_andreasde> unless A is going to be expicitly coupled to the implementation rather than to the I
[16:01:00 EDT(-0400)] <apetro_andreasde> but then it should be taking Impl as arguments rather than I if at all possible
[16:01:14 EDT(-0400)] <apetro_andreasde> maybe it's gotta take I as arguments because it implements interface I'
[16:01:41 EDT(-0400)] * esm (n=esm@asdf.dkc.jhu.edu) has joined ##uportal
[16:01:47 EDT(-0400)] <apetro_andreasde> but if you cannot imagine I having any implementation other than the one that you're using so that the DAO can CRUD it
[16:01:54 EDT(-0400)] <apetro_andreasde> then maybe I doesn't need to exist and you can just have the impl
[16:02:10 EDT(-0400)] <EricDalquist> hrm
[16:02:20 EDT(-0400)] <EricDalquist> so the more concrete example is
[16:02:38 EDT(-0400)] <esm> there is the question of how many implementations one would have in this concrete example
[16:04:06 EDT(-0400)] <EricDalquist> IPortletDefinitionRegistry has methods 'IPortletDefiniton getPortletDefinition(long)' and 'void storePortletDefinition(IPortletDefinition)'
[16:05:17 EDT(-0400)] <EricDalquist> the returned IPortletDefinition wraps a IPortletDefinitionTransfer
[16:06:22 EDT(-0400)] <EricDalquist> when storePortletDefinition is called
[16:08:06 EDT(-0400)] <EricDalquist> the registry needs to be able to provide a transfer object back to the dao
[16:12:11 EDT(-0400)] <EricDalquist> grr
[16:12:38 EDT(-0400)] <EricDalquist> as interesting as the dao/transfer/registry/domain architecture sounds
[16:12:48 EDT(-0400)] <EricDalquist> getting a design that works well has been a problem
[16:12:54 EDT(-0400)] <EricDalquist> getting the read side of it is easy
[16:13:00 EDT(-0400)] <EricDalquist> but persisting changing isn't
[16:14:00 EDT(-0400)] <apetro_andreasde> sure
[16:14:18 EDT(-0400)] <apetro_andreasde> is a viable approach to build something that works, and refactor towards more ideal interface-happy architecture later?
General
Content
Integrations