[jira] Closed: (GERONIMO-235) No JSP support without tools.jar

2004-09-09 Thread dev
Message:

   The following issue has been closed.

   Resolver: Dain Sundstrom
   Date: Wed, 8 Sep 2004 8:34 PM

Added hack to find tools.jar and forcibly install it into the system class 
loader when a java compiler is not available
-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-235

Here is an overview of the issue:
-
Key: GERONIMO-235
Summary: No JSP support without tools.jar
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: Dain Sundstrom
   Reporter: David Blevins

Created: Tue, 18 May 2004 1:18 AM
Updated: Wed, 8 Sep 2004 8:34 PM

Description:
Geronimo only uses libraries in the geronimo.home/repository/ directory.  The 
JAVA_HOME/lib/tools.jar is not one of them, therefore no JSP support is 
possible as Java files can't be compiled.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-281) Optional packages support

2004-09-09 Thread dev
The following issue has been updated:

Updater: Dain Sundstrom (mailto:[EMAIL PROTECTED])
   Date: Wed, 8 Sep 2004 8:47 PM
Changes:
 description changed from 
Add optional packages support. Optional packages are resources listed in 
META-INF/MANIFEST.MF as a value of the Class-Path main attribute.

As a workaround it's possible to copy the resources to repository directory and 
specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.

The suggested approach to handle it is (Dain's email to OpenEJB dev mailing 
list):

[...]Instead I would create a lib directory in the config-store directory for 
the module (i.e., a config-store/${number}/lib directory).  Then, just read in 
the manifest class path entries for the ejb jar, copy them into the lib dir and 
add them to the configuration class-path.  One trick is you must repeat this 
for each jar copied into the lib as each of these can have manifest class path 
entries.  Also watch out for circular dependencies in the manifest class path 
entries.[...] to Add optional packages support. Optional packages are resources 
listed in META-INF/MANIFEST.MF as a value of the Class-Path main attribute.

As a workaround it's possible to copy the resources to repository directory and 
specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.

The suggested approach to handle it is (Dain's email to OpenEJB dev mailing 
list):

[...]Instead I would create a lib directory in the config-store directory for 
the module (i.e., a config-store/${number}/lib directory).  Then, just read in 
the manifest class path entries for the ejb jar, copy them into the lib dir and 
add them to the configuration class-path.  One trick is you must repeat this 
for each jar copied into the lib as each of these can have manifest class path 
entries.  Also watch out for circular dependencies in the manifest class path 
entries.[...]
 Version changed to 1.0-M1
-
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/GERONIMO-281?page=history

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-281

Here is an overview of the issue:
-
Key: GERONIMO-281
Summary: Optional packages support
   Type: New Feature

 Status: In Progress
   Priority: Major

Project: Apache Geronimo
 Components: 
 deployment
 OpenEJB
   Versions:
 1.0-M1

   Assignee: Jacek Laskowski
   Reporter: Jacek Laskowski

Created: Tue, 3 Aug 2004 4:37 AM
Updated: Wed, 8 Sep 2004 8:47 PM

Description:
Add optional packages support. Optional packages are resources listed in 
META-INF/MANIFEST.MF as a value of the Class-Path main attribute.

As a workaround it's possible to copy the resources to repository directory and 
specify them in a vendor specific way/DD, e.g. META-INF/openejb-jar.xml.

The suggested approach to handle it is (Dain's email to OpenEJB dev mailing 
list):

[...]Instead I would create a lib directory in the config-store directory for 
the module (i.e., a config-store/${number}/lib directory).  Then, just read in 
the manifest class path entries for the ejb jar, copy them into the lib dir and 
add them to the configuration class-path.  One trick is you must repeat this 
for each jar copied into the lib as each of these can have manifest class path 
entries.  Also watch out for circular dependencies in the manifest class path 
entries.[...]


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-234) Build fails when maven/plugins is not writable

2004-09-09 Thread dev
The following issue has been updated:

Updater: Dain Sundstrom (mailto:[EMAIL PROTECTED])
   Date: Wed, 8 Sep 2004 8:47 PM
Changes:
 description changed from When building by invoking 'maven' the 
build fails with the following error message when the maven plugin directory is 
not writable:

+
| Executing (default): Geronimo :: Deployment
| Memory: 34M/43M
+
Attempting to download geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar.
Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
Attempting to download geronimo-system-1.0-SNAPSHOT.jar.

BUILD FAILED
File.. file:/home/username/apache/incubator-geronimo/
Element... maven:reactor
Line.. 180
Column 27
/usr/local/maven-1.0-rc1/plugins/geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar 
(Permission denied)

The immediate fix is to make plugins folder writable.

I don't like any project modifying their sibbling projects... couldn't this 
also lead to unexpected results in a multi-user environment where maven is 
shared among users?

 to When building by invoking 'maven' the build fails with the following error 
