On 2/06/2019 4:13 pm, Jean-Baptiste Onofré wrote:
In your case, you should have (standard, http),vaadin-flow.
So, how would this be represented in the assembly pom, also if concrete
standard features are used?
Brackets in my tests are ignored in the assembly pom.
<bootFeatures>
<feature>standard</feature>
<feature>{standard,pax-http)</feature>
<feature>vaadin-flow</feature>
</bootFeatures>
Paul
By the way, I recommend to not use standard meta feature in boot, but
rather the concrete features defined by standard meta feature.
Regards
JB
On 02/06/2019 07:26, Paul Fraser wrote:
Sounds good.
How do I handle it in the assembly pom to get it into features.cfg?
<bootFeatures>
<feature>standard</feature>
<feature>{pax-http)</feature>
<feature>vaadin-flow</feature>
</bootFeatures>
If only one level, how is standard staged?
Or should vaadin-flow be placed in <startupFeatures> ?
Paul
On 2/06/2019 3:06 pm, Jean-Baptiste Onofré wrote:
Hi,
yes, stage boot is present, and used.
Currently, it supports one level (I plan to add several levels).
You can do (in etc/org.apache.karaf.features.cfg):
featuresBoot=(...),...
The features in the parentheses will be started before the one outside
of the parentheses.
Regards
JB
On 02/06/2019 07:03, Paul Fraser wrote:
Hi,
Back in 2016 there was some discussion about predicable boot feature
startup order.
Staged boot was mentioned and the solution involved parentheses, but
current documentation does not mention "staged boot".
Is this functionality still available?
How and where are the parentheses used if staged boot available?
My need relates to previous discussion about service loading. I have an
absolute need for aries dynamic spyfly to be running before the vaadin
flow server is activated.
At present, the only way I can get the correct order is to include
pax-http in my assembly and start a vaadin flow feature containing the
vaadin server after karaf is running.
Paul Fraser
