Open311 Warwick (Exor) Integration

 ::Integration::Warwick subclasses ::Integration::Exor
 refactor request_class and new_request
 Exor service
 Warwickshire updates retrieval, with datetimes
 stubbing out of Oracle constants, for local testing

We also edit FMS's core PopulateServiceList routine to hide system
fields from FMS:

Bromley/Warwickshire send metadata in their services/FOO.xml
advising that you can pass, e.g. attributes[easting].

FMS by default shows all of these to the user to fill in, however
we don't *want* the user to supply these, rather they are added
by the cobrand.

Bromley had an exception for this (keyed by $body->areas->id).
We write this more generally for Warwickshire too, keying instead
by $body->name (as this is far less likely to be overridden for
installs using global or custom Mapit's)

1 files changed, 1 insertions, 3 deletions

diff --git a/t/open311/endpoint/Endpoint1.pm b/t/open311/endpoint/Endpoint1.pm
index 257a94b64..c4119075c 100644
--- a/t/open311/endpoint/Endpoint1.pm
+++ b/t/open311/endpoint/Endpoint1.pm
@@ -9,8 +9,6 @@ use t::open311::endpoint::ServiceType1;
 use Open311::Endpoint::Service::Attribute;
 use Open311::Endpoint::Service::Request;
 
-use constant request_class => 'Open311::Endpoint::Service::Request';
-
 sub services {
     return (
         t::open311::endpoint::ServiceType1->new(
@@ -76,7 +74,7 @@ sub services {
 sub post_service_request {
     my ($self, $service, $args) = @_;
 
-    my $request = $self->request_class->new(
+    my $request = $self->new_request(
 
         # NB: possible race condition between next_request_id and _add_request
         # (this is fine for synchronous test-cases)