Karan Malhi wrote:
I think OPENEJB-516 (https://issues.apache.org/jira/browse/OPENEJB-516)
can be closed, as the plugin will now add the javaee-api and openejb-client
JARs to the classpath of projects associated with its runtime - does anyone
have any thoughts on this?
I also think OPENEJB-525 (
https://issues.apache.org/jira/browse/OPENEJB-525) can be closed as the
plugin is now built with Maven.
Yes, these issues should be closed.
Done. I also closed OPENEJB-687 as its really a duplicate of OPENEJB-674.
Also, I think David just implemented the DependsOn functionality. What do
you think about generating a dependency graph in eclipse? i.e the plugin
could scrape through the EJB's / descriptors and generate this graph (which
could possibly also be modified).
I think this is cool idea - its certainly possible to detect which
classes have the @Singleton annotation and analyze their usages. As Dain
has pointed out, it would definitely be tricky if the singleton is
referred to in a method that is called by the Pre/PostConstruct method.
We could search for all usages of singletons and traverse the call
hierarchy and see if we end up at a Pre/Post construct method, although
I could imagine this being a pretty intensive operation. Do you have any
thoughts on how this would be invoked? I guess it wouldn't be via the
wizard we have for annotation generation from ejb-jar.xml we have at the
moment. I was thinking perhaps adding a builder which spots references
being added, and showing a warning with a code completion would be
pretty cool - don't know how much work would be involved though.
Jon
