On Mon, 17 Jul 2006 10:15:54 +0200, Ole Matzura <ole(a)eviware.com> wrote:
Hi all!
We have just released the first beta of soapui 1.6 (including our
initial jbossws wstools integration) and I am now finally writing a
specification for the "jbosside-soapui-plugin".. one issue that struck
me was the fact the jbossws is no longer tied to jboss (ie it can be run
in a standalone tomcat installation).. should our plugin support that
setup? How would that be affected by jbosside functionality (packaging,
deployment, etc..), do we need to provide this functionality "by
ourselves" our could the jbosside infrastructure still be used for
standalone jbossws-installations?
what are your thoughts?
I don't what the problem is ;)
Doesn't the soapui-thingy "just" allow for editing ws specific files
independent
of what target it is being deployed to ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss Inc
max.andersen(a)jboss.com