[jira] Created: (GERONIMO-2022) New printed Book available - patch for documentation page attached

New printed Book available - patch for documentation page attached -- Key: GERONIMO-2022 URL: http://issues.apache.org/jira/browse/GERONIMO-2022 Project: Geronimo Type: Improvement Security: public

[jira] Assigned: (GERONIMO-2022) New printed Book available - patch for documentation page attached

[ http://issues.apache.org/jira/browse/GERONIMO-2022?page=all ] Hernan Cunico reassigned GERONIMO-2022: --- Assign To: Hernan Cunico New printed Book available - patch for documentation page attached

[jira] Commented: (GERONIMO-2022) New printed Book available - patch for documentation page attached

[ http://issues.apache.org/jira/browse/GERONIMO-2022?page=comments#action_12402215 ] Hernan Cunico commented on GERONIMO-2022: - Kristian, pls re-attach patch or provide details about the book. Cheers! Hernan New printed Book available - patch

[jira] Updated: (GERONIMO-2022) New printed Book available - patch for documentation page attached

[ http://issues.apache.org/jira/browse/GERONIMO-2022?page=all ] Kristian Koehler updated GERONIMO-2022: --- Attachment: book.patch sorry for the inconvenience here is the patch New printed Book available - patch for documentation page attached

[jira] Commented: (GERONIMO-1900) Sample app links on welcome app are broken by default

[ http://issues.apache.org/jira/browse/GERONIMO-1900?page=comments#action_12402233 ] Aaron Mulder commented on GERONIMO-1900: OK, looking at patch 9... I still am not thrilled with this. In no particular order: - it seems too complex for what

[jira] Closed: (GERONIMO-1822) Connector builder doesn't check consistency of transaction settings

[ http://issues.apache.org/jira/browse/GERONIMO-1822?page=all ] David Jencks closed GERONIMO-1822: -- Resolution: Fixed Since the plan is to merge the 1.2 changes back into 1.1, I think we can close this one now. Connector builder doesn't check

[jira] Closed: (GERONIMO-2012) Reflect configuration - module change in config.xml

[ http://issues.apache.org/jira/browse/GERONIMO-2012?page=all ] Dain Sundstrom closed GERONIMO-2012: Resolution: Fixed Reflect configuration - module change in config.xml Key:

[jira] Closed: (GERONIMO-2018) Change temporary system proerty flags to start with X

[ http://issues.apache.org/jira/browse/GERONIMO-2018?page=all ] Dain Sundstrom closed GERONIMO-2018: Resolution: Fixed Change temporary system proerty flags to start with X ---

Re: Please try out the upgrade jar

Hi David J., This is very helpful! So far it worked for the simple ejb, war, ear that I've tested. I'll let you know if I ran into problems deploying other modules. Dave Colasurdo, FYI, I tried upgrading my geronimo-web.xml and it was converted from: web-app

Re: Please try out the upgrade jar

Thanks for trying it out. I changed how it starts quite a bit today -- I hope it hasn't become too slow. I also think I fixed the schema issue Dave Colasurdo found. thanks david jencks On May 14, 2006, at 3:57 PM, Chris Cardona wrote: Hi David J., This is very helpful! So far it worked

[jira] Created: (GERONIMO-2023) Improve sample app install process

Improve sample app install process -- Key: GERONIMO-2023 URL: http://issues.apache.org/jira/browse/GERONIMO-2023 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: sample apps Versions: 1.1

[jira] Resolved: (GERONIMO-1900) Sample app links on welcome app are broken by default

[ http://issues.apache.org/jira/browse/GERONIMO-1900?page=all ] Aaron Mulder resolved GERONIMO-1900: Resolution: Fixed Put in a fairly straightforward welcome app installer. Remaining issues are described in the new linked issue. Prasad, if

[jira] Resolved: (GERONIMO-1756) Move from 1.1-dev version of commons-fileupload to version 1.1

[ http://issues.apache.org/jira/browse/GERONIMO-1756?page=all ] Aaron Mulder resolved GERONIMO-1756: Fix Version: (was: 1.2) Resolution: Fixed Move from 1.1-dev version of commons-fileupload to version 1.1

[jira] Resolved: (GERONIMO-1212) Timeouts in commons-fileupload

[ http://issues.apache.org/jira/browse/GERONIMO-1212?page=all ] Aaron Mulder resolved GERONIMO-1212: Fix Version: 1.1 (was: 1.x) Resolution: Fixed Assign To: Aaron Mulder Timeouts in commons-fileupload

[jira] Commented: (GERONIMO-1981) Web Connector has GBean=(container name) in AbstractName

[ http://issues.apache.org/jira/browse/GERONIMO-1981?page=comments#action_12402249 ] Aaron Mulder commented on GERONIMO-1981: It looks like the GBean=JettyWebContainer part of the ObjectName is only added to the ObjectName of a web connector added

[jira] Assigned: (GERONIMO-1981) Web Connector has GBean=(container name) in AbstractName

[ http://issues.apache.org/jira/browse/GERONIMO-1981?page=all ] David Jencks reassigned GERONIMO-1981: -- Assign To: Dain Sundstrom (was: Aaron Mulder) The problem here is to get a sibling name from an abstract name. We have the web container

[jira] Commented: (GERONIMO-1638) Multiple servers sharing the same repo and config store

[ http://issues.apache.org/jira/browse/GERONIMO-1638?page=comments#action_12402251 ] David Jencks commented on GERONIMO-1638: Backported revisions r378827, r379430, r382366 in rev 406493. We still need to tweak the scripts. Multiple servers

[jira] Assigned: (GERONIMO-2020) Relative symlinks to the shell scripts were not handled correctly

[ http://issues.apache.org/jira/browse/GERONIMO-2020?page=all ] John Sisson reassigned GERONIMO-2020: - Assign To: John Sisson Relative symlinks to the shell scripts were not handled correctly

[jira] Resolved: (GERONIMO-1934) Incomplete dependency resolution assumes JAR as type

[ http://issues.apache.org/jira/browse/GERONIMO-1934?page=all ] Aaron Mulder resolved GERONIMO-1934: Resolution: Fixed Incomplete dependency resolution assumes JAR as type Key:

[jira] Updated: (GERONIMO-1569) improve packaging plugin control of logging.

[ http://issues.apache.org/jira/browse/GERONIMO-1569?page=all ] David Jencks updated GERONIMO-1569: --- Fix Version: 1.1 Backported fix to 1.1 in rev 406500 improve packaging plugin control of logging.

[jira] Created: (GERONIMO-2024) namespace updates were turned off in 1.1

namespace updates were turned off in 1.1 Key: GERONIMO-2024 URL: http://issues.apache.org/jira/browse/GERONIMO-2024 Project: Geronimo Type: Bug Security: public (Regular issues) Components: deployment Versions:

[jira] Commented: (GERONIMO-2024) namespace updates were turned off in 1.1

[ http://issues.apache.org/jira/browse/GERONIMO-2024?page=comments#action_12402253 ] David Jencks commented on GERONIMO-2024: uncommented the line in rev 406502 lets check for bad effects for a day or two. namespace updates were turned off

[jira] Resolved: (GERONIMO-1936) WAR deployed with configId with no type isn't treated as WAR by deploy tool, is by console

[ http://issues.apache.org/jira/browse/GERONIMO-1936?page=all ] Aaron Mulder resolved GERONIMO-1936: Resolution: Cannot Reproduce Looks like this was fixed by one of the previous changes? WAR deployed with configId with no type isn't treated

[jira] Commented: (GERONIMO-1905) Confirm deploy/undeploy/redeploy for WARs with no configId

[ http://issues.apache.org/jira/browse/GERONIMO-1905?page=comments#action_12402256 ] Aaron Mulder commented on GERONIMO-1905: If you deploy a web app with no moduleId, you can redeploy it and the settings are migrated to the new version. However,

[jira] Created: (GERONIMO-2025) Undeploy and redeploy with no version leaves dangling entries in config.xml

Undeploy and redeploy with no version leaves dangling entries in config.xml --- Key: GERONIMO-2025 URL: http://issues.apache.org/jira/browse/GERONIMO-2025 Project: Geronimo Type: Bug

[jira] Commented: (GERONIMO-1905) Confirm deploy/undeploy/redeploy for WARs with no configId

[ http://issues.apache.org/jira/browse/GERONIMO-1905?page=comments#action_12402257 ] Aaron Mulder commented on GERONIMO-1905: Previous behavior fixed. Next problem: if you redeploy with a plan that has an environment with no module ID, the deploy