message when the maven plugin directory is not writable:

+
| Executing (default): Geronimo :: Deployment
| Memory: 34M/43M
+
Attempting to download geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar.
Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
Attempting to download geronimo-system-1.0-SNAPSHOT.jar.

BUILD FAILED
File.. file:/home/username/apache/incubator-geronimo/
Element... maven:reactor
Line.. 180
Column 27
/usr/local/maven-1.0-rc1/plugins/geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar 
(Permission denied)

The immediate fix is to make plugins folder writable.

I don't like any project modifying their sibbling projects... couldn't this 
also lead to unexpected results in a multi-user environment where maven is 
shared among users?

 environment changed from Linux [Debian | SuSE ], Maven RC1, 
Geronimo HEAD
 to Linux [Debian | SuSE ], Maven RC1, Geronimo HEAD
 Version changed to 1.0-M1
-
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/GERONIMO-234?page=history

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-234

Here is an overview of the issue:
-
Key: GERONIMO-234
Summary: Build fails when maven/plugins is not writable
   Type: Improvement

 Status: Open
   Priority: Minor

Project: Apache Geronimo
 Components: 
 buildsystem
   Versions:
 1.0-M1

   Assignee: Dain Sundstrom
   Reporter: Bernd Fondermann

Created: Sat, 15 May 2004 2:34 AM
Updated: Wed, 8 Sep 2004 8:47 PM
Environment: Linux [Debian | SuSE ], Maven RC1, Geronimo HEAD

Description:
When building by invoking 'maven' the build fails with the following error 
message when the maven plugin directory is not writable:

+
| Executing (default): Geronimo :: Deployment
| Memory: 34M/43M
+
Attempting to download geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar.
Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
Attempting to download geronimo-system-1.0-SNAPSHOT.jar.

BUILD FAILED
File.. file:/home/username/apache/incubator-geronimo/
Element... maven:reactor
Line.. 180
Column 27
/usr/local/maven-1.0-rc1/plugins/geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar 
(Permission denied)

The immediate fix is to make plugins folder writable.

I don't like any project modifying their sibbling projects... couldn't this 
also lead to unexpected results in a multi-user environment where maven is 
shared among users?



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-242) Keep history of running configurations

2004-09-09 Thread dev
The following issue has been updated:

Updater: Dain Sundstrom (mailto:[EMAIL PROTECTED])
   Date: Wed, 8 Sep 2004 8:48 PM
Changes:
 Version changed to 1.0-M2
-
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/GERONIMO-242?page=history

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-242

Here is an overview of the issue:
-
Key: GERONIMO-242
Summary: Keep history of running configurations
   Type: Improvement

 Status: Reopened
   Priority: Minor

Project: Apache Geronimo
 Components: 
 management
   Versions:
 1.0-M2

   Assignee: 
   Reporter: Jeremy Boynes

Created: Fri, 4 Jun 2004 10:51 AM
Updated: Wed, 8 Sep 2004 8:48 PM

Description:
The server should keep a list of previously known running configurations rather 
than just the last one (just in case it it broken or gets corrupted during 
shutdown).


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



why is SpringGBean.createGBean() not implemented?

2004-09-09 Thread Bruce Snyder
Can someone tell me why this method has not been implemented yet? What 
are the repercussions of creating a GBean wrapper for the 
BeanPostProcessor.postProcessAfterInitialization() method?

Any tips or hints are appreciated.
Bruce
--
perl -e 'print 
unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O;0\\`\\`);'

The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html


Eve integration with Geronimo

2004-09-09 Thread Bruce Snyder
Does anyone have a configuration or a plan that integrates Eve with 
Geronimo? If not, can anyone tell me if there are any tricks to creating 
one?

Bruce
--
perl -e 'print 
unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O;0\\`\\`);'

The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html


clustering module

2004-09-09 Thread Bruce Snyder
I see that there is a clustering module in CVS created by Alan. Has 
anyone given any thought on how the clustering can be achieved? Are 
there any projects out there with a BSD derived license that can assist 
us with clustering in the same or similar manner that JGroups is used by 
JBoss?

Bruce
--
perl -e 'print 
unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O;0\\`\\`);'

The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html


[jira] Closed: (GERONIMO-205) J2EE Connector support for JMS Providers

2004-09-09 Thread dev
Message:

   The following issue has been closed.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-205

Here is an overview of the issue:
-
Key: GERONIMO-205
Summary: J2EE Connector support for JMS Providers
   Type: New Feature

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 7:18 PM
Updated: Wed, 8 Sep 2004 9:50 PM

Description:
No J2EE Connector (JSR 112) exists for deploying JMS Providers.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Reopened: (GERONIMO-206) Hot deployment of EJB, WAR, and RAR archives

