[JBoss jBPM] - Re: TaskInstance.setActorId(String) causes set TaskInstance
by Octomac
Thanks for your responses so far, Salaboy.
The reason I elected to use a single "dummy" ActorID instead of a group of pooled actors is that this will be a long-running application, and people come and go from different departments often enough that maintaining a list of available pooled actors for each task will be difficult. For instance, if persons A, B, and C are all in the list of pooled actors for a task X, they would all see X in their list of available tasks. However, if person D joins the group before X is taken by either A, B, or C, he will not see that task as available, because he is not in the list of pooled actors available for task X. D would only be able to see available tasks that were created after he'd been added to the system. It was considered less maintenance to simply have a single user ID, such as "Accounting" or "Provisioning" to represent groups of people, and then tell JBPM to fetch all tasks with those ActorIDs as available tasks for people in those groups.
This much seems to be working correctly, but I am still experiencing the two problems from my first post. For one, whenever I reassign a task, it is canceled. For two, my changes are not shown in the user interface until I redeploy the application, even though those same changes are shown in the database; JBPM continues to use old data.
Thanks for the help so far, and if you have any other suggestions, I would greatly appreciate it!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157794#4157794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157794
18 years, 1 month
[JBoss Messaging] - Re: Clearing up confussion
by timfox
"ejb3workshop" wrote : Maybe I didn't explain is correctly. I am sending a message as well as persisting and entity. Since I would like to use XA, I'd expect both to succeed. For this to be the case the entity should be persisted and the message should be placed on the queue. However the message is already being received on the other end by the next bean, while the entity is not yet persisted.
|
Yes, that can happen with XA even though they are both in the same tx!
This is what happens (simplified):
1. JTA tx starts to commit
2. Commit called on jms xa resource - message gets sent
3. Commit called on db xa resource - row gets stored in DB
4. JTA tx has finished committing
Now, between 2 and 3 since it takes a finite time, the message can hit the queue, get consumed, and the consumer won't find the row in the db since the original tx has not finished committing yet.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157789#4157789
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157789
18 years, 1 month
[JBoss Portal] - specifying javascript location in portal-themes.xml
by rohit000
Hi,
The theme I'm using for portal has CSS which depends a lot on javascripts.
I'm specifying the javascript sources in portal-themes.xml. Also packaging those javascripts in the same theme folders where the css files reside. This is specificaly based on the guideliens given in Reference Guide document where it is said that 'A Portal theme is collection of CSS, javascript and images' (section 24.5.1).
However, the problem I'm facing in this is though I've put the CSS declarations before javascript declaration in the portal-themes.xml, the javascript is getting loaded before the css and it is causing problem in the UI behaviour.
Need some opinion/vision on -
a) Why javascript is getting loaded before css ? Is this a bug ? Is there a work around to make it otherway ?
b) Confirmation on packaging javascript in theme along with css and image
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157779#4157779
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157779
18 years, 1 month
[Persistence, JBoss/CMP, Hibernate, Database] - Evicting via the JBoss JMX console
by kevinstembridge
Hi all,
Is it possible to use the JBoss JMX console to evict individual objects from the Hibernate 2nd-level cache?
I've managed to evict all instances of a single class but I can't find a syntax that will allow me to evict just one instance.
So, for a class named com.mycompany.MyClass with a primary key of 12345, I get a node in the cache that looks like /com/mycompany/MyClass/com.mycompany.MyClass#12345.
Via the JMX console I am able to evict all instances of this class by invoking the remove() method on the TreeCache MBean with the input value com/mycompany/MyClass. But when I provide the value /com/mycompany/MyClass/com.mycompany.MyClass#12345, nothing happens. I've tried various other syntaxes as well, such as escaping dots with backslashes, replacing dots with slashes and using double quotes. No luck though.
Any help would be great.
Thanks,
Kevin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157778#4157778
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157778
18 years, 1 month