[jbossws-dev] [Design of JBoss Web Services] - Re: [Productivity] Level 1 - Start from scratch

[max.andersen@jboss.com]

anonymous wrote : 
  | 1) The only WS tooling we have right now in RHDS is what comes with Eclipse WTP (and that is mainly axis biased)
  | 
  | 2) We *want* to get SoapUI back into the JBossTools build again - once when we get over the release hurdle of JBossTools/RHDS GA this will be a priority 
OK, these are 2 important things, thanks for stating them clearly.
In particular I also think it will be really good to have the SoapUI plugin back in the build again; I expect this integration to give JBossTools the same functions RHDS has from the WTP Eclipse, but based on JBossWS instead of Axis.


SoapUI and the Eclipse WTP integration are not integrated afaik. They have different purposes in life.

The bad news is that soapui is not going to continue supporting the jbossws specific parts of their tooling anymore - This might not be a big issue if JBossWS are going to change some of their tool/stack....is there any status/updates on that ? (I haven't followed it closely - I just heard it was on the table of upcoming changes)

anonymous wrote : 
  | 3) Be aware that just because something is in JBoss Tools does not mean it will show up in RHDS 
Does this simply means that things from JBossTools are not automatically coded into RHDS too, but they require additional work and this depends on strategic decisions about RHDS features, or I am missing something else?


RHDS goal is to match what is in the JBoss EAP platform and related products. That can result in things being excluded; also if something in jbosstools is deemed not mature enough for full support we will exclude it or simply disable it by default in RHDS and giving the option for theuser to enable it (with the notice it is not supported)

But the general rule is that JBossTools has all the new things and RHDS will follow that as closely as possible.

anonymous wrote : 
  | 5) Providing Ant or Maven kind of samples is good - neither of these exclude good JBoss Tools support as long as they are done correctly
  | 
  | 6) We/you shouldn't just go out and create an isolated WS-way of creating sample/projects - look into how the eclipse best support it...just using Eclipse as an glorified text editor to calling ant isn't really adding value ;)
I agree with you, Ant based samples and JBoss Tools / Eclipse support do not exclude each other and I believe providing both is the right things to do. In particular on point 6, I think I get the overall idea that is, of course, let's leverage what Eclipse is beyond a powerful text editor to provide ws added value. May be we might go a bit further into details on this in future..


yup.

anonymous wrote : 7) We need someone who knows about WS to build proper WS support into tooling....preferably someone who likes to do both WS and write plugins ;)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104228#4104228

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104228