On Mar 4, 2009, at 11:50 AM, David Jencks wrote:
On Mar 4, 2009, at 8:39 AM, Joe Bohn wrote:
Forrest, Thanks for finding this problem and raising the issue.
IMO this is a critical issue that breaks backward compatibility.
I had validated that our 2.1.2 samples installed and worked in our
2.1.4 server image prior to this change. Since this change has
been made this is no longer true. I suspect this will also break
other component installations (such as directory) and perhaps user
created components.
We need another solution that support backward compatibility.
I guess we need to revert my attempt to fix the original problem.
Maybe we can change the ejb-webservice deployers to use two abstract
name queries that will pick up either the jetty or tomcat web
container. That would only prevent people from running both jetty
and tomcat at once if they have ejb web services.... maybe not a
serious limitation.
I'd agree that would not be a serious limitation.
--kevan