2004-09-09 Thread dev
Message:

   The following issue has been reopened.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-206

Here is an overview of the issue:
-
Key: GERONIMO-206
Summary: Hot deployment of EJB, WAR, and RAR archives
   Type: Task

 Status: Reopened
   Priority: Major

Project: Apache Geronimo
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 9:37 PM
Updated: Wed, 8 Sep 2004 9:51 PM

Description:
At current time it is not possible to deploy an ejb, war, or rar while the 
server is started.  Due to the read-only nature of Geronimo config-stores, 
deployment may only happen when the server is stopped.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Closed: (GERONIMO-206) Hot deployment of EJB, WAR, and RAR archives

2004-09-09 Thread dev
Message:

   The following issue has been closed.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-206

Here is an overview of the issue:
-
Key: GERONIMO-206
Summary: Hot deployment of EJB, WAR, and RAR archives
   Type: New Feature

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 9:37 PM
Updated: Wed, 8 Sep 2004 9:53 PM

Description:
At current time it is not possible to deploy an ejb, war, or rar while the 
server is started.  Due to the read-only nature of Geronimo config-stores, 
deployment may only happen when the server is stopped.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



Re: using resource-ref in web.xml?

2004-09-09 Thread Rajesh Ravindran
Hey All,

I used to get a problem while giving the ejb-ref in
geronimo-jetty.xml(openejb-jar.xml). It wouldnt lookup for the
target-name.

So I had to add ejb-links in web.xml (ejb-jar.xml).  then it worked.
Did the fix by David mean that this problem has been fixed  i can
work without the ejb-links?

Thanks
Rajesh


[jira] Reopened: (GERONIMO-211) Servlet web.xml resource-ref support to JMS

2004-09-09 Thread dev
Message:

   The following issue has been reopened.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-211

Here is an overview of the issue:
-
Key: GERONIMO-211
Summary: Servlet web.xml resource-ref support to JMS
   Type: Task

 Status: Reopened
   Priority: Major

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 10:04 PM
Updated: Wed, 8 Sep 2004 10:01 PM

Description:
Support for JMS Topics or Queues via the resource-ref element in the web.xml is 
not yet implemented.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Closed: (GERONIMO-211) Servlet web.xml resource-ref support to JMS

2004-09-09 Thread dev
Message:

   The following issue has been closed.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-211

Here is an overview of the issue:
-
Key: GERONIMO-211
Summary: Servlet web.xml resource-ref support to JMS
   Type: New Feature

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 10:04 PM
Updated: Wed, 8 Sep 2004 10:02 PM

Description:
Support for JMS Topics or Queues via the resource-ref element in the web.xml is 
not yet implemented.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Reopened: (GERONIMO-212) EJB ejb-jar.xml resource-ref support to JMS

2004-09-09 Thread dev
Message:

   The following issue has been reopened.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-212

Here is an overview of the issue:
-
Key: GERONIMO-212
Summary: EJB ejb-jar.xml resource-ref support to JMS
   Type: Task

 Status: Reopened
   Priority: Major

Project: Apache Geronimo
 Components: 
 OpenEJB
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 10:05 PM
Updated: Wed, 8 Sep 2004 10:03 PM

Description:
Support for JMS Topics or Queues via the resource-ref element in the 
ejb-jar.xml is not yet implemented.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-212) EJB ejb-jar.xml resource-ref support to JMS

2004-09-09 Thread dev
The following issue has been updated:

Updater: Dain Sundstrom (mailto:[EMAIL PROTECTED])
   Date: Wed, 8 Sep 2004 10:04 PM
Changes:
 type changed from Task to New Feature
-
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/GERONIMO-212?page=history

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-212

Here is an overview of the issue:
-
Key: GERONIMO-212
Summary: EJB ejb-jar.xml resource-ref support to JMS
   Type: New Feature

 Status: Reopened
   Priority: Major

Project: Apache Geronimo
 Components: 
 OpenEJB
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 10:05 PM
Updated: Wed, 8 Sep 2004 10:04 PM

Description:
Support for JMS Topics or Queues via the resource-ref element in the 
ejb-jar.xml is not yet implemented.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Closed: (GERONIMO-212) EJB ejb-jar.xml resource-ref support to JMS

2004-09-09 Thread dev
Message:

   The following issue has been closed.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-212

Here is an overview of the issue:
-
Key: GERONIMO-212
Summary: EJB ejb-jar.xml resource-ref support to JMS
   Type: New Feature

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
 Components: 
 OpenEJB
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: David Blevins

Created: Sun, 25 Apr 2004 10:05 PM
Updated: Wed, 8 Sep 2004 10:04 PM

