Now we can parse a big file containing multiple types of objects. It is
also supported to include files by using the <IncludeFile file="" />
element.
Including tests
Performing a Service is as simple as this:
GreetingService greetingService = new GreetingService();
GreetingArgument greetingArgument = new GreetingArgument();
greetingArgument.name = "Robert";
GreetingResult greetingResult = serviceHandler.
doService(null, greetingService, greetingArgument);
assertThat(greetingResult.getGreeting(),
containsString("Hello Robert. Nice to meet you!"));
So that components/observers can be notified of changes to the model,
the completion of a TX now triggers an ObserverHandler update of the
modified objects
This allows reflecting on actual changes performed by the transaction if
this is needed by the caller. One use case would be to perform observer
updates after a transaction was completed.
This allows reflecting on actual changes performed by the transaction if
this is needed by the caller. One use case would be to perform observer
updates after a transaction was completed.
The container how sets its own state once it has changed the state of
the components. Now the DefaultStrolchPrivilegeHandler checks that the
container has started before allowing any methods to be called.
This might still be too restrictive in that when the container is
stopped, that then an admin can not log in and perform any actions, but
this can then be changed when needed.
Also renamed it from RMI to FileServer/Client. There is no reason this
has to be RMI bound, as a client must simply implement FileClient where
the upload/download methods can be implemented to be done over any kind
of remote connection
- We now have a container which can be configured with components, can
be setup, started, stopped and destroye.
- Missing is still the implementation of the dependencies.
Now added method to add single element, or get parent. Also removed
restriction for element to have at least three elements. Now one element
is sufficient.
Robert von Burg