- #180 Headers not usable as environment variable. We discovered that variable expansion of headers did not cover environment variables.
- New Feature #160 Introduce Extraction Plugins. We have now introduced a new plugin mechanism so you can define how an object you are expecting should be deserialized. Please refer to the chapter on "Deserialization Plugins" in the README doc.
- New Feature #162 Deserializing Date Objects. We now allow the deserialization of Date objects. You can decide the formatting of the value. For more information please refer to Formatting Dates in the README doc.
- #159 Errors when deserializing Milti-Part Mime Object: We have included a couple of resilience features to better handle the deserialization of complex Objects. This includes:
- Nested scraping. We allow a nested scraping of objects.
- Ignoring calls that throw errors. We now log the error and continue with the next call.
- Ignoring methods returning objects that we do not have the rights to execute/access.
- New Environment Variables
- IBS.DESERIALIZATION.DEPTH.LIMIT : This value sets the maximum depth of the deserialization. By default, we go to a depth of 1.
- IBS.DESERIALIZATION.DATE.FORMAT : The format in which the date should be deserialized. By default, it is "NONE" meaning no date transformation is performed.
- IBS.PLUGINS.PACKAGE : The package path in which the IBS should search for the plugins you write. By default, we look in this package : "IBS.PLUGINS.PACKAGE"
- #176 ClassCastException when the second call argument is an array. We discovered a bug regarding arrays. Whenever the second argument was an array, we would get a ClassCastException.
- New Feature #3 Include an Assertion Feature. We have now included the possibility for users to define assertions. This allows you to clarify accepted results for the call you make with the IBS.
- New Feature #79 Allow or passing secrets in headers. You can now pass variables and secrets as headers.
- New Feature #110 Allow for Fileuploading and Multi-part requests. We can now upload a file and reference it in the request.
- #111 Allowing the passing of array and vararg arguments. Previously we were unable to execute methods accepting Arrays and varargs. This has now been corrected.
- #88 Logging action steps. We now log the steps we take during execution for better debugging.
- #48 Logging action steps. We now log the current class and method being executed.
- #71 Adding step name when throwing exceptions. When an exception happens, include the step in which it occurred.
- #72 Provide the stack trace of the root cause of the errors. With issue #9 we discovered that the stack trace should be that of the original cause.
- #78 Trimming error messages. We now trim the error messages.
- #80 Removing stack trace for certain errors. We removed the stack trace for errors, where the method or class cannot be found or accessed.
- #83 Adapting log files for production. We now limit the log files so not too much log data is stored. More details to be found in the Technical Doc.
- Moved the log level for the loading of the classes to 'trace' instead of 'debug'.
- We have now introduced a dedicated exception for when a public Method in a Java class with no scope definition. This created linkage errors.
- #61 Allowing Map/JSON return type. Until recently we were not able to correctly accept map and JSON Objects.
- #63 Fixed bug when return object has methd called get. Corrected bug related to classes that have a method called get. In these cases we have a 500 error. We have now added an error category which is internal.
- #9 Include error stack trace. The stack trace is part of the error object. We have decided not tolter, and simply add the error stadk trace.
- #64 Managing internal errors better. We now deal with ibs-internal error so that we can better debug them.
DEPRECATED due to false merge
- Disabled automatic mode as discovered some issues with the loading (Issue #55).
- #43 Introduce automatic loading of classes: Instead of selectively loading classes from designated packages, we now load all needed classes in the class loader.
- #34 java.lang.LinkageError: loader constraint violation: loader 'app' (instance of jdk.internal.loader.ClassLoaders: Discovered a problem with Linkage error when using the traditional class loader. We now load everything locally, this means that all static variables are stored in the context (Issue #43).
- We started reorganizing the errors, and have started doing a more predefined error management. For more info please refer to the Technical Documentation .
- #35 When calling a class with no modifiers we do not get enough information
- #37 Better error formatting We now end errors as a JSON data including errors and messages.
- #36 Make the /test endpoint return a JSON By sending the /test data as json we make it more legible.
- #38 Better information if the deployment port is already in use Whenever we are starting the bridgeService on a port that is already in use, we throw a IBSConfigurationException exception.
- Merged the document
./docs/Context.mdinto the./docs/Technical.mddocument.
This is the first version that is on the public github. Hence we have the issue numbers being reset. Old issue titles are marked in bold:
- Call Timeout Management: Introducing the timeout, mechanism. We have a global timeout, and a call session timeout. We also log the individual call durations in the return payload.
- Object Instance Management : We can now instantiate objects and call their instance methods.
- Integro Independance: We are now completely independant of integro as a library. For testing purposes we now use dedicated classes that are available in the module "bridgeService-data". This can be included in a deployment by setting
demo.project.mode=compile. - multi-module solution: Moved to a multi-module approach. This we can better manage and maintain the dependant test classes.
- Public GitHub: Migrated from the Adobe Enterprise artefactory to the public GitHub, adapted deployment scripts and devOps methods.
- Available JavaDoc: Made the javaDoc available.
- Java 11 Compatibility: Integro Bridge Service is now Java 11 compatible. From now on the standard builds are in Java 11. (Java 8 is also available, but is made on demand).
- Dynamically load all called classes: Previously, we were loading a preset set of packages for managing the static variable contexts in calls. We now automatically include the classes that are being called. This solves the following issues:
- Ensuring that the system value handler is included in the static paths: We were discovering that static variables are not automatically included in the static cpath context.
- Issue with Server=null when calling PushNotifications with IBS: We discovered that when the environment variables are in one context, and that the following java call isn't, we would not have access to those variables.
- Renamed Configuration class
com.adobe.campaign.tests.service.ConfigValueHandlertocom.adobe.campaign.tests.bridge.service.ConfigValueHandlerIBS. This is to avoid confligt with projects using the same design pattern. - Added Continuous Integration Scripts.
- Environment variables are always strings: Facing issues with integegers in environment variables not being picked up, we decided to force all environment variables as Strings.
- We now include two new Exceptions:
- IBSConfigurationException : thrown whenever the configuration we set (currently only for the setting of the environment variables) does not match an existing class/method.
- IBSRunTimeException : When for some reason the payload has issues non-related to JSON.
- We now include two new Exceptions:
- Implementation of the Injection model. IntegroBridgeService is added as a dependency in projects and can now be spawned in any environment.
- Move from an aggregator model to an insertion model. From now on IBS is put in the libraries that we want to interface.
- externalizing environment variables
- Updated the README to include clearer information about call chaining
- The classpath is no longer hard-coded
- introduced continuous integration
- Allow projects injecting the IBS to append their version number to the IBS test end point
- Make SSL params in main configurble
- First working version. Using Aggregator model, containing Integro-ACC