-
Notifications
You must be signed in to change notification settings - Fork 303
Added two batch job tests in the restaurant sample #442
Conversation
Can one of the admins verify this patch? |
import org.springframework.context.annotation.Bean; | ||
import org.springframework.context.annotation.Configuration; | ||
import org.springframework.context.annotation.DependsOn; | ||
import org.springframework.transaction.PlatformTransactionManager; | ||
|
||
/** | ||
* This class contains the configuration like jobLauncher,Jobrepository etc. | ||
* @author ssarmoka | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duplicated javadoc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please consolidate with class javadoc. This doc is currently connected to an import, which is obviously a mistake.
@maihacke can you have a look at this PR as you have been strongly involved into the batch design? |
btw @maybeec is it recommended to merge current changes of oasp4j/develop into PRs when they are outdated? This branch has some conflicts now that I could resolve with a merge. Is there a general best practice? |
For updating pull requests, there is basically just one rule: If you can resolve the merge without guessing what might be the right solution. Go ahead! Von: Simon Röger [email protected] btw @maybeechttps://github.com/maybeec is it recommended to merge current changes of oasp4j/develop into PRs when they are outdated? This branch has some conflicts now that I could resolve with a merge. Is there a general best practice? — Firma: Capgemini Deutschland GmbH Amtsgericht Berlin-Charlottenburg, HRB 98814 |
/** | ||
* {@inheritDoc} | ||
*/ | ||
@Override |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove unnecessary @inheritdoc javaDoc comments. They are simply not needed as @OverRide is sufficient for the IDE.
Thanks for the comments.
|
@Override | ||
public void postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory) throws BeansException { | ||
|
||
beanFactory.registerScope("step", new StepScope()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
muss dieser Scope wirklich so manuell registriert werden? Gibt es da keinen eleganteren Weg?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the two ways of ENUM-Mapping. I think both ways are eligible. It's more or less a matter of taste and I don't think we need standardize this in OASP. Just leave it as it is...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prinzipiell nein, man könnte den ganzen Stack an Einstellungen und Konfigurationen über @EnableBatchProcessing beziehen. Ich hab angenommen, wir machen das absichtlich alles manuell, um mehr Kontrolle zu haben. Oder wäre es im Zuge der Umstellung auf Spring Boot auch besser, alles über die Annotation zu laden?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull requests looks verý good overall. There are some minor issues/questions left. After "fixing" these, PR can be merged... |
Please stick to english language :) |
The two concerns regarding
are documented in the given issues. Other than these issues the only remaining point for this PR is the registering of the scope step. Imho the only other (maybe more elegant) option is to use Spring Boot's annotation @EnableBatchProcessing but this would change many of our configurations. Maybe someone can think of another solution for CustomBeanFactoryPostProcessor registered in |
@maihacke , As discussed , assigned it to you for the review . Thanks for your time. Just to keep you posted , this has to be merged onto develop-2.3.0 as this is the branch that is used for oasp4j 2.3.0 release. Thanks, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Questions were answered. No required changes since last review.
@maihacke , Thanks for your time for the review . As discussed , I will take care of the merging. |
This PR adds:
@maihacke can you review the changes?