On Tuesday 19 July 2011, javaxmlsoapdev wrote: > I am trying to start introducing scala into existing Java application > that's being developed, slowly and at most appropriate places in the > code. Have a use case to copy one class' properties to another where > 2nd class properties are named differently. I am well aware of > reflection based APIs like dozer etc in Java but not a big fan of > those APIs. Any scala way to achieve this for Java classes? This is > purely in quest to introduce some scala in the Java app mainly for > it's conciseness and prettiness. > > Thanks,
This isn't a JVM languages thing, is it? Ask on the Scala-User mailing list / Google Group. Anyway... If the names are not the same, you're going to have to write code that captures the correspondence, and thus you have no real need for reflection. Why does the Scala side need to see different names for the Java members? Why do you want to transform the Java instances into disparate Scala counterparts? Why not let the Scala code use and act directly upon the Java instances? It's quite good at that. Randall Schulz -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com. To unsubscribe from this group, send email to jvm-languages+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