Description:
Support for JMS Topics or Queues via the resource-ref element in the 
ejb-jar.xml is not yet implemented.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Reopened: (GERONIMO-223) Upgrade Jetty5.0beta0 to Jetty5.0RC0

2004-09-09 Thread dev
Message:

   The following issue has been reopened.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-223

Here is an overview of the issue:
-
Key: GERONIMO-223
Summary: Upgrade Jetty5.0beta0 to Jetty5.0RC0
   Type: Task

 Status: Reopened
   Priority: Major

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: Jan Bartel

Created: Mon, 26 Apr 2004 1:36 AM
Updated: Wed, 8 Sep 2004 10:05 PM

Description:
The latest release of Jetty5 is RC0. Geronimo should be upgraded prior to 
release.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Closed: (GERONIMO-223) Upgrade Jetty5.0beta0 to Jetty5.0RC0

2004-09-09 Thread dev
Message:

   The following issue has been closed.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-223

Here is an overview of the issue:
-
Key: GERONIMO-223
Summary: Upgrade Jetty5.0beta0 to Jetty5.0RC0
   Type: Improvement

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: 
   Reporter: Jan Bartel

Created: Mon, 26 Apr 2004 1:36 AM
Updated: Wed, 8 Sep 2004 10:06 PM

Description:
The latest release of Jetty5 is RC0. Geronimo should be upgraded prior to 
release.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-245) OutOfMemoryError while running ConnectionManagerStressTest

2004-09-09 Thread dev
The following issue has been updated:

Updater: Dain Sundstrom (mailto:[EMAIL PROTECTED])
   Date: Wed, 8 Sep 2004 10:07 PM
Changes:
 type changed from Task to Bug
-
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/GERONIMO-245?page=history

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-245

Here is an overview of the issue:
-
Key: GERONIMO-245
Summary: OutOfMemoryError while running ConnectionManagerStressTest
   Type: Bug

 Status: Reopened
   Priority: Minor

Project: Apache Geronimo
 Components: 
 buildsystem
 connector
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M2

   Assignee: 
   Reporter: Ralf Barkow

Created: Sat, 12 Jun 2004 2:44 PM
Updated: Wed, 8 Sep 2004 10:07 PM
Environment: Windows 2000 Prof DE (5.00.2195) SP4, Java 1.4.2_04-b05, maven 
1.0-rc2
AMD-K6(tm) 3D processor with 384 MB RAM

Description:
Building the current 1.0-SNAPSHOT on my 'thin-chested' Win2kProf DE box with 
java v1.4.2_04-b05, there's now an OutOfMemoryError while running the 
connector.outbound.ConnectionManagerStressTest.  Okay, 384 MB RAM isn't that 
much, but obviously no problem if I run this test in Eclipse3M8. Everything's 
green there -- test(s) passed.  

Setting MAVEN_OPTS=-Xmxmemory_size didn't help.  I tried 512m and -- probably 
more realistic -- 256M, which I also use in the comand line arguments for 
Eclipse.  

Workaround: I build -- successfully btw -- with 
maven -Dmaven.test.failure.ignore=true 
for now.

Is this a maven bug (v. 1.0-rc2) ?  Or a problem with the installed JREs?  
Eclipse runs under/uses AppServer-jdk-1.4.2_04-b04, which is JAVA_HOME also, 
vs. j2re-1.4.2_04-b05 in WINNT/system32/ and programs, which seems to be 
launched by maven, shells, etc.  

Any ideas?
--  
/rgb


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Reopened: (GERONIMO-245) OutOfMemoryError while running ConnectionManagerStressTest

2004-09-09 Thread dev
Message:

   The following issue has been reopened.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-245

Here is an overview of the issue:
-
Key: GERONIMO-245
Summary: OutOfMemoryError while running ConnectionManagerStressTest
   Type: Task

 Status: Reopened
   Priority: Minor

Project: Apache Geronimo
 Components: 
 buildsystem
 connector
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M2

   Assignee: 
   Reporter: Ralf Barkow

Created: Sat, 12 Jun 2004 2:44 PM
Updated: Wed, 8 Sep 2004 10:07 PM
Environment: Windows 2000 Prof DE (5.00.2195) SP4, Java 1.4.2_04-b05, maven 
1.0-rc2
AMD-K6(tm) 3D processor with 384 MB RAM

Description:
Building the current 1.0-SNAPSHOT on my 'thin-chested' Win2kProf DE box with 
java v1.4.2_04-b05, there's now an OutOfMemoryError while running the 
connector.outbound.ConnectionManagerStressTest.  Okay, 384 MB RAM isn't that 
much, but obviously no problem if I run this test in Eclipse3M8. Everything's 
green there -- test(s) passed.  

Setting MAVEN_OPTS=-Xmxmemory_size didn't help.  I tried 512m and -- probably 
more realistic -- 256M, which I also use in the comand line arguments for 
Eclipse.  

