[JBoss jBPM] - Re: Inputting context variables to actions
by kukeltje
James, one tip: the search in the forum is an OR so you should put an AND between it, or use the other radiobutton.
Second tip: Look at the testcases. There are lots, and prove to be a valuable source of information (not documenation if you followed the 'other' thread ;-)
You will find things like
| ProcessInstance processInstance = new ProcessInstance(processDefinition);
| processInstance.signal();
|
| TaskMgmtInstance taskMgmtInstance = processInstance.getTaskMgmtInstance();
| TaskInstance changeNappy = (TaskInstance) taskMgmtInstance.getTaskInstances().iterator().next();
| SwimlaneInstance stalker = taskMgmtInstance.getSwimlaneInstance("stalker");
| assertEquals("me", stalker.getActorId());
| assertEquals("me", changeNappy.getActorId())
|
|
The apidocs is also a valuable source of information
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960044#3960044
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960044
19 years, 9 months
[JBoss jBPM] - Re: org.hibernate.engine.StatefulPersistenceContext.ProxyWar
by kukeltje
Do you see the contradiction here?
anonymous wrote : This is a public forum, and one can post whatever one wants!
Besides the fact that I have a different opinion, I choose to post whatever I wanted so.
And no, I did not have to reply BUT YOU SHOULD HAVE THOUGHT AND SEARCHED BEFORE POSTING.
Besides that. You give WAY to little information on your environment (another misdemeanour IMNSHO). So who started this 'inappropriate' stuff?
And by referincing 'the' book again, which is btw not MY book but based on lots of earlier experiences by other people anonymous wrote : Remember: When that hacker tells you that you've screwed up, and (no matter how gruffly) tells you not to do it again, he's acting out of concern for (1) you and (2) his community. It would be much easier for him to ignore you and filter you out of his life. If you can't manage to be grateful, at least have a little dignity, don't whine, and don't expect to be treated like a fragile doll just because you're a newcomer with a theatrically hypersensitive soul and delusions of entitlement.
|
You only point to me... he, he, he, you, you, you.... where is the I? Oh here it is I DID give you the answer, right? So Therefor I DID have to reply.
Oh and btw, how corteous to remain anonymous...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960039#3960039
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960039
19 years, 9 months
[JBoss Seam] - Re: Proper way to instantiate seam managed component
by iradix
anonymous wrote : You should really use Component.getInstance(), not Component.newInstance().
The problem with getInstance() is after I create the first instance subsequent calls will retrieve the same instance from whatever context it was published to. I need seperate, unique instances of the same bean and from a quick look through the code newInstance() was the only way to accomplish that.
anonymous wrote :
| Are you saying that when you do that, the Log does not get injected?
That's exactly what I'm saying, although after I changed the definition from
@Logger private Log log
To
| private Log log = new LogImpl(ClassName.class)
It started working even though it extends an abstract class that also uses Logger injection. In other words, the subclass seems to correctly recieve a Log instance but the superclass does not. Maybe it's a bug in Component where a Log is only injected into the first annotation along the class heirarchy?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960037#3960037
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960037
19 years, 9 months