In order to avoid confusion, I think it is important that we stopreferring to JAX-RPC deployments as "JSR-109 deployments". It's notreally correct since JSR-109 governs EE integration for both JAX-WS andJAX-RPC. Instead, we should just call them "JAX-RPC deployments"

Also, I think it is important that we make a clear distinction betweenJAX-WS and JSR-181. We should refer to the annotated endpoints that arein JBossWS 2.0.x as "JAX-WS endpoints", and only use the term "JSR-181endpoints" to refer to the old JAX-RPC based preview technology that wasin 1.0.x.

So these two changes leave us with the following deployment types

JAX-WS - 2.0.xJSR-181 - 1.0.x onlyJAX-RPC - 1.0.x and 2.0.x

This usage of terminology should be consistent in both our code anddocumentation.

As part of my work in JBCTS-414 and the eventual SPI, I have refactoredthe metadata builders. This also included renaming them to match thisterminology change. I also have split them into separate packages sothat each deployment type can eventually be pluggable.

As part of my work in JBCTS-414 and the eventual SPI, I have refactoredthe metadata builders. This also included renaming them to match thisterminology change. I also have split them into separate packages sothat each deployment type can eventually be pluggable.