Using manual’s example code for writing a `UI` subclass in Vaadin Flow
On the page of the manual for Differences Between V10 and V8 Applications, there is this example code for those who want to write a UI subclass as we did in Vaadin 8, despite being no longer required in Vaadin Flow.
(changing the original mydomain-dot-com to example.com to appease the Stack Overflow censor robot)
@WebServlet(urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam(name = "frontend.url.es6", value = "http://example.com/es6/"),
@WebInitParam(name = "frontend.url.es5", value = "http://example.com/es5/") })
// The UI configuration is optional
@VaadinServletConfiguration(ui = MyUI.class, productionMode = false)
public class MyServlet extends VaadinServlet {
}
// this is not necessary anymore, but might help you get started with migration
public class MyUI extends UI {
protected void init(VaadinRequest request) {
// do initial steps here.
// previously routing
}
}
Syntactically that is either incorrect or is meant to be written into two separate .java files.
Or should the MyServlet class be set within the MyUI class, as was done by default in Vaadin 8? Like this:
package com.raddkit;
import com.vaadin.flow.component.UI;
import com.vaadin.flow.server.VaadinRequest;
import com.vaadin.flow.server.VaadinServlet;
import com.vaadin.flow.server.VaadinServletConfiguration;
import javax.servlet.annotation.WebInitParam;
import javax.servlet.annotation.WebServlet;
public class MyUI extends UI {
protected void init ( VaadinRequest request ) {
}
@WebServlet ( urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam ( name = "frontend.url.es6", value = "http://example.com/es6/" ) ,
@WebInitParam ( name = "frontend.url.es5", value = "http://example.com/es5/" ) } )
// The UI configuration is optional
@VaadinServletConfiguration ( ui = MyUI.class, productionMode = false )
public class MyServlet extends VaadinServlet {
}
}
java web-applications view vaadin vaadin-flow
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
add a comment |
On the page of the manual for Differences Between V10 and V8 Applications, there is this example code for those who want to write a UI subclass as we did in Vaadin 8, despite being no longer required in Vaadin Flow.
(changing the original mydomain-dot-com to example.com to appease the Stack Overflow censor robot)
@WebServlet(urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam(name = "frontend.url.es6", value = "http://example.com/es6/"),
@WebInitParam(name = "frontend.url.es5", value = "http://example.com/es5/") })
// The UI configuration is optional
@VaadinServletConfiguration(ui = MyUI.class, productionMode = false)
public class MyServlet extends VaadinServlet {
}
// this is not necessary anymore, but might help you get started with migration
public class MyUI extends UI {
protected void init(VaadinRequest request) {
// do initial steps here.
// previously routing
}
}
Syntactically that is either incorrect or is meant to be written into two separate .java files.
Or should the MyServlet class be set within the MyUI class, as was done by default in Vaadin 8? Like this:
package com.raddkit;
import com.vaadin.flow.component.UI;
import com.vaadin.flow.server.VaadinRequest;
import com.vaadin.flow.server.VaadinServlet;
import com.vaadin.flow.server.VaadinServletConfiguration;
import javax.servlet.annotation.WebInitParam;
import javax.servlet.annotation.WebServlet;
public class MyUI extends UI {
protected void init ( VaadinRequest request ) {
}
@WebServlet ( urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam ( name = "frontend.url.es6", value = "http://example.com/es6/" ) ,
@WebInitParam ( name = "frontend.url.es5", value = "http://example.com/es5/" ) } )
// The UI configuration is optional
@VaadinServletConfiguration ( ui = MyUI.class, productionMode = false )
public class MyServlet extends VaadinServlet {
}
}
java web-applications view vaadin vaadin-flow
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
Strange, true. But I would just do separate files.
– Steffen Harbich
Nov 13 '18 at 15:54
add a comment |
On the page of the manual for Differences Between V10 and V8 Applications, there is this example code for those who want to write a UI subclass as we did in Vaadin 8, despite being no longer required in Vaadin Flow.
(changing the original mydomain-dot-com to example.com to appease the Stack Overflow censor robot)
@WebServlet(urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam(name = "frontend.url.es6", value = "http://example.com/es6/"),
@WebInitParam(name = "frontend.url.es5", value = "http://example.com/es5/") })
// The UI configuration is optional
@VaadinServletConfiguration(ui = MyUI.class, productionMode = false)
public class MyServlet extends VaadinServlet {
}
// this is not necessary anymore, but might help you get started with migration
public class MyUI extends UI {
protected void init(VaadinRequest request) {
// do initial steps here.
// previously routing
}
}
Syntactically that is either incorrect or is meant to be written into two separate .java files.
Or should the MyServlet class be set within the MyUI class, as was done by default in Vaadin 8? Like this:
package com.raddkit;
import com.vaadin.flow.component.UI;
import com.vaadin.flow.server.VaadinRequest;
import com.vaadin.flow.server.VaadinServlet;
import com.vaadin.flow.server.VaadinServletConfiguration;
import javax.servlet.annotation.WebInitParam;
import javax.servlet.annotation.WebServlet;
public class MyUI extends UI {
protected void init ( VaadinRequest request ) {
}
@WebServlet ( urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam ( name = "frontend.url.es6", value = "http://example.com/es6/" ) ,
@WebInitParam ( name = "frontend.url.es5", value = "http://example.com/es5/" ) } )
// The UI configuration is optional
@VaadinServletConfiguration ( ui = MyUI.class, productionMode = false )
public class MyServlet extends VaadinServlet {
}
}
java web-applications view vaadin vaadin-flow
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
On the page of the manual for Differences Between V10 and V8 Applications, there is this example code for those who want to write a UI subclass as we did in Vaadin 8, despite being no longer required in Vaadin Flow.
(changing the original mydomain-dot-com to example.com to appease the Stack Overflow censor robot)
@WebServlet(urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam(name = "frontend.url.es6", value = "http://example.com/es6/"),
@WebInitParam(name = "frontend.url.es5", value = "http://example.com/es5/") })
// The UI configuration is optional
@VaadinServletConfiguration(ui = MyUI.class, productionMode = false)
public class MyServlet extends VaadinServlet {
}
// this is not necessary anymore, but might help you get started with migration
public class MyUI extends UI {
protected void init(VaadinRequest request) {
// do initial steps here.
// previously routing
}
}
Syntactically that is either incorrect or is meant to be written into two separate .java files.
Or should the MyServlet class be set within the MyUI class, as was done by default in Vaadin 8? Like this:
package com.raddkit;
import com.vaadin.flow.component.UI;
import com.vaadin.flow.server.VaadinRequest;
import com.vaadin.flow.server.VaadinServlet;
import com.vaadin.flow.server.VaadinServletConfiguration;
import javax.servlet.annotation.WebInitParam;
import javax.servlet.annotation.WebServlet;
public class MyUI extends UI {
protected void init ( VaadinRequest request ) {
}
@WebServlet ( urlPatterns = "/*", name = "myservlet", asyncSupported = true,
// Example on initialization parameter configuration
initParams = {
@WebInitParam ( name = "frontend.url.es6", value = "http://example.com/es6/" ) ,
@WebInitParam ( name = "frontend.url.es5", value = "http://example.com/es5/" ) } )
// The UI configuration is optional
@VaadinServletConfiguration ( ui = MyUI.class, productionMode = false )
public class MyServlet extends VaadinServlet {
}
}
java web-applications view vaadin vaadin-flow
java web-applications view vaadin vaadin-flow
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
edited Nov 12 '18 at 22:51
Basil Bourque
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
asked Nov 12 '18 at 22:43
Basil BourqueBasil Bourque
107k25366529
107k25366529
Strange, true. But I would just do separate files.
– Steffen Harbich
Nov 13 '18 at 15:54
add a comment |
Strange, true. But I would just do separate files.
– Steffen Harbich
Nov 13 '18 at 15:54
Strange, true. But I would just do separate files.
– Steffen Harbich
Nov 13 '18 at 15:54
Strange, true. But I would just do separate files.
– Steffen Harbich
Nov 13 '18 at 15:54
add a comment |
1 Answer
1
active
oldest
votes
That example is meant to be written into two separate .java files. Alternatively, you can define the servlet as a public static inner class, enclosed in a UI class. In that case, the ui attribute of @VaadinServletConfiguration defaults to the enclosing UI.
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271168%2fusing-manual-s-example-code-for-writing-a-ui-subclass-in-vaadin-flow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That example is meant to be written into two separate .java files. Alternatively, you can define the servlet as a public static inner class, enclosed in a UI class. In that case, the ui attribute of @VaadinServletConfiguration defaults to the enclosing UI.
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
add a comment |
That example is meant to be written into two separate .java files. Alternatively, you can define the servlet as a public static inner class, enclosed in a UI class. In that case, the ui attribute of @VaadinServletConfiguration defaults to the enclosing UI.
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
add a comment |
That example is meant to be written into two separate .java files. Alternatively, you can define the servlet as a public static inner class, enclosed in a UI class. In that case, the ui attribute of @VaadinServletConfiguration defaults to the enclosing UI.
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
That example is meant to be written into two separate .java files. Alternatively, you can define the servlet as a public static inner class, enclosed in a UI class. In that case, the ui attribute of @VaadinServletConfiguration defaults to the enclosing UI.
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
answered Nov 13 '18 at 15:56
JavierJavier
9,47943546
9,47943546
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271168%2fusing-manual-s-example-code-for-writing-a-ui-subclass-in-vaadin-flow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Strange, true. But I would just do separate files.
– Steffen Harbich
Nov 13 '18 at 15:54