hi, I'd need a little help with this one:
I'd like to print all comments of a node in an email template, like this:
| <mail-templates>
| <mail-template name="error-report">
| <subject>Error in process '#{processDefinition.name}'</subject>
| <text>
| Process: #{processDefinition.name} id = #{processInstance.id}
|
| Variables:
| #{contextInstance.variables}
|
| Comments:
| #{token.comments}
| </text>
| </mail-template>
| </mail-templates>
|
now how to express to print all elements of "token.comments"? in JSP you could do a "foreach", but how in jpdl? thanks for any kind of help,
alex
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051293#4051293
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051293
Jon,
If the child processes are really trivial, and you don't need to be able to deploy new versions of them independently, then maybe just fork. Otherwise, probably subprocess.
Another thing to consider is what monitoring and/or intervention you will need on the child processes. If you need to examine and/or change variables at the child process level, subprocesses may be easier.
Forking is probably more efficient, but I don't know how much, or whether it's significant in your context.
There are probably other factors I'm not thinking of. You really need to look at your own requirements first.
-Ed Staub
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051292#4051292
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051292
The beans are pooled inside the ThreadlocalPool. This means that each remoting thread is given an instance when asked. Depending on how many remoting threads you have it can take a while for the whole ThreadlocalPool to fill up.
You can switch to a more traditional pool: StrictMaxPool, but this does introduce congestion on the semaphore regulating the pool.
A completely different approach would be to optimize cache usage of your entities.
Commonly the PostConstruct is only used for setting up resource connections to slow XA resources. You shouldn't store any data there that is common accross multiple stateless beans or data that is really state.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051288#4051288
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051288