WildFly 10: minimum requirements

[alicia-lobo]

Warning: complete newbie here. Sorry if this is something I should know but as I mentioned in my previous question I cannot find WildFly10-specific documentation, only for version 8, so I'm a bit lost at the moment.

What are the minimum requirements for WildFly 10? I'm asking not only memory, etc. (which I'd definitely want to know about), but also Java version. From the release announcement I see:

As with WildFly 8 and WildFly 9, WildFly 10 implements the Java EE 7 Full and Web Profile standards.

But also:

Java 7 support has been discontinued allowing for deeper integration with the Java 8 runtime. While Java 9 is still in development, this release runs on the current development snapshots.

It may be my noobness but I'm not sure if this means it's not possible to use Java 7 at all, or if it is possible but you will not get support if you run into problems. Could someone clarify?

Also: is it possible to use Java SE instead of EE? And does it make sense at all? Meaning: will I be missing out on important features to such an extent that it makes more sense to use a non-EE-compliant web server like Tomcat? Can I benefit from scalability and clustering at all if I use SE?

Most of the code in my web application has to be plain SE because it is also used for other projects that have this requirement, so I really cannot switch to EE. I could deploy the application on top of EE (should I?) but my code needs to be compatible with plain SE.

Thanks,

Alicia

[ctomc]

yes, as release notes mention, JDK8 is *hard* requirement, it wont run on JDK7 at all.

as runtime you have Java SE 8 if you want to be specific,

Java EE  is specification, which WildFly itself implements, so there is no such thing as java ee 8 download (btw current latest is EE7)

memory requirements of WildFly itself are low, it uses less than 20mb of ram on default (empty) standalone config.

but, it is more important how much will your application use/need.

[alicia-lobo]

Thank you Tomaz for your very clear answer. In that case WildFly 9 is the one for me.

Is there really no list of minimum system requirements anywhere? This is something that most people expect to see when they download an application or tool.

[ctomc]

Alicia Lobo wrote:

Thank you Tomaz for your very clear answer. In that case WildFly 9 is the one for me.

Why? you have requirement to still use JDK7 as run time environment? keep in mind that JDK is EOL since April last year http://www.oracle.com/technetwork/java/eol-135779.html

You can still compile your project for JDK7 but deploy it on JDK8 runtime.

[alicia-lobo]

Tomaz Cerar wrote:

Why? you have requirement to still use JDK7 as run time environment? keep in mind that JDK is EOL since April last year http://www.oracle.com/technetwork/java/eol-135779.html

Unfortunately I do have the requirement to use JDK7, EOL and all

Tomaz Cerar wrote:

You can still compile your project for JDK7 but deploy it on JDK8 runtime.

True, although I would feel more comfortable keeping my development and production environments as similar as possible.

In any case I've just discovered that WildFly no longer supports OSGi out of the box and the JBoss OSGi project is not active enough for my peace of mine... so afaics WildFly is not an option for me.

Thanks a lot for your inputs in any case!

Alicia

[ctomc]

True, although I would feel more comfortable keeping my development and production environments as similar as possible.

You can always use newer version of JDK and compile to lower one, for example use JDK8 everywhere, but force source & target version of compiler to 1.7, which is quite common practice everywhere.

If you need to use OSGi for your work, all I can say is good luck with your endeavors.

Personally I would go mad if I had to use it...

[alicia-lobo]

You can always use newer version of JDK and compile to lower one, for example use JDK8 everywhere, but force source & target version of compiler to 1.7, which is quite common practice everywhere.

Right, you mean set the compiler compliance to 7 but actually run on 8, even during development. Sorry, it's the end of a long day and I'm being a bit thick

Yes, that makes sense.

If you need to use OSGi for your work, all I can say is good luck with your endeavors.

Personally I would go mad if I had to use it...

Actually, although I definitely needed to adjust when I first started using OSGi I do enjoy it now. I don't know if it's the most practical thing ever but it does encourage good programming practices.

Having to target Java 7 is more of a pain