Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Inventory system assumptions

 
Marcelo Ortega
Ranch Hand
Posts: 528
Eclipse IDE Hibernate Java
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Guys,

Do you think it is fair to assume that an inventory system which we know little about, will support WS-Coordination and WS-Transaction spec? I think it may be a little far fetched in reality.

Another way around it is to implement custom transaction logic around inventory system access (e.g if we're updating the inventory system and we get no response - then we inform the user that the transaction has failed, rolling back where needed/possible). But what if the SOAP message gets to the inventory system, but simply doesn't reply? We would then have stale/corrupt data.

Any suggestions around this matter would be greatly appreciated.

Thanks

 
Rishi Shehrawat
Ranch Hand
Posts: 218
Hibernate Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In case you are developing custom transaction logic, you could assume that the inventory system provides a querying interface. In case you don't get a response for initial web service call, you could use this interface to get status of transaction & based on the status returned make a decision to commit or rollback transaction. The downside of this approach is that if done synchronously it could in some cases impact the page response times. For this you could look at possibility of doing this asynchronously.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic