concept work in category java

This is an excerpt from Manning's book Spring Integration in Action.
A message is a unit of information that can be passed between different components, called message endpoints. Messages are typically sent after one endpoint is done with a bit of work, and they trigger another endpoint to do another bit of work. Messages can contain information in any format that’s convenient for the sending and receiving endpoints. For example, the message’s payload may be XML, a simple string, or a primary key referencing a record in a database. See figure 1.3.
Asynchronous communication offers better opportunities to organize the work on the service provider’s side. Requests aren’t processed immediately but left in an intermediate storage and from there are delivered to the service provider whenever it can handle them (see figure 2.5). This means the requests will never be lost, even if the service provider is temporarily down, and also that a pool of concurrent processes or threads can be used to handle multiple requests in parallel.

This is an excerpt from Manning's book The Well-Grounded Java Developer.
This makes syntactic sugar changes to a language easier to implement because they usually involve a relatively small amount of work, and only involve changes to the compiler (javac in the case of Java).
Designs of this type are very well-suited to being implemented using the classes found in java.util.concurrent. The package contains thread pools for execution (and a nice set of factory methods in the Executors class to create them) and queues for handing work off between pools. There are also concurrent data structures (for building shared caches and other use cases) and many other useful low-level tools.

This is an excerpt from Manning's book Griffon in Action.
That’s it! You can give yourself a pat on the back, because you’ve already done a lot of the work that would have taken you considerably longer in regular Java/Swing. The create-app command created the appropriate directory structure, the application, and even skeleton code that can be used to launch the application.
jxwithWorker(start: true) { work { // work, work, and more work } onDone { // we're done! } }