: 2416 | 60365 | 6953
|
: 23 : 24 : 1 |
I developed a website where there is a feature to sort/move the content documents. A sort/move action would modify (Sort Order Number) most of the documents. If some error came up, some of the documents will be in modified state and some will be in original state. This mess up the whole website layout.
Though chances of error is very rear, I still implemented a commit/rollack mechanism myself. This is by saving the new values to temporary fields and as the last line of the agent, moving the new values to the actual fields. It wasn't that hard to implement this.
But, if Domino itself provides this Commit/Rollback feature......may be that will help us save some time.
|
1) Axel Janssen (12 Dec 2007)
I think it will be quite hard to implement this ex-post. But I see it as important. Especially for integration with other systems. If its there, this domino-transaction should be able to participate in 2-phase-commit transactions of J2EE/EE5. This would make integration of Domino applications in SOA architecture or J2EE/EE5 a lot more straight forward.
2) Thomas Bahn (13 Dec 2007)
Yeah, DominoTxn! :-D
3) Thomas Bahn (13 Dec 2007)
Sorry, couldn't resist. ;-)
Axel is absolutely right: It would be great for integration, but HARD to implement. VERY HARD!
Axel is absolutely right: It would be great for integration, but HARD to implement. VERY HARD!
4) Giulio C (25 Aug 2008)
This has been one of the gaping weaknesses for Domino. How many times have complex document hierarchies and relationships been corrupted when a process only completes half the changes because of an "object variable not set error" ?
I would like the idea of a commit/rollback in script. Seeing as document models can take any shape, something like a "Transaction Start" and a "Transaction Commit" commands in your code would be great.
I suppose the caveat would be that transaction command pairs (ie start/commit) would have to be in the same sub. I think this would only work in a scheduled agent to. Because re-running the log would be way to hard from UI. The next step would be working out how to link transaction dependancies between subs so if an error occured in a called sub that the rollback would be reported to the calling sub so it could take action in completing the roll-back...
The other problem would be storing the log somewhere in cases where people are modifying very large collections of documents, the log would be humungous. Probably from a transaction server/file store ?
Not so simple.. but if it could be done, it would put all those relational zealots in their place.. LOL.. Thumbs up from me... I wish people who demote ideas justified their answer. It may provide some insight in refining the idea...
I would like the idea of a commit/rollback in script. Seeing as document models can take any shape, something like a "Transaction Start" and a "Transaction Commit" commands in your code would be great.
I suppose the caveat would be that transaction command pairs (ie start/commit) would have to be in the same sub. I think this would only work in a scheduled agent to. Because re-running the log would be way to hard from UI. The next step would be working out how to link transaction dependancies between subs so if an error occured in a called sub that the rollback would be reported to the calling sub so it could take action in completing the roll-back...
The other problem would be storing the log somewhere in cases where people are modifying very large collections of documents, the log would be humungous. Probably from a transaction server/file store ?
Not so simple.. but if it could be done, it would put all those relational zealots in their place.. LOL.. Thumbs up from me... I wish people who demote ideas justified their answer. It may provide some insight in refining the idea...
Purchase IdeaJam Today
You can run IdeaJam in your company. It's easy to install, setup and customize. Learn more here.
Welcome to IdeaJam
IdeaJam is a place where people can post and share their ideas, and gauge the marketability, popularity and viability with input from others.
When an idea gets posted, others can help promote or demote the idea and provide comments. Popular ideas will bubble to the top.
Make your opinion count.
 | SharePost your idea - from ways we can improve IBM Lotus Software to things we've haven't even yet thought of. |
 | VoteCheck out other people's ideas and vote on the ones you like best. The community votes. The community decides. |
 | DiscussTalk about ideas with your peers in the IBM Lotus Community and help make them even better. |