Workaround: I build -- successfully btw -- with 
maven -Dmaven.test.failure.ignore=true 
for now.

Is this a maven bug (v. 1.0-rc2) ?  Or a problem with the installed JREs?  
Eclipse runs under/uses AppServer-jdk-1.4.2_04-b04, which is JAVA_HOME also, 
vs. j2re-1.4.2_04-b05 in WINNT/system32/ and programs, which seems to be 
launched by maven, shells, etc.  

Any ideas?
--  
/rgb


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Closed: (GERONIMO-245) OutOfMemoryError while running ConnectionManagerStressTest

2004-09-09 Thread dev
Message:

   The following issue has been closed.

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-245

Here is an overview of the issue:
-
Key: GERONIMO-245
Summary: OutOfMemoryError while running ConnectionManagerStressTest
   Type: Bug

 Status: Closed
   Priority: Minor
 Resolution: FIXED

Project: Apache Geronimo
 Components: 
 buildsystem
 connector
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M2

   Assignee: 
   Reporter: Ralf Barkow

Created: Sat, 12 Jun 2004 2:44 PM
Updated: Wed, 8 Sep 2004 10:07 PM
Environment: Windows 2000 Prof DE (5.00.2195) SP4, Java 1.4.2_04-b05, maven 
1.0-rc2
AMD-K6(tm) 3D processor with 384 MB RAM

Description:
Building the current 1.0-SNAPSHOT on my 'thin-chested' Win2kProf DE box with 
java v1.4.2_04-b05, there's now an OutOfMemoryError while running the 
connector.outbound.ConnectionManagerStressTest.  Okay, 384 MB RAM isn't that 
much, but obviously no problem if I run this test in Eclipse3M8. Everything's 
green there -- test(s) passed.  

Setting MAVEN_OPTS=-Xmxmemory_size didn't help.  I tried 512m and -- probably 
more realistic -- 256M, which I also use in the comand line arguments for 
Eclipse.  

Workaround: I build -- successfully btw -- with 
maven -Dmaven.test.failure.ignore=true 
for now.

Is this a maven bug (v. 1.0-rc2) ?  Or a problem with the installed JREs?  
Eclipse runs under/uses AppServer-jdk-1.4.2_04-b04, which is JAVA_HOME also, 
vs. j2re-1.4.2_04-b05 in WINNT/system32/ and programs, which seems to be 
launched by maven, shells, etc.  

Any ideas?
--  
/rgb


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



Re: clustering module

2004-09-09 Thread Dain Sundstrom
That module has basically been abandoned.  I expect us to use  
ActiveCluser for the clustering.

-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Sep 8, 2004, at 9:06 PM, Bruce Snyder wrote:
I see that there is a clustering module in CVS created by Alan. Has  
anyone given any thought on how the clustering can be achieved? Are  
there any projects out there with a BSD derived license that can  
assist us with clustering in the same or similar manner that JGroups  
is used by JBoss?

Bruce
--  
perl -e 'print  
unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O; 
0\\`\\`);'

The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html



Re: is anyone working on integration with Derby yet?

2004-09-09 Thread Jeremy Boynes
I have been tracking the Derby lists and brought it up there but did not 
get any comment. It already does XA and I believe they have a connector 
so there may not be much to do except a GBean wrapper.

I would like to propose we switch to it rather than Axion for the 
embedded database we include in the distro. However, Derby takes quite a 
while to initialize a db so it is probably worth sticking to Axion for 
the unit tests where we continually build/destroy dbs.

--
Jeremy
Bruce Snyder wrote:
I was thinking of starting to work with Derby in general and wondering 
if it had been integrated into Geronimo yet? Has anyone given this any 
thought yet?

Bruce


[status] build: FAILED, test: FAILED | Linux 2.4.26, 2004-09-09

2004-09-09 Thread dblevins
NIGHTLY BUILD/TEST
  Date: Thu Sep  9 05:44:04 EDT 2004
  Kernel: Linux 2.4.26
  Host: beaver.codehaus.org
  Java: 1.4.2_04-b05, mixed mode
  Maven: 1.0

CHECKOUT: incubator-geronimo

BUILDING: incubator-geronimo
[junit] [ERROR] TEST 
org.apache.geronimo.security.bridge.CallerIdentityUserPasswordBridgeTest FAILED
BUILD FAILED

BUILD FAILED
Total time: 11 minutes 12 seconds
Finished at: Thu Sep 09 05:57:31 EDT 2004


Re: clustering module

2004-09-09 Thread John Woolsey
Isn't the standard way to implement clustering to implement a clustered 
JMS and then make everything else rely on that?

Also for a clustering implementation. Let's say I have information on 
Server A and I want to ensure it is clustered so I send it to server B. 
Is a standard implementation to fire it over a socket and wait for 
receipt confirmation and then move on or are people generally more 
sophisticated then that?


  - bfn - JAW

