Hi All,
Just wanted to give you an update on the Eclipse plugin.
In response to a couple of bugs logged in Jira (OPENEJB-869 and
OPENEJB-876) I've made a couple of changes around the server runtime.
Specifically, I've changed how deployment works - previously a deploy
simply built a jar file based on the output paths of a project and
copied it to the apps folder of the standalone server. This worked ok,
but caused problems with file locking on un-deploying and republishing.
Now we hold a cache of which projects have been deployed, and then once
the server has started, we use the WTP export feature to build the jar,
and then use the Deployer bean openejb-core to do the actual deployment.
I also corrected a bug where multiple server monitor threads were being
created when restarting the server. The server icon is now the pepper
instead of just a red square.
I've published my latest update site on my people page:
http://people.apache.org/~jgallimore/update-site
The feedback on these changes (via Jira) has been very positive. Many
thanks to Kaloyan Raev for taking the time to test and re-test the
plugin, and for logging the issues.
In terms of extending the plugin further, I was going to look at doing
the following:
* see if I can replace any usages of finder and create methods on Entity
beans with EJB 3 style EntityManager code
* add support for using websphere/weblogic descriptors instead of
openejb-jar.xml for generating annotations
* Karan suggested a drag-n-drop dependency injection idea, which I was
going to look at too.
Does anybody have any other thoughts or suggestions?
I was also thinking it might perhaps be a good idea to either close
OPENEJB-674 and open new issues for these tasks or to add subtasks to
OPENEJB-674 - anyone got any thoughts on this?
Cheers
Jon
