[JBoss jBPM] - Re: Modifying a process already in progress
by lfelser
Definitely looking to solve the general case.
In the typical case, the process is not changed once started, but occasionally either the task assignment has to change (prior to the task being assigned) or a new user and new task assigned. Sometimes the task is removed, but that's a relatively easy case that I've got working now.
Some notes:
1) assignments can't be taken from a pool for the tasks. They are very specific and are set up when the process is created (using custom assignment handlers that get the assignment name from the data given in the process definition's XML).
2) each process definition is unique because of the above.
3) we have custom web-based process authoring that allows the process author to assign variable numbers of parallel tasks. The forks and joins are added by my code in this case. While the processes always have the same general sequence, entire sets of nodes may not be created if the process author has decided that those steps are not necessary for a particular case. Being red-blooded human users though, they sometimes change their minds.
LF
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079276#4079276
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079276
18Â years, 7Â months
[Messaging, JMS & JBossMQ] - Re: JBossMQ Remote Client receives java.io.EOFException
by NANJUNDA
Hi ,
I am getting this error when i sent Message which size is big (Around 13MB). here below pasted my exception, Please any one can help me on this ?
DEBUG : 20070829.123141.972 : ServerSocketManagerHandler : UIL2.SocketManager.Re
adTask#11 client=138.8.17.249:32950 : Exiting on IOE
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputSt
ream.java:2666)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:875)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:31
7)
at java.lang.Thread.run(Thread.java:595)
DEBUG : 20070829.123142.464 : BasicQueue : UIL2.SocketManager.ReadTask#11 client
=138.8.17.249:32950 : Nacked 1 messages for removed subscription Subscription[su
bId=-2147483644connection=ConnectionToken:ID:6/d2d5abe2e5cf2bf55a65e2df3c248ee7
destination=QUEUE.SyncMarginRequest messageSelector= Local Create]
DEBUG : 20070829.123142.468 : SocketManager : UIL2.SocketManager.WriteTask#12 cl
ient=138.8.17.249:32950 : End WriteTask.run
DEBUG : 20070829.123142.468 : SocketManager : UIL2.SocketManager.ReadTask#11 cli
ent=138.8.17.249:32950 : End ReadTask.run
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079273#4079273
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079273
18Â years, 7Â months
[JBoss Seam] - Re: iText PDF not working with DocumentStore and SeamServlet
by wquraishi
Woohooo...I got it working. For everyone else that's in this situation, in order to rectify the problem, I simply commented the following:
<!--
<filter-name>Seam Servlet Filter</filter-name>
<filter-class>
org.jboss.seam.servlet.SeamServletFilter
</filter-class>
<filter-mapping>
<filter-name>Seam Servlet Filter</filter-name>
<url-pattern>*.pdf</url-pattern>
</filter-mapping>
-->
<servlet-name>Document Store Servlet</servlet-name>
<servlet-class>
org.jboss.seam.pdf.DocumentStoreServlet
</servlet-class>
<servlet-mapping>
<servlet-name>Document Store Servlet</servlet-name>
<url-pattern>*.pdf</url-pattern>
</servlet-mapping>
I think it had to do with the two URL mappings both pointing to *.pdf. The one commented out was in the web.xml by default when creating an application using seam-gen.
So for everyone else, that starts of using inline PDF and then switches to using the link, you MUST comment out the code above.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079272#4079272
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079272
18Â years, 7Â months