DerbySystemGBean doesn't call System.gc() in doStop() and soFail() as
recommended in the Derby doco
---
Key: GERONIMO-453
URL: http://nagoya.apache.org/jira/browse/GERONIMO-453
So it looks like our EAR deployment plan can hold nested
deployment plans for all the modules within it, using the any area of
the module element in the geronimo-application.xml.
I'm concerned that we may eventually want more than one nested
deployment plan per module. For
A good concern but I don't think we'll need to do this.
Each module in the EAR can be deployed standalone where we only get the
single plan allowed by JSR-88; therefore we need to be able to nest
plans for other things such as webservices or portlets inside that
single plan.
The ANY element in
Support Group Name = Role Name Role Mapping
---
Key: GERONIMO-454
URL: http://nagoya.apache.org/jira/browse/GERONIMO-454
Project: Apache Geronimo
Type: Improvement
Components: deployment, security
Versions: 1.0-M2
On Sun, 7 Nov 2004, Aaron Mulder wrote:
We will attempt to do this without breaking backward compatibility
with the security realm API for now, though the security realm
configuration in the deployment plans will need to change a bit, and we're
going to mark the getXXXPrincipal() methods
[ http://nagoya.apache.org/jira/browse/GERONIMO-424?page=history ]
Alan Cabrera reassigned GERONIMO-424:
-
Assign To: Aaron Mulder (was: Alan Cabrera)
ConfigurationEntry support for multiple LoginModules
[ http://nagoya.apache.org/jira/browse/GERONIMO-421?page=history ]
Alan Cabrera reassigned GERONIMO-421:
-
Assign To: Aaron Mulder (was: Alan Cabrera)
Better handling for null/empty users in default LoginModules
This checkin:
geronimo/trunk/modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/EARConfigBuilder.java
Revision 56855 - (view) (download) - [select for diffs]
Modified Sun Nov 7 17:26:43 2004 UTC (7 hours, 50 minutes ago) by djencks
File length: 26550 byte(s)
Diff to
On Sun, 7 Nov 2004, Dain Sundstrom wrote:
God I hope not. I spend a long long long time making sure our code
would work with unpacked archives. People don't want to jar up a
deployment during development. Having the tool jar it up, is a bit
better than no support at all, but the extra
Actually as far as I can tell Dims' patch fixed the problem. If you
get a different result reply soon... I won't be up much longer.
Thanks, Dims.
david jencks
On Nov 7, 2004, at 11:34 PM, Aaron Mulder wrote:
If there's anything I can do to help, I'm still up, and my Axis
build works
Yeah, you're right. Sorry I didn't give him credit! :)
Aaron
On Sun, 7 Nov 2004, David Jencks wrote:
Actually as far as I can tell Dims' patch fixed the problem. If you
get a different result reply soon... I won't be up much longer.
Thanks, Dims.
david jencks
On Nov 7,
[ http://nagoya.apache.org/jira/browse/GERONIMO-430?page=history ]
Aaron Mulder updated GERONIMO-430:
--
Assign To: Aaron Mulder
Generalize security realms, consolidate logic into Login Modules
To help new users understand what is currently supported by Geronimo and
what is still under development, I've started the following wiki page:
http://wiki.apache.org/geronimo/RoadMap
It breaks down functionality from the user's point of view and has a
graphical status indicator next to each
[ http://nagoya.apache.org/jira/browse/GERONIMO-386?page=history ]
Gianny DAMOUR reassigned GERONIMO-386:
--
Assign To: Gianny DAMOUR
openejb cmp attempt to modify identity columns
--
Key:
[ http://nagoya.apache.org/jira/browse/GERONIMO-455?page=history ]
Alan Cabrera reassigned GERONIMO-455:
-
Assign To: Alan Cabrera
Too many ControlFlag arrays
---
Key: GERONIMO-455
URL:
Within the ASF, the use of the development mailing list is *the* method
of development discussion. That's the reason for it.
Wikis are good for after the fact documentation.
IRC is good when a small subset of developers need to
get together quickly to talk about some aspects of
development, but it
[ http://nagoya.apache.org/jira/browse/GERONIMO-455?page=history ]
Alan Cabrera closed GERONIMO-455:
-
Resolution: Fixed
Too many ControlFlag arrays
---
Key: GERONIMO-455
URL:
On 8/11/2004 8:19 AM, David Jencks wrote:
I'm not exactly ready to vote -1, but I think we should resolve these
issues before M3:
1. http://issues.apache.org/jira/browse/GERONIMO-386 Make cmp work
with derby. Prove it with the itests
I had a look to this one. I have committed a partial
[
http://nagoya.apache.org/jira/browse/GERONIMO-386?page=comments#action_55189 ]
Gianny DAMOUR commented on GERONIMO-386:
I have committed a new primary key generator, which uses table auto-generated
primary key to generate the primary keys of
Jim Jagielski wrote:
Within the ASF, the use of the development mailing list is *the* method
of development discussion. That's the reason for it.
Wikis are good for after the fact documentation.
IRC is good when a small subset of developers need to
get together quickly to talk about some aspects
This is pretty cool!
-Original Message-
From: Erin Mulder [mailto:[EMAIL PROTECTED]
Sent: Monday, November 08, 2004 4:22 AM
To: [EMAIL PROTECTED]
Subject: Feature list on wiki - please help update status
To help new users understand what is currently supported by Geronimo
and
For the record, when the words hidden agenda came up, my exact response
was, Can we turn this back into a technical discussion?
Talking offline is fine. Throw in beer and it's even better. Can't
wait to see everyone at ApacheCon next week.
My beef was in the very first sentence of Aaron's
The vote to do a M3 release before ApacheCon was positive. Now
the question is when. I know many of us are travelling on Friday. I
suggest we prepare the release on Wednesday, so we have a bit of time to
look it over before anyone hops on a plane.
I'm not really looking for
I think that this is an important issue, but not the important one for
this thread, and we're getting caught in a rathole.
The conversation in question started on the dev list, had a phone call
between two individuals that really respect each other and wanted to
figure out where the crossed
On Nov 8, 2004, at 12:24 PM, Jeremy Boynes wrote:
Jim Jagielski wrote:
Within the ASF, the use of the development mailing list is *the*
method
of development discussion. That's the reason for it.
Wikis are good for after the fact documentation.
IRC is good when a small subset of developers need
On Nov 8, 2004, at 1:44 PM, Jeremy Boynes wrote:
David Blevins wrote:
My apologies to Jeremy as I had assumed the decision to commit a new
deployer was part of a their discussion.
Appreciated, thank you. To be clear, it _was_ part of the discussion;
we were discussing the best way to proceed
I never considered this issue as anything serious at all.
Quite the opposite; as I mentioned just about every ASF project
has had this pop up. I was simply stating the general rule, without
any sort of interpretation of the events that lead to
it. :)
+1 Wednesday
I think the most important thing is we all agree to whined down
development as Wednesday approaches. I know that normally there is a
flood extra activity as a release approaches, which would make this
release impossible, but I'm concerned that even at our current rate of
change
Wednesday is good for me. More below
On Nov 8, 2004, at 2:29 PM, Aaron Mulder wrote:
The vote to do a M3 release before ApacheCon was positive. Now
the question is when. I know many of us are travelling on Friday. I
suggest we prepare the release on Wednesday, so we have a bit of time
to
Aaron Mulder wrote:
The vote to do a M3 release before ApacheCon was positive. Now
the question is when. I know many of us are travelling on Friday. I
suggest we prepare the release on Wednesday, so we have a bit of time to
look it over before anyone hops on a plane.
I'm not really
On Mon, 8 Nov 2004, David Blevins wrote:
Here is the filter settings you should use to create the Unfinished
section of the changelog:
Project: Apache Geronimo
Status: Open, In Progress, Reopened
Fix Version/s: No versions
Affects Version/s: 1.0-M1,1.0-M2
Sorted by: Key descending
David Blevins wrote:
Wednesday is good for me. More below
On Nov 8, 2004, at 2:29 PM, Aaron Mulder wrote:
The vote to do a M3 release before ApacheCon was positive. Now
the question is when. I know many of us are travelling on Friday. I
suggest we prepare the release on Wednesday, so
Either my email got lost in the flood or people are not too opinionated
on logging. Anyway, does anyone have an opinion on point 2 Commons
Log?
-dain
On Nov 5, 2004, at 1:29 PM, Dain Sundstrom wrote:
After working with geronimo for a while, I am convinced our current
logging solution was a
Yes that is the one.
-dain
On Nov 8, 2004, at 4:03 PM, Aaron Mulder wrote:
If you mean the bit about distribute 1 class or repackage, I vote
repackage.
Aaron
On Mon, 8 Nov 2004, Dain Sundstrom wrote:
Either my email got lost in the flood or people are not too
opinionated
on logging.
On Nov 8, 2004, at 3:51 PM, Aaron Mulder wrote:
On Mon, 8 Nov 2004, David Blevins wrote:
Here is the filter settings you should use to create the Unfinished
section of the changelog:
Project: Apache Geronimo
Status: Open, In Progress, Reopened
Fix Version/s: No versions
Affects Version/s:
[ http://nagoya.apache.org/jira/browse/GERONIMO-457?page=history ]
Davanum Srinivas resolved GERONIMO-457:
---
Resolution: Fixed
already fixed. try latest SVN.
-- dims
Missing dependency in modules/axis
--
36 matches
Mail list logo
