[JBoss jBPM] - Re: mail node issue
by debnathm
Hi
I have run the following test case and used the
jbpm-starters-kit-3.1.4. Under this environment
it shows the parse warning as mentioned in my post.
The test case is:
package com.jbpm.tutorial.mailtest;
|
| import junit.framework.TestCase;
| import org.jbpm.graph.def.ProcessDefinition;
| import org.jbpm.graph.exe.ProcessInstance;
|
| public class MailTest extends TestCase {
| public void setUp()
| {
|
| }
|
| public void testMail()
| {
| ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
| "<process-definition> " +
| " <start-state name='start'>" +
| " <transition to='mailnode1' name='to_mailnode'></transition>" +
| " </start-state> " +
| " <mail-node name='mailnode1' to='abc(a)mailserver.com' >" +
| " <subject>a</subject> " +
| " <text>This is regarding</text>" +
| " <transition to='end' name='to_end'></transition> " +
| " </mail-node> " +
| "<end-state name='end'></end-state>" +
| "</process-definition>");
|
|
| ProcessInstance processInstance = new ProcessInstance(processDefinition);
| assertEquals(false, processInstance == null);
| }
| }
The warning is :
17:30:11,218 [main] WARN JpdlXmlReader : process xml warning: transition to='mailnode1' on node 'start' cannot be resolved
If you kave any ideas, please let me know.
Debnath
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124031#4124031
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124031
18 years, 3 months
[JBoss Messaging] - Re: Clustered environment with non persistent messages ?
by timfox
The point with non persistent messages, is they are not persisted, ==> they do not survive failure.
Users use non persistent messages when they want higher performance but they can cope with message loss.
If we had to persist non persistent messages too, that would kind of defeat the purpose for their existence! :)
E.g. a stock ticker application would probably use non persistent messages, since market data goes out of date very quickly (sub second) and later messages can supercede earlier messages so you don't care if you lose messages.
If we didn't have non persistent messages and only had persistent messages then we would be losing performance for applications that don't need the reliability
It would be silly if we persisted non persistent messages too - since they wouldn't be non persistent any more.
The JMS spec is quite clear on this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124026#4124026
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124026
18 years, 3 months