+1
I'm also curious about what the newest features would be missing... I saw this but haven't found out what this means anywhere.
jcompagner wrote: but we still allow exporting without a solution and you are in the old mode
mboegem wrote:I don't really see what this discussion is about...
For quite some time you have 2 options when working with war deployment:
1) export war-file including your active solution (and optional solutions)
2) export war-file without the solution.
The 2nd method allows you to import solutions as you were used to, through the admin page.
[] Include active solution and modules a war export without solution does not support newest features)
mboegem wrote:Looking at NG it's good to realise that all of your webpackages are exported with the war and not with export of the solution
So when you are using a new web component you will need to update the war file, this is kind of similar to adding a new plugin/bean to the application server in the past. Which sometimes required restart of the application server (so downtime)
mboegem wrote:When I see Johan's response, nothing seems to change here:jcompagner wrote: but we still allow exporting without a solution and you are in the old mode
mboegem wrote:For all people finding this 2-step approach confusing, there's also something in tomcat called 'parallel deployment'.
Basically this is using the version number in your filename to spin up a 2nd container of your solution in the same tomcat instance.
Alle new sessions will be directed to the newest versions and old sessions will continue to use the old version (until shutdown, tomcat will cleanup the old container when all sessions are gone)
Having 2 war-containers means 2 application servers, meaning you will have to setup RabbitMQ in order to handle data-broadcast between those.
This approach allows deployment of the full war-file without downtime, but requires some setup and thinking about situations like shutting down batch-processors on the old version.
rafig wrote:The first bit sounds great (what is naming convention though for WAR files & version numbers??), but I have no idea how to set up RabbitMQ...
mboegem wrote:Versioning is [containername##v2.0], where part after hashtags can be anything.
[] Include active solution and modules a war export without solution does not support newest features)
jcompagner wrote:Stuff about those new features are described in the release notes of 2022.09
https://wiki.servoy.com/display/DOCS/2022.09+Whats+new
this is about the part of "columns sort on null and sorting case insensitive
that information doesn't get into the WAR when you are just using .servoy files (because the .servoy file doesn't have that)
sbutler wrote:If there is enough interest, we'd consider formalizing that into something that could be easily used by others and able to be purchased (or included for those that already purchase our All Products Pack bundle)
rafig wrote:If the price is right
sbutler wrote:rafig wrote:If the price is right
Sounds like Rafi!
sbutler wrote: If there is enough interest, we'd consider formalizing that into something that could be easily used by others and able to be purchased (or included for those that already purchase our All Products Pack bundle)
Users browsing this forum: No registered users and 2 guests