[jBPM] New message: "Re: How to invoke applications in a task activity"
by Ronald van Kuijk
User development,
A new message was posted in the thread "How to invoke applications in a task activity":
http://community.jboss.org/message/524025#524025
Author : Ronald van Kuijk
Profile : http://community.jboss.org/people/kukeltje
Message:
--------------------------------------------------------------
> Can JSP be used for a taskform?
Yes, but NOT in the (j)BPM console, at least not easily
> What does mean a actionhandler that fires a jBPM event?
A piece of javacode (See the link e.g. of the jsf actionhandler, jsf bean, but this could als be a struts action or whatever) using the jBPM api (well, with one cast) to have some java code run in jBPM
> When should the method you talk about in ExecutionService be invoked, if this methode would be provided?
Whenever you think it is needed... I cannot decide that for you.
> I don't really understand your concept.
You want at the push of a button to have some java code in jBPM that is related to a task to be executed
button = html (jsp,jsf, ....)
actionhandler = javacode on serverside that belongs to jsf
eventlistener = javacode in jBPM that can belong to a task definition (triggered by fireing an event)
That is the concept...
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524025#524025
16 years, 2 months
[jBPM] New message: "Re: Upgrade from JBPM3 to JBPM4 woes"
by nick bauman
User development,
A new message was posted in the thread "Upgrade from JBPM3 to JBPM4 woes":
http://community.jboss.org/message/524023#524023
Author : nick bauman
Profile : http://community.jboss.org/people/nick.bauman
Message:
--------------------------------------------------------------
Thanks Ronald,
That's too bad. We're blazing a trail with what we can get compiling and passing tests, hoping your warnings aren't going to be showstoppers.
Well, we interact directly with the ProcessInstance on workflow start. We also have a couple of places where external timers work with processes in progress.
Specifically what we do in v3:
Node currentWaitState = pi.getRootToken().getNode();
for (int i = 0; i < timedNodes.length; i++) {
if (timedNodes[i].equals(currentWaitState.getName())) {
// Can we get out of here?
if (currentWaitState.hasLeavingTransition(TIME_OUT)) {
pi.signal(TIME_OUT);
return;
}
// Misconfigured process definition
throw new RuntimeException("Workflow timed out on current state, but no corresponding timeout transition found.");
}
}
log.debug("Workflow departed any timed state.");
Not sure how we sort that atm for v4. v3 was much more "hackable", and I mean that in a good way. The model was pretty small and coherent: the only thing that didn't make a lot of sense was why you have Node and State. Should be just State is a non-transient and Node is a transient state. IOW a boolean would have worked, my $0.02.
Spring integration: What worked well with us was making various adaptors for Spring DI into a process defintion where JbpmTemplate was less than perfect.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524023#524023
16 years, 2 months
[JBoss Tools] New message: "Re: Adding JBoss AS source to a project"
by henk de boer
User development,
A new message was posted in the thread "Adding JBoss AS source to a project":
http://community.jboss.org/message/524020#524020
Author : henk de boer
Profile : http://community.jboss.org/people/henk53
Message:
--------------------------------------------------------------
> mailto:max.andersen@jboss.com wrote:
> > dgolovin wrote:
> >
> > It looks like launch configuration for server should be altered after project deployed/undeployed to/from the server. WTP JBoss AS adapter does that but JBossTools JBossAS adapter doesn't.
> hmm - I would be surprised if the wtp adapters does that...it sounds wrong.
I'm of course not 100% sure whether that is what is technically happening under the hood, but the UI surely does suggest this is what happening. The screenshots posted by Denis Golovin show that and I observed the exact same thing as I described earlier. I haven't yet tested with the latest nightly build of Jboss Tools, I used 3.1 CR1.
When my project is not deployed to the wtp adapter, the launch config contains only the JDK jars. With the project deployed, my project folders are there as well as all the Jboss jars. At any length, whatever is happening, the wtp adapter gives me the source of my own files in the debugger while the jboss tools adapter doesn't.
I also vaguely remember that the MyEclipse deployer does a similar thing; adding the project's libs and folders to the launch configuration.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524020#524020
16 years, 2 months
[JBoss Tools] Document updated/added: "JBossToolsGeneralFAQ"
by Denis Golovin
User development,
The document "JBossToolsGeneralFAQ", was updated Feb 3, 2010
by Denis Golovin.
To view the document, visit:
http://community.jboss.org/docs/DOC-10797#cf
Document:
--------------------------------------------------------------
h1. JBoss Tools General FAQ
h2. Read this before adding an entry
This FAQ is intended to provide information on the everyday use of JBoss Tools. Questions related to installation are addressed http://www.jboss.org/community/docs/DOC-10799. There are many posts in the http://www.jboss.org/index.html?module=bb&op=viewforum&f=162 that are related to the subject, so it is a good place to gather the experience of the community. Please, follow the format of this page's setup and don't duplicate information.
h3. *Q:* Why is it called JBoss Tools when it's a set of plug-ins for Eclipse?
*A:* Eclipse is NOT an IDE but an application framework. It is a container for plug-ins, like JBoss is a container for MBeans. And as the J2EE support of JBoss is just an MBean, the Java-IDE of Eclipse is just a set of plug-ins. In both cases, it will become clearer and clearer in the future that the scope is much broader. IBM is thinking about using Eclipse as a framework for all(!) of their future applications. And that's how we see Eclipse and the people from Eclipse see it. (Have a look at the http://www.eclipse.org/articles/Article-Branding/branding-your-applicatio... that are based on Eclipse.) IBM's Websphere Studio Application Developer is a set of plug-ins (something like 500) on top of Eclipse and it's (of course) a product by itself. We're starting smaller (-: but nevertheless...
h3. Q: Do you plan to integrate with IDE's not based on Eclipse?
*A:* No. There are other projects that care of that.
h3. Q: It doesn't install or work correctly !!!
*A:* First of all, don't panic. Second, ask yourself if you haven't made a mistake. If you can't solve your own problem, take a look at the http://community.jboss.org/en/jbosstools. There are plenty of answers for the most common problems. Please, use search to find answer to your question and if it doesn't help start a new discussion.
h3. Q: I found a bug, what should I do?
*A:* File a bug report on https://jira.jboss.org/jira/browse/JBIDE. Be sure to put everything needed to correct the bug: OS, Eclipse version, component version, JVM version, and the steps to reproduce the bug. It is even better if you provide a patch.
h3. Q: What is the difference between stable, development and nightly versions?
*A:* *+Stable version+* means that it went through full quality control cycle, it had enough real-world testing and has no significant problems, that's why this version is recommended for every day development. *+Development version+* is a step on the way from one stable version to another. Usually there are several development versions between two stable versions. Each development version also goes though full quality control cycle and real-world testing, thus it is also good enough to use as every day tool, but it can contain unfinished functionality and unknown problems.
*+Nightly version+* is is built form most recent sources every day or even several times a day. This version doesn't go through full quality control cycle and you might be first person who gives it real-word testing, so it sure contains unknown problems and also might be not so good for every day development. It is good for those developers who wants to be on the edge of technology to try out fresh features and give a feedback to the development team on early stages of development.
h3. Q: Where can I find sources for this project?
*A:* Sources are available on download site for every stable, development or nightly build as zip archive with all sources included. Follow the links in "Downloads" part http://www.jboss.org/tools/download.html and then look for "All Sources" part in download page. Sources also are available form public Subversion repository: https://anonsvn.jboss.org/repos/jbosstools.
h3. Q: I have an idea about new feature, what should I do?
*A:* The better way for that is open an discussion about new feature in JBossTools Forum and then create a Feature Request in JBossTools JIRA project based on forum feedback from developers.
h3. Q: Why is better to request new feature throug JBossTools Forum?
A: JBossTools is a composition of several depended components and number of components grows in each new version. It is not easy to collect all required information like: affected component, affected version, summary, description, environment, use case to create JIRA issue. If you go right to the JIRA, you are on your own and most likely your New Feature request will produce discussion in JIRA to fill all required fields with right information. That usually makes JIRA issue less clear and thus it takes more time to fix or implement. If you started from discussion on forum, the development team will help you out to clarify all information you need and in most cases will open JIRA issue for you
h3.
--------------------------------------------------------------
16 years, 2 months
[JBoss Tools] New message: "Re: Error in Eclipse when adding server, saving properties, and publishing"
by Pedro Gomes
User development,
A new message was posted in the thread "Error in Eclipse when adding server, saving properties, and publishing":
http://community.jboss.org/message/524017#524017
Author : Pedro Gomes
Profile : http://community.jboss.org/people/PedroGomes
Message:
--------------------------------------------------------------
What OSGi bundel did you add?
The bundle that I was adding was simply a group of interfaces and classes made by me in Eclipse and exported throught the "export plug-in and fragments" menu. Then Execution Environment: JavaSE-1.6
I don't know what extra info to give.
What is the version for org.jboss.tools.jmx.core and org.jboss.tools.jmx.ui plugins?
The actual version is : 1.1.0.v200910281724M-H247-M4
As I said, I have updated some plugins through the manager, I don't know if this was the version, when the bug happened (by the version date it seems so).
http://community.jboss.org/people/mareshkau:
I didn't try the reinstall through the zip, because I have work to deliver, so I didn't have time, sorry.
I'a already working in another folder of Eclipse, but I maintained the old one, if you want other information.
Thanks for your time
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524017#524017
16 years, 2 months