-
1. Re: #{taskInstance} is null on Notify='yes'
james_hays May 29, 2007 11:05 AM (in response to james_hays)Has anybody had success in working with the notify='yes' attribute? If so, could you post an example?
Thanks, -
2. Re: #{taskInstance} is null on Notify='yes'
james_hays Jun 5, 2007 3:05 PM (in response to james_hays)I'm stilling running into issues with jBPM's notify feature. Can anybody from jboss verify that this is an issue, or point me to an example?
Thanks, -
3. Re: #{taskInstance} is null on Notify='yes'
kukeltje Jun 5, 2007 8:14 PM (in response to james_hays)did you look at the testcases?
-
4. Re: #{taskInstance} is null on Notify='yes'
james_hays Jun 6, 2007 1:16 PM (in response to james_hays)Yes, I did. The tests dealing with Mail failed. This from from CVS on 5/25/2007. I updated CVS to 6/6/2007 and it is still failing.
junit.framework.AssertionFailedError
at org.jbpm.mail.TaskMailTest.testTaskInstanceNotification(TaskMailTest.java:78)
junit.framework.AssertionFailedError
at org.jbpm.mail.TaskMailTest.testTaskInstanceReminder(TaskMailTest.java:140)
I'm not 100% sure this isn't a local issue, though my symantic filter is saying that the email address I'm sending to is invalid or null. Which is the same issue I was having when I first posted. -
5. Re: #{taskInstance} is null on Notify='yes'
james_hays Jun 7, 2007 3:31 PM (in response to james_hays)Should this be added as a Jira issue? I didn't find anything in there regarding this.
-
6. Re: #{taskInstance} is null on Notify='yes'
james_hays Jun 7, 2007 6:18 PM (in response to james_hays)I've dumped the notify='yes' for an event that fires on "task-assign" so I can do more debugging. I've verified that taskInstance is not being injected, but I can inject processInstance into my POJO in my seam app. Inside processInstance, I can dig down in the object to get the taskInstance and the data in there is correct.
any more thought from the jboss crew? -
7. Re: #{taskInstance} is null on Notify='yes'
kukeltje Jun 8, 2007 3:42 AM (in response to james_hays)where does seam come from? Did you use that from the beginning? I cannot help further then, since I have no knowlegde about the seam/jbpm integration
-
8. Re: #{taskInstance} is null on Notify='yes'
james_hays Jun 8, 2007 9:38 AM (in response to james_hays)Yes, this is a full seam app with jBPM integration. I will start posting in the seam forum as well on this issue. I would have a hard time seeing that this is a seam issue since I initially had the issue when using notify="yes" and the mail templates.
I'll post over there and cross reference this thread and see if anything develops. -
9. Re: #{taskInstance} is null on Notify='yes'
james_hays Jun 26, 2007 3:41 PM (in response to james_hays)So, it's been awhile since I last worked on this issue, but I'm not back on it and using the latest jBPM 3.2.1
Just to clarify,
Yes, this is a SEAM/jBPM application. All seam is doing in this instance is creating/starting the process. As far as I understand, everything should now be internal to jBPM. My mail template is the same as the tests, but when it comes across any EL that deals with #{taskInstance}, I get a null result.
Any help would be appreciated. Everything from my fist post is still valid.
Thanks, -
10. Re: #{taskInstance} is null on Notify='yes'
kukeltje Jun 26, 2007 7:33 PM (in response to james_hays)James,
If you can provide a unit test that I can run out of the box and that demonstrates the problem, I can look into it. It would take to much time for me to create a test case for this. -
11. Re: #{taskInstance} is null on Notify='yes'
tom.baeyens Jul 2, 2007 3:22 AM (in response to james_hays) -
12. Re: #{taskInstance} is null on Notify='yes'
koen.aers Jul 6, 2007 5:18 AM (in response to james_hays)"james_hays@mac.com" wrote:
Yes, I did. The tests dealing with Mail failed. This from from CVS on 5/25/2007. I updated CVS to 6/6/2007 and it is still failing.
junit.framework.AssertionFailedError
at org.jbpm.mail.TaskMailTest.testTaskInstanceNotification(TaskMailTest.java:78)
junit.framework.AssertionFailedError
at org.jbpm.mail.TaskMailTest.testTaskInstanceReminder(TaskMailTest.java:140)
I'm not 100% sure this isn't a local issue, though my symantic filter is saying that the email address I'm sending to is invalid or null. Which is the same issue I was having when I first posted.
James, were you able to run these tests in the meantime? On my box they give green light. If you are able to run them and the issue still remains we have to dig deeper.
Regards,
Koen -
13. Re: #{taskInstance} is null on Notify='yes'
james_hays Jul 6, 2007 11:08 AM (in response to james_hays)I will attempt to pull the latest from CVS and run the tests again. Does anybody have a simple demo application that shows this working? I'd love to be able to say this is simply my environment or a configuration. I can only show it not working.