Is anyone working on embedding Tomcat in Geronimo?
I would like to help out and tackle this issue.
Any helpful information would be appreciated.
Thanks,
Jeff Genender
[
http://nagoya.apache.org/jira/browse/GERONIMO-448?page=comments#action_55412 ]
Alan Cabrera commented on GERONIMO-448:
---
OpenORB v1.4.0-B2 does not currently support JDK15
> OpenEJB ITests Fail under Sun JDK 1.5.0 (RMIoverIIOP failure)
> ---
On Nov 11, 2004, at 7:15 PM, Srinath Perera wrote:
Thanks Geir, Thanks everybody :)
Is there any place(some one I should contact so) that I can find the
information I should know being a Geronimo committer, to clarify my
account access rights etc?
I added the appropriate karma for you.
Let us know
On Fri, 12 Nov 2004, Peter Nabbefeld wrote:
> Hmm, the source and binary distributions are also in the wiki
> (http://wiki.apache.org/geronimo#head-a862c2b21b5e1337de2b76d5e43ae1375117d34d)
>
> - so what's the problem with adding the installer version?
The files aren't actually on the W
Project: Apache Geronimo
Status: Resolved, Closed (25 items)
Updated In Last: Week (7 days)
** New Feature
* [GERONIMO-429] Foreign key constraints are not enforced for CMP 2.x
EntityBean
* [GERONIMO-281] Optional packages support
** Bug
* [GERONIMO-307] servlet tries to lookup resource
Aaron Mulder schrieb:
I've been playing around with a free install tool (IzPack), and I
have an installer package for the M3 release (of the "java -jar
installer.jar" type). Importantly, it lets you choose your username,
password, and network ports during the installation. As a side effec
I've been playing around with a free install tool (IzPack), and I
have an installer package for the M3 release (of the "java -jar
installer.jar" type). Importantly, it lets you choose your username,
password, and network ports during the installation. As a side effect, it
leaves your serv
The DefaultDB is older and predates Derby's arrival at the ASF. Services
that needed a database backend were using it.
When Derby arrived and was integrated I added it as System DB so we
could see how it would work out without disrupting any of the existing
services.
In our environment Derby h
Actually, that should be "Purpose of Derby & System DB". I was
mixed up -- the "default DB" is the Axion one that's used, the "system DB"
is the Derby one that seems optional. Sorry.
Aaron
On Thu, 11 Nov 2004, Aaron Mulder wrote:
> What's the use of loading the default Derby dat
What's the use of loading the default Derby database? Just for
grins? I mean, it looks like the system DB is used by the (EJB?) timer
service... but I don't see anything using the default DB.
Thanks,
Aaron
Thanks Geir, Thanks everybody :)
Is there any place(some one I should contact so) that I can find the
information I should know being a Geronimo committer, to clarify my
account access rights etc?
cheers
Srinath
On Thu, 11 Nov 2004 13:03:33 -0800, Geir Magnusson Jr. <[EMAIL PROTECTED]>
wrote:
On 12/11/2004 8:38 AM, David Jencks wrote:
However, I think the original goal was to have the builder modules not
actually directly use classes from the runtime modules, but allow such
classes to be loaded from the configuration's classloader only. At
the moment we cannot achieve this goal bec
2 people have been unable to build M3 from the source distro. It
appears that the problem is that the copy of openejb-core-2.0-G1M3.jar
used in the build is seriously out of date with references to
GBeanInfoFactory rather than GBeanInfoBuilder in OpenEJBModuleBuilder.
thanks
david jencks
Deployer must not echo password when prompting
--
Key: GERONIMO-478
URL: http://nagoya.apache.org/jira/browse/GERONIMO-478
Project: Apache Geronimo
Type: Bug
Components: deployment
Reporter: Jeremy Boynes
When no
14 matches
Mail list logo
