Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Getting Rid of Package-Based GWT URL's

DZone's Guide to

Getting Rid of Package-Based GWT URL's

· Java Zone
Free Resource

What every Java engineer should know about microservices: Reactive Microservices Architecture.  Brought to you in partnership with Lightbend.

Deploying a fancy GWT application loses a lot of its shine when you see a my.package.gwt url in your browser. To get rid of this, you only need two extra lines of configuration in your application module:

<module>
    <source path="my/package/gwt"/>
    <public path="gwt/public"/>
    <inherits name='com.google.gwt.user.User'/>
    <entry-point class='my.package.gwt.Application'/>
    <stylesheet src="gwt.css"/>
</module>

This source node points to the Java application implementation, the public node to the application's resources. 

There's one thing you need to keep in mind, though: both paths are considered to be relative to the module configuration file.

Microservices for Java, explained. Revitalize your legacy systems (and your career) with Reactive Microservices Architecture, a free O'Reilly book. Brought to you in partnership with Lightbend.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}