JMS Connection To Human Task

I am creating a human task application that receives messages request from JMS
input queue. The application  introspect the XML message, retrieve the requester
userid and then create the human task with the requester as the task start (task
initiator). <br />
<br />

That is a good question.  My understanding is that Task Owners can be changed
... but the Task Initiator is the identity of the user who created the task.  In
the SCA world, I am not aware of any supported mechanism for programatically
"becoming" a specificly named user.  When a request arrives at a
Export component in a Module, I am assuming that the module will run with the
identity of the user that sumitted the request (if one exists).  For example,
the JMS userid property.  But if I hear you correctly, the userid you want is
not the one who submitted the JMS message but rather the userid which was
extracted as data from the payload of the message.<br />
<br />
When we look at the API for Human Task management, there are no APIs to say
"Do this work on behalf of this user" ... rather the APIs work from
the context of the incoming request as the current identity.<br />
<br />
One potential solution to your problem would be to create an EJB that creates a
Human Task.  In the EJB code, you can perform an explicit "sign-on"
assuming the userid and password are available.  Then you can make the API calls
to create the task.<br />
<br />

Kolban,



What a response? Thanks a lot for the thought. I am also thinking of maybe
receiving the request and in-turn, call a web services export with JAX-RPC
Handler attached to it. My thinking is that the Security would be added in the
SOAP header prior.