[JBoss Seam] - Re: Running the booking example on JBoss with the JSF 1.2 RI
by stan.silvertï¼ jboss.com
Yes, we need new threads for this stuff. You have different issues. Can each of you start a new thread with all relevant info? I'll do my best to help you. When you are done, post links here.
Note that for JBoss 5.0, this is beta code. I've also noticed that hot deploy is a little flaky. You might need to restart the server sometimes instead of using hot deploy. Sometimes, if it doesn't hot deploy you can hit Ctrl-C in the server window and it will start deploying.
Also, there are lots of configuration and deployment issues with JSF right now. The main reason is that we are moving away from the old deployment model where you had to bundle and configure a lot of things inside your WAR. With JBoss 4.2 and JBoss 5, a lot of this (plus new functionality) is done automatically by the container. If you try to do things the old way, it often won't work.
So please help me out where you can. I want to make sure that documentation is clear for this stuff. Please let me know how we can make the wiki better or how we can better communicate the changes.
BTW, the wiki for JSF starts here: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces
Thanks,
Stan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021624#4021624
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021624
19Â years, 1Â month
[JBoss jBPM] - Re: jbpmContext in Web Application
by symmetrysolutions
OK, I agree with your last comment (not to imply that I disagreed with other comments) since I would only store information that is relevant to process flow in a task or process variable. All other information would be stored using my own persistence of my own domain objects.
You mentioned "Copying them over should not be for you to worry, but the container and api of the engine (and it does that for you). Variables for tasks are stored separately and only when ' committed' (task is finished) they are copied to the processlevel again.... so I do not see a problem here."
You mean copying them from the task to the process instance?
But if I can not hold on to a task across contexts then I have to copy any working task variables out of the task and into my own session container, is that correct?
Again, I guess this is not that big of a deal since I would not use the task or process instance as a container for application data only for values that are relevant to process flow.
The BPM engine that I have been using has a logon/logoff session model and I guess I just got used to being able to retain whatever process objects I wanted in the session. It is just a matter of understanding jBPM operational requirements and changing my thinking. Your comments have been helpful.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021610#4021610
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021610
19Â years, 1Â month