zk spring boot payara 5 deployment error

answered 2020-11-30 09:50:36 +0800

cor3000
6280 ● 2 ● 7

updated 2020-12-01 10:39:05 +0800

In order to deploy a springboot application into an existing application server (e.g. paraya/tomcat/wildfly ...) I assume you are building a war-file. When doing so you have to also configure zkspringboot to activate the war-file specific configuration.

this means the configuration should configure the HttpSessionListener in lines 78-80 and NOT run the block in lines 81-100

You have to set the application property:

zk.springboot-packaging=war

Then also remove the HttpSessionListener from your web.xml in case you added it.

If you prefer to configure ZK manually in your web.xml/zk.xml you don't need zkspringboot-autoconfig, especially in a war file desployment all the classical (without spring boot) configuration options are available.

In case my assumption was wrong about the deployment type please provide the related configuration leading to this error.

Besides this has nothing to do with ZATS, if you read the code carefully the configuration only activates when ZATS is NOT on the classpath (Line 76 @ConditionalOnMissingClass)

@ConditionalOnMissingClass("org.zkoss.zats.mimic.Zats")

answered 2020-12-01 17:39:30 +0800

cor3000
6280 ● 2 ● 7

updated 2020-12-01 17:39:46 +0800

yes a 404 occurs if the web application can't locate the resource based on its configuration. Most likely there is not servlet or view resolver configured to search in your classpath. Without your whole application source code it's hard to tell. Spring boot offers many configuration options.

Here our demo for a minimal war file, maybe you can find the difference to your setup or adapt the example to your requirements.

https://github.com/zkoss/zkspringboot/tree/master/zkspringboot-demos/zkspringboot-minimal-war

answered 2020-12-02 16:00:28 +0800

cor3000
6280 ● 2 ● 7

for no 3, I think there is a misunderstanding here. In the zk spring boot tutorial I was instructed to create a "web" folder under src/main/resources.

sounds like a misunderstanding ... all these changes are only necessary when packaging as self runnable spring boot .jar file

for a .war file you can just keep the file structure as in any other zk web application

src/main/webapp

When packaging a spring boot application as a .jar file the src/main/webapp folder (including WEB-INF) is not available, that's why the alternative folder locations need to be chosen below src/main/resources/web. zk-springboot-autoconfig will adjust the configuration to either the war or the jar file model automatically.

e.g. in the ".war" scenario the view resolver will look for zul files in the src/main/webapp folder (webcontent) and no longer under src/main/resources (classpath) as you can see in the source code.

https://github.com/zkoss/zkspringboot/blob/v2.3.1/zkspringboot-autoconfig/src/main/java/org/zkoss/zkspringboot/ZkWebMvcConfiguration.java#L28-L32

The autoconfig module just assumes the natural default for war- and jar-files packaging. That doesn't mean this is set in stone. You can disable the built-in view resolver and configure your own, spring mvc is quite flexible there. Even Spring-mvc is optional in case of a war file deployment. ZK's default servlet will still handle zul files as enabled here:

https://github.com/zkoss/zkspringboot/blob/v2.3.1/zkspringboot-autoconfig/src/main/java/org/zkoss/zkspringboot/ZkAutoConfiguration.java#L39

answered 2020-12-07 09:46:34 +0800

cor3000
6280 ● 2 ● 7

I agree duplicating the files is nonsense ... what I don't fully understand is the benefit of switching the deployment methods between dev and production. I'd suggest just creating a war file in both cases, you can still run a war application efficiently during development without spring boot (e.g. using jetty-runner or webapp-runner) however that's just my preference. Spring boot should also be possible it's just more of a challenge. Anyway I don't need to agree and understand everyone's intentions and preference so here the answers to your question.

1. (not really a question but) that's possible just keep them there, ZK will be able to handle them as long as you resolve them correctly in your custom view resolver.

2. yes configuring your own view resolver is definitely possible, simply disable the one provided within zkspringboot (in application.properties: zk.zul-view-resolver-enabled=false ) and configure/implement one as needed.

Here the code how zkspringboot implements the view resolver depending on the war/jar packaging option for your reference:

https://github.com/zkoss/zkspringboot/blob/v2.3.1/zkspringboot-autoconfig/src/main/java/org/zkoss/zkspringboot/ZkWebMvcConfiguration.java

answered 2020-12-08 10:49:41 +0800

cor3000
6280 ● 2 ● 7

updated 2020-12-09 10:28:59 +0800

I tried what you describe and I can't see a problem

configure war packaging / disable the provided view resolver:

zk.springbootPackaging=war
zk.zul-view-resolver-enabled=false

register my own view resolver:

@SpringBootApplication
@Controller
public class Application implements WebMvcConfigurer {

    public static void main(String[] args) throws Throwable {
        SpringApplication.run(Application.class, args);
    }

    @Override
    public void configureViewResolvers(ViewResolverRegistry registry) {
        // just hard coding one possible prefix/suffix here (your path might be different)
        registry.viewResolver(new InternalResourceViewResolver("/zkau/web/zul/", ".zul"));
    }
}

This just works, since you forgot to provide the relevant configuration I can't comment on that.