During migration from Java EE to Jakarta EE (jakarta.servlet.jsp-api:3.1.0 and jakarta.servlet-api:6.0.0) I got exception java.lang.ClassNotFoundException: javax.servlet.jsp.tagext.DynamicAttributes.

I think it's because of migration namespaces from javax.* to jakarta.* .

Could you provide Telerik for UI which support jakarta.* namespace.

I am using kendo-taglib-2023.1.117.jar 

Bug report

The 'k-state-' classes are supposed to be updated when UI for JSP is used. However, the classes are still present in some of the ItemsTag.java files, thus the classes are added to the rendering.

Reproduction of the problem

1. Run the JSP demos locally
2. Open a TabStrip demo and inspect it

Current behavior

Both classes 'k-state-active' and 'k-active' are applied (screencast).
Other classes that appear in the ITemTag.java files are k-state-disabled and k-state-selected. Components that should be revised are - - ContextMenu,

• Menu,
• PanelBar,
• TreeView

Expected/desired behavior

The state classes should be upgraded when using the UI for JSP wrappers according to the new rendering.
https://docs.telerik.com/kendo-ui/styles-and-layout/components-rendering-overview#state-classes

Environment

• Kendo UI version: 2022.3.913
• Browser: [all ]

It is showing Unknown tag (kendo:editor-pdf).

I want to use pdf with pagesize a4 but I am not able to use kendo:editor-pdf tag.

I am using kendo-taglib-2012.3.1322.jar.

This is a regression since R3 2018 - GitHub issue.
The issue is reproducible when title is set as window tag attribute:

Workaround:
Instead of using title attribute, set the title through window-title tag:

Currently only "true" is possible. Like in HTML5 / Javascript passing an array of custom values (like documented) should be possible

I would like to see wrappers for Java Server Faces. The focus of Java EE development is on JSF and i.m.o. not on JSP. Look e.g at PrimeFaces (a lot of UI components). They are now developing as a spin off PrimeUI,  a Javascript UI component library.

<kendo:grid-filterable extra="true"> 
<kendo:grid-filterable-operators> 
<kendo:grid-filterable-operators-enums neq="Is NOT equal to:" eq="Is equal to:" /> 
</kendo:grid-filterable-operators> 
</kendo:grid-filterable>

AND

<kendo:grid-filterable extra="true"> 
<kendo:grid-filterable-operators> 
<kendo:grid-filterable-operators-enums eq="Is equal to:" neq="Is NOT equal to:" /> 
</kendo:grid-filterable-operators> 
</kendo:grid-filterable>

always gives the same result: neq is always the first element in the filter combobox and eq est the second item.

Would be nice to control display order from the <kendo:grid-filterable-operators-enums /> JSP tag

Play framework is probably the fastest growing framework in the Java space due to its container-less deployment and non-blocking IO features.
I think its an ideal vehicle for Kendo/Kendo MVVM to visit Java land for the first time!
Normally this means adopting logic-less mustache templating (see https://github.com/pk11/play-scalate/)  but other options may exist.

Consider “Java” wrappers for the KendoUI . The use case for “Java” wrappers is for existing Java server side applications that embed the UI code in the Java classes (no JSP / JSF), similar to the Vaadin philosophy, but without having to adopt Vaadin and yet be able to incrementally enhance existing / stable, line of business web applications, without a complete rewrite.

Allow generation of kendo:grid columns using JSP tags, such as c:forEach. Currently throws an error as grid:column needs its immediate parent to be a grid:columns tag.