I am currently reworking this code to integrate it with JBossTS and XTS. The current plan is to have it available in JBossTS 4.15 and from there to eventually include it as a supported product in EAP 6.0.
would'nt it be a better solution to implement a managed client
webservice as with a conector mechanism.
I think i would be an advantage to get my ressource out
of a pool of connection. Beside it would be preferable, to
have watermarks, in oder to limit the use of connections.
Last not least the configuration is a task, that needs to
be acomplished. Timeout and overwritten target URL
need to be managed, cause nobody wants to use the
default target given by a wsdl file.
Any overridden parametes should be stored in a datasource-file,
that should stay, regardless iff the aplication has been undeployed
or broght back into business.
Maybe we can provide a sort of generic connector, that
gets a wsdl a dynymic template pater, in order to generate
the filter files while deploying the app.
I think a