FYI, Chrome doesn't allow notifications anymore from unsecure sites. So if

Directory Notify
1

FYI, Chrome doesn’t allow notifications anymore from unsecure sites. So if you use this add-on, make sure you use HTTPS.

And for my demo site (as it’s not using HTTPS), use Firefox or Safari.

2

Hi Sami,
thanks for your shared job,

we use vaadin 7.7.6 and including your dependencies packages we take this error to build our projects

[INFO]
Compiling module rv.RVWidgetset
[INFO]
Tracing compile failure path for type ‘org.vaadin.alump.notify.client.util.NotifyUtil’
[INFO]
[ERROR]
Errors in ‘jar:file:/C:/Users/ZEUS-HP/.m2/repository/org/vaadin/alump/notify/0.1.0/notify-0.1.0.jar!/org/vaadin/alump/notify/client/util/NotifyUtil.java’
[INFO]
[ERROR]
Line 39: The method forEach(( n) → {}) is undefined for the type List
[INFO]
[ERROR]
Line 73: The method forEach(( l) → {}) is undefined for the type List
[INFO]
[ERROR]
Line 44: The method forEach(( l) → {}) is undefined for the type List
[INFO]
[ERROR]
Line 73: Lambda expressions are allowed only at source level 1.8 or above
[INFO]
[ERROR]
Line 44: Lambda expressions are allowed only at source level 1.8 or above
[INFO]
[ERROR]
Line 182: The method forEach(( l) → {}) is undefined for the type List
[INFO]
[ERROR]
Line 182: Lambda expressions are allowed only at source level 1.8 or above
[INFO]
[ERROR]
Line 39: Lambda expressions are allowed only at source level 1.8 or above
[INFO]
[ERROR]
Aborting compile due to errors in some input files
[INFO]

[INFO]
BUILD FAILURE
[INFO]

[INFO]
Total time: 01:59 min
[INFO]
Finished at: 2019-08-12T18:21:10+02:00
[INFO]
Final Memory: 63M/539M

Can you send us solution or link to update working version?

Thanks in advance

3

With vaadin7 you should use 0.1.0-vaadin7 version of add-on, not 0.1.0 (it’s for Vaadin 8)

4

Thanks a lot Sami!
very nice work - the best Vaadin!

5

Hi Sami Viitanen,

we try to insert DemoUI in our projects to test patterns,
we encounter errors,as this very strange because according to the link of this article stackoverflow
https://stackoverflow.com/questions/17234558/the-type-jcombobox-is-not-generic-it-cannot-be-parameterized-with-arguments-ob

we are aligned using Java 8 (jdk 1.8.0_144) but ComboBox it cannot be parameterized with generic arguments (Resource, Integer, or <>)

!(localhost:8080\Raccolte\Documenti\demoUI error ComboBox generic.png)

Installed JREs
jdk.1.8.0_144 (default)

have you an idea?
thanks in advance

6

Sorry, looks like demoui on vaadin7 branch wasn’t backported with add-on itself. So I made fast conversion of it, please try new version:

https://github.com/alump/Notify/blob/vaadin7/notify-demo/src/main/java/org/vaadin/alump/notify/demo/DemoUI.java

Hopefully it works, I didn’t test it.

I won’t make new release as demo ui isn’t really part of release. Old add-on code is good as it is.

7

Hi sami,
thank you for your reply and for your attention,

I tried to insert the Notify’s packages in our packages and now it works,

I created two identical classes:

Notify.java - added two methods to send notifications to all active webapp sessions (following only relative browser session and a specific user connected in webapp)

NotifySharedState.java - Boolean checkbox added to manage Boolean selection 1 VS session All sessions

here identical code

package rv.webpush.notifications;

import com.vaadin.shared.AbstractComponentState;

public class NotifySharedState extends AbstractComponentState {

public integer defaultTimeoutMs = null;
public boolean closeOnClick = false;
public boolean showAllSessions = true;

}

(that’s to test a necessity more than we have)

now … if I use tin a class Demo to call methods in Notify.class of your native package it works fine all button’s function … notifications are shown in calling browser session,

import org.vaadin.alump.notify.Notify;

if I use “our” Notify (identical, we have not changed code, only added two new methods) something wrong, nothing works fine, notifications don’t shown

import rv.webpush.notifications.Notify;

also the import clauses are identical (always referring to your package)

Here they are in “our” Notify.java

package rv.webpush.notifications;

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.concurrent.atomic.AtomicInteger;

import org.vaadin.alump.notify.NotifyClickEvent;
import org.vaadin.alump.notify.NotifyItem;
import org.vaadin.alump.notify.NotifyStateEvent;
import org.vaadin.alump.notify.NotifyStateListener;

// import org.vaadin.alump.notify.client.share. ; (don’t take it, delete it by importing and details of the classes used)

import org.vaadin.alump.notify.client.share.NotifyClientRpc;
import org.vaadin.alump.notify.client.share.NotifyServerRpc;
import org.vaadin.alump.notify.client.share.NotifyState;
import org.vaadin.alump.notify.client.share.SharedNotification;
// import org.vaadin.alump.notify.client.share.NotifySharedState;

import org.vaadin.alump.notify.exceptions.NotificationAPINotSupportedException;
import org.vaadin.alump.notify.exceptions.NotificationsDeniedByUserException;
import org.vaadin.alump.notify.exceptions.NotifyRuntimeException;
import org.vaadin.alump.notify.exceptions.NotifyUINotResolvedException;

import com.vaadin.server.AbstractExtension;
import com.vaadin.server.Extension;
import com.vaadin.server.Resource;
import com.vaadin.ui.UI;
import my.vaadin.WebAppUI;

HOW IS IT POSSIBLE?
DO I LEAVE ANYTHING?
DO YOU HAVE AN IDEA ABOUT?

Thanks & Regards
Joe

8

Can I use this component in vaadin14? I am getting issues regarding ‘jsoup-version’ in dependency hierarchy pom.xml.

Please suggest some solutions!

Thanks