Dain Sundstrom wrote:
That module has basically been abandoned.  I expect us to use  
ActiveCluser for the clustering.

-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Sep 8, 2004, at 9:06 PM, Bruce Snyder wrote:
I see that there is a clustering module in CVS created by Alan. Has  
anyone given any thought on how the clustering can be achieved? Are  
there any projects out there with a BSD derived license that can  
assist us with clustering in the same or similar manner that JGroups  
is used by JBoss?

Bruce
--  perl -e 'print  
unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O; 0\\`\\`);'

The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html





Re: using resource-ref in web.xml?

2004-09-09 Thread toby cabot
On Wed, Sep 08, 2004 at 05:31:45PM -0500, David Jencks wrote:
 Don't know about the wiki but it ought to look like this (taken from an  
 openejb example):
 resource-ref
 ref-namestateless/references/Resource_manager_access/ref-name
 target-nameDefaultDatasource/target-name
 /resource-ref

Thanks as always for your help.  With this tip I think that I'm
getting close but still no cigar.  My RA's
connectiondefinition-instance name is testCF and if I use:

web.xml:
resource-ref
res-ref-namera/CF/res-ref-name
res-typeg6o.ra.ConnectionFactory/res-type
res-authApplication/res-auth
/resource-ref

geronimo-jetty.xml:
resource-ref
ref-namera/CF/ref-name
target-nametestCF/target-name
/resource-ref

...I can deploy, and the server runs, but I get a NamingException in
the servlet init which I've attached as a postscript.  The strange
part is that if I cut and paste the target name that the exception
message indicated was not started into the debug console Filter
Output box it shows up as running.  Perhaps there's an issue with the
order in which the components within the ear are being started?  Can I
influence that order somehow?

As an aside, this is a soft exception in that Geronimo keeps running
after it happens; even the servlet is running.  If I do something to
cause a different error, i.e. try to look up an obviously bogus JNDI
name, then Geronimo will shut down.

Thanks,
Toby

PS: EJB lookup with an ejb-link works now (didn't before), and I'll
look into the non-ejb-link case.

PPS: stack trace:

javax.naming.NamingException: could not look up : env/ra/CF [Root exception is 
java.lang.IllegalStateException: Proxy not returned. Target 
geronimo.server:J2EEServer=geronimo,j2eeType=JCAManagedConnectionFactory,name=testCF
 not started]
at 
org.apache.geronimo.naming.java.ReadOnlyContext.lookup(ReadOnlyContext.java:209)
at 
org.apache.geronimo.naming.java.RootContext.lookup(RootContext.java:55)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at g6o.servlet.Servlet.init(Servlet.java:51)
at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:226)
at 
org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:390)
at 
org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:287)
at 
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:421)
at 
org.apache.geronimo.jetty.JettyWebAppContext.doStart(JettyWebAppContext.java:219)
at org.apache.geronimo.gbean.jmx.GBeanMBean.doStart(GBeanMBean.java:593)
at 
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:479)
at 
org.apache.geronimo.gbean.jmx.SingleProxy.attemptFullStart(SingleProxy.java:154)
at 
org.apache.geronimo.gbean.jmx.SingleProxy.addTarget(SingleProxy.java:119)
at 
org.apache.geronimo.gbean.jmx.GBeanMBeanReference.handleNotification(GBeanMBeanReference.java:307)
at 
mx4j.server.interceptor.NotificationListenerMBeanServerInterceptor$ListenerWrapper.handleNotification(NotificationListenerMBeanServerInterceptor.java:57)
at 
javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:346)
at 
javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:320)
at 
org.apache.geronimo.gbean.jmx.AbstractManagedObject.sendNotification(AbstractManagedObject.java:244)
at 
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:500)
at 
org.apache.geronimo.gbean.jmx.AbstractManagedObject.start(AbstractManagedObject.java:279)
at 
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:303)
at 
org.apache.geronimo.gbean.jmx.GBeanMBean$9.invoke(GBeanMBean.java:940)
at 
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:767)
at 
mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:218)
at 
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:121)
at 
mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:86)
at 
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:121)
at 
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:121)
at 
mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:205)
at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1079)
  

[jira] Reopened: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support

2004-09-09 Thread dev
Message:

   The following issue has been reopened.

   Reopener: David Jencks
   Date: Thu, 9 Sep 2004 9:48 AM

taglib tags move into jsp-config tag.  This is not handled by jetty.
-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-278

Here is an overview of the issue:
-
Key: GERONIMO-278
Summary: Servlet/JSP 2.3 DTD deployment descriptor support
   Type: New Feature

 Status: Reopened
   Priority: Major

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1

   Assignee: David Jencks
   Reporter: David Blevins

