Hi
So I figured out what is preventing the Segment Node Store and with it JCR
being created.
During the conversion this snippet is created inside the boot_boot.json:
"org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.runmodes.oak_tar":{
"name":"Default NodeStore”
}
This is preventing the Segment Node Store to be create and the repository.home
property being set.
Instead it will create another configuration with that name.
Changing it to:
"org.apache.jackrabbit.oak.segment.SegmentNodeStoreService":{
"name":"Default NodeStore”
}
does the trick.
Is there a way in the Feature Model to have conditional configurations?
- Andy
> On Apr 22, 2019, at 2:50 AM, Robert Munteanu <[email protected]> wrote:
>
> Hi Andy,
>
> On Fri, 2019-04-19 at 18:26 -0700, Andreas Schaefer wrote:
>> Hi
>>
>> I found a solution for the OSGi dependencies issues by adding these
>> properties to the framework-properties:
>>
>> "felix.systempackages.substitution":"true",
>> "felix.systempackages.calculate.uses":"true"
>>
>> Now Sling starts up but is stuck in the never ending startup loop. It
>> looks like that no JCR repository is created.
>
> Looking at the README, especially the part that says
>
> The 3 non-activating bundles should be prevent Sling from starting
> but when I open http://localhost:8080 I get the If you start me up
> page and it stays there
>
> I would suggest to remove the 'starter.startup' bundle and see if that
> at least allows you to access the system console and see what is going
> on.
>
> https://github.com/schaefa/sling-featuremodel-starter/blob/92a0441e53f2e5e6591565d7527cea2f5eddeb1f/src/main/features/sling_sling.json#L264
>
> Thanks,
>
> Robert
>
>>
>> - Andy
>>
>>> On Apr 19, 2019, at 1:56 PM, Andreas Schaefer <
>>> [email protected]> wrote:
>>>
>>> Hi
>>>
>>> This is my project where I try to convert Sling Starter to a
>>> Feature Model based starter:
>>>
>>> https://github.com/schaefa/sling-featuremodel-starter
>>>
>>> The Readme file contains the instruction on how to build and start
>>> it as well as my findings and how I converted the Sling 11
>>> Provisioning Model into a Feature Model. That was not as straight
>>> forward as I expected it but I got it done.
>>>
>>> That said the missing bundles should not affect Sling but when
>>> opening the landing page (or any other page for that matter like
>>> Composum) leads me to the Starting Up page and it looks like Sling
>>> is never getting out of the starting up page.
>>>
>>> Any help is appreciated.
>>>
>>> Cheers - Andy Schaefer
>>>
>>>> On Apr 19, 2019, at 12:27 AM, Robert Munteanu <[email protected]
>>>>> wrote:
>>>>
>>>> Hi Andy,
>>>>
>>>> On Thu, 2019-04-18 at 18:04 -0700, Andreas Schaefer wrote:
>>>>> Hi
>>>>>
>>>>> Since a few days I try to make Sling Launchpad starting from a
>>>>> Feature Model of the Sling Starter kit.
>>>>>
>>>>> After I converted all the provisioning files to a FM I wanted
>>>>> launch
>>>>> it but that does failed due to javax dependency issues.
>>>>>
>>>>> Eventually I found a solution by adding all the necessary
>>>>> packages to
>>>>> org.osgi.framework.system.packages.extra property and that
>>>>> works to
>>>>> most part except for exporting javax.xml.stream.
>>>>>
>>>>> When comparing the FM to the Provisioning Model bundles then I
>>>>> see
>>>>> that in the PM bundle 0: org.apache.felix.framework is
>>>>> exporting many
>>>>> javax packages but not in the FM launch.
>>>>>
>>>>> Is there a flag to make this happening?
>>>>
>>>> I don't have an answer but maybe if you put up what you have done
>>>> so
>>>> far on a repo on Github it might be easier to see what is
>>>> missing.
>>>>
>>>> Thanks,
>>>>
>>>> Robert
>
