[jbosside-dev] regarding jbossws / wstools / soapui integration

[Ole Matzura]

thanks for your replies Max, I've added some more comments below and 
await comments from the others..

regards!

/Ole

Max Rydahl Andersen skrev:
>
>> since the 2 scenarios for running jbossws differ in terms of 
>> deployment and available functionality, we need to decide how we 
>> handle that difference.. consider the situation when a developer runs 
>> jbossws standalone;
>>
>> 1) there is no "JBoss Server" to deploy to..
>>   - do we need to create a new "server plugin" in wtp for this setup 
>> or can we use the existing Tomcat Server?
>
> Don't know ;) Rob ?
>
>>   - will the deployment-features in jbosside still be usable for 
>> another server type?
>
sorry.. here I also meant the "packaging-stuff" that marshall is working 
on..
> We use WTP, so hopefully yes (to a certain degree ;)
>
>> 2) there is no support for remaining JBoss functionality (EJBs, etc..)
>>   - should related features in the jbosside be disabled / adapted?
>
> Why disabled ?
> Adapted ? I don't think our ejb stuff is tied hardly to jboss (only 
> our own WTP plugin is jboss specific)
>
>> should jbosside even support this setup?
>
> Our priority is of course that it works with JBoss.
> After that deployment of WS to Websphere and weblogic would be 
> interesting.
>
>> or should we create a standalone "jbossws-eclipse-plugin" that is 
>> independant of jboss/jbosside?
>
> I don't see the need ;)
I do, it would be great to be able to just use the jbossws stack without 
being required to use either jboss or jbosside.. (that's a personal note 
;-)
>
>> There is maybe also a "strategic" aspect.. does jboss want to push 
>> jbossws as a standalone ws-stack (as for example axis, xfire, etc..) 
>> or is this more a "sidekick" that we can initially "ignore" in 
>> jbosside and our plugin?
>
> I would say ignore for now unless it is trivial to create some initial 
> support for it.
>
> /max
>
>> Max Rydahl Andersen skrev:
>>> On Mon, 17 Jul 2006 10:15:54 +0200, Ole Matzura <ole at 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 at hibernate.org
>>> http://hibernate.org
>>>
>>> JBoss Inc
>>> max.andersen at jboss.com
>>>
>>>
>>
>>
>> _______________________________________________
>> jbosside-dev mailing list
>> jbosside-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosside-dev
>
>
>
> ----
> Max Rydahl Andersen
> callto://max.rydahl.andersen
>
> Hibernate
> max at hibernate.org
> http://hibernate.org
>
> JBoss Inc
> max.andersen at jboss.com
>
>