[jbossws-dev] [Design of JBoss Web Services] - Re: JBossWS Deployers Integration

[alessio.soldano@jboss.com]

"richard.opalka at jboss.com" wrote : "alessio.soldano at jboss.com" wrote : 
  |   | Basically, we had a abstraction to support AS4.2 deployment in a similar way to AS 5.x, now most of that additional abstraction is gone, why DA are still there? Can't we simply move each of them in a different deployer? (considering the WSDeploymentDeployer seems to me just something like a wrapper of the DAs)
  |   | 
  | Yes, DA abstraction is still there and will probably stay there ;)
  | There are two main reasons why we're wrapping JBossWS DAs:
  | 
  |  we can't replace DAs with Deployers, otherwise our stacks would be tightly coupled with AS internals. To separate all supported SOAP stacks from different AS versions we have AS IL (JBoss AS Integration Layer) that does that abstraction job.
OK... there's actually not much of that abstraction left, anyway I see your point of view of keeping the DA concept for generic deployment (see point below).
Btw, would it still be possible (if reasonable of course) for a non-ws deployer to be plugged in between two instances of WSDeploymentDeployer without touching anything of the current architecture?
Is the case Anil mentioned here before addressed by the current architecture? (just to be sure)

anonymous wrote : 
  |  we will need to implement Endpoint.publish() in near future (this will use DAs via DAManager - DAManager will be used as the replacement of deployers chain on Java client side)
  | 
  | 
OK, I agree on this.

anonymous wrote : 
  | IMHO the JBDEPLOY-201 title is self descriptive. Regarding that issue Ales Justin just wrote me:
  | 
  | Currently there is no rush for it.
  | Hence I don't see the point of cutting new release,
  | as I have already done them too many.
  | I rather wait and get any additional fixes in (e.g. recent 208, 209).
  | 
  | I'll at least try to port the changes to Branch_2_0 asap,
  | so you can easily run a 2.0.9-SNAPSHOT version to test your stuff. 
  | 
  | 
  | I just asked him to port the changes to JBDeploy Branch_2_0 branch so we can test the fix using 2.0.9-SNAPSHOT

Thanks for the update.

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

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