i have met same question .and so many people met same question. could you please to provide a standard sample with PIPA.

Post edited by: sanswordke, at: 2006/12/07 19:52

Eric,
Fasten here fundamental sample for PIPA in which I’m capable to deploy and execute this without any flaws in the most recent versions.

Please let me how it works for you!


Thanks,
Shivanand.

Hi there- I got the same problem-
When loggin in as msmith, the screen shows:
Error:Error while retrieving tasks
I have almost given up on making the time example work so have moved on to this one. I got 'Hello World' to work from start to finish and thats about it. Geronimo Log below (could not attach)

Also- I have tried the example you attached. Still same error.

The Intial problem with the deployment batch file was fixed by removing the whitespace (HTTP 400 erro in Cmd line)
Editing the supplied XML in the descriptor file to remoe the whitespace seems to have fixed it. Maybe edit the example?
-Shawn

Post edited by: sbougheyasfa, at: 2006/12/11 19:46

4611: 14:47:00,485 ERROR [TasksAction] org.apache.axis2.AxisFault: unknown
4612: org.intalio.tempo.workflow.tms.client.RemoteTMSException: org.apache.axis2.AxisFault: unknown
4613: at org.intalio.tempo.workflow.tms.client.RemoteTMSClient.sendRequest(RemoteTMSClient.java:91)
4614: at org.intalio.tempo.workflow.tms.client.RemoteTMSClient.getTaskList(RemoteTMSClient.java:105)
4615: at org.intalio.tempo.uiframework.actions.TasksAction.retrieveTasks(TasksAction.java:207)
4616: at org.intalio.tempo.uiframework.actions.TasksAction.execute(TasksAction.java:224)
4617: at com.intalio.bpms.web.controller.Action.doExecution(Action.java:156)
4618: at org.intalio.tempo.uiframework.SecuredController.showForm(SecuredController.java:73)
4619: at org.springframework.web.servlet.mvc.AbstractFormController.showNewForm(AbstractFormController.java:324)
4620: at org.springframework.web.servlet.mvc.AbstractFormController.handleRequestInternal(AbstractFormController.java:264)
4621: at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:139)
4622: at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
4623: at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:717)
4624: at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:658)
4625: at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:392)
4626: at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:347)
4627: at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
4628: at com.intalio.bpms.web.SpringDispatcherServlet.service(SpringDispatcherServlet.java:38)
4629: at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
4630: at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
4631: at org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:104)
4632: at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
4633: at org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
4634: at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
4635: at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
4636: at org.apache.geronimo.jetty.JettyWebApplicationHandler.dispatch(JettyWebApplicationHandler.java:59)
4637: at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
4638: at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
4639: at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
4640: at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
4641: at org.mortbay.http.HttpServer.service(HttpServer.java:909)
4642: at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
4643: at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
4644: at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
4645: at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
4646: at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
4647: at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
4648: Caused by: org.apache.axis2.AxisFault: unknown
4649: at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287)
4650: at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:457)
4651: at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:399)
4652: at org.intalio.tempo.workflow.tms.client.RemoteTMSClient.sendRequest(RemoteTMSClient.java:88)
4653: ... 34 more
4654: Caused by: java.lang.Exception: org.apache.axis2.AxisFault
4655: at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:102)
4656: at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
4657: at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
4658: at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
4659: at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
4660: at javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
4661: at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
4662: at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
4663: at org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:104)
4664: at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
4665: at org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:170)
4666: at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
4667: at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
4668: at org.apache.geronimo.jetty.JettyWebApplicationHandler.dispatch(JettyWebApplicationHandler.java:59)
4669: at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
4670: at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
4671: at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
4672: at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
4673: at org.mortbay.http.HttpServer.service(HttpServer.java:909)
4674: at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
4675: at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
4676: at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
4677: at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
4678: at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
4679: at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
4680:
4681: at org.apache.axis2.AxisFault.<init>(AxisFault.java:159)
4682: ... 38 more

Post edited by: sbougheyasfa, at: 2006/12/11 19:47

Post edited by: sbougheyasfa, at: 2006/12/11 20:14

Shawn,
Have you tried this process deployment/execution with an unsullied bpms installation?


Thanks,
Shivanand.

HI , i deployed your PIPA and it could be run successfully , thank you very much , but i really want to know why my PIPA can't run and what difference is in both two PIPA , as you know there are so many people met this problem , should you improve a detailed guide for us.

Post edited by: sanswordke, at: 2006/12/11 21:03

In view of the fact that, to create deployment descriptor for the process you need to confirm with the wsdl file generated while process deployment.


Thanks,
Shivanand.

I have re-installed the server and got YOUR example working. I will re-try getting MY example to work, by working through the tutorials. Have not been able to get any of the tutorials to work from my side.
I'll let you know how it goes. Thanks for your help.

-Shawn

I Have tried to re-work the example on a freshly installed server. All seems fine untill I login as msmith, and then I get the "Error while retireving tasks". Logging in as msmith and running the Absence Request worked before this, so I believe this should mean my environment is OK. I ran the wds-cli.bat routine without error. Please help!

I have compared your PIPA.xform.complete.wsdl with mine and hav found a difference: In the namespace, yours has:
targetNamespace="http://www.intalio.com/bpms/workflow/xforms/PIPA/PIPA"


Mine has

targetNamespace="http://www.intalio.com/bpms/workflow/xforms/PIPA"

Could this account for the problems I'm having? How did you get this result (these files are auto-generated by the dessigner).
-S

Also found a difference in your PIPA.xform.xsd file vs mine:
Yours has a node:
<xs:element name="input32" type="xs:boolean"/>
Whereas mine doesn't.



PS - If you could Tell Me what you changed when you fixed it that would be more helpfull than fixing it yourself.

Post edited by: sbougheyasfa, at: 2006/12/12 15:50

Post edited by: sbougheyasfa, at: 2006/12/12 16:36

Found it!
That was the problem:
The provided example used a different namespace for the form than the one I used.
I recommend checking all of the namespaces that are generated based on the file locations used at the time of creating the forms.
Also to use a new 'workspace' each time you are trying so that the file metadata from the last attempt does not conflict.
I don't quite understand the problem 100%, but it does have to do with the autogenerated namespaces, and I have maanged to fix it in my example.
Thanks again for your help!
On to the next one!

Cheers-
Shawn

Shawn,
Its very nice to hear from you as you resolved the issue for PIPA process execution.


Thanks,
Shivanand.