When you make a droppable jar you usually only have one Module class
specified in the jar file. If you need more, you annotate the specified
module to point it to other submodules. So you should probably be able to
do the same thing for your AppModule to point it to other submodules as
well. Ad
Thank you Mark,
That explained lots of things :). I want to make a separate module class
just for the sake of code organization. May be It's wrong to create a module
class for every service category(data access, business logic..etc). What do
you think ? Is it ok performance and architecture wise ?
On Sat, Oct 23, 2010 at 6:29 PM, Muhammad Mohsen wrote:
>
> 2.Modules
> I simply created a class, suffixed it "Module" so it ended up being named
> "DataAccessModule".
> I added a
> public static void bind(ServiceBinder binder) {
> binder.bind(UserDAO.class, UserDAOImpl.class);
> }
> method just l
Hello everyone,
I have a couple of questions I believe to be so primitive but I hope you
don't mind answering them :)
1.Services
I understand that sfl4j Logger class and ObjectLocator class are
automatically available for services and they are considered resources.
*http://tapestry.apache.org/tap
