On Aug 2, 2005, at 12:06 AM, Dr. Michael Lipp wrote:
Hi,
I have been looking a bit into what David Jencks
suggests here. We could indeed write a custom
deployer for Jetspeed.
1. Custom JBoss deployer that would ignore jetspeed
configuration files (OJB and Castor for data binding).
2. Move OJB and Castor files into JETSPEED-INF. This
change could be quickly implemented as the location of
the configuration files location is injected through
spring assembly.
I believe that 2. is an acceptable solution. What do
others think?
I support moving the configuration files out of META-INF. Though
writing
a deployer is of course possible, it introduces a strong dependency of
Jetspeed on JBoss (I haven't looked into this closely, but it may even
be possible that you need the JBoss libraries to compile the custom
deployer, so you won't be able to compile Jetspeed without a JBoss
installation). Besides, such like APIs are never 100% stable, so maybe
we will need a different deployer for JBoss 3.x, 4.x etc.
It's conceivable that jboss would be interested in such a deployer.
You could make it generic so it would ignore a configurable list of
.xml files in META-INF, thus helping JBoss work with other projects
facing the same problem.
I think that using META-INF for these files is wrong anyway. Despite
its
generic name, META-INF is a directory with a layout governed by the
Java/J2EE specifications and adding your own files there implies always
the risk of a conflict.
If JBoss followed your logic, this situation would not have arisen, as
JBoss would look in META-INF only for Java/J2ee required files and
would ignore the jetspeed ones. In addition, no one would put vendor
plans in META-INF for pre-j2ee 1.4 applications. As IIRC the original
author of the JBoss code in question, I can assure you that the problem
there is not some altruistic desire to preserve the purity of the
contents of META-INF but rather the lack of a way to explicitly specify
the classpath for a server and over-reliance on guessing based
directory scanning deployment.
thanks
david jencks
- Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
