Community
Participate
Working Groups
The subject pretty much says it all but does org.apache.axis really need org.eclipse.tomcat? This drags in a complete appserver into our batch tool infrastructure making it more heavyweight than necessary. Jeffrey speculated that this dependency is to resolve servlet.jar. Isn't there a better way to do this in WTP?
I'll see what we can do. At present, yes, Axis needs Tomcat as a provider of servlet.jar. We tried including our own copy of servlet.jar but all sorts of legal bells started ringing, so we backed off. Is this really a "major" issue?
Chris, It's major in that we're trying to remove bloat from our batch headless product and I'm forced to look into questionable dependencies that get dragged in.
FYI ... we had some similar requirement in JSP/Taglib function. In our case, it was isolated enough we could easily list the tomcat plugin as "optional", and if it wasn't there, we just didn't do that part of the function (it is for content assist, validation). I believe we do check for a "class not found" sort of exception, and just "do nothing" if that function should ever be accidently executed without the plugin in the stack (would not happen normally, just if someone was "messing around" with plugins). If you are really using tomcat to launch a web app, that should be possible for you as well .. of course, if you are using it for some intricate function, could take a lot of work. Again .. just FYI.
Via bug 136954, org.apache.tomcat has been removed from org.apache.axis. We don't suspect any fallout from this (specifically wrt. the emitters running within Eclipse), but still have to verify this.
please verify all is is well in RC1.
FYI. I've tested the Axis emitters in the WTP 1.5RC1 200604191317 build. The smoke tests are running smoothly as before.
As we are trying to close down WTP 1.5, please get the latest WTP 1.5 driver to verify the bug and reopen if the problem had not been fixed. If this defect is not verified/reopened by end of day 06/16, I'll attempt to verify the defect by reproducing the problem as described in the defect. However, since you know your scenario best, it would be more appropriate if you verify the fix.
Closed.
