On 12/02/2013 21:39, Danny Coward wrote:
> Hi folks,
>
> As promised, here is a cleanup of the configuration APIs. For
> background, please take a look at the email I sent last week "Reworking
> Configuration/Deployment APIs". In sum, programmatic deployment was very
> heavyweight (almost unusable), and there was too much scope for altering
> configuration at the wrong time.
>
> This proposal addresses those two issues by tweaking the
> ServerApplicationConfiguration programmatic endpoint deployment, and
> refactoring the *Configuration classes so that the configuration data is
> immutable, while the configuration behaviors remain overridable.
>
> Once we've cleaned this up, we can move quickly on to some of the other
> requests and clarifications on this bit of the API.
>
> To summarize the changes in this proposal:-
Danny,
I might be missing something but is there a way to deploy an endpoint
programmatically on the server side without any scanning taking place?
The use case I'm thinking of is a large application with lots of JARs
that knows exactly which endpoints need to be deployed and does not want
to incur the start-up delay that scanning requires.
Mark