On Wed, Aug 25, 2004 at 12:24:25AM +0200, Jose Gonzalez Gomez wrote:
> Yes, I agree with you... anyway I heard some time ago of a JSR
> regarding a standard API for deployment of J2EE applications, I think
> this is definitely worth investigating, as it may solve half the problem
> as long as we don't mind to have a java application to take care of
> these issues.
As a configuration step, or as a helper function along the installation
process, this will work quite nicely. Ebuilds are not allowed to write
directly to the root file system, the complete installation occurs in
/var/tmp/portage/{packagename}/image/
From this directory (called ${D} in the ebuilds), portage will install the
files, record which files it installed, take mtimes, md5sums, strip binaries,
etc.
If modifications to the host configuration files are needed (which we
generally discourage), either a gentoo-specific tool should be used, such as
java-config, or on can modify the config files in a post-installation step.
As long as a JSR-mandated installation system can play along those rules, I
don't see why we couldn't use it.
[snip]
> If we're able to achieve this, users would have the freedom to choose an
> open source server installed with an ebuild, or a commercial server with its
> own installer.
This would be a very nice goal, however it's not top priority at the moment,
we have far too much basic infrastructure work to do ourselves before doing
field testing with commerical offerings, too.
> Well, I think right now Gentoo is not missing any critical part of
> the stack. Jboss is available in an ebuild, and I think they include
> support for the whole J2EE platform. A time ago there were a certain
> trend where people created servers implementing just part of the stacks
> (Jboss started as a EJB container, Tomcat is just an JSP/Servlet
> container,...) but I think now they tend to offer the whole stack (Jboss
> now includes the whole J2EE stack, from JSP/Servlets, to EJBs, including
> JMS, JCA, web services,...)
This is where I always get confuzzled. jBoss seems quite complete, but there
are numerous other implementations of JMS for instance.
Is it possible to freely mix and match any JMS for jBoss, or does it need to
be their version?
How about servlet containers?
The way gentoo has resolved this traditionally, where multiple packages
provide the same functionality, is by virtual packages.
E.g. we have virtual/jdk that can be satisfied by installing any our JDKs.
Does it make sense to do something similar for tomcat, jetty, jboss, whatever,
by grouping them behind a virtual/servlet-container ?
If so, which virtual packages should we have?
> Sure... it comes to mind Open For Business (http://www.ofbiz.org/),
> Compiere (http://www.compiere.org/) or OpenCMS
> (http://www.opencms.org/). I'm sure we may find more.
If we can get any of these running on Gentoo without too much configuration
work, and make them all compile completely from source-code, I'm all for it.
> Well, just drop me a line whenever you need help... by the way, is
> there any other list I may subscribe where you discuss about these issues?
This is the list. But for some reason, people want to discuss on IRC instead:)
As for what to do, I think you're in a much better position to answer that,
being a Gentoo user with experience in this field. What do _you_ see as
missing? Why wouldn't _you_ use Gentoo in your one-man shop, or as a
development platform for J2EE stuff?
-- Karl T
pgpTCHhkebrgK.pgp
Description: PGP signature
|