[jboss-dev-forums] [Design of JBoss Web Services] - Re: JBossWS brings Metro/CXF but in what version?

[heiko.braun@jboss.com]

I would just regard the prefix as branding. As thomas said, it's a new era.
Therefore I would opt for jbossws-wsf-XYZ. WSF (web service framework) is something we included in the brand when we started the SPI. It's reflected in the package names as well.

 
  | * jbossws-wsf-native-2.0.3
  | * jbossws-wsf-metro-1.0.0
  | * jbossws-wsf-cxf-1.0.0
  | 

Changes to SPI, framework, etc would trigger new releases of each stack anyway, right? I am looking at this from a users point of view. The prefix versioning just confuses people. "Did they release a new metro version?" This is what I would ask myself. Regardless if that was causing changes to the SPI or the framework. If any fix requires changes to the SPI, all stacks need to update anyway. 

So I'd say we release by a rule of thumb:

- Any change to the SPI, framework requires an update to each stack
- At least each stack needs to be run through QA
- QA means a tagged framework version and thus an update to the stack (version.properties)

In this case I don't see the need for a confusing prefix versioning like 'jbossws-3.0-XYZ'. 

Does this make sense to you guys?

   

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

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