COLLADA serializer seems to ignore roid about bimserver

[rubendel]

What do you mean with the "JSON "download" method"?

[ChuckAditazz]

For example a POST to:

http://localhost:8082/json

with the payload:

{
"request": {
"interface": "org.buildingsmart.bimsie1.Bimsie1ServiceInterface",
"method": "download",
"parameters": {
"roid": 655363,
"serializerOid": 1245222,
"showOwn": true,
"sync": true
}
},
"token": "823bbbc8bb99fe64eda9ffd37cb6766113957c72f3d5c8eee8ffa92042a2bf76dfb6bd5afcb961d726274111f5b44a76"
}

[rubendel]

And the "roid" here is the roid of the second revision?

[ChuckAditazz]

Yes, the listed roid is the second revision...

[rubendel]

I just tried reproducing this but I got two different models. Did you use the checkin methods to get the models in the project, or did you use the commit method (low level modifications)?

[rubendel]

Test script: 270d8b5

[ChuckAditazz]

The commit was done using low-level modifications.

[rubendel]

Just a heads up, I have never been able to reproduce this until last week. The problem for me arose when using low-level-changes and full-model-checkins on the same project. So for example uploading an initial file (1), changing stuff with low-level-calls (2), uploading a new file (3), changing stuff with low level calls (4). In this case the 4th revision would contain objects from the first revision. I have fixed this in the dev branch.

[rubendel]

So not sure if this is the same problem you had, in my case it wasn't specific for Collada.