Task-oriented Client Development - TechHui2024-03-29T11:12:55Zhttp://www.techhui.com/forum/topics/1702911:Topic:8626?commentId=1702911%3AComment%3A8824&feed=yes&xn_auth=noI've done some work on the Ku…tag:www.techhui.com,2008-03-06:1702911:Comment:88242008-03-06T02:28:27.023ZJ. David Beutelhttp://www.techhui.com/profile/JDavidBeutel
I've done some work on the Kuali Financial System, which is a client of <a href="http://kew.kuali.org/">Kuali Enterprise Workflow</a>. For UI insight, you could look at its <a href="https://test.kuali.org/confluence/display/KULRICE/Action+List+Guide">action list</a>.<br />
<br />
For API insight, I suggest:<br />
1. synchronous, because users want feedback,<br />
2. simple for the client callback code, and<br />
3. fast for clients and tests.<br />
<br />
So, I recommend an API embedded with the client. Its callbacks can take advantage…
I've done some work on the Kuali Financial System, which is a client of <a href="http://kew.kuali.org/">Kuali Enterprise Workflow</a>. For UI insight, you could look at its <a href="https://test.kuali.org/confluence/display/KULRICE/Action+List+Guide">action list</a>.<br />
<br />
For API insight, I suggest:<br />
1. synchronous, because users want feedback,<br />
2. simple for the client callback code, and<br />
3. fast for clients and tests.<br />
<br />
So, I recommend an API embedded with the client. Its callbacks can take advantage of second-level caching of the client database. XML binding and XPath are not as simple or fast, so I don't recommend marshaling the client data to a web service. Thanks for pointing me to Jir…tag:www.techhui.com,2008-03-05:1702911:Comment:88012008-03-05T06:44:51.526ZCraig Petershttp://www.techhui.com/profile/CraigPeters
Thanks for pointing me to Jira. It looks interesting, but not much similar to the kind of API I'm working on. Jira doesn't seem to have a workflow system for orchestrating work between people and systems. Take a look at the <a href="http://www.ibm.com/developerworks/webservices/library/specification/ws-bpel4people/">IBM whitepapers</a> for some more background.
Thanks for pointing me to Jira. It looks interesting, but not much similar to the kind of API I'm working on. Jira doesn't seem to have a workflow system for orchestrating work between people and systems. Take a look at the <a href="http://www.ibm.com/developerworks/webservices/library/specification/ws-bpel4people/">IBM whitepapers</a> for some more background. Hi Craig,
We have worked wit…tag:www.techhui.com,2008-03-02:1702911:Comment:87472008-03-02T13:27:39.097ZDaniel Leuckhttp://www.techhui.com/profile/dleuck
Hi Craig,<br />
<br />
We have worked with <a href="http://www.atlassian.com/software/jira/">Jira</a>. It has a nice Java plugin API. Note: We are an Atlassian shop, so I am biased. That being said, I have done dozens of installations, and people really seem to like the task management.<br />
<br />
Ive read about BPEL4People, but havent had a chance to work with it.
Hi Craig,<br />
<br />
We have worked with <a href="http://www.atlassian.com/software/jira/">Jira</a>. It has a nice Java plugin API. Note: We are an Atlassian shop, so I am biased. That being said, I have done dozens of installations, and people really seem to like the task management.<br />
<br />
Ive read about BPEL4People, but havent had a chance to work with it.