Re: [morph-developer] SimpleLanguageBeanReflector

[Matt B. <gud...@ya...>]

--- Matt Sgarlata
<Mat...@wh...> wrote:

> 
> > One thing that might work here is to implement a
> > Spring 2.0 XML schema, but just use nested text
> (of
> > the format I outlined) in a <morph:something>
> element.
> >  :)  Have your cake and eat it too.
> >   
> Excellent idea.
> 
> I've been thinking more about the
> SimpleLanguageBeanReflector and I am 
> still concerned that we could be introducing
> something dangerous into 
> the API.  Is there a reason you can't use the
> Language API directly to 
> implement what you are working on?
> 
> This would also free you from the depending on a
> concrete implementation 
> of the Language interface...


"What I am working on" = basically a deep
PropertyNameMappingCopier .  IMO, Languages depend
mostly on Reflectors rather than Transformers so a
Transformer that uses a Language rather than a
Reflector is possibly a positive thing.  And as for
depending explicitly on SimpleLanguage, I am
defenseless on that front.  My approach here was to
reduce code duplication--"a deep property mapping
copier is similar to a shallow one"--but I will weigh
my options here and inform.

-Matt B

> 
> Matt
> 
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
> the chance to share your
> opinions on IT & business topics through brief
> surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> morph-developer mailing list
> mor...@li...
>
https://lists.sourceforge.net/lists/listinfo/morph-developer
> 




 
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265