[Design of JBoss jBPM] - Re: added job executor servlet to the jbpm-console.war
by david.lloyd@jboss.com
"david.lloyd(a)jboss.com" wrote : "tom.baeyens(a)jboss.com" wrote : david, i assume that you want to uncomment the servlet while you're developing. can you figure out a way to do this with a separate target in the console/build.xml somewhere ? you can have a look at enterprise/ear/build.xml for an example of how to comment out the job servlet with an ant script. i would like the default build target to keep the job executor servlet in the console web application. especially since the default targets will be used for automatic testing.
|
| It wasn't anything even that complex... I noticed that the jars were already in the server classpath so I commented them out figuring they may not be needed. I have no problem at all putting them back in.
Whoops, ignore that. I completely misread your post :)
I can figure out something for development.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982409#3982409
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982409
18 years, 2 months
[Design of JBoss jBPM] - Re: Web console enhancements
by david.lloyd@jboss.com
"tom.baeyens(a)jboss.com" wrote : Works out of the box for me now. Thanks.
|
| Awsome look and feel ! A core developer with a great sense for colors: that is unique and just what we needed.
Thanks... I tried to focus more on function than appearance but I really wanted to update it to the Red Hat color scheme to some degree.
"tom.baeyens(a)jboss.com" wrote : One thing i would do different was the filtercriteria on the task lists; i would put that underneath or at the right of the actual list.
Yeah, I debated about that one for a while, and I think I tend to agree.
"tom.baeyens(a)jboss.com" wrote : A planning note: In this month, we should try to finish a certain the feature set we have now and decorate all the loose ends that we've got. So that after this month, there is a web app in which simple navigation, doesn't lead to stack traces. I don't mind if there are: "this page is not yet implemented" kind of pages.
|
| Then in december we should go for stabilization and bug fixing.
Ok, sounds like a good plan.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982361#3982361
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982361
18 years, 2 months
[Design of JBoss jBPM] - enterprise test set up
by tom.baeyens@jboss.com
i have completed the first enterprise test set up.
as a prerequisite, a jboss should be installed with a jbpm server configuration and some jbpm deployments. this can be created with the jboss/configuration/build.xml, target install.jboss.and.configure.jbpm
then, the test stuff is added to the enterprise/ear subproject. there is a target called test.serverside. that script will do the following:
1) build the normal .ear first.
2) unzip it
3) add a jbpm-test.war with cactus based junit tests
4) repackage this into a new .ear file jbpm-test.ear
5) deploy this .ear file to jboss using jmx
6) run the cactus tests in jboss
7) generate the html test report
8) on windows, a browser is automatically opened to view the test results
that should help in developing, testing and guarding the enterprise confiugrations of jbpm usage.
next i will be adding actual tests that will check for the proper operation of asynchronous continuations over a jms based messaging service.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982357#3982357
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982357
18 years, 2 months