B
Ben Jessel
I have an idea for a tool, but I thought I would just subject it you
all to see whether it is viable, if indeed useful.
When you create an EJB, you have to be quite careful what classses are
actually in your EJB; you don't want servlet or IO classes. You also
don't want to bloat your jars with pattern matching eg, "oh hell just
include everything in com/myproject/*/*/*". Conversely, you do want to
make sure that you include the EJB classes and any dependent classes
that don't exist in libraries in your EJB's lib sub-tree.
This can be trial and error - you can get many iterations of
ClassNotFoundException before you can be sure that you have included
everything.
I'm interested in creating an eclipse plug-in, which will generate ant
pattern sets for including all classes that do not exist in libraries
within your EJB tree, but are required ( i.e are a dependency on your
initial EJB ).
What do you think?
all to see whether it is viable, if indeed useful.
When you create an EJB, you have to be quite careful what classses are
actually in your EJB; you don't want servlet or IO classes. You also
don't want to bloat your jars with pattern matching eg, "oh hell just
include everything in com/myproject/*/*/*". Conversely, you do want to
make sure that you include the EJB classes and any dependent classes
that don't exist in libraries in your EJB's lib sub-tree.
This can be trial and error - you can get many iterations of
ClassNotFoundException before you can be sure that you have included
everything.
I'm interested in creating an eclipse plug-in, which will generate ant
pattern sets for including all classes that do not exist in libraries
within your EJB tree, but are required ( i.e are a dependency on your
initial EJB ).
What do you think?