Created: Thu, 29 Jul 2004 5:53 PM
Updated: Thu, 9 Sep 2004 9:48 AM

Description:
Servlet/JSP 2.2 DTD deployment descriptor support


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



[jira] Closed: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support

2004-09-09 Thread dev
Message:

   The following issue has been closed.

   Resolver: David Jencks
   Date: Thu, 9 Sep 2004 9:50 AM

Schema utils modified to move taglib tags into a new jsp-config tag.
-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-278

Here is an overview of the issue:
-
Key: GERONIMO-278
Summary: Servlet/JSP 2.3 DTD deployment descriptor support
   Type: New Feature

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M3
   Versions:
 1.0-M1

   Assignee: David Jencks
   Reporter: David Blevins

Created: Thu, 29 Jul 2004 5:53 PM
Updated: Thu, 9 Sep 2004 9:50 AM

Description:
Servlet/JSP 2.2 DTD deployment descriptor support


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



Re: [jira] Reopened: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support

2004-09-09 Thread David Jencks
What don't you understand about my comment?  It seems short but fairly 
clear to me.

david jencks
On Sep 9, 2004, at 12:01 PM, Dain Sundstrom wrote:
David,
Can you update this issue to reflect what is actually broken or open a 
new issue?

-dain
On Sep 9, 2004, at 9:49 AM, [EMAIL PROTECTED] wrote:
Message:
   The following issue has been reopened.
   Reopener: David Jencks
   Date: Thu, 9 Sep 2004 9:48 AM
taglib tags move into jsp-config tag.  This is not handled by jetty.
-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-278
Here is an overview of the issue:
-
Key: GERONIMO-278
Summary: Servlet/JSP 2.3 DTD deployment descriptor support
   Type: New Feature
 Status: Reopened
   Priority: Major
Project: Apache Geronimo
 Components:
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1
   Assignee: David Jencks
   Reporter: David Blevins
Created: Thu, 29 Jul 2004 5:53 PM
Updated: Thu, 9 Sep 2004 9:48 AM
Description:
Servlet/JSP 2.2 DTD deployment descriptor support
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the 
administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira




Re: Installing Confluence

2004-09-09 Thread Dain Sundstrom
So last night as part of the release schedule I needed to update our 
wiki, and it took me a half hour just to figure out how to login 
MoinMoin...

Can anyone give us an up or down answer on if we can get confluence 
installed at Apache?  If it we can't, I propose we find confluence 
space for Geronimo somewhere offsite.

-dain
On Sep 8, 2004, at 1:59 PM, David Blevins wrote:
I also volunteered to help when the original thread was going on.  
Would be nice to see this setup.

-David
On Tue, Sep 07, 2004 at 10:08:20AM -0700, Dain Sundstrom wrote:
Does anyone know where we are at with this?  I am more than willing to
help.
-dain
On Jul 22, 2004, at 9:11 PM, [EMAIL PROTECTED] wrote:
I'm willing to help out - I just about qualify for the requirements I
guess.
On 23 Jul 2004, at 02:51, Jeff Turner wrote:
Would anyone else be willing to help with care and feeding of an ASF
Confluence instance?  Requirements for the job:
a) an ASF committer, preferably been around a few years
b) know how to deploy a webapp and admin a Tomcat instance
c) somewhat unix-savvy
d) willing to commit random bits of time for months to come to do
things
   like upgrades
If there's a volunteer or two, I guess the next steps would be to
hold a
(PMC-ratified) vote and send a mail off to infrastructure@ for 
advice.
They may wish to delay installation until a successor to nagoya is
ready.

--Jeff
On Thu, Jul 22, 2004 at 05:11:40PM +0100, [EMAIL PROTECTED] wrote:
On 21 Jul 2004, at 17:15, Matt Kurjanowicz wrote:
Hmm, are we moving a little too fast on moving to Confluence?   
Like
someone said earlier, we've already switched wiki's once, and I
don't
know (beyond wiki - xdoc) what benefits Confluence has over 
Wikis.
Security, features, wiki language, macros for integrating with unit
test code / JIRA reports - but mostly its just a nice tool to use
etc.
Its like saying, hey this JIRA things OK but whats wrong with
bugzilla.
If you've used both you'll know what I mean.

It may even be easier to update the tool (wiki-xdoc) to 
understand
the wiki we have now, rather than transferring the entire site 
over
to
a different wiki system, with yet another syntax...
There's not that much content. But we could start with just the
manual
in the new wiki, then see how we get on. The great thing about this
internet thing is we can link across websites :). So even if the 
old
wiki stays around for a while its no biggie

James
---
http://radio.weblogs.com/0112098/

James
---
http://radio.weblogs.com/0112098/



Re: [jira] Reopened: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support

