I can't see what you've edited to fix it - do you now have three entries for <moduleName>? Or did you remove gwt-app as the packaging?
There are many ways to achieve what you're after, depending on what tradeoffs you want. The simplest option in terms of build configuration and fastest option in terms of compilation is to keep a single module, and edit the EntryPoint to test the URL of the page that loaded, and delegate accordingly to two different "sub entrypoints". Odds are very high that this will reduce downloaded code size if users often will load both pages with the same browser cache, since there will likely be a fair amount of shared code between the two pages.
If there is little to no overlap between the pages, that at least suggests that there will be minimal caching benefits in splitting the modules. In that case, both to avoid overlap and to easily use gwt-app packaging to give you the configuration you want, the next best option is to have three pom files - a parent, and two children, where each child has its own src/main/module.gwt.xml and its own src/main/java full of sources. This has the advantage of using configuration and features of maven that you already understand. Note that if both modules share some library code, a shared cache can still be beneficial.
Last main option is to continue as you're doing - make sure you've removed gwt-app as the packaging, and explicitly control the goal wiring in all ways.
Technically, the GWT compiler can take more than one module as input, so you don't need to invoke the compiler twice in a single module as you're doing - but as I mentioned the gwt-maven-plugin is intended to encourage a 1:1 mapping from maven module to gwt module. If you want to invoke the compiler only once to save some build time, you could set up an exec:java goal that directly calls the compiler with a handwritten argument list. I would strongly encourage one of the two earlier options.
On Saturday, December 28, 2024 at 10:45:10 AM UTC-6 ne...@propfinancing.com wrote:
> Only one of your <execution>s defines <moduleName>, and the error is letting you know that
> at least one execution doesn't define a moduleName.
Oops. I was editing the file and accidentally deleted that. I fixed it, but I am still getting
the error.
> What are you trying to achieve with this?
I am trying to create a war file which has two GWT endpoints in it.
I would like to access them by these URLs:
https://dev.3dmathpuzzles.com/3dmp/DiagonalSlitherlink.html
and
https://dev.3dmathpuzzles.com/3dmp/DiagonalSlitherlink2.html
Thank you,
Neil
--
Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com
We offer 30 year loans on single family houses!
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/b3a24205-2977-47be-97bc-a7a812209b9bn%40googlegroups.com.
No comments:
Post a Comment