Query regarding upgrade of Modeshape from 2.7.0 to 3.7.0

[deepak_a]

All,

I am in the middle of upgrading modeshape from 2.7.0 to 3.8.0.

The architecture involves EAP 6.3.0, Modeshape 3.8.0, Infinispan 5.3.0.Final

I upload my artifacts to modeshape via modeshape-jcr-rest API.

When I access the artifacts I get hold of a node object and I can see the following values for the node object.

(artifacts uploaded and accessed with version 3.8.0)

/current/reform-emir-config {jcr:primaryType=nt:unstructured, properties={"jcr:primaryType":"nt:folder"}}

(artifacts uploaded and accessed with version 2.7.0)

/current/reform-emir-config {jcr:createdBy=admin, jcr:primaryType=nt:folder, jcr:created=2014-10-03T16:52:58.885+01:00, }

the node object is of type: javax.jcr.Node

From the above object - /current is the root directory and directory /reform-emir-config is its child.

and there will be subsequent child nodes under /reform-emir-config

What I don't understand is the change in the attributes of the Node object.

why do I see jcr:primaryType=nt:unstructured when I use Modeshape 3.8.0???

Where/how is this set? (since I don't set this while uploading the artifatcs via modeshape-jcr-rest)

Are these default properties that get set within modeshape-jcr?

regards,

Deepak.

[hchiorean]

When you create a node via the REST service, if you don't specify a primary type, it will default to "nt:unstructured". If you want any other type, you must explicitly add it to the JSON request.

See REST Service 3.x - ModeShape 3 - Project Documentation Editor for an example.

[deepak_a]

Hi,

Thanks for pointing out, however I don't actually create a Node object,

I simply do a 'publish' of the file the jcr via the JsonRestClient API.

i.e.

publish

public Status publish(Workspace workspace, String path, File file)

I don't see an option to set the primary type. Should I be publishing artifacts to jcr in a different manner?

regards

[hchiorean]

The RestClient  was never meant for these kinds of usage. It has extremely limited purposes (mainly used from JBoss Developer Studio via the JBoss Integration Tools stack).

It will become deprecated in 3.8.1 and has been removed altogether from ModeShape 4.

So if you plan on inserting data into ModeShape 3.x using one of the services, I'd suggest you use the REST Service.

[deepak_a]

Thanks,

Just noticed that

modeshape-web-jcr-rest-client and

modeshape-web-jcr-rest-war

have been removed in Modeshape 4.0

But modeshape-web-jcr-rest is still available.

Any reason for this?

Does this mean - Clients can't access Modeshape via HTTP using a API? starting from 4.0, or can this still be achieved with modeshape-web-jcr-rest?

If yes - can you pls point me to some test classes.

regards,

Deepak.

[hchiorean]

modeshape-web-jcr-rest is the implementation of the REST service (server). Its documentation is the one from the link I posted previously and you interact with it via HTTP requests containing JSON bodies.

There is no dedicated Java client API atm

Instead, you interact with a ModeShape server using one of the following:

• REST service (RW)
• WebDAV service (RW but limited to files & folders only)
• CMIS (RW)
• JDBC (R)