On Jul 24, 2005, at 4:14 PM, Jeremy Boynes wrote:
I would suggest adding a property for the primary interface that the
component provides e.g.
service=org.apache.geronomo.module.SomeService
This would provide an easy way to identify what was offering a service.
I'd go further and say you
I'd like to make it clear that my objections are not to fixing the
naming system currently used, which I think has some problems other
than those noted here, but to changing it without careful thought, and
destabilizing geronimo during the change.
The idea of putting the primary interface in
Following default installation in izpack installer in M4 results in Error:
Cannot read file C:\Program
Files\GeronimoM4QA\installer-temp\j2ee-server-tomcat-plan.xml
All,
I've been working on getting Trade 6 deployed on Geronimo. For those that
are not familiar, Trade 6 is a sample J2EE application provided by IBM on
their website for testing of J2EE AppServers for functionality as well as
performance. You can find more information at this link:
[
http://issues.apache.org/jira/browse/GERONIMO-810?page=comments#action_12316655
]
John Sisson commented on GERONIMO-810:
--
Fixed in v1_0_M4-QA branch.
Modified:
OpenSourceJava\geronimo_m4qa\geronimo\modules\assembly\src\izpack\izpack-process.xml
[
http://issues.apache.org/jira/browse/GERONIMO-810?page=comments#action_12316656
]
John Sisson commented on GERONIMO-810:
--
The change was tested with Tomcat unselected (the default) and with it selected
in the installer.
Following default
Lack of information for those using izpack installer on how to enable Tomcat in
M4
--
Key: GERONIMO-811
URL: http://issues.apache.org/jira/browse/GERONIMO-811
Project: Geronimo
Type:
Thanks for the suggestion Simone.
I haven't found anything with that setting yet ... but I'm still looking.
However, the problem has disappeared again as quickly as it came the
last 2 times. I simply waited a few hours and attempted to start the
server again without any changes in the
[
http://issues.apache.org/jira/browse/GERONIMO-809?page=comments#action_12316658
]
John Sisson commented on GERONIMO-809:
--
Fixed in v1_0_M4-QA branch:
Deleting:
[
http://issues.apache.org/jira/browse/GERONIMO-796?page=comments#action_12316659
]
Joe Bohn commented on GERONIMO-796:
---
The problem appears to be a simple matter of the GBean name for the Jetty Web
Container being incorrect in
On Mon, 25 Jul 2005, David Jencks wrote:
Why do you think there is a runtime dependency of the kernel on the
j2ee module? The type string included in GBeanInfo is used only at
deploy time to help resolve gbean references.
Well, the GBean factory does have a special constructor field
Unfortunately JIRA is down, so I'm sending this email for now. Does
anyone have any ideas regarding the problem described below..
In an attempt to test modifying the M4 plan files so that Geronimo only
uses Tomcat in M4, I ran into some problems.
My changes were:
1. I added the following
David Jencks wrote:
Why do you think there is a runtime dependency of the kernel on the j2ee
module? The type string included in GBeanInfo is used only at deploy
time to help resolve gbean references.
I remember that when I was developing the packaging plugin I needed to
include the
This is an issue we've been considering formalizing for a while, and
I decided to run with the ball that Dims recently tossed.. :)
I've added the refactored HTTPD project guidelines as PROPOSED in our
site. I haven't published to the public site because I wanted some
feedback and give
There is a mechanism to save out he current state of GBeans on a
clean shutdown of the configuration (i.e., when you stop the
configuration). If it is not running, then there is a bug. The code
is in org.apache.geronimo.kernel.config.Configuration.doStop();
-dain
On Jul 24, 2005, at
I think we should consider the object name conventions laid out here:
http://java.sun.com/products/JavaManagement/best-practices.html
I like the idea of query by interface, but I doubt it is something we
want to add before 1.0.
-dain
On Jul 24, 2005, at 2:24 PM, Aaron Mulder wrote:
I think we should start with guidelines that are from a project that
is in a much earlier stage of development. These guidelines work
well for httpd since it is such a stable code base, but I believe
unworkable for us. Are there other project guidelines we can start
with? Perhaps
On Jul 25, 2005, at 11:29 AM, Geir Magnusson Jr. wrote:
On Jul 25, 2005, at 1:37 PM, Dain Sundstrom wrote:
I think we should start with guidelines that are from a project
that is in a much earlier stage of development. These guidelines
work well for httpd since it is such a stable code
On Jul 25, 2005, at 4:29 PM, Dain Sundstrom wrote:
On Jul 25, 2005, at 11:29 AM, Geir Magnusson Jr. wrote:
On Jul 25, 2005, at 1:37 PM, Dain Sundstrom wrote:
I think we should start with guidelines that are from a project
that is in a much earlier stage of development. These guidelines
On Jul 25, 2005, at 1:52 PM, Geir Magnusson Jr. wrote:
The guidelines are clearly marked as PROPOSED on the page, under
a Proposed section of the left side menu. Does that sufficiently
address that concern?
No. Having them on the website gives me the feeling that they are a
lot further
undeployment sometimes seems incomplete
---
Key: GERONIMO-812
URL: http://issues.apache.org/jira/browse/GERONIMO-812
Project: Geronimo
Type: Bug
Versions: 1.0-M4, 1.0-M5
Reporter: David Jencks
Assigned to: David
[ http://issues.apache.org/jira/browse/GERONIMO-664?page=all ]
David Blevins updated GERONIMO-664:
---
Fix Version: 1.0-M5
(was: 1.0-M4)
Version: 1.0-M4
Moving this to M5
Tomcat need webservices integrated
Corba interop problem
-
Key: GERONIMO-813
URL: http://issues.apache.org/jira/browse/GERONIMO-813
Project: Geronimo
Type: Bug
Components: CORBA
Versions: 1.0-M4, 1.0-M5
Reporter: David Jencks
Assigned to: Dain Sundstrom
Fix
[ http://issues.apache.org/jira/browse/GERONIMO-677?page=all ]
David Blevins updated GERONIMO-677:
---
Fix Version: (was: 1.0-M4)
Repeated login (after session invalidation) with different credentials
results in incorrect role set.
[
http://issues.apache.org/jira/browse/GERONIMO-809?page=comments#action_12316694
]
David Blevins commented on GERONIMO-809:
Is this issue completed?
Some bundled Web Applications still use geronimo-jetty.xml - causes problems
when using Tomcat
[
http://issues.apache.org/jira/browse/GERONIMO-811?page=comments#action_12316696
]
David Blevins commented on GERONIMO-811:
Could we simply remove the Tomcat option from M4 and get this right in M5
which already has many other Tomcat related
Fair enough. The point of putting on the website was to let everyone
see and let us get patch streams to get to a point where we can vote.
I'll remove the link on our public site before pushing out, but keep
the content there and post a link for discussion. Does that solve
it for you?
Aaron Mulder wrote:
I thought we had a mechanism in place to store the state of a
GBean after a change at runtime -- which I assume would include storing
new values for persistent attributes as well as storing the data for new
GBeans added to a Configuration at runtime (for example, if you
Alright, here is the deal on M4. We have OSCON coming up and from my
experience, if we don't get M4 out the door this week, then we won't
see it till the week after OSCON. I actually tried to cut M3 at
OSCON last year and we all know how that went.
If we don't get M4 out the door this
[ http://issues.apache.org/jira/browse/GERONIMO-809?page=all ]
John Sisson resolved GERONIMO-809:
--
Resolution: Fixed
Some bundled Web Applications still use geronimo-jetty.xml - causes problems
when using Tomcat
[
http://issues.apache.org/jira/browse/GERONIMO-809?page=comments#action_12316706
]
John Sisson commented on GERONIMO-809:
--
Fixed in HEAD:
Deleting:
OpenSourceJava\geronimo_head\geronimo\applications\demo\src\webapp\WEB-INF\geronimo-jetty.xml
[ http://issues.apache.org/jira/browse/GERONIMO-809?page=all ]
John Sisson updated GERONIMO-809:
-
Description:
Fixed.
Previously, when running with only Tomcat the following was observed:
* the demo application was running with a configId of
[ http://issues.apache.org/jira/browse/GERONIMO-809?page=all ]
John Sisson closed GERONIMO-809:
Some bundled Web Applications still use geronimo-jetty.xml - causes problems
when using Tomcat
Javamail Axis...
- Am done with changes to JavaMail. tests are working as well.
- We most probably can't squeeze in a new release of Axis this week.
What do we do? (dated snapshot?)
thanks,
-- dims
On 7/25/05, David Blevins [EMAIL PROTECTED] wrote:
Alright, here is the deal on M4. We have
[ http://issues.apache.org/jira/browse/GERONIMO-811?page=all ]
John Sisson reassigned GERONIMO-811:
Assign To: John Sisson
Lack of information for those using izpack installer on how to enable Tomcat
in M4
For my part, I'm not convinced that it makes sense for
configurations to be immutable. I think the export/import feature would
be nice -- I finally got my web container configured 'just right', now
let me export it and load it into my cluster of 30 boxes. I wouldn't
even mind giving
WRT Tomcat, I think we should just comment out that block from the
installer config files in M4. The procedure for getting it running is way
too arcane, and we have something much better in place in HEAD already.
Also, I'd like to see Tomcat get a bit more testing before making noise
I have been thinking about this issue for months now and haven't come
to any good solutions. I think it would be cool to have imutable
configuration, but just think it is practical at this point. The
console and the tomcat/jetty selection issues really show off where
our current design
As far as the Tomcat/Jetty thing goes, that will be interesting to
explore as we think over how we should deal with interfaces in some
future release. I mean, I think our dependencies should ideally be
expressed as I require a servlet 2.4-compatible web container not I
require the
Davanum Srinivas [EMAIL PROTECTED] wrote on 26/07/2005 09:22:34 AM:
Javamail Axis...
- Am done with changes to JavaMail. tests are working as well.
Dims, are you going to build a new release candidate of the javamail spec
jar - GERONIMO-802 and update the M4 branch to point to it?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 6:01 PM
To: dev@geronimo.apache.org
Subject: Re: Attacking M4
David Blevins [EMAIL PROTECTED] wrote on 26/07/2005
07:59:47 AM:
Alright, here is the deal on M4. We have OSCON
Sorry for this late reply; I was on holidays last week and I am still
catching up with emails.
John, you can remove it as it was solely used to enable remote classloading.
Thanks,
Gianny
On 23/07/2005 9:53 AM, [EMAIL PROTECTED] wrote:
AFAIK, the policy file was to be used when running the
sisson,
On 7/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Davanum Srinivas [EMAIL PROTECTED] wrote on 26/07/2005 09:22:34 AM:
Javamail Axis...
- Am done with changes to JavaMail. tests are working as well.
Dims, are you going to build a new release candidate of the javamail spec
I'd ask you to set aside traditional thinking and try this out for a bit.
When you write code, you edit a couple of source files, compile it, fix
the typos, build a jar, test it, decide its good enough and commit the
change. After doing this a few times you decide its good enough and do a
Does anyone know if the J2EE 1.5 (now called 5.0) include JBI?
Quote from http://radio.weblogs.com/0112098/2005/07/25.html#a532:
Am looking forward to it passing the JBI TCK through the Geronimo project.
-- dims
--
Davanum Srinivas -http://blogs.cocoondev.org/dims/
So, how do I get this plugin working?
-David
On Mon, Jul 25, 2005 at 08:09:43PM -0700, i386-redhat-linux-gnu wrote:
BUILD FAILED
See details at:
http://people.apache.org/~dblevins/build-20050725-2008
Simple grep of build output:
[jar] Building jar:
/home/users/dblevins/tmp
Davanum Srinivas [EMAIL PROTECTED] wrote on 26/07/2005 11:47:05 AM:
sisson,
On 7/25/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Davanum Srinivas [EMAIL PROTECTED] wrote on 26/07/2005 09:22:34 AM:
Javamail Axis...
- Am done with changes to JavaMail. tests are working as well.
I've revised my build script and am very much hoping some other people
will bite on this one and install it and/or fix it up.
HOW TO USE THIS SCRIPT
Executing the script like the following will run the build and, in
the event of a failure, send an email message to
scm@geronimo.apache.org
Jeff Genender [EMAIL PROTECTED] wrote on 26/07/2005 10:42:06
AM:
-Original Message-
From: Aaron Mulder [mailto:[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 5:59 PM
To: dev@geronimo.apache.org
Subject: Re: Attacking M4
WRT Tomcat, I think we should just comment out
[ http://issues.apache.org/jira/browse/GERONIMO-802?page=all ]
John Sisson reassigned GERONIMO-802:
Assign To: John Sisson (was: Davanum Srinivas)
Publish new geronimo_spec_javamail jar since changes have been made since
1.3.1-rc4 was published
-redhat-linux-gnu wrote:
BUILD FAILED
See details at:
http://people.apache.org/~dblevins/build-20050725-2008
Simple grep of build output:
[jar] Building jar:
/home/users/dblevins/tmp/geronimo/modules/j2ee/target/geronimo-j2ee
-1.0-SNAPSHOT.jar
Copying: from
'/home/users/dblevins/tmp
Get stack trace from ActiveMQ when shutting down geronimo
-
Key: GERONIMO-815
URL: http://issues.apache.org/jira/browse/GERONIMO-815
Project: Geronimo
Type: Bug
Components: ActiveMQ
Versions: 1.0-M4
52 matches
Mail list logo
