[Design of POJO Server] - Re: Removing ClassLoading from jboss-bootstrap
by wolfc
"adrian(a)jboss.org" wrote : The basic idea is to have a pluggable bootstrap. The bootstrap.start() should run
| under its own classloader as TCL not the classpath otherwise all sort of side effects
| break (e.g. loading property editors, and other dynamic classloading, etc.).
I still don't see how this can happen?
The app classloader contains virtually nothing.
"adrian(a)jboss.org" wrote : In JBoss the bootstrap is two stage (actually it is multiple).
|
| 1) To load the bootstrap implementation itself (the mc + profile service)
Profile Service isn't in scope yet. We're at rock bottom, stage #1, a bootstrapping framework with which Reloaded can bootstrap Profile Service itself.
"adrian(a)jboss.org" wrote :
| 2) To load the bootstrap xmls
|
| As long as the called code doesn't have to worry about setting the TCL itself
| (error prone and it is not likely to know what the correct CL is)
| I don't have a problem.
I think I'm getting it: Bootstrap should execute the following 'psuedo' descriptor:
<deployment>
| <classloader>preboot-cl</classloader>
| <bean class="org.jboss.bootstrap.MCServerImpl"/>
| <bean class="org.jboss.bootstrap.BootstrapDeployer"/>
| <classloader name="preboot-cl">
| bits and pieces specified by the launcher
| </classloader>
| </deployment>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223913#4223913
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223913
17 years
[Design of JBoss jBPM] - Re: jBPM 4 Emails Sync vs Async
by tom.baeyens@jboss.com
"jbarrez" wrote : Tom, I don't follow you with the global setting. I still think it should be able to be configured on the node itself.
|
they don't exclude each other. ideally we have them both. in the configuraiton file, the default value can be specified and in the process, the default can be overwritten. but we need to prioritize which one we build first. my take on prioritization would be this:
1) direct sending
2) global configuration setting
3) configuration per usage in the process file
"jbarrez" wrote :
| Imo, there are cases in which you want the mail directly: eg for handling an exception or a timer times out when waiting for an external system -> send an email to the system admin directly.
|
| In this case, scheduling it and waiting for the jobExecutor will cause a serious and unacceptable slow-down ... unless the jobExecutor is polling all the time (which is not good for performance).
|
there is no delay. even inbetween polls. the job executor is notified of new jobs by means of a synchronization.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223890#4223890
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223890
17 years