Re: Modules as directories

2010-06-01 Thread leslie
I discovered part of the the answer to this.  I didn't realize that I
had an additional attribute in the "module" element of the xml file
called "rename-to".  So In the xml file of the module directory named
"bar", the module element looks like



Wheres for the other it is simply



-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



Modules as directories

2010-05-28 Thread leslie
My application contains code which is organized into packages like
"view", or "controller", or "persist".  I've identified these packages
as modules in my GWT projecct.  I notice that the compiler has created
directories for these in my war folder.  I also notice that some of
the names are the fully qualified name and others are just the name.
Like one directory is named "com.mycompany.foo" and the other is just
named "bar".  Is there any reason for this difference in naming
convention of modules as directories?

I also notice that some of the modules which are purely server side
nevertheless have folders created for them with a hosted.html file and
a js file.  But what is the need for this?  What have I done wrong in
the effort to define the module?

I realize this is confusing.. Thanks for any help.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.