Friday, December 4, 2009

Playing with RAP

Last week I found some time to play around with Eclipse RAP, some first steps were easy to take. I then got eager and tried to run a bigger RCP application on RAP which worked out to not to work. It was that some things from the current RCP platform we use extensivly do not work on RAP (for e.g. StyledLabelProvider). I did not spent too much time on it, and it seems to be I good advice I read somewhere else, if you want to develop on RAP and RCP start with RAP and then port tp RCP.

I then started of with a prototype for a new app, that will possibly run on RAP next year and I really had some fun with it. I used the styling examples projects to do some styling on my app, integrated my own logo and some css. Was all really easy and I got a web app running in little time.

Tried to follow the instructions on deployment then, which turned out to be a little complicated. Tooling is missing some things there currently. Had to take a count of manual steps to finally get a war archive that I could sent to a friend for testing. Surely I missed to put my plugin.xml in which caused some headache as the deployed app showed all bundles in the osgi console but surely refused to work.

I like the idea of having the Eclipse concepts and the platform alongside for web app development. Our app will be running whith not too heavy load, so that common concern doesn't matter to me. I wonder if there are experiences with RAP applications under heavy load. I still have to figure out whats the best way to have a cross user application model (most of out data will be shared across the users). As I'm so used to it I guess I will go for hibernate, which will turn out be be interesting on where to place the EntityManager Sessions to get all out of Lazy loading inside the platform.

Jupyter Kernel for Java9