Why not use the plugins portlet in the admin console? From the admin
console in tomcat6-jee5 I was able to stop the axis components and
then install the cxf and cxf-deployer plugins from the online
Geronimo plugin repository all within about a minute.
Best wishes,
Paul
On Nov 2, 2007,
On Nov 2, 2007, at 1:32 PM, David Jencks wrote:
On Nov 2, 2007, at 10:14 AM, Paul McMahan wrote:
Why not use the plugins portlet in the admin console? From the
admin console in tomcat6-jee5 I was able to stop the axis
components and then install the cxf and cxf-deployer plugins from
the
On Nov 2, 2007, at 10:14 AM, Paul McMahan wrote:
Why not use the plugins portlet in the admin console? From the
admin console in tomcat6-jee5 I was able to stop the axis
components and then install the cxf and cxf-deployer plugins from
the online Geronimo plugin repository all within
I made the plugin system support the condition expressions we've been
using to select a web service container but I can't see how to make
it work usefully so I wonder if we need a new approach.
Previously the conditions for axis2 and cxf we different in the jetty
and tomcat servers, so cxf
I also like 2, 3, and 4. But with a twist, setting up server
configuration 'templates' and allowing users to do the same. Then
allowing the user/administrator to change which template their server
should morph to.
We would supply templates for all of our default builds (essentially a
copy
