You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Class DevModeInitializer scanning for jar files in classloader fails because classloader returns all paths starting with vfs (vfs:/C:/jboss-eap-7.2.0/jboss-eap-7.2/bin/content/test.war/WEB-INF/lib/vaadin-date-picker-flow-2.0.2.jar/META-INF/resources/frontend/) , and JAR_FILE_REGEX pattern looks for ".file:(.+\.jar)." and none of entries match.
In this case, method getJarFilesFromClassloader always returns empty set.
Versions:
Vaadin / Flow version - 14.0.0.rc7
flow-server-2.0.7.jar
JBOSS 7.2 eap (and all jboss/wildfly family)
The text was updated successfully, but these errors were encountered:
This is still a problem in Vaadin 14.0.3 using flow 2.0.10. I managed to get around it if i modified the DIR_REGEX by adding the possibility of a trailing slash. It seems to work in that case.
See https://issues.jboss.org/browse/JBVFS-147 -- manipulating the "vfs:/D:/foo/wildfly-11.0.0.Final.bar/content/selfservices-pkh-1.0.0.war/WEB-INF/lib/flow-data-2.0.11.jar/META-INF/resources/frontend/" so that we have a URL of "vfs:/D:/foo/wildfly-11.0.0.Final.bar/content/selfservices-pkh-1.0.0.war/WEB-INF/lib/flow-data-2.0.11.jar" will not allow to read from the url.openConnection().getInputStream(). These reads are short reads, EOF ("-1") is read only.
In Class DevModeInitializer scanning for jar files in classloader fails because classloader returns all paths starting with vfs (vfs:/C:/jboss-eap-7.2.0/jboss-eap-7.2/bin/content/test.war/WEB-INF/lib/vaadin-date-picker-flow-2.0.2.jar/META-INF/resources/frontend/) , and JAR_FILE_REGEX pattern looks for ".file:(.+\.jar)." and none of entries match.
In this case, method getJarFilesFromClassloader always returns empty set.
The text was updated successfully, but these errors were encountered: