[ http://issues.apache.org/jira/browse/GERONIMO-791?page=all ]
Dain Sundstrom closed GERONIMO-791:
---
Fix Version: 1.0-M5
Resolution: Fixed
Deleting
modules/kernel/src/java/org/apache/geronimo/gbean/GBeanLifecycleController.java
Sending
[
http://issues.apache.org/jira/browse/GERONIMO-778?page=comments#action_12316866
]
Bruce Snyder commented on GERONIMO-778:
---
Why not just contribute this to the XDoclet project? I hazard a guess the
XDoclet team might offer you committer status to
Andy Piper wrote:
Hi Jules
It sounds like you've been working hard!
yes - I need a break :-)
I think you might find you run into reliability issues with a
singleton coordinator. This is one of those well known Hard Problems
and for session replication its not really necessary. In
I'm listening to this discussion and trying to make sense of it so that
I can understand how it will affect our users. Keep in mind that I'm
still grasping at the fundamentals of Geronimo and G-beans so this may
be off in the weeds (and for which I will apologize for right now).
As I think
Joe Bohn wrote:
One final question I'll toss out (and possibly show my ignorance ... but
at least I'll learn the answer :-) ) ... Aren't the applications that
are deployed themselves represented by Gbeans in the bundle and
therefore the bundle is already mutable in that sense? I read an
Aaron Mulder wrote:
Of the two, I like option 5 more -- and more than all the
UUID-based options. I'm not sure the mutability needs to be reflected in
the configuration name, though -- couldn't we have non-name properties for
the version and mutability? That way the start/stop command
Thanks Jeremy. That helps a lot. I think it also helps me understand
how potentially different types of configuration data might be organized
and managed (which I'd also like to hear some thoughts on too).
IIUC then, any configuration that changes a GBean's persistent state in
the server
Invalid sigantures in JavaMail API jar
--
Key: GERONIMO-821
URL: http://issues.apache.org/jira/browse/GERONIMO-821
Project: Geronimo
Type: Bug
Components: specs
Versions: 1.0-M4
Reporter: Jeremy Boynes
Assigned
We should accept (and ignore) simple type mappings in a jaxrpc-mapping file
---
Key: GERONIMO-823
URL: http://issues.apache.org/jira/browse/GERONIMO-823
Project: Geronimo
Type: Bug
Components:
[
http://issues.apache.org/jira/browse/GERONIMO-823?page=comments#action_12316948
]
Dain Sundstrom commented on GERONIMO-823:
-
Why not allow them to override the default built in simple types?
We should accept (and ignore) simple type mappings in
Need more flexibility in interpreting jaxrpc mappings of ArrayOfFoo elements
Key: GERONIMO-822
URL: http://issues.apache.org/jira/browse/GERONIMO-822
Project: Geronimo
Type: Bug
MdbBuilder sets the Listener Type incorrectly causing NPEs at initialization
Key: GERONIMO-824
URL: http://issues.apache.org/jira/browse/GERONIMO-824
Project: Geronimo
Type: Bug
[
http://issues.apache.org/jira/browse/GERONIMO-823?page=comments#action_12316950
]
David Jencks commented on GERONIMO-823:
---
Thanks for volunteering! For now I'll stick with what I think I can implement
:-)
We should accept (and ignore) simple
[ http://issues.apache.org/jira/browse/GERONIMO-824?page=all ]
Aaron Mulder updated GERONIMO-824:
--
Fix Version: 1.0-M4
1.0-M5
Version: 1.0-M3
(was: 1.0-M4)
(was: 1.0-M5)
[ http://issues.apache.org/jira/browse/GERONIMO-823?page=all ]
David Blevins closed GERONIMO-823:
--
Resolution: Fixed
Checked into OpenEJB by Matt Hogstrom. Closing the issue for him as he doesn't
have Geronimo access.
We should accept (and
FYI. Do not cross-post replies.
--- Noel
-Original Message-
From: A mailing list for discussion of the JavaMail(tm) API
[mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, July 27, 2005 14:28
To: [EMAIL PROTECTED]
Subject: JavaMail and JAF available as Open
Is there a build in a Maven repo? Are we allowed to distribute it
as part of Geronimo, given that it's under the CDDL?
Thanks,
Aaron
On Wed, 27 Jul 2005, Noel J. Bergman wrote:
FYI. Do not cross-post replies.
--- Noel
-Original Message-
From: A mailing
Oops...my JIRA was 824 :)
- Original Message -
From: David Blevins (JIRA) dev@geronimo.apache.org
To: dev@geronimo.apache.org
Sent: Wednesday, July 27, 2005 3:55 PM
Subject: [jira] Closed: (GERONIMO-823) We should accept (and ignore) simple
type mappings in a jaxrpc-mapping file
[ http://issues.apache.org/jira/browse/GERONIMO-824?page=all ]
David Jencks closed GERONIMO-824:
-
Fix Version: (was: 1.0-M4)
Resolution: Fixed
Assign To: David Jencks
Should actually be assigned to Matt Hogstrom.
Fixed by patch above
[
http://issues.apache.org/jira/browse/GERONIMO-780?page=comments#action_12316982
]
David Jencks commented on GERONIMO-780:
---
GERONIMO-824 is a second instance of the same problem. I don't know how I
fixed one and not the other and thought I was
[ http://issues.apache.org/jira/browse/GERONIMO-823?page=all ]
David Jencks reopened GERONIMO-823:
---
read carefully before closing, Matt fixed GERONIMO-824
We should accept (and ignore) simple type mappings in a jaxrpc-mapping file
schemaLocation attribute values in deployment plans contain problematic
schema\ prefix.
-
Key: GERONIMO-825
URL: http://issues.apache.org/jira/browse/GERONIMO-825
Project: Geronimo
[ http://issues.apache.org/jira/browse/GERONIMO-145?page=all ]
Dain Sundstrom resolved GERONIMO-145:
-
Fix Version: 1.0-M5
Resolution: Fixed
Applied
The CachingLog4jTest and Log4jLog no longer seem relevant, but the rest of the
tests were
Added support to configure min and max threads to the Jetty Container
-
Key: GERONIMO-826
URL: http://issues.apache.org/jira/browse/GERONIMO-826
Project: Geronimo
Type: Improvement
Environment: All
[ http://issues.apache.org/jira/browse/GERONIMO-826?page=all ]
Matt Hogstrom updated GERONIMO-826:
---
Attachment: jetty.diff
Added support to configure min and max threads to the Jetty Container
[ http://issues.apache.org/jira/browse/GERONIMO-826?page=all ]
Jeremy Boynes reassigned GERONIMO-826:
--
Assign To: Jeremy Boynes
Added support to configure min and max threads to the Jetty Container
[ http://issues.apache.org/jira/browse/GERONIMO-824?page=all ]
David Jencks reopened GERONIMO-824:
---
Needs to go into M4 as well.
MdbBuilder sets the Listener Type incorrectly causing NPEs at initialization
[ http://issues.apache.org/jira/browse/GERONIMO-826?page=all ]
Matt Hogstrom updated GERONIMO-826:
---
Attachment: jetty.diff
prior diff did not include Jetty-Builder changes. This is the complete diff
Added support to configure min and max threads to
[ http://issues.apache.org/jira/browse/GERONIMO-824?page=all ]
David Jencks closed GERONIMO-824:
-
Fix Version: 1.0-M4
Resolution: Fixed
m4 fix:
Checking in
modules/openejb-builder/src/java/org/openejb/deployment/MdbBuilder.java;
new revision:
Matt,
If you're up to it, can you submit an additional patch for the
Jetty connectors to fully implement
modules/j2ee/src/java/org/apache/geronimo/j2ee/management/geronimo/WebConnector.java
I've verified that the underlying product supports all the methods
in there (I put the
[ http://issues.apache.org/jira/browse/GERONIMO-796?page=all ]
Aaron Mulder resolved GERONIMO-796:
---
Fix Version: 1.0-M5
Resolution: Fixed
Assign To: Aaron Mulder
Web Server Manager portlet returns error in view mode.
Please revert the change to modules/assembly/maven.xml in HEAD
from revision 219816. I don't know if there's a polite way to present
this, but I am -1 on this change as it results in the openejb schemas not
being present in the output schema/ directory. The change was made by
djencks
I was going to do that tonight or tomorrow and give Tomcat the same lovin.
Matt
- Original Message -
From: Aaron Mulder [EMAIL PROTECTED]
To: dev@geronimo.apache.org
Sent: Wednesday, July 27, 2005 8:44 PM
Subject: Jetty Max Threads Patch
Matt,
If you're up to it, can you submit an
Tomcat will be a little more complicated because we have to break
everything out of the initProps, and create a subclass for the SSL
connector GBean, but it does support all the stuff we need, so it's mostly
a matter of re-arranging.
Thanks,
Aaron
On Wed, 27 Jul 2005, Matt
I certainly have no problem with getting all the schemas into the
output schema directory. I don't remember too clearly but I think I
commented that out because it was causing an error. All the schemas
should be present in the builder jar files now, so I will look for a
more uniform way of
The only case I'm aware of where it caused an error was if you
didn't do an uberbuild (because at the time the latest published OpenEJB
JARs didn't have the schemas included). Anyway, it's not urgent, but I
don't want to forget either. Our schema directory tends to steadily
What's the purpose of the ejb-relation-name and
ejb-relationship-role-name elements at:
openejb-jar/relationships/ejb-relation/ejb-relation-name
openejb-jar/relationships/ejb-relation/ejb-relationship-role/
ejb-relationship-role-name
It
Hi,
They are indeed not used except for documentation purposes. I am not
sure that we should rename them documentation as this will not mirror
the standard DD.
Thanks,
Gianny
On 28/07/2005 12:43 PM, Aaron Mulder wrote:
What's the purpose of the ejb-relation-name and
Aaron Mulder wrote:
What's the purpose of the ejb-relation-name and
ejb-relationship-role-name elements at:
openejb-jar/relationships/ejb-relation/ejb-relation-name
openejb-jar/relationships/ejb-relation/ejb-relationship-role/
On 28/07/2005 1:01 PM, Aaron Mulder wrote:
On Wed, 27 Jul 2005, Jeremy Boynes wrote:
I believe there are certain scenarios where multiple relationships can
exist between a pair of entities and there is no other way to tell them
apart.
Well if this was true, then our code is broken,
I don't like including fields for documentation purposes that have
a name that doesn't make it clear that they're only for documentation.
As Jeremy just demonstrated, it's easy to convince yourself that those
fields should be used in some cases (and I was moderately convinced of
that
Aaron Mulder wrote:
Tomcat will be a little more complicated because we have to break
everything out of the initProps, and create a subclass for the SSL
connector GBean, but it does support all the stuff we need, so it's mostly
a matter of re-arranging.
For subclassing to make an SSL
On Wed, 27 Jul 2005, Jeff Genender wrote:
For subclassing to make an SSL Gbean, I am against this...this nails up
a particular connector GBean, where what I have allows the connector to
be used for just that...a connector...any protocol, etc, makes no
difference here. The Connector
[ http://issues.apache.org/jira/browse/GERONIMO-760?page=all ]
Dain Sundstrom resolved GERONIMO-760:
-
Resolution: Fixed
Changed tmporb to 1.0-DEAD
Move tmporb SNAPSHOT dependency to a dated version in M4 Geronimo OpenEJB
branches
Aaron Mulder wrote:
On Wed, 27 Jul 2005, Jeff Genender wrote:
For subclassing to make an SSL Gbean, I am against this...this nails up
a particular connector GBean, where what I have allows the connector to
be used for just that...a connector...any protocol, etc, makes no
difference here.
[ http://issues.apache.org/jira/browse/GERONIMO-518?page=all ]
Dain Sundstrom reassigned GERONIMO-518:
---
Assign To: Aaron Mulder (was: Dain Sundstrom)
Which app causes this?
Deploying Struts app fails on Logging ClassCastException
[ http://issues.apache.org/jira/browse/GERONIMO-797?page=all ]
Dain Sundstrom resolved GERONIMO-797:
-
Fix Version: (was: 1.1)
Resolution: Fixed
Proxies are registered in the BasicProxyManager:188
public synchronized Object
[ http://issues.apache.org/jira/browse/GERONIMO-677?page=all ]
Kevan Miller updated GERONIMO-677:
--
Attachment: my-changes.patch
Repeated login (after session invalidation) with different credentials
results in incorrect role set.
[
http://issues.apache.org/jira/browse/GERONIMO-677?page=comments#action_12317015
]
Kevan Miller commented on GERONIMO-677:
---
The problem lies in org.apache.geronimo.security.realm.providers.SQLLoginModule
(that's why David wasn't able to reproduce
You convinced me. Let's rename these elements description.
Thanks,
Gianny
On 28/07/2005 1:07 PM, Aaron Mulder wrote:
I don't like including fields for documentation purposes that have
a name that doesn't make it clear that they're only for documentation.
As Jeremy just demonstrated, it's
You might look at the dynamic attributes used in
ManagedConnectionFactoryWrapper, AdminObjectWrapper, and
ResourceAdapterWrapper. They require some xml up front from ra.xml to
determine the exposed properties, but don't require extra
code/implementation class. I am still not happy with
[ http://issues.apache.org/jira/browse/GERONIMO-677?page=all ]
David Jencks updated GERONIMO-677:
--
Summary: Repeated login (after session invalidation) with different
credentials results in incorrect role set. LOGIN MODULES ARE BEING REUSED
(was:
David Jencks wrote:
You might look at the dynamic attributes used in
ManagedConnectionFactoryWrapper, AdminObjectWrapper, and
ResourceAdapterWrapper. They require some xml up front from ra.xml to
determine the exposed properties, but don't require extra
code/implementation class.
53 matches
Mail list logo
