anonymous wrote : Please learn how to use an appserver before posting (sorry if I sound
grumpy, it has been a busy week)
|
This touches on an important issue - so many deep technologies are involved, unless you
know them cold, you're flying blind to a large extent.
Developers who don't know app servers inside out could really use a lot more
procedural explanations of how things work to help get oriented. For example: 1) request
is posted by browser to Tomcat, 2) tomcat hands off request to servlet, 3) servlet blah
blah blah... I know it isn't easy to find an appropriate level of explanation for
everyone, but just some kind of explanation of how the thing works as a mechanism would
help.
Generally all the documentation describes objects and configuration but not in terms of
how it works as a machine - sequences of actions, what happens synchronously, what happens
asynchronously, etc.
From reading the very simple examples, such as the "Hello
World", I feel I know enough to perhaps roll my own workflow "controller"
(creating, managing, monitoring processes), but I have the feeling that jBPM comes with
much more stuff I can leverage. I just can't tell exactly where the boundaries are.
For example, should I take the web ap the runs under JBoss, strip out stuff, put in under
Tomcat? What do I strip out / replace? In other words, what is the core that the webapp
is built on?
It's just hard, short of reverse engineering the code, to understand what is going on.
I'll keep digging, but more docs on "how it works" are always appreciated.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035169#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...