Enthuware

Hi,
Could you give an explanation to
Api.bloggerservice should be defined in serviceapi module
, please?

From the two lines in the definition of abc.blogger module :
requires serviceapi; <----- This means api.BloggerService is in serviceapi module
provides api.BloggerService with abc.SimpleBlogger; <---- This means abc.SimpleBlogger implements api.BloggerService.

but why can´t SimpleBlogger be in another module?
Is it because it would need another requires statement?

sir_Anduin@yahoo.de wrote: ↑

Wed Sep 04, 2019 11:44 pm

but why can´t SimpleBlogger be in another module?
Is it because it would need another requires statement?

Correct. The existing requires statement is "requires serviceapi;".

abc.blogger module should be on --module-path while executing author module but is not required while compiling.

In my view, it is not necessary. We can run author module without abc.blogger module. In this case, ServiceLoader returns nothing, but it is not an error.

That's why the problem statement says "should" and not "must". From the problem statement, it is clear that the idea is to be able to use the abc.blogger module.

Sorry But how can "author module" use api.BloggerService if there is no "requires abc.blogger" in module-info? (and also exports statement in module abc.blogger module-info)

The author module already has "requires serviceapi;"
and that is why option 3 "api.BloggerService should be defined in serviceapi module." is a correct option.

Yes, sorry I expressed my question wrongly somehow))

Real question was - why do author module even need abc.blogger module while executing?
It can be on module path, but there will be no use of it for author right ?

Well, the serviceapi module only contains the service interface. No implementation. It is the abc.blogger module that contains the implementation. Observe the line "provides api.BloggerService with abc.SimpleBlogger;" in abc.blogger's module info.
When you run the author module, you need abc.blogger module on the path, so that an implementation for the BloggerService can be availed by the classes of the author module.

Hi Admin,

Could you please explain how to determine which modules are needed for compilation vs. executing the application?

The process is same for regular packages/classes. If you are directly using a class name in your code (for example, for a variable type or in extends/implements/throw clause and so on), the compiler will need to read that class and so that is a compile time dependency. If a class is loaded only at run time without getting referenced directly in code, then it is a runtime dependency. For example, you do Class.forName("a.b.c.MyClass"), here MyClass is not being referenced directly in the code (as far as the compiler is concerned, "a.b.c.MyClass" is just a string. But the forName method will try to load this class at runtime. So, this class will be required only at runtime.

Modules also work similarly. If you have a requires clause that refers to a module then you will need that module at compile time. Otherwise, only at runtime.

For complete details, you may go through this document: https://openjdk.org/jeps/261

This seems different from the Boyarsky book.

abc.blogger module is the provider of the service. Agreed.
From the explanation on the last option, are you saying that author is a consumer?
From Boyarsky's book, it would be a service locator.
Java 17. page 682. Creating a Service Locator Consumer Perhaps I misunderstood?

The author module says it "uses" BloggerService. So it is a consumer of that service. Where is the confusion?
BloggerService does not depend on author module so abc.blogger module doesn't need the author module. That is why the last option is wrong.

Service locators are higher level abstractions, which an application may or may not use. Modules have nothing to do with it.

admin wrote: ↑

Mon Apr 22, 2024 11:23 pm

The author module says it "uses" BloggerService. So it is a consumer of that service. Where is the confusion?
BloggerService does not depend on author module so abc.blogger module doesn't need the author module. That is why the last option is wrong.

Service locators are higher level abstractions, which an application may or may not use. Modules have nothing to do with it.

According to Boyarsky's book, the Consumer only has "requires", the Service Locator has "uses". author would be a ServiceLocator, according to the book.

You need to check with the author of the book. As explained above, the modules functionality doesn't know or care about service locator or any other design pattern.

You need to check with the author of the book.