DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Changing Locale Based on Domain

Taha Siddiqi user avatar by
Taha Siddiqi
·
Jan. 11, 13 · Interview
Like (0)
Save
Tweet
Share
2.40K Views

Join the DZone community and get the full member experience.

Join For Free

Happy New Year to everybody!!.

With Tapestry one of the advantages is that you can override almost everything but then there are always some parts which are less overridable. One such place is setting locale based on some custom criteria. The locale logic is embedded a bit deeper than you expect into the request processing cycle and that might give you an impression that you won’t be able to override it.

Of course I did find the solution (otherwise I would be writing to the very helpful mailing list Tapestry has) and it was so easy that you just got to admire Tapestry. All you have to do is decorate the ComponentEventLinkEncoder in the Application Module

public class AppModule {
    @Match("ComponentEventLinkEncoder")
    public ComponentEventLinkEncoder decorateComponentEventLinkEncoder(Logger logger,
        ComponentEventLinkEncoder delegate, DomainService domainService, ThreadLocale threadLocale) {
        return new DomainLinkTransformerInterceptor(logger, domainService, delegate, threadLocale);
    }
}

In our interceptor we intercept the calls to url decoding and set the locale there.

public class DomainLinkTransformerInterceptor implements ComponentEventLinkEncoder {

    private final Logger logger;

    private final DomainService domainService;

    private final ComponentEventLinkEncoder delegate;

    private ThreadLocale threadLocale;

    public DomainLinkTransformerInterceptor(Logger logger, DomainService domainService,
        ComponentEventLinkEncoder delegate, ThreadLocale threadLocale) {
        this.logger = logger;
        this.domainService = domainService;
        this.delegate = delegate;
        this.threadLocale = threadLocale;
    }

    @Override
    public Link createPageRenderLink(PageRenderRequestParameters parameters) {
        return delegate.createPageRenderLink(parameters);
    }

    @Override
    public Link createComponentEventLink(ComponentEventRequestParameters parameters, boolean forForm) {
        return delegate.createComponentEventLink(parameters, forForm);
    }

    @Override
    public ComponentEventRequestParameters decodeComponentEventRequest(Request request) {
        ComponentEventRequestParameters parameters = delegate.decodeComponentEventRequest(request);
        threadLocale.setLocale(domainService.getCurrentDomain().getLanguage().getLocale());
        logger.debug("For Domain {} setting locale to {}", domainService.getCurrentDomain(),
            threadLocale.getLocale());
        return parameters;
    }

    @Override
    public PageRenderRequestParameters decodePageRenderRequest(Request request) {
        PageRenderRequestParameters parameters = delegate.decodePageRenderRequest(request);
        threadLocale.setLocale(domainService.getCurrentDomain().getLanguage().getLocale());
        logger.debug("For Domain {} setting locale to {}", domainService.getCurrentDomain(),
            threadLocale.getLocale());
        return parameters;
    }

}

and you are done!.


 

Locale (computer hardware)

Published at DZone with permission of Taha Siddiqi, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Apache Kafka vs. Memphis.dev
  • The Enterprise, the Database, the Problem, and the Solution
  • DevOps Roadmap for 2022
  • Handling Automatic ID Generation in PostgreSQL With Node.js and Sequelize

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: