[JBoss jBPM] - Re: How to invoke a business process in JBoss
by kukeltje
No answers? I'll only respond to one thing now, the 3.0.3/3.1.1 thing.
The moment you mentioned you were using 3.03 instead of the latest 3.1.x you got an answer that 3.03 and 3.1 are different. If you had stated that earlier, you would have gotten a more specific response. Still then, the examples/testcases that come with the 3.03 source clearly show how to use the api.
I'll let Tom/Koen respond to the other questions (Assuming you've read the fine document about posting smart questions) and if they want me to stop answering questions, I will, certainly. I do not want my personal attitude to have a negative impact on JBoss, so that is up to them.
In the future, I'll *not* respond to *any* basic questions again.
May the source be with you
_________________
Ronald
Former jBPM forum moderator
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957053#3957053
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957053
19 years, 9 months
[JBoss Seam] - Re: Breaking changes to pageflow
by rpiaggio
Ok, solved the problem.
The ClassCastException seems to happen when the flow cannot land on a page. In this case, the problem of not working on the page action seemed to derive from having an unnamed transition on the start-state. This would match on a normal action but not on the page action. This is how the pageflow and code looked like:
| <start-state name="start">
| <transition to="selectSource">
| <action expression="#{sourceManager.selectSource}"/>
| </transition>
| </start-state>
|
@Begin(pageflow="PaymentAuthorization")
| public void start() {
| }
|
Everything worked OK when I changed to:
<start-state name="start">
| <transition name="proceed" to="selectSource">
| <action expression="#{sourceManager.selectSource}"/>
| </transition>
| </start-state> @Begin(pageflow="PaymentAuthorization")
| public String start() {
| return "proceed";
| }
|
If this is a bug, it's a very minor one.
Actually, I think that having an unnamed transition should make it the default one, and should always be triggered when all other transitions don't match. This would ensure the pageflow always works. Any opinions on this feature request before I JIRA it?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957052#3957052
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957052
19 years, 9 months
[Performance Tuning] - Re: Performance Disapointment
by pferreira
Sorry for the repetition but I pressed submit before I finished :P
---
I'm running a custom benchmark which simulates an intensive database access to a J2EE aplication I've migrated from OpenEJB 1.4 + Tomcat 5.0 to JBossAS 4.0.4:
A single client, requesting 1, 10, 100, 1000 and 10000 ocurrences of the test case;
Multiple clients (1, 10 and 100 threads) requesting 1, 10 and 100 ocurrences of the test case (to test the connection pool).
The results I've got so far are very disappointing. JBoss is up to 2 x slower than OpenEJB + Tomcat 5.0 (in my test, of course).
The J2EE aplication uses the DAO pattern for persistence.
The DBMS is MS SQL Server 2000 and I'm using the jTDS driver.
The test case simulates a set typical uses for the aplication (only reads).
I've made some optimizations (log4j level = ERROR & file only) but it doesn't seem to have a significant impact on the performance.
Any suggestions / questions / help would be apreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957048#3957048
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957048
19 years, 9 months