2004-09-09 Thread David Jencks
in web-app 2.3, taglib was at the same level as servlet,  
servlet-mapping etc.  In 2.4 it is moved into a jsp-config tag.  The  
2.3 to 2.4 conversion in M2 did not move the taglib tags.  I changed  
the schema conversion util to move the taglib tags into a new  
jsp-config tag.

I can add this verbose comment if you want, but I don't really  
understand the pattern of reopening and reclosing I've been seeing, so  
I won't until I get some advice on the procedure you have been  
following. Or, you can add it.

david jencks
On Sep 9, 2004, at 12:19 PM, Dain Sundstrom wrote:
What wasn't working in M2 that you just fixed?
-dain
On Sep 9, 2004, at 10:15 AM, David Jencks wrote:
What don't you understand about my comment?  It seems short but  
fairly clear to me.

david jencks
On Sep 9, 2004, at 12:01 PM, Dain Sundstrom wrote:
David,
Can you update this issue to reflect what is actually broken or open  
a new issue?

-dain
On Sep 9, 2004, at 9:49 AM, [EMAIL PROTECTED] wrote:
Message:
   The following issue has been reopened.
   Reopener: David Jencks
   Date: Thu, 9 Sep 2004 9:48 AM
taglib tags move into jsp-config tag.  This is not handled by jetty.
 
-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-278

Here is an overview of the issue:
 
-
Key: GERONIMO-278
Summary: Servlet/JSP 2.3 DTD deployment descriptor support
   Type: New Feature

 Status: Reopened
   Priority: Major
Project: Apache Geronimo
 Components:
 web
   Fix Fors:
 1.0-M2
   Versions:
 1.0-M1
   Assignee: David Jencks
   Reporter: David Blevins
Created: Thu, 29 Jul 2004 5:53 PM
Updated: Thu, 9 Sep 2004 9:48 AM
Description:
Servlet/JSP 2.2 DTD deployment descriptor support
 
-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the  
administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira





Re: [jira] Reopened: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support

2004-09-09 Thread Dain Sundstrom
On Sep 9, 2004, at 10:55 AM, David Jencks wrote:
in web-app 2.3, taglib was at the same level as servlet, 
servlet-mapping etc.  In 2.4 it is moved into a jsp-config tag.  The 
2.3 to 2.4 conversion in M2 did not move the taglib tags.  I changed 
the schema conversion util to move the taglib tags into a new 
jsp-config tag.

I can add this verbose comment if you want, but I don't really 
understand the pattern of reopening and reclosing I've been seeing, so 
I won't until I get some advice on the procedure you have been 
following. Or, you can add it.
I'll add it.  The reason you have to reopen and reclose, is JIRA 
doesn't let you change a closed issue.  When we were generating the 
Release Notes last night, we found several issues that were 
miscategorized,  had the wrong version number, or bad descriptions.  
Hopefully, we can all work to keep JIRA up to date so releases don't 
take so long to push out.

-dain


[jira] Commented: (GERONIMO-278) Servlet/JSP 2.3 DTD deployment descriptor support

2004-09-09 Thread dev
The following comment has been added to this issue:

 Author: Dain Sundstrom
Created: Thu, 9 Sep 2004 12:00 PM
   Body:
In web-app 2.3, taglib was at the same level as servlet, servlet-mapping etc.  
In 2.4 it is moved into a jsp-config tag.  The 2.3 to 2.4 conversion in M2 did 
not move the taglib tags.  David Jencks changed the schema conversion util to 
move the taglib tags into a new jsp-config tag.
-
View this comment:
  http://issues.apache.org/jira/browse/GERONIMO-278?page=comments#action_53002

-
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-278

Here is an overview of the issue:
-
Key: GERONIMO-278
Summary: Servlet/JSP 2.3 DTD deployment descriptor support
   Type: New Feature

 Status: Closed
   Priority: Major
 Resolution: FIXED

Project: Apache Geronimo
 Components: 
 web
   Fix Fors:
 1.0-M3
   Versions:
 1.0-M1

   Assignee: David Jencks
   Reporter: David Blevins

Created: Thu, 29 Jul 2004 5:53 PM
Updated: Thu, 9 Sep 2004 12:00 PM

Description:
Servlet/JSP 2.2 DTD deployment descriptor support


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



Logo ideas

2004-09-09 Thread David Armitage
Title: Message



To 
whoever,

Could not add to 
page, but would like to offer attached images as ideas. If they are of any use / 
interest / or potential for development, please pass on to someone who can do a 
better job graphically,

The design is based 
on the headdress worn by Geronimo in 1907 combined with the Apache 
feather.

Regards,

 
Dave
attachment: ApacheGeronimo450.gifattachment: ApacheGeronimo32.gifattachment: ApacheGeronimo100.gif