[
https://issues.apache.org/jira/browse/GERONIMO-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated GERONIMO-3609:
--
Attachment: GERONIMO-3609.patch
Proposed fix for this issue.
> JNDI lookup problem on fowa
[
https://issues.apache.org/jira/browse/GERONIMO-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianny Damour closed GERONIMO-3610.
---
Resolution: Fixed
Now implemented.
> Allows the override of XML JavaBean attribute in con
Allows the override of XML JavaBean attribute in config.xml
---
Key: GERONIMO-3610
URL: https://issues.apache.org/jira/browse/GERONIMO-3610
Project: Geronimo
Issue Type: Improvement
There is also a comma in the filename!! Should that be got rid of too?
++Vamsi
On Nov 20, 2007 1:27 AM, Jarek Gawor <[EMAIL PROTECTED]> wrote:
> SVN checkout on Windows is failing for me becuase recently a file was
> renamed to have ":" in the name. That's not supported on Windows. Can
> we cha
[
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Warner updated GSHELL-20:
---
Attachment: GShell-20.patch
I was hoping to handle this purely in the parser, but I'm not sure if that
[
https://issues.apache.org/jira/browse/GERONIMO-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543772
]
Jarek Gawor commented on GERONIMO-3609:
---
First, we are dealing with two different web application
contexts (
I've looked at this a bit and here's my current understanding of the
problem. First, we are dealing with two different web application
contexts (/console and /MonitoringPortlet) and both web app contexts
have different JNDI trees with different resources. The console is
basically forwarding a reque
JNDI lookup problem on fowarded calls in Jetty
--
Key: GERONIMO-3609
URL: https://issues.apache.org/jira/browse/GERONIMO-3609
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular
Geronimo Revision: 596510 built with tests included
See the full build-2100.log file at
http://people.apache.org/~prasad/binaries/2.0/20071119/build-2100.log
Download the binaries from
http://people.apache.org/~prasad/binaries/2.0/20071119
[INFO] BUILD SUCCESSFUL
[INFO
[
https://issues.apache.org/jira/browse/GERONIMO-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543754
]
Anita Kulshreshtha commented on GERONIMO-3608:
--
committed in rev. 596514, also fixed statistics names
Move Jetty*Stats and Jetty*StatsImpl to geronimo-management
Key: GERONIMO-3608
URL: https://issues.apache.org/jira/browse/GERONIMO-3608
Project: Geronimo
Issue Type: Improvement
On Nov 19, 2007, at 7:33 AM, Viet Nguyen wrote:
I believe Anita is correct on this one. The specs define that we need
the getXYZ() methods for each statistics named XYZ. At this point, I
think we need to move forward with a decision a) put everything in
g-management or b) split jetty/tomcat sta
Hi, does anyone have a general understanding of how remote deployment using the
Geronimo CLI is supposed to work ?? Reason I ask is that it doesn't appear to be
working. Here are the messages I'm getting below:
Uploading 1 file(s) to server
Uploading mytime.ear: 11 KB
Uploading myti
SVN checkout on Windows is failing for me becuase recently a file was
renamed to have ":" in the name. That's not supported on Windows. Can
we change this back?
Here's the change:
http://svn.apache.org/viewvc/geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/src/main/underlay/etc/rc.d/
[
https://issues.apache.org/jira/browse/GERONIMO-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh resolved GERONIMO-3271.
-
Resolution: Fixed
Fix Version/s: 2.1
All programs that were referencing attribu
[
https://issues.apache.org/jira/browse/GERONIMO-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh resolved GERONIMO-3266.
-
Resolution: Fixed
Fix Version/s: 2.1
I believe that the attributes-1.2.xsd is s
[
https://issues.apache.org/jira/browse/GERONIMO-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543651
]
Jay D. McHugh commented on GERONIMO-1265:
-
Committed revision 596403.
Here is a new set of changes that s
I believe Anita is correct on this one. The specs define that we need
the getXYZ() methods for each statistics named XYZ. At this point, I
think we need to move forward with a decision a) put everything in
g-management or b) split jetty/tomcat stats apart.
As for me, I say let's just go with optio
Geronimo Revision: 596295 built with tests included
See the full build-0900.log file at
http://people.apache.org/~prasad/binaries/2.0/20071119/build-0900.log
Download the binaries from
http://people.apache.org/~prasad/binaries/2.0/20071119
[INFO] BUILD SUCCESSFUL
[INFO
Hey Dave,
for some reason my reply never went out.
This is great, let's keep it here on GMOxDEV while you still working on it and
then we'll see how to include/move over the 2.1 doc.
Cheers!
Hernan
David Jencks wrote:
I started a page on new plugin stuff over here...
http://cwiki.apache.org
[
https://issues.apache.org/jira/browse/GERONIMO-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543593
]
Jarek Gawor commented on GERONIMO-3545:
---
Just committed the change (revision 596325). I already sent some no
[
https://issues.apache.org/jira/browse/GERONIMO-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen closed GERONIMO-3586.
--
Resolution: Invalid
Fix Version/s: 2.1
The problem is now invalid. There are
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543523
]
Jason Dillon commented on GSHELL-81:
Do you have a stack trace for this?
>From looking at the XStream src it appe
What JVM were you using BTW?
--jason
-Original Message-
From: "Guillaume Nodet" <[EMAIL PROTECTED]>
Date: Mon, 19 Nov 2007 10:41:32
To:dev@geronimo.apache.org
Subject: [[GShell] Dependency on sun.* packages
It seems that GShell is currently unable to run without the sun.* packages in
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543518
]
Jason Dillon commented on GSHELL-81:
I think that the pure java stuff should probably work, we can give that a try
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-81:
---
Component/s: Core
Fix Version/s: 1.0-alpha-2
Description:
It seems that GShell is currentl
[
https://issues.apache.org/jira/browse/GSHELL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-81:
---
Description:
It seems that GShell is currently unable to run without the sun.* packages in
the classl
Depdendency on sun.* packages
-
Key: GSHELL-81
URL: https://issues.apache.org/jira/browse/GSHELL-81
Project: GShell
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Guillaume Nod
Can ya put this in JIRA please?
--jason
On Nov 19, 2007, at 1:41 AM, Guillaume Nodet wrote:
It seems that GShell is currently unable to run without the sun.*
packages in the classloader.
The reason is that it uses xstream advanced mode which make use of
these packages.
If these packages ar
It seems that GShell is currently unable to run without the sun.* packages
in the classloader.
The reason is that it uses xstream advanced mode which make use of these
packages.
If these packages are not on the classpath, xstream will default to the pure
java reflection provider which will cause ex
Geronimo Revision: 596217 built with tests included
See the full build-0300.log file at
http://people.apache.org/~prasad/binaries/2.0/20071119/build-0300.log
Download the binaries from
http://people.apache.org/~prasad/binaries/2.0/20071119
[INFO] BUILD SUCCESSFUL
[INFO
31 matches
Mail list logo
