What is a “behavior rich object” and why would it be advantageous?
I am referring to the article Mocks aren’t Stubs by Martin Fowler. When naming cases when he think “mockist” TDD will be advantageous, he said
How to handle committed and merged code that has no tests?
When developing an application in a team not everyone on this team will be equally good developers. Some will be skilled in some things and some in others and some not at all.
Is there an established pattern for associating a database entry with a Java class that executes on that data?
I have a behavior tree with different leaf nodes that execute tasks. When building out the tree relationship in the database I need an association between the leaf node entry and the Java class that will actually perform the task execution. I’ve seen some examples that store the canonical name of the Java task class with the leaf node data, and then instantiate the class at runtime using reflection. I’m not sure I like that approach, but I’m looking for all of the alternatives so I can make an informed decision.
Is there an established pattern for associating a database entry with a Java class that executes on that data?
I have a behavior tree with different leaf nodes that execute tasks. When building out the tree relationship in the database I need an association between the leaf node entry and the Java class that will actually perform the task execution. I’ve seen some examples that store the canonical name of the Java task class with the leaf node data, and then instantiate the class at runtime using reflection. I’m not sure I like that approach, but I’m looking for all of the alternatives so I can make an informed decision.
Is there an established pattern for associating a database entry with a Java class that executes on that data?
I have a behavior tree with different leaf nodes that execute tasks. When building out the tree relationship in the database I need an association between the leaf node entry and the Java class that will actually perform the task execution. I’ve seen some examples that store the canonical name of the Java task class with the leaf node data, and then instantiate the class at runtime using reflection. I’m not sure I like that approach, but I’m looking for all of the alternatives so I can make an informed decision.
Is there an established pattern for associating a database entry with a Java class that executes on that data?
I have a behavior tree with different leaf nodes that execute tasks. When building out the tree relationship in the database I need an association between the leaf node entry and the Java class that will actually perform the task execution. I’ve seen some examples that store the canonical name of the Java task class with the leaf node data, and then instantiate the class at runtime using reflection. I’m not sure I like that approach, but I’m looking for all of the alternatives so I can make an informed decision.
Is there an established pattern for associating a database entry with a Java class that executes on that data?
I have a behavior tree with different leaf nodes that execute tasks. When building out the tree relationship in the database I need an association between the leaf node entry and the Java class that will actually perform the task execution. I’ve seen some examples that store the canonical name of the Java task class with the leaf node data, and then instantiate the class at runtime using reflection. I’m not sure I like that approach, but I’m looking for all of the alternatives so I can make an informed decision.