Should I use SimpleSubDeployerSupport?

[leifj]

I am working on a type of component which requires a new deployer. I am thinking about subclassing SimpleSubDeployerSupport and would like to know if this is a good idea or if the near-time development of jboss makes this a bad idea (for instance if the deployer architecture is scheduled for rewrite soon).

In short I want to know if (to the extent that this is at all possible) if I am wasting cycles imlementing stuff like this outside the core jboss team :-)

For reference my application is XMPP event-driven "agents" using XMPP publish-subscribe. The reason I can't use inbound JCA communication (I already have a JCA for outgoing XMPP) is that XMPP services are XMPP clients - incoming messaging is run over outgoing TCP connections - i.e the service is required to maintain connection to the messagebus instead of the other way around. Think of it as pull messaging if you will.

[adrian.brock]

We are not dropping the old deployer framework.

It just won't be able to take advantage of some of the features of the new framework,
when it is eventually written.

Using something like SimpleSubDeployerSupport frees you of the most of the
dependency on the deployment framework.

[adrian.brock]

e.g. I recently wrote the new Bean Deployer using SimpleSubDeployerSupport

[starksm64]

The SimpleSubDeployerSupport will continue to be supported as its used by 4.0.x implementations. If you want more assurance create a unit test that illustrates you deployers usage and submit it to jira as a patch so that it can be integrated into the testsuite.

http://jira.jboss.com/jira/browse/JBAS

The 5.0 codebase is potentially a different story.

[leifj]

Thanks for good and quick replies!