[PATCH] new constructor for Service

[Tim Stephenson <ti...@thestephensons.me.uk>]

Hi

I experienced a problem in my configuration of a dynamic call to a service
where neither the service nor the transport had been pre-registered.

My problem was that I could not configure the service with my modified
engine config AND give the service a QName as the constructors do not allow
both and there are not the right setters to do it after instantiation.
Despite being able to set the engine configuration you cannot change the
internally used engine after construction.

My solution is to add extra constuctor (patch attached):

    Service(EngineConfiguration config, QName serviceName)

does this seem reasonable or have i missed something?

Tim

Re: [PATCH] new constructor for Service

[Steve Loughran <st...@iseran.com>]

Tim Stephenson wrote:
> Hi
> 
> I experienced a problem in my configuration of a dynamic call to a service
> where neither the service nor the transport had been pre-registered.
> 
> My problem was that I could not configure the service with my modified
> engine config AND give the service a QName as the constructors do not allow
> both and there are not the right setters to do it after instantiation.
> Despite being able to set the engine configuration you cannot change the
> internally used engine after construction.
> 
> My solution is to add extra constuctor (patch attached):
> 
>     Service(EngineConfiguration config, QName serviceName)
> 
> does this seem reasonable or have i missed something?
> 
> Tim

seems reasonable. A test would be good,

If you open a bugzilla report and attach this we wont forget about it.

-steve