Extending RESTful web service resources in a JAVA-component-driven-architecture application
A system and method are disclosed for an application server having one or more web application archives and one or more endpoints, determining whether a functionality of one or more endpoints is to be changed, and responsive to the determination of whether an endpoint of the one or more endpoints is to be changed, determining a link to a functionality component located external to the one or more web application archive that is to replace the functionality of the endpoint, and causing the external functionality component to link to the endpoint.
1. A system, comprising:
an application server comprising a processor and a memory, and comprising one or more web application archive, each of the one or more web application archive comprises one or more endpoints, wherein a domain identifying a location of each of the one or more endpoints is omitted, a servlet and a mapping configuration layer, the application server configured to:
map the one or more endpoints to one or more functionality components;
determine, for each endpoint of the one or more endpoints, whether a functionality of the endpoint is to be changed;
responsive to the determination of whether an endpoint is to be changed, determine a link to a functionality component of the one or more functionality components located external to the one or more web application archive that is to replace the functionality of the endpoint, and cause the external functionality component to link to the endpoint, wherein the functionality component located external to the one or more web application archive provides functionality to the application server,
identify a functionality component which does not link to any of one or more existing endpoints;
receive a determination that the functionality of the functionality component which does not link to any of the one or more existing endpoints is to be included in at least one of the one or more web application archive;
create a new endpoint in the at least one of the one or more web application archive, wherein create the new endpoint comprises modification of a configuration file and the at least one of the one or more web application archive is unchanged; and
cause the functionality component which does not link to any of the one or more existing endpoints to link to the new endpoint.
2. The system of claim 1 , wherein the programming language of the external functionality component is a different programming language than the one or more web application archive.
3. The system of claim 2 , wherein the programming language of the external functionality component is native code.
4. The system of claim 1 , wherein an original implementation of an application executed by the application server in accordance with the one or more web application archive and one or more endpoints replaces a current implementation of the application when the configuration file is restored to its state in the original implementation.
5. The system of claim 4 , wherein the application server exposes at least one of the one or more endpoints as a representational state transfer (RESTful) web service.
6. A method, comprising:
identifying, by an application server comprising one or more web application archive, a servlet and a mapping configuration layer, an endpoint of the one or more web application archive, wherein a domain identifying a location of the endpoint is omitted;
mapping the endpoint to one or more functionality components;
determining, by the application server, whether a functionality of the endpoint is to be changed;
responsive to the determination of whether the endpoint is to be changed, determining, by the application server, a link to a functionality component of the one or more functionality components located external to the one or more web application archive that is to replace the functionality of the endpoint, and cause the external functionality component to link to the endpoint, wherein the functionality component located external to the one or more web application archive provides functionality to the application server,
identifying, by the application server, an endpoint wherein a functionality component which does not link to the endpoint;
receiving, by the application server, a determination that the functionality of the functionality component which does not link to the endpoint is to be included in at least one of the one or more web application archive;
creating, by the application server, a new endpoint in the at least one of the one or more web application archive, wherein creating the new endpoint comprises modification of a configuration file and the at least one of the one or more web application archive is unchanged; and
causing, by the application server, the functionality component which does not link to the endpoint to link to the new endpoint.
7. The method of claim 6 , wherein the programming language of the external functionality component is a different programming language than the one or more web application archive.
8. The method of claim 7 , wherein the programming language of the external functionality component is native code.
9. The method of claim 6 , further comprising:
replacing, by the application server, a current implementation of an application when the configuration file is restored to its state in an original implementation.
10. The method of claim 9 , further comprising:
exposing, by the application server, the endpoint as a representational state transfer (RESTful) web service.
11. A non-transitory computer-readable medium embodied with software, the software when executed configured to:
identify an endpoint of one or more endpoints of one or more web application archive, wherein each of the one or more web application archive comprises one or more endpoints, wherein a domain identifying a location of each of the one or more endpoints is omitted, a servlet and a mapping configuration layer;
map the one or more endpoints to one or more functionality components;
determine whether a functionality of the endpoint is to be changed;
responsive to the determination of whether the endpoint is to be changed, determine a link to a functionality component of the one or more functionality components located external to the one or more web application archive that is to replace the functionality of the endpoint, and cause the external functionality component to link to the endpoint, wherein the functionality component located external to the one or more web application archive provides functionality to the application server,
identify an endpoint wherein a functionality component which does not link to the endpoint;
receive a determination that the functionality of the functionality component which does not link to the endpoint is to be included in at least one of the one or more web application archive;
create a new endpoint in the at least one of the one or more web application archive, wherein create the new endpoint comprises a modification of a configuration file and the at least one of the one or more web application archive is unchanged; and
cause the functionality component which does not link to the endpoint to link to the new endpoint.
12. The non-transitory computer-readable medium of claim 11 , wherein the programming language of the external functionality component is a different programming language than the one or more web application archive.
13. The non-transitory computer-readable medium of claim 12 , wherein the programming language of the external functionality component is native code.
14. The non-transitory computer-readable medium of claim 7 , wherein the software when executed is further configured to:
expose the endpoint as a representational state transfer (RESTful) web service.