Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to treat beans split up into interface and implementation #181

Closed
hoijui opened this issue Dec 24, 2017 · 6 comments
Closed

How to treat beans split up into interface and implementation #181

hoijui opened this issue Dec 24, 2017 · 6 comments

Comments

@hoijui
Copy link

hoijui commented Dec 24, 2017

So i have two OSGi bundles, one with interfaces, one with implementations.
Lets say, i have public interface Person in one bundle, and public class PersonImpl implements Person in th other.
I would like to generate getters, setters and addPropertyChangeListener() in the interface, and the implementations of those in the class.
Is this possible with JodaBeans, and if so, how?
If not, can you recommend some other library or tool that can do this?
...or am i not seeing some fundamental problem about this idea here?

@jodastephen
Copy link
Member

This is not possible with Joda-Beans. It would take a lot of work to add such a separation, and I'm not likely to do it. The Immutables project may be what you want.

@hoijui
Copy link
Author

hoijui commented Jan 8, 2018

ahh perfect, thanks you stephen! :-)
in the meantime, i have decided to learn scala instead. i am not sure if it solves my problem well, but so far it looks good, and it seems like a language i really would like to get to know anyway.
... but indeed, immutables seems like a good thing for my use-case, should i go back to java with this after all.

@jodastephen
Copy link
Member

My views on Scala are well known, if you are looking for an alternative language, Kotlin is a far better choice.

@hoijui
Copy link
Author

hoijui commented Jan 12, 2018 via email

@jodastephen
Copy link
Member

Fantom is very interesting due to its weak type system. Kotlin is likely to be a relatively major language due to the Android ecosystem, so is a much better choice to learn for practical industry usage as of now.

@hoijui
Copy link
Author

hoijui commented Jan 15, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants