Accepted for Google Summer of Code 2006!
Congratulations! This email is being sent to inform you that your application was accepted to take part in the Summer of Code.
My project: “Text Viewer and Editor needs to support word wrap” for eclipse.
I invite you to be my reader - especially if you know or want to know about eclipse platform inner-life!
Are you a SOC-developer working with eclipse? Please contact me if interested in knowledge-sharing!
My tiny diary is going to be especially useful for those who have never written anything FOR eclipse platform (not IN). As this is my first such, you can learn a lot and leave mistakes for me :)
Current progress is posted within 24 hours - stay tuned!
PS. I added all known Google Summer of Code (SOC 2006) accepted developers blogs to my blogroll for easy reference. Mail me if you’ve been left out or would like to be called with another name in this link-list.
Congratulations to everyone@SOC and have fun!
junit rollback after transaction commit
AbstractTransactionalDataSourceSpringContextTests (from springframework spring-mock.jar) is used to provide atomic junit-tests that won’t affect database state. This kind of isolation is achieved by running each test in a transaction that is rolled back after each test-run.
The problem might start when you are using AbstractTransactionalDataSourceSpringContextTests with multiple sessions committing transactions (and commit cannot be rolled back, as you know). For this I propose a solution where you could turn off all commits but keep rollback functionality (of course only in junit test-environment, NOT in production).
Be aware that this solution has at least one weak spot:multiple connections can’t read data if commits are not actually executed. But you should try to avoid multiple-connections in your junit-tests anyway.
Are there any other problems? Let me know :)
Following example is providing rollback-only transaction support for hibernate:
If using spring, put following into SessionFactory hibernateProperties:
hibernate.transaction.factory_class=com.ahtik.RollbackTransactionFactory
and then have following classes in your classpath:
Lazy-init variables are not always safe
Have you ever used following to lazy-initialize your variable?
If you have then don’t.
Just to remind or introduce, it looks OK but it isn’t - this is a pretty serious bug you can easily make.
And it’s called Double-Checked Locking.
Very good and easy-to-understand explanation is here
Be ready for artistic process
There is a good read from Seth Godin about processes and why you don’t like them. He has his point.
Worth reading because he’s a cool man. I know, I’ve experienced this.
Fixing Eclipse Mylar jira integration
Be aware that when adding new jira source to Mylar with HTTPS protocol then you MIGHT get error saying host not found or wrong username&password.
The reason for this could be missing certificate in your trusted keystore.
Here’s how to fix it:
- Run: openssl s_client -connect your.secured.host.com:https
- Copy-paste certificate from previous output to text-file (for example /tmp/key2trust.pem).
Be sure to include BEGIN and END CERTIFICATE rows!! - Run: keytool -import -alias your.secured.host.com -keystore
/home/ahtik/.eclipsekeystore -file /tmp/key2trust.pem - Edit eclipse.ini in eclipse home dir to have -Djavax.net.ssl.trustStore=/home/ahtik/.eclipsekeystore
- Start Eclipse and be sure to run with Java 5!
- Let me now if it didn’t help.
