Yes, the last three releases of gwt-ol have a separate releases for GWT 2.9-support (version with suffix 'gwt2_9'). Actually I updated the demos and plugins when releasing but used the GWT-2.8 version I think. I think all should work fine when using the version '8.1.0-gwt2_9'. Let me know if it shouldn't work or if I can help on this!<!-- https://mvnrepository.com/artifact/com.github.tdesjardins/gwt-ol3 --> <dependency> <groupId>com.github.tdesjardins</groupId> <artifactId>gwt-ol3</artifactId> <version>8.1.0-gwt2_9</version> </dependency>
there is 2 ways to do it depends on how you need to handle things and what is your security implementation
first you can use a
@RevealCondition in your presenters, in the condition you decide if the view should be revealed based on user authentication status
the other way to do it is to wrap the Token filter in a custom token filter that does the check for authentication/authorization
we use the second method
public abstract class AuthorizationProxy<V extends View> extends LoadableProxy<V> {
@RoutingTokenFilter
public static TokenFilter onRoutingToken(String token) {
return AuthorizationTokenFilter.make(TokenFilter.endsWithPathFilter(token));
}
@StartupTokenFilter
public static TokenFilter onStartupToken(String token) {
return AuthorizationTokenFilter.make(TokenFilter.endsWithPathFilter(token));
}
}public class AuthorizationTokenFilter implements TokenFilter {
private static final Logger LOGGER = LoggerFactory.getLogger(AuthorizationTokenFilter.class);
private final TokenFilter tokenFilter;
private StateHistoryToken historyToken;
private AuthorizationTokenFilter(TokenFilter tokenFilter) {
this.tokenFilter = tokenFilter;
}
public static AuthorizationTokenFilter make(TokenFilter tokenFilter){
return new AuthorizationTokenFilter(tokenFilter);
}
@Override
public boolean filter(HistoryToken token) {
boolean filter = tokenFilter.filter(token);
boolean authorized = isAuthorized();
return filter && authorized;
}
private boolean isAuthorized() {
return TokenAuthorizationChecker.isAuthorized(historyToken);
}
@Override
public NormalizedToken normalizeToken(String rootPath, String token) {
this.historyToken = new StateHistoryToken(rootPath, token);
return tokenFilter.normalizeToken(rootPath, token);
}
}@TDesjardins I have updated the project, added github actions to release it but since I am runing maven enforcer plugin ..there was a dependency mix that I tried to solve, can you please give it a quick check.
I will have a look in the evening. Have you updated the plugin project or also the demo app for plugin integration?
Or I think so
I will update this later.
Thanks for updating the map plugin @vegegoku
Hm, don't see any changes here: https://github.com/DominoKit/domino-ui-addons
in the documentation https://github.com/DominoKit/domino-mvp/wiki/Layout there is "@Slot(DOCUMENT_BODY)" but I do not see where is "DOCUMENT_BODY" coming from?
4 replies
Also a new cli version will land soon
@howudodat If you are welling to gve this a test I have fixed the depndencies and added github actions to the repository, a HEAD-SNAPSHOT is in its way ... and if you test this and it works for you we can do a release
ok the app compiles now, so I think we are good there.
I also have the demo running, but I dont get a map in my app. I am probably missing a simple step. One that I can't deduce from the nalu framework
here is how I am setting up the panel (BTW, this is the method I use for all of my panels. I left in all empty code in case you see something crazy wrong with the overall method)
public class PnlHomes extends FlexLayout implements IToolbarListener {
protected FlexLayout content = FlexLayout.create();
protected Map map = null;
protected MapView mapview = null;
public PnlHomes() {
initUI();
}
protected void initUI() {
content.setDirection(FlexDirection.TOP_TO_BOTTOM);
this.appendChild(content);
initHeader();
initContent();
Scheduler.get().scheduleDeferred(new Command() {
@Override
public void execute() {
initPostVisible();
}
});
}
protected void initHeader() {}
protected void initContent() {
// create all the elements
mapview = new MapView("homesmap");
map = MapPresets.getOsmMap("homesmap");
// set attributes necessary to the elements
// add to the container
content.appendChild(mapview.element());
}
protected void initPostVisible() {}
}
maybe you are attaching the map too eqarly before the div is actually attached
what is
content btw?
and can you please use the MapCard for now I need to understand something