My project is built with Vaadin 6.8.4. I need to use Vaadin server as well. However I can find vaadin server 7.0.0 but I need version 6 which I cannot find anywhere. I don't want to upgrade my project as now. Kindly, can anyone help me out here?
I tried using Vaadin server 7.0.0 with Vaadin 6.8.4 but in the module of sending file as download for client, I get this error:-
java.lang.VerifyError: (class: com/vaadin/server/FileDownloader, method: extend signature: (Lcom/vaadin/ui/AbstractComponent;)V) Incompatible argument to function
In vaadin 6 there was no vaadin-server-xxxx.jar.
Everything is in the vaadin-6.8.xx.jar.
If your code is referencing com/vaadin/server, then probably you have some components which require vaadin 7.
It's not possible to mix components between 6.x and 7.x
Related
I have an Angular app which doesn't load on older iOS version (14 & lower). Angular documentation on browser support mentions that the support is only available for latest 2 versions.
I am assuming polyfill is the solution to support older versions; but I am not able to figure out which polyfill to use and where to download it from.
Any help would be much appreciated.
The browsers you support are defined in your browserlist.src you can see which browsers are supported by running the command npx browserslist. You can play around with your browserlist in here browserlist playground. If you edit your browserlist the polyfills will be automatically added on build.
When I am making a Barcode Scanner Using ZXing Nuget Package. As I am new to the Xamarin, When I run it in the Xamarin.forms. I am receiving that error. I have the updated version of Xamarin.The program shows me the runtime Exception as mentioned in the title.
This is more than likely due to the version of Xamarin.Forms that you are referencing. You need to make sure that your version of Xamarin.Forms is at least version 2.2, which has the AutomationId support.
I use PrimeFaces 3.5.x and Mojarra JSF 2.1.x
I would like to access and show the versions of both libraries programmatically.
I use the versions as maven2 properties, but I hope there is an easier way to get the versions.
I hope to find something like:
Primeface.getVersion();
FacesContext.getCurrentInstance();
A JavaScript based solution would be fine too, since I only want to display the version on a status page.
In PrimeFaces 4.0, Constants.VERSION is removed in favor of;
RequestContext.getCurrentInstance().getApplicationContext().getConfig().getBuildVersion();
Also watch out for FacesContext.class.getPackage().getImplementationVersion();, it doesn't work on some app servers like websphere.
For JSF:
//returns the major version (2.1)
FacesContext.class.getPackage().getImplementationVersion();
//returns the specification version (2.1)
Package.getPackage("com.sun.faces").getSpecificationVersion();
//returns the minor implementation version (2.1.x)
Package.getPackage("com.sun.faces").getImplementationVersion();
For Primefaces 3.x you can use the Constants class in utils package:
import org.primefaces.util.Constants;
Constants.VERSION
For PrimeFaces, you can use the Constants class:
org.primefaces.util.Constants.VERSION
If you need to get the Version on runtime, there will not be any instance of RequestContext. Therefore you could use the ImplementationVersion of the package:
Package.getPackage("org.primefaces").getImplementationVersion()
If the package cannot be resolved, you can try to resolve the version via PrimeFaces class:
PrimeFaces.class.getPackage().getImplementationVersion()
I am working with Vaadin 6 and want to use InvientCharts because it is free.
After compiling the widgetset, all vaadins component instead of invientCharts are working. The error which appears as text on my app is the following:
After trying everything, including setting up a complete new project, I followed this tutorial: http://www.nightswatch.de/?x=entry:entry120125-234412
But it is still not working and shows the same error.
Has anyone an idea what is going on here?
Thanks in advance!
When you receive the message that the widgetset does not contain implementation of XY,
then usually you have forgotten to compile it with the additional jar files or you did not specify the new widgetset.
The nightswatch example is incomplete, you need to compile the widgetset.
Simplest would be to use the maven build script to build all dependencies and compile stuff as needed (or use eclipse for this)
I am trying my hands on vaadin and would like to use gantt chat add-on in my vaading 7 project.
https://vaadin.com/directory#addon/vaadin-gantt-diagram:vaadin
since this is not compatible with vaadin 7, I am trying to fix some code from the add-on to make it compatible with vaadin 7.
I checked out source code of vaadin-6.8 from repository and vaadin-gantt (add-on) from available downloads.
I changed the code a bit in vaadin-6.8 and built. I am using this customized vaadin-6.8 jar inside vaadin-gantt add-on. Now I am able to build vaadin-gantt add-on by using customized vaadin-6.8 jar. I want to use this add-on inside vaadin-7 project.
compiling went through, but i am getting below message on console while displaying gantt chart
"Widgetset does not contain implementation for ru.bazon.vaadin.ganttdiagram.canvas.GanttDiagramCanvas. Check its component connector's #Connect mapping, widgetsets GWT module description file and re-compile your widgetset. In case you have downloaded a vaadin add-on package, you might want to refer to add-on instructions."
I compiled the gantt widgetset using eclipse plugin and could see the below entry in my projects *.gwt.xml file
I would like to make use of gannt chart add-on for vaadin-7. I didn't find any other add-on for vaadin-7 apart from this which is not compatible with vaadin 7.
any pointers?
Regards,
Azhar
Please make sure You have added #Widgetset("path of *.gwt.xml") on your main UI class.I have solved by adding this
I just had this error as well and it was caused by missing source files in the addon jar. Both .java and .class files must be present in the addon jar file as GWT compiles from sources. But most likely the addons form vaadin directory should include also the sources. And ofcourse don't forget to compile the widgetset and themes after importing your addon to your project.
Just leaving this here in case someone has the same case as I had. Our project is in Vaadin 8, and we already had #Widgetset("com.company.OurWidgetSet") as annotation on our UI-extending class.
However, I still received the same error as OP when accessing a pop-up of a separated component. Although we did try to migrate this component of ours to Vaadin 8 in the past, due to lack of time to do this properly, it was still mostly using Vaadin7 imports and functionality.
Because of this I had to add the following to our OurWidgetSet.gwt.xml file (within the <module>-tag) in our main project, to fix the functionality of the used component:
<inherits name="com.vaadin.v7.Vaadin7WidgetSet" />
just had the same issue as well, another thing to make sure if you use vaadin is the web.xml inside the WEB-INF folder of deployed resources.
Make sure the widgetset is also specified there:
<init-param>
<description>AWidgetSet</description>
<param-name>widgetset</param-name>
<param-value>com.example.a.widgetset.AWidgetset</param-value>
</init-param>
When using Java Config with Annotation #VaadinServletConfiguration an additional Solution is to add this as Annotation-Parameter widgetset:
#VaadinServletConfiguration(ui = MyUI.class, productionMode = true, heartbeatInterval = 500, closeIdleSessions = true, widgetset = "com.myapp.MyWidgetset")