Hi all There is many times that i saw similar public api from ivy then i could not distinguish between them, i believe some of my co-workers has the same feeling. In this post i need your help to make it more clear. Does they return the same result? 1/ Application:
2/ ProcessModel
3/ ProcessModels
4/ ProcessModelVersion
There is some more but first i stop here :) Thanks in advance asked 29.12.2016 at 02:25 trungdv |
First we have to separate between
The following APIs return runtime objects:
The following APIs return configuration objects:
Further calls on a configuration object returns always further configuration objects:
Hope this information will help. Don't hesitate to ask further question as comment. I will update the answer. answered 30.12.2016 at 12:55 Flavio Sadeghi ♦♦ hi @Flavio Sadeghi ♦♦ Yes, i have another question, as you said "Case/Task lives always in the PMV the Case was started in". so for example i have a project A then i deploy it to PMV 1, i create some cases/tasks on this version. Then i change implementation of Project A (i keep all task elements, just implement some new java class, new api, new logic). Now i deploy project A to PMV 2 (new version) and make it Active and Released. Question: What happen if i start cases/task of PMV1 from released PMV (version 2)? which classes will be loaded? I have some small test and i saw the old task will run on released PMV (PMV2), is it correct? Thanks
(05.01.2017 at 05:50)
trungdv
Hello @trungdv How do you start a case/task of PMV1 from PMV2? I would argue that the the case/task is started in PMV1 and that classes of PMV2 are not visible in PMV1, since this would lead to conflicts, because classes exist in both PMVs, at least the class of the process itself... (except you have some application-wide caching , which is not allowed in such use cases) If it should be possible, I would classify this as an bug. Of course, I would be happy for the test projecte to verify the behaviour.
(05.01.2017 at 09:51)
Flavio Sadeghi ♦♦
hi @Flavio Sadeghi ♦♦ thanks a lot. I just realize that somehow is a problem of deployment wizard tool, when i use it to deploy, it always deploy latest version on PMV1 (even i select PMV2 as the target). that's why i see the new logic on old cases. So when i try with Deploy button on each PMV, it work as you said. I'm using version 6.3.0, don't know whether this is an issue or not.
(06.01.2017 at 02:31)
trungdv
hi @trungdv The deployment wizard decides on the basis of the project version (IvyProject -> Definitions -> Deployment -> Project Version) if a new PMV has to be created or an already existing PMV can be used. And yes, there were some fixes since 6.3...
(09.01.2017 at 14:05)
Flavio Sadeghi ♦♦
hi @Flavio Sadeghi ♦♦ Continuous with PMV, i have a case as below: In my app, we store the task in two places, when creating task, for the main data model, we store in our persistence (BusinessReposiroty) and we take out the id from there then store to Ivy Task. Q1: When user open task, we have that id then load business data from Repository. this case will work.i guess it will load with classLoader of pmv which the task belong to. is it correct? Q2: for the case we have that id then load directly data model from repo(not start from task), it could be an issue? any way to avoid it? Thanks
(10.01.2017 at 10:23)
trungdv
hi @trungdv. I have copied you last question into a new one and edited it, as I have understood the question. Feel free to commet it if I have misunderstood it. See here: http://answers.axonivy.com/questions/2364/how-is-the-handling-when-loading-business-data-in-different-pmvs
(10.01.2017 at 11:18)
Flavio Sadeghi ♦♦
showing 5 of 6
show 1 more comments
|
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 29.12.2016 at 02:25
Seen: 2,352 times
Last updated: 10.01.2017 at 11:20
We can write some small test processes to check it right? :D
Yes and no. If you do not understand it, I think we have to update the java-doc...
Yes, thanks. Actually i can create test and check for myself but can't do fo everyone. They need a clear documentation. This post here for them. They dont need to ask around everytime they use it. :)