DDevelopment & Design

GWT Designer for Eclipse 3.6 can cause project compile freeze

Lately I installed GWT Designer for Eclipse Helios (3.6). I wanted to check it’s features. They aren’t so cool I’ve expected but that’s other story. The problem was that suddenly my main GWT enabled project began to freeze during compilation.  The…Lately I installed GWT Designer for Eclipse Helios (3.6). I wanted to check it’s features. They aren’t so cool I’ve expected but that’s other story. The problem was that suddenly my main GWT enabled project began to freeze during compilation.  The…

Lately I installed GWT Designer for Eclipse Helios (3.6). I wanted to check it’s features. They aren’t so cool I’ve expected but that’s other story. The problem was that suddenly my main GWT enabled project began to freeze during compilation.  The project is maven enabled also.

So it freezed in about half of compilation. All other features of Eclipse worked well. Restarting Eclipse and Windows didn’t help anyway.
After about an hour of investigating I’ve found that GWT Designer caused this. After removing it all came back to order.

Ofcourse I suspect that something is wrong with my Eclipse for example I have too many bizzarre plugins installed but if I could have such problems you could have them too. So be warned :-)

— Previous article

Spring Security by example: securing methods

Next article —

Testing ServiceMix 4.3 services with PaxExam

You May Also Like
DDevelopment & Design

Distributed scans with HBase

HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?