Hi Robert, Thanks for you response, I tried updating the Composum Nodes package to the latest version I could find which is 4.2.3, still facing the same issue, here is the problem in detail - I have 3 files which I use to start my sling12 server - sling12-kickstart.jar custom-feature.json custom-script Now, when I start the server everything works fine, but when I go to the bin browser to try and create a node with primary type - vlt:PackageDefinition It gives me - Error - 400 javax.jcr.nodetype.NoSuchNodeTypeException: Node type vlt:PackageDefinition does not exist But when I go to the packages section in the bin browser and come back to create a node with the same type it is successful. First of all, I don't understand the behavior of this and how do I fix this as I want that node type on startup? The composum node version in my feature.json is 4.2.3!
On 2024/02/06 16:15:13 Robert Munteanu wrote: > Hi Rahul, > > On Tue, 2024-02-06 at 12:29 +0530, Rahul Rupani wrote: > > I am using the sling12 kickstart jar with my custom feature.json file > > and a > > custom script, > > The problem is when i try to create a node in my bin browser with the > > jcr:PrimaryType as vlt:PackageDefinition it gives me - > > Error - 400 javax.jcr.nodetype.NoSuchNodeTypeException: Node type > > vlt:PackageDefinition does not exist > > But when i go to Packages inside bin browser and then go back to > > creating > > the same node it is successful, first of all let me know why and what > > is > > this behaviour and also how can i add the custom node type in my > > feature.json or my start script as i want it on a fresh server start, > > Thanks > > I suspect 'bin browser' is the Composum Nodes package installed by > Sling. I would first start by upgrading to the latest Composum Nodes > version, and if that does not work ask at > https://github.com/ist-dresden/composum-nodes . > > Thanks, > Robert >
