Sacha Labourey wrote:
This places restrictions on the class loader implementation, and if you are talking
Why? This would be our classloader that we setup during the micro-kernel
startup: instead of simply setting one, we would possibly set two. In
org.jboss.system.server.ServerImpl.initBootLibra
> Most services using the conf directory are just doing a
> ClassLoader.getResource() so overriding the conf with a user
> specific one means there is a directory in the classpath
> search order ahead of the default. This places restrictions
Yes.
> on the class loader implementation, and if y
Yes, which is why this discussion cannot scale to the point of fantasy
where a client inputs an arbitrary of list of services, OS, JDK, existing
configs and have a custom build magically appear.
That will be possible when Charles Simonyi’s fantasy development env exists:
http://www.technologyreview
Sacha Labourey wrote:
This is asking for a configuration service. The notion here
of merging overrides based on speical URLs has too many
implementation requirements.
What do you mean?
Most services using the conf directory are just doing a ClassLoader.getResource() so
overriding the conf with a
> We already have this capability, its just a question of using
> it. The hsqldb-ds.xml can reference a
>
> There is no reason to add new semantics to the current
> classpath element.
> There are new semantics in terms of identity of classes by
> virture of the fact that the hsqsdb.jar c
Hi all,
During my fresh and enduring experiences of porting the
3.0.4/3.0.8/3.2.1/3.2.2 to AIX 4.3.3 I have the feeling there should by
a seperation between the TBB - to be build and tested - cycle, the
configuration cycle and the lifecycle of the productive JBoss System as
a whole: the enclos
Some questions points on the main issues here.
Sacha Labourey wrote:
1) /lib
===
/lib is maybe the easiest case: it mostly contains JBoss's needed classes.
One small problem maybe: some of these classes are not directly use by the
JBoss microkernel directly (nor by the services in conf/J
Hello,
I would like to continue our discussion of JBoss configuration as I think we
must make that much better for future releases of JBoss.
There are lots of facets to this problem but in order to keep things simply,
I would like to start talking about a single one: user configuration of
JBoss a
