[jira] Commented: (GERONIMODEVTOOLS-596) Geronimo 1.1.1 Server Adapter Error on GEP 2.2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760528#action_12760528 ] Rodger Zhang commented on GERONIMODEVTOOLS-596: --- For java.lang.ClassCastException: org.apache.geronimo.gbean.AbstractName incompatible with org.apache.geronimo.gbean.AbstractName reported by viola.lu: The first AbstractName class is loaded from v11 runtime, whereas the second AbstractName class is loaded from v22 runtime. I find that v11.core and v11.ui depend on v21.core, as well as other unclear dependencies. I think we should make sure v11 absolutely depends on non-v2* bundle. Geronimo 1.1.1 Server Adapter Error on GEP 2.2 Key: GERONIMODEVTOOLS-596 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-596 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Environment: OS:winxp Eclipse 3.5 JDK:1.6 Reporter: viola.lu Assignee: Delos Dai Priority: Minor Attachments: namespace_error_fix_for_11.patch, openWithDefaultEditor.patch 1.Install GEP 2.2 on eclispe 3.5 2.Create a server instance, add a geronimo server 1.1.1, click next but get an loop event exception, can't go to next page, error track trace: ava.lang.NullPointerException at org.apache.geronimo.st.ui.internal.GeronimoRuntimeWizardFragment.validate(GeronimoRuntimeWizardFragment.java:309) at org.apache.geronimo.st.ui.internal.GeronimoRuntimeWizardFragment.exit(GeronimoRuntimeWizardFragment.java:384) at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.switchWizardFragment(TaskWizard.java:274) at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.setVisible(TaskWizardPage.java:89) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1171) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149) at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:830) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
[jira] Updated: (GERONIMODEVTOOLS-596) Geronimo 1.1.1 Server Adapter Error on GEP 2.2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-596: -- Attachment: namespace_error_fix_for_11.patch There are namespace mapping error in 1.1 adapter. The url for the schema used in *.xsd(as well as generated ObjectFactory) and NamespacePrefix are inconsistent. For example,http://www.openejb.org/xml/ns/openejb-jar-2.1; V.S. http://openejb.apache.org/xml/ns/openejb-jar-2.1;. As a result , there are prefix like ns8... not ejb... Geronimo 1.1.1 Server Adapter Error on GEP 2.2 Key: GERONIMODEVTOOLS-596 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-596 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Environment: OS:winxp Eclipse 3.5 JDK:1.6 Reporter: viola.lu Assignee: Delos Dai Priority: Minor Attachments: namespace_error_fix_for_11.patch, openWithDefaultEditor.patch 1.Install GEP 2.2 on eclispe 3.5 2.Create a server instance, add a geronimo server 1.1.1, click next but get an loop event exception, can't go to next page, error track trace: ava.lang.NullPointerException at org.apache.geronimo.st.ui.internal.GeronimoRuntimeWizardFragment.validate(GeronimoRuntimeWizardFragment.java:309) at org.apache.geronimo.st.ui.internal.GeronimoRuntimeWizardFragment.exit(GeronimoRuntimeWizardFragment.java:384) at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.switchWizardFragment(TaskWizard.java:274) at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.setVisible(TaskWizardPage.java:89) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1171) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149) at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:830) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java
[jira] Updated: (GERONIMODEVTOOLS-596) Geronimo 1.1.1 Server Adapter Error on GEP 2.2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-596: -- Attachment: openWithDefaultEditor.patch Hi,Delos I remove the throw new PartInitException, let the plan to be corrected or opened with default editor when catch an Exception. Pls review the patch to check if it feasible. Geronimo 1.1.1 Server Adapter Error on GEP 2.2 Key: GERONIMODEVTOOLS-596 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-596 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Environment: OS:winxp Eclipse 3.5 JDK:1.6 Reporter: viola.lu Assignee: Delos Dai Priority: Minor Attachments: openWithDefaultEditor.patch 1.Install GEP 2.2 on eclispe 3.5 2.Create a server instance, add a geronimo server 1.1.1, click next but get an loop event exception, can't go to next page, error track trace: ava.lang.NullPointerException at org.apache.geronimo.st.ui.internal.GeronimoRuntimeWizardFragment.validate(GeronimoRuntimeWizardFragment.java:309) at org.apache.geronimo.st.ui.internal.GeronimoRuntimeWizardFragment.exit(GeronimoRuntimeWizardFragment.java:384) at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.switchWizardFragment(TaskWizard.java:274) at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.setVisible(TaskWizardPage.java:89) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1171) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149) at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:830) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java
[jira] Created: (GERONIMODEVTOOLS-592) Extend rename for ejb/connector/ear project,too, meanwhile rename artifactId in these deployment plans.
Extend rename for ejb/connector/ear project,too, meanwhile rename artifactId in these deployment plans. - Key: GERONIMODEVTOOLS-592 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-592 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 2.1.5, 2.2.0 Reporter: Rodger Zhang Assignee: Tim McConnell GERONIMODEVTOOLS-283 only extend rename for a web project, which can also be applied to other javaee project, with renaming artifactId in all these projects' deployment plans. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-592) Extend rename for ejb/connector/ear project,too, meanwhile rename artifactId in these deployment plans.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-592: -- Attachment: rename_for_other_kind_projects.patch Attach the patch, pls help review. Extend rename for ejb/connector/ear project,too, meanwhile rename artifactId in these deployment plans. - Key: GERONIMODEVTOOLS-592 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-592 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 2.1.5, 2.2.0 Reporter: Rodger Zhang Assignee: Tim McConnell Attachments: rename_for_other_kind_projects.patch GERONIMODEVTOOLS-283 only extend rename for a web project, which can also be applied to other javaee project, with renaming artifactId in all these projects' deployment plans. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-590) org.eclipse.ltk.core.refactoring added in Require-Bundle must be set visibility:=reexport,
org.eclipse.ltk.core.refactoring added in Require-Bundle must be set visibility:=reexport, -- Key: GERONIMODEVTOOLS-590 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-590 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.5, 2.2.0 Reporter: Rodger Zhang Assignee: Tim McConnell GERONIMODEVTOOLS-283's patch works fine in development environment, but throws a ClassNotFound Exception when using the built GEP plugin. The required bundle org.eclipse.ltk.core.refactoring must be set visibility:=reexport. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-590) org.eclipse.ltk.core.refactoring added in Require-Bundle must be set visibility:=reexport,
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-590: -- Attachment: reexport_org.eclipse.ltk.core.refactoring.patch Attach a patch, pls help review. org.eclipse.ltk.core.refactoring added in Require-Bundle must be set visibility:=reexport, -- Key: GERONIMODEVTOOLS-590 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-590 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.5, 2.2.0 Reporter: Rodger Zhang Assignee: Tim McConnell Attachments: reexport_org.eclipse.ltk.core.refactoring.patch GERONIMODEVTOOLS-283's patch works fine in development environment, but throws a ClassNotFound Exception when using the built GEP plugin. The required bundle org.eclipse.ltk.core.refactoring must be set visibility:=reexport. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-456) Add Security Realm Wizard to GEP to deploy security realm directly from GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-456: -- Attachment: updated_security_realm.patch replace the patch wizard_for_add_security_realm_to_plan.patch, improved. Add Security Realm Wizard to GEP to deploy security realm directly from GEP --- Key: GERONIMODEVTOOLS-456 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Saurabh Sharma Assignee: Saurabh Sharma Fix For: 2.2.0 Attachments: GERONIMODEVTOOLS-455-456-consolidated.patch, updated_security_realm.patch, wizard_for_add_security_realm_to_plan.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-283: -- Attachment: extend_rename.patch Pls help review. Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root - Key: GERONIMODEVTOOLS-283 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.2.0 Attachments: extend_rename.patch When a Dynamic Web Project with name say tt is created, a Geronimo deployment plan geronimo-web.xml will get created with module-id as default/tt-1.0.car and context-root as /tt. When this project is re-factored to say tz, the module-id will still be the same default/tt-1.0.car (note that artifact id is not re-factored from tt to tz). The context-root also remains the same /tt. Although this doesn't pose any problem, wouldn't it be better to refactor the artifact-id context-root to match the project name? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12752991#action_12752991 ] Rodger Zhang commented on GERONIMODEVTOOLS-283: --- After a deeper investigation, this feature can be implemented by contributing to a extension-point. The UI is like pictures attached. Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root - Key: GERONIMODEVTOOLS-283 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.2.0 Attachments: extend_rename.patch When a Dynamic Web Project with name say tt is created, a Geronimo deployment plan geronimo-web.xml will get created with module-id as default/tt-1.0.car and context-root as /tt. When this project is re-factored to say tz, the module-id will still be the same default/tt-1.0.car (note that artifact id is not re-factored from tt to tz). The context-root also remains the same /tt. Although this doesn't pose any problem, wouldn't it be better to refactor the artifact-id context-root to match the project name? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-283: -- Attachment: screenshot-1.jpg Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root - Key: GERONIMODEVTOOLS-283 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.2.0 Attachments: extend_rename.patch, screenshot-1.jpg When a Dynamic Web Project with name say tt is created, a Geronimo deployment plan geronimo-web.xml will get created with module-id as default/tt-1.0.car and context-root as /tt. When this project is re-factored to say tz, the module-id will still be the same default/tt-1.0.car (note that artifact id is not re-factored from tt to tz). The context-root also remains the same /tt. Although this doesn't pose any problem, wouldn't it be better to refactor the artifact-id context-root to match the project name? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-283: -- Attachment: screenshot-2.jpg Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root - Key: GERONIMODEVTOOLS-283 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.2.0 Attachments: extend_rename.patch, screenshot-1.jpg, screenshot-2.jpg When a Dynamic Web Project with name say tt is created, a Geronimo deployment plan geronimo-web.xml will get created with module-id as default/tt-1.0.car and context-root as /tt. When this project is re-factored to say tz, the module-id will still be the same default/tt-1.0.car (note that artifact id is not re-factored from tt to tz). The context-root also remains the same /tt. Although this doesn't pose any problem, wouldn't it be better to refactor the artifact-id context-root to match the project name? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-453) JAXB Classes support for schema geronimo-login-config-2.0.xsd
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12753005#action_12753005 ] Rodger Zhang commented on GERONIMODEVTOOLS-453: --- Thanks. This patch jaxb-loginconfig.patch has been merged into GERONIMODEVTOOLS-455's wizard_for_adding_dbpool_to_application_plan.patch. Only need to apply 2 patches wizard_for_adding_dbpool_to_application_plan.patch(455) and wizard_for_add_security_realm_to_plan.patch(456). JAXB Classes support for schema geronimo-login-config-2.0.xsd - Key: GERONIMODEVTOOLS-453 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-453 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.1.2, 2.1.3 Reporter: Saurabh Sharma Assignee: Saurabh Sharma Fix For: 2.2.0 Attachments: jaxb-loginconfig.patch There is no JAXB class support for schema geronimo-login-config-2.0.xsd. Login Configuration settings must be specified as a element of xml-reference while generating security realm plan. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751276#action_12751276 ] Rodger Zhang commented on GERONIMODEVTOOLS-283: --- The rename item is bond with a action, and probably there is no extension point to modify the action's wizard. Like wtp's rename , its wizard does not provide a check box for changing display-name/ in web.xml. It is possible to implement this tiny feature but with a large effort, because the rename is not implemented by GEP. Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root - Key: GERONIMODEVTOOLS-283 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.2.0 When a Dynamic Web Project with name say tt is created, a Geronimo deployment plan geronimo-web.xml will get created with module-id as default/tt-1.0.car and context-root as /tt. When this project is re-factored to say tz, the module-id will still be the same default/tt-1.0.car (note that artifact id is not re-factored from tt to tz). The context-root also remains the same /tt. Although this doesn't pose any problem, wouldn't it be better to refactor the artifact-id context-root to match the project name? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-588) Fixed GEP2.2 automatic testsuite
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-588: -- Attachment: NLS_for_eclipse_ui_texts.patch Fixed GEP2.2 automatic testsuite Key: GERONIMODEVTOOLS-588 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: Eclipse3.5 Reporter: Rodger Zhang Assignee: Tim McConnell Attachments: config.xml, gep22_auto_testsuite_fixed.patch, NLS_for_eclipse_ui_texts.patch, updated_gep22_auto_testsuite_fixed.patch I've fixed GEP2.2 automatic testsuite to be fit for GEP2.2 and Eclipse3.5.Please help apply the patch to check if it can run smoothly. I have the testsuite passed on my personal computer. Any problem, please add a comment. Attention: Target testing server 2.1.4 download from the maven repository has a problem. Its config.xml is incomplete. To make the testsuite run successfully, we must replace the config.xml with a complete one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-481) Convert all Junit testcases to use the new NamespacePrefix class (instead of NamespacePrefixMapper)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12750244#action_12750244 ] Rodger Zhang commented on GERONIMODEVTOOLS-481: --- Currently, a test version NamespacePrefix(named org.apache.geronimo.jee.common.NamespacePrefixMapperImpl) works. All NamespacePrefixMapper have already been replaced with NamespacePrefixMapperImpl. So, suggest close this jira. Convert all Junit testcases to use the new NamespacePrefix class (instead of NamespacePrefixMapper) --- Key: GERONIMODEVTOOLS-481 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-481 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Tim McConnell Assignee: Ashish Jain Fix For: 2.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-588) Fixed GEP2.2 automatic testsuite
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-588: -- Attachment: updated_gep22_auto_testsuite_fixed.patch Sorry for a mistake added into the previous patch. So attach a updated patch which can been applied to both 2.1.5 and 2.2 Fixed GEP2.2 automatic testsuite Key: GERONIMODEVTOOLS-588 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: Eclipse3.5 Reporter: Rodger Zhang Assignee: Tim McConnell Attachments: config.xml, gep22_auto_testsuite_fixed.patch, updated_gep22_auto_testsuite_fixed.patch I've fixed GEP2.2 automatic testsuite to be fit for GEP2.2 and Eclipse3.5.Please help apply the patch to check if it can run smoothly. I have the testsuite passed on my personal computer. Any problem, please add a comment. Attention: Target testing server 2.1.4 download from the maven repository has a problem. Its config.xml is incomplete. To make the testsuite run successfully, we must replace the config.xml with a complete one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-589) If GEP2.2 needs to support Eclipse3.3
If GEP2.2 needs to support Eclipse3.3 - Key: GERONIMODEVTOOLS-589 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-589 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 2.2.0 Environment: Eclipse3.3 Reporter: Rodger Zhang Assignee: Tim McConnell If GEP2.2 needs to support Eclipse3.3, there a a few codes required modifying. 2 compiling errors exists: 1. org.apache.geronimo.st.core.GeronimoLaunchConfigurationDelegate ... if (configuration.hasAttribute(...)) ... There is no hasAttribute() method in previous version. 2. org.apache.geronimo.st.v21.ui.ServerPluginPage ... setManagedForm(managedForm); ... There is no setManagedForm() method in previous version. === For the first point, I have a solution as in patch. Please check if feasible. For the second point, a discussion ? Please add comment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-589) If GEP2.2 needs to support Eclipse3.3
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-589: -- Attachment: hasAttribute_not_used.patch If GEP2.2 needs to support Eclipse3.3 - Key: GERONIMODEVTOOLS-589 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-589 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 2.2.0 Environment: Eclipse3.3 Reporter: Rodger Zhang Assignee: Tim McConnell Attachments: hasAttribute_not_used.patch If GEP2.2 needs to support Eclipse3.3, there a a few codes required modifying. 2 compiling errors exists: 1. org.apache.geronimo.st.core.GeronimoLaunchConfigurationDelegate ... if (configuration.hasAttribute(...)) ... There is no hasAttribute() method in previous version. 2. org.apache.geronimo.st.v21.ui.ServerPluginPage ... setManagedForm(managedForm); ... There is no setManagedForm() method in previous version. === For the first point, I have a solution as in patch. Please check if feasible. For the second point, a discussion ? Please add comment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-588) Fixed GEP2.2 automatic testsuite
Fixed GEP2.2 automatic testsuite Key: GERONIMODEVTOOLS-588 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: Eclipse3.5 Reporter: Rodger Zhang Assignee: Tim McConnell I've fixed GEP2.2 automatic testsuite to be fit for GEP2.2 and Eclipse3.5.Please help apply the patch to check if it can run smoothly. I have the testsuite passed on my personal computer. Any problem, please add a comment. Attention: Target testing server 2.1.4 download from the maven repository has a problem. Its config.xml is incomplete. To make the testsuite run successfully, we must replace the config.xml with a complete one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-588) Fixed GEP2.2 automatic testsuite
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-588: -- Attachment: gep22_auto_testsuite_fixed.patch There are so many item texts ,such as Show View,Java EE (default),Add and Remove Projects..., which are changed from one eclipse version to another. I've an idea that if we could use a NLS class to manage all the text messages in a file like Messages.properties, just like what we do in geronimo project. Fixed GEP2.2 automatic testsuite Key: GERONIMODEVTOOLS-588 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: Eclipse3.5 Reporter: Rodger Zhang Assignee: Tim McConnell Attachments: gep22_auto_testsuite_fixed.patch I've fixed GEP2.2 automatic testsuite to be fit for GEP2.2 and Eclipse3.5.Please help apply the patch to check if it can run smoothly. I have the testsuite passed on my personal computer. Any problem, please add a comment. Attention: Target testing server 2.1.4 download from the maven repository has a problem. Its config.xml is incomplete. To make the testsuite run successfully, we must replace the config.xml with a complete one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-588) Fixed GEP2.2 automatic testsuite
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-588: -- Attachment: config.xml Attach a complete v2.1 config.xml for convenience。 Fixed GEP2.2 automatic testsuite Key: GERONIMODEVTOOLS-588 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-588 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: Eclipse3.5 Reporter: Rodger Zhang Assignee: Tim McConnell Attachments: config.xml, gep22_auto_testsuite_fixed.patch I've fixed GEP2.2 automatic testsuite to be fit for GEP2.2 and Eclipse3.5.Please help apply the patch to check if it can run smoothly. I have the testsuite passed on my personal computer. Any problem, please add a comment. Attention: Target testing server 2.1.4 download from the maven repository has a problem. Its config.xml is incomplete. To make the testsuite run successfully, we must replace the config.xml with a complete one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-587) Using GEP to convert an application to a plugin, if add prerequisite module,will encouter an error when install the plugin
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-587: -- Attachment: gep_587.patch I add a patch to fix the problem. However, it seems there are more potential same problems like === if(!.equals(version.getText())) artType.setVersion(version.getText()); === Furthermore, if we could treat version/ the same as no version element in components about deployment and resolve dependency in geronimo. Or meet one then fix one. Using GEP to convert an application to a plugin, if add prerequisite module,will encouter an error when install the plugin -- Key: GERONIMODEVTOOLS-587 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-587 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: windows xp sp3 jdk IBM 1.6 eclipse 3.5 Reporter: liangkun Assignee: Tim McConnell Attachments: gep_587.patch 1.Start a G server2.2 in eclipse using GEP. 2.Double click the server and click the plugin button. 3.Click the Convert Apps to Plugins button and create a Geronimo Plugin. 4.Choose the destination of the export plugin and an application want to be converted the click the next button. 5.You will see the pageupdating plugin information ,click the next button. 6.In the next page ,click button add to add the prerequisite module, you can try any prerequisite module which exists in the server.Please leave the version blank.Then click the next. 7.You will find the plugin at the destination you just choose.Install the plugin you will get the output that the prerequisite module can not be found. Check the file Geronimo-plugin.xml and you will find that the version of the prerequisite module is ns2:version/,that is the key why there is no the module and actually if you want to install the plugin you can just delete the ns2:version/. By the way ,when I finish converting an application to a plugin,I can still click next button,at the beginning I thought the process is not finished but actually it is done and this is a new process of converting. So,if the last button can be set to finish button that will be fine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-586) Index.jsp can not find servlet in the same project when use jsp:include page=/ConverterHandler /
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744044#action_12744044 ] Rodger Zhang commented on GERONIMODEVTOOLS-586: --- I follow the doc,seems no problem.Make sure your project's structure(files's location) is right. Index.jsp can not find servlet in the same project when use jsp:include page=/ConverterHandler / Key: GERONIMODEVTOOLS-586 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-586 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: OS:xp sp3 JDK:IBM jdk1.6 Eclipse:3.5 GEP:2.2 Reporter: liangkun Assignee: Tim McConnell According to doc2.2 Accessing EJB in Web applications ,when use eclipse 3.5 and GEP2.2 to create the index.jsp in a web application eclipse will report a error: Multiple annotations found at this line: - Fragment /ConverterHandler was not found at expected path /WebEJB/ WebContent/ConverterHandler - Fragment /ConverterHandler was not found at expected path /WebEJB/ WebContent/ConverterHandler Eclipse can not find the servlet in the same project. Doc link:http://cwiki.apache.org/GMOxDOC22/accessing-ejb-in-web-applications.html#AccessingEJBinWebapplications-AddingcodetoWebProject -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-586) Index.jsp can not find servlet in the same project when use jsp:include page=/ConverterHandler /
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744329#action_12744329 ] Rodger Zhang commented on GERONIMODEVTOOLS-586: --- Opps, I used eclipse3.4. Eclipse3.5 do have the problem.Sorry. Index.jsp can not find servlet in the same project when use jsp:include page=/ConverterHandler / Key: GERONIMODEVTOOLS-586 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-586 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: OS:xp sp3 JDK:IBM jdk1.6 Eclipse:3.5 GEP:2.2 Reporter: liangkun Assignee: Tim McConnell According to doc2.2 Accessing EJB in Web applications ,when use eclipse 3.5 and GEP2.2 to create the index.jsp in a web application eclipse will report a error: Multiple annotations found at this line: - Fragment /ConverterHandler was not found at expected path /WebEJB/ WebContent/ConverterHandler - Fragment /ConverterHandler was not found at expected path /WebEJB/ WebContent/ConverterHandler Eclipse can not find the servlet in the same project. Doc link:http://cwiki.apache.org/GMOxDOC22/accessing-ejb-in-web-applications.html#AccessingEJBinWebapplications-AddingcodetoWebProject -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-456) Add Security Realm Wizard to GEP to deploy security realm directly from GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-456: -- Attachment: wizard_for_add_security_realm_to_plan.patch I complete a new feature about add security realm as gbean/ into plan(geronimo-application.xml,geronimo-web.xml,openejb-jar.xml),as well as supporting editing and removing the realm. So attach the patch. Pls help review. Add Security Realm Wizard to GEP to deploy security realm directly from GEP --- Key: GERONIMODEVTOOLS-456 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-456 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Saurabh Sharma Assignee: Saurabh Sharma Fix For: 2.2.0 Attachments: GERONIMODEVTOOLS-455-456-consolidated.patch, wizard_for_add_security_realm_to_plan.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-455) Add Database pool wizard in GEP to enable application specific pools
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-455: -- Attachment: wizard_for_adding_dbpool_to_application_plan.patch This patch is about wizard for adding dbpool as ext-module into geronimo-application.xml plan. Add Database pool wizard in GEP to enable application specific pools Key: GERONIMODEVTOOLS-455 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-455 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Sainath Chowdary Assignee: Sainath Chowdary Fix For: 2.2.0 Attachments: GERONIMODEVTOOLS-455-456-consolidated.patch, wizard_for_adding_dbpool_to_application_plan.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-573) sec:security/ was added to plan after add a resource-ref via GEP UI
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12738856#action_12738856 ] Rodger Zhang commented on GERONIMODEVTOOLS-573: --- When first click the Security page, then Click Naming page and add resource-ref(or other elements) ,the very error happens. = Initial Security page-fillBody()-new SecurityRoleMappingSection()-createClient()-viewer.setInput(getInput())-getRoleMappings(getPlan(), false)-JAXBModelUtils.getSecurity(plan) = Because JAXBModelUtils.getSecurity() set add security element to plan if the plan doesn't contain security/. I attached a patch to modify the method getSecurity(), but I'm not sure whether other problems may be imported.Pls help review. sec:security/ was added to plan after add a resource-ref via GEP UI - Key: GERONIMODEVTOOLS-573 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-573 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.4 Environment: OS:suse 10 Sp2 JDK:1.5 Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Steps: 1.Create a dynamic web app. and edit its geronimo-web.xml via UI tool 2.Click Naming tab, and add a resource-ref: mail/TestMailSession and save it. 3.Open source tab, an extral sec:security/ is appended to geronimo-web.xml, and error exists.Must remove it manually from it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-573) sec:security/ was added to plan after add a resource-ref via GEP UI
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-573: -- Attachment: not_to_add_security.patch sec:security/ was added to plan after add a resource-ref via GEP UI - Key: GERONIMODEVTOOLS-573 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-573 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.4 Environment: OS:suse 10 Sp2 JDK:1.5 Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: not_to_add_security.patch Steps: 1.Create a dynamic web app. and edit its geronimo-web.xml via UI tool 2.Click Naming tab, and add a resource-ref: mail/TestMailSession and save it. 3.Open source tab, an extral sec:security/ is appended to geronimo-web.xml, and error exists.Must remove it manually from it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-454) Add support to GEP for various Admin Console wizards like Database pool, Security realm etc
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737443#action_12737443 ] Rodger Zhang commented on GERONIMODEVTOOLS-454: --- So, it's clear that both generated dbpool and security realm plans to be added to the geronimo-application.xml (dbpool plan added as a ext-module and security realm plan added as gbean). Any comments? Add support to GEP for various Admin Console wizards like Database pool, Security realm etc --- Key: GERONIMODEVTOOLS-454 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-454 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Sainath Chowdary Fix For: 2.2.0 Attachments: wizard1.JPG, wizard2.JPG Currently GEP has no support for creating application specific security realms, database pools and other message destinations etc., These features should be added to GEP to make it more robust instead of users creating the plan in admin console and then copying to deployment plan. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
connector/ of module/ and ext-module/ in http://geronimo.apache.org/xml/ns/j2ee/application-2.0
Hi, It is clear that connector/ in module/ provides URI of resource adapter archive file path relative to the enterprise application package main directory. But in ext-module, there is a element external-path to provide the very URI, what is connector/ in ext-module used for? If we use both connector/ and external-path , which URI will be accepted? -- Best Regards, Rodger.
Re: connector/ of module/ and ext-module/ in http://geronimo.apache.org/xml/ns/j2ee/application-2.0
I see. Take daytrader for example, in its geronimo-application.xml: app:ext-module app:connectorTradeDataSource/app:connector app:external-path dep:groupIdorg.tranql/dep:groupId dep:artifactIdtranql-connector-derby-embed-xa/dep:artifactId dep:typerar/dep:type /app:external-path conn:connector .. Both connector and external-path can be chose. -- Best Regards, Rodger.
[jira] Commented: (GERONIMODEVTOOLS-454) Add support to GEP for various Admin Console wizards like Database pool, Security realm etc
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737422#action_12737422 ] Rodger Zhang commented on GERONIMODEVTOOLS-454: --- What is the exact meaning of these feature, or rather, how to use the wizard? As my comprehension, we can store the dbpool plan generated by the wizard in a xml file(e.g. named dbpool-plan.xml) and add module/ or ext-module/ into geronimo-application.xml, with a alt-dd linking to dbpool-plan.xml. However, there is no element alt-dd defined forext-module, we need to add the necessary part of the plan into ext-moduleconnector/connector/ext-module for there is no alt-dd. For the security realm, I think, is your meaning to deploy the generated plan independently, or to add the necessary part (a gbean) into geronimo-application.xml? By the way, there are some problems in the wizards ,see attached pictures, if choose the ladp realm type,the current and next pages are also for sql realm configuration. A properties file realm type is also required. Add support to GEP for various Admin Console wizards like Database pool, Security realm etc --- Key: GERONIMODEVTOOLS-454 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-454 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Sainath Chowdary Fix For: 2.2.0 Currently GEP has no support for creating application specific security realms, database pools and other message destinations etc., These features should be added to GEP to make it more robust instead of users creating the plan in admin console and then copying to deployment plan. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-314) Fix warning messages in modified JAXB classes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12734874#action_12734874 ] Rodger Zhang commented on GERONIMODEVTOOLS-314: --- This warning is caused by suggesting to use generic type for Class. But the Class used here is just a judgment condition. If we could tolerate it, this jira could be closed. Any clear suggestion? Fix warning messages in modified JAXB classes - Key: GERONIMODEVTOOLS-314 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-314 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Tim McConnell Assignee: Ashish Jain Priority: Minor Fix For: 2.2.0 Attachments: Image1.png -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-198) Daytrader deployment exception in Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12734051#action_12734051 ] Rodger Zhang commented on GERONIMODEVTOOLS-198: --- Are you migrate the daytrader app from maven-building-version to GEP? If so, possibly, some configuration file (like manifest.mf, deployment plan) may have bot been configured incorrectly. I have a very daytrader app which can be deployed successfully with GEP. I'll attach it. Conclusively, it is not a GEP bug, suggest to close this jira. Daytrader deployment exception in Eclipse - Key: GERONIMODEVTOOLS-198 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-198 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0 There is a deployment exception occurring in Eclipse when deploying Daytrader, although it seems to be fairly benign since Daytrader ultimately does deploy and seems to function correctly. Booting Geronimo Kernel (in Java 1.5.0_12)... Module 1/31 org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car started in 1.453s Module 2/31 org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car started in .359s Module 3/31 org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car started in .875s Module 4/31 org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car started in .000s Module 5/31 org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/car INFO - Configuring Service(id=Default MDB Container, type=Container, provider-id=Default MDB Container) INFO - Configuring Service(id=Default Stateless Container, type=Container, provider-id=Default Stateless Container) INFO - Configuring app: jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/ INFO - Loaded Module: jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/ INFO - Assembling app: jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/ INFO - Jndi(name=MEJBGBean/MEJB/javax.management.j2ee.ManagementHome) INFO - Created Ejb(deployment-id=MEJBGBean/MEJB, ejb-name=MEJB, container=Default Stateless Container) INFO - Configuring Service(id=Default Stateful Container, type=Container, provider-id=Default Stateful Container) INFO - Configuring Service(id=Default BMP Container, type=Container, provider-id=Default BMP Container) INFO - Configuring Service(id=Default CMP Container, type=Container, provider-id=Default CMP Container) started in 11.328s Module 6/31 org.apache.geronimo.configs/j2ee-corba-yoko/2.1-SNAPSHOT/car started in 1.782s Module 7/31 org.apache.geronimo.configs/system-database/2.1-SNAPSHOT/car started in .000s Module 8/31 org.apache.geronimo.configs/activemq-broker/2.1-SNAPSHOT/car started in .000s Module 9/31 org.apache.geronimo.configs/activemq-ra/2.1-SNAPSHOT/car started in .000s Module 10/31 org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car started in .000s Module 11/31 org.apache.geronimo.configs/myfaces/2.1-SNAPSHOT/car started in .016s Module 12/31 org.apache.geronimo.configs/tomcat6/2.1-SNAPSHOT/car ERROR - Restricted listeners property file not found started in 3.172s Module 13/31 org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car started in .844s Module 14/31 org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car started in .516s Module 15/31 org.apache.geronimo.configs/connector-deployer/2.1-SNAPSHOT/car started in .234s Module 16/31 org.apache.geronimo.configs/persistence-jpa10-deployer/2.1-SNAPSHOT/car started in .172s Module 17/31 org.apache.geronimo.configs/openejb-deployer/2.1-SNAPSHOT/car started in .219s Module 18/31 org.apache.geronimo.configs/client-deployer/2.1-SNAPSHOT/car started in .250s Module 19/31 org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car started in .312s Module 20/31 org.apache.geronimo.configs/axis-deployer/2.1-SNAPSHOT/car started in 1.672s Module 21/31 org.apache.geronimo.configs/javamail/2.1-SNAPSHOT/car started in .125s Module 22/31 org.apache.geronimo.configs/sharedlib/2.1
[jira] Updated: (GERONIMODEVTOOLS-198) Daytrader deployment exception in Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMODEVTOOLS-198: -- Attachment: daytrader.zip Daytrader deployment exception in Eclipse - Key: GERONIMODEVTOOLS-198 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-198 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0 Attachments: daytrader.zip There is a deployment exception occurring in Eclipse when deploying Daytrader, although it seems to be fairly benign since Daytrader ultimately does deploy and seems to function correctly. Booting Geronimo Kernel (in Java 1.5.0_12)... Module 1/31 org.apache.geronimo.configs/rmi-naming/2.1-SNAPSHOT/car started in 1.453s Module 2/31 org.apache.geronimo.configs/j2ee-server/2.1-SNAPSHOT/car started in .359s Module 3/31 org.apache.geronimo.configs/transaction/2.1-SNAPSHOT/car started in .875s Module 4/31 org.apache.geronimo.configs/j2ee-security/2.1-SNAPSHOT/car started in .000s Module 5/31 org.apache.geronimo.configs/openejb/2.1-SNAPSHOT/car INFO - Configuring Service(id=Default MDB Container, type=Container, provider-id=Default MDB Container) INFO - Configuring Service(id=Default Stateless Container, type=Container, provider-id=Default Stateless Container) INFO - Configuring app: jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/ INFO - Loaded Module: jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/ INFO - Assembling app: jar:file:/C:/TEMP/TRUNK/TC/repository/org/apache/geronimo/modules/geronimo-openejb/2.1-SNAPSHOT/geronimo-openejb-2.1-SNAPSHOT.jar!/org/apache/geronimo/openejb/ INFO - Jndi(name=MEJBGBean/MEJB/javax.management.j2ee.ManagementHome) INFO - Created Ejb(deployment-id=MEJBGBean/MEJB, ejb-name=MEJB, container=Default Stateless Container) INFO - Configuring Service(id=Default Stateful Container, type=Container, provider-id=Default Stateful Container) INFO - Configuring Service(id=Default BMP Container, type=Container, provider-id=Default BMP Container) INFO - Configuring Service(id=Default CMP Container, type=Container, provider-id=Default CMP Container) started in 11.328s Module 6/31 org.apache.geronimo.configs/j2ee-corba-yoko/2.1-SNAPSHOT/car started in 1.782s Module 7/31 org.apache.geronimo.configs/system-database/2.1-SNAPSHOT/car started in .000s Module 8/31 org.apache.geronimo.configs/activemq-broker/2.1-SNAPSHOT/car started in .000s Module 9/31 org.apache.geronimo.configs/activemq-ra/2.1-SNAPSHOT/car started in .000s Module 10/31 org.apache.geronimo.configs/jasper/2.1-SNAPSHOT/car started in .000s Module 11/31 org.apache.geronimo.configs/myfaces/2.1-SNAPSHOT/car started in .016s Module 12/31 org.apache.geronimo.configs/tomcat6/2.1-SNAPSHOT/car ERROR - Restricted listeners property file not found started in 3.172s Module 13/31 org.apache.geronimo.configs/geronimo-gbean-deployer/2.1-SNAPSHOT/car started in .844s Module 14/31 org.apache.geronimo.configs/j2ee-deployer/2.1-SNAPSHOT/car started in .516s Module 15/31 org.apache.geronimo.configs/connector-deployer/2.1-SNAPSHOT/car started in .234s Module 16/31 org.apache.geronimo.configs/persistence-jpa10-deployer/2.1-SNAPSHOT/car started in .172s Module 17/31 org.apache.geronimo.configs/openejb-deployer/2.1-SNAPSHOT/car started in .219s Module 18/31 org.apache.geronimo.configs/client-deployer/2.1-SNAPSHOT/car started in .250s Module 19/31 org.apache.geronimo.configs/axis2-deployer/2.1-SNAPSHOT/car started in .312s Module 20/31 org.apache.geronimo.configs/axis-deployer/2.1-SNAPSHOT/car started in 1.672s Module 21/31 org.apache.geronimo.configs/javamail/2.1-SNAPSHOT/car started in .125s Module 22/31 org.apache.geronimo.configs/sharedlib/2.1-SNAPSHOT/car started in .015s Module 23/31 org.apache.geronimo.configs/tomcat6-deployer/2.1-SNAPSHOT/car started in .187s Module 24/31 org.apache.geronimo.configs/jasper-deployer/2.1-SNAPSHOT/car started in .063s Module 25/31 org.apache.geronimo.configs/myfaces-deployer/2.1-SNAPSHOT
Re: [jira] Commented: (GERONIMO-4760) Started ejb module cannot be stopped
I meet the same problem in geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip http://ce20.cn.ibm.com/geronimo_builds/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip 17-Jul-2009 02:58 95M It is latest build I can get. I'll test in the new build,if there is. when stop the ejb, ERROR [GBeanInstance] Problem in doStop of org.apache.geronimo.samples/calculator-ejb/2.2.0/jar?J2EEApplication=null,j2eeType=EJBModule,name=org.apache.geronimo.samples/calculator-ejb/2.2.0/jar java.lang.ClassCastException: org.apache.geronimo.openejb.DeepBindableContext$ContextWrapper incompatible with org.apache.openejb.core.ivm.naming.IvmContext
[jira] Commented: (GERONIMODEVTOOLS-510) Deployment plan editor warning message when opening source tab for openejb-jar.xml file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12733487#action_12733487 ] Rodger Zhang commented on GERONIMODEVTOOLS-510: --- http://openejb.apache.org/xml/ns/openejb-jar-2.2 http://openejb.apache.org/xml/ns/pkgen-2.1 are not available. These urls are not linked to: http://openejb.apache.org/xml/ns/openejb-jar-2.2.xsd http://openejb.apache.org/xml/ns/pkgen-2.1.xsd So,the openejb-jar.xml created by GEP like ?xml version=1.0 encoding=UTF-8? ejb:openejb-jar xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; xmlns:client=http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0; xmlns:conn=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:ejb=http://openejb.apache.org/xml/ns/openejb-jar-2.2; xmlns:name=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pers=http://java.sun.com/xml/ns/persistence; xmlns:pkgen=http://openejb.apache.org/xml/ns/pkgen-2.1; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1; dep:environment dep:moduleId dep:groupIddefault/dep:groupId dep:artifactId/dep:artifactId dep:version1.0/dep:version dep:typecar/dep:type /dep:moduleId /dep:environment /ejb:openejb-jar === has a warning:No grammar constraints (DTD or XML schema) detected for the document. Some should fix it. Deployment plan editor warning message when opening source tab for openejb-jar.xml file --- Key: GERONIMODEVTOOLS-510 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-510 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Tim McConnell Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0 Warning message as shown in Eclipse: No grammar constraints (DTD or XML schema) detected for the document. openejb-jar.xml testEJB/ejbModule/META-INF line 1 XML Problem -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Security configuration principal-role mapping
In the online schema http://geronimo.apache.org/xml/ns/security-2.0 , there is no definition for xsd:attribute name=name But I really find the attribute in geronimo_home/schema/geronimo-security-2.0.xsd. Dose the online schema need to be updated? -- Best Regards, Rodger.
Security configuration principal-role mapping
Previously and in a common way, we do principal-role mapping in a deployment plan (such as geronimo-web.xml,openejb-jar.xml), like: role-mappings role role-name=user principal class=o.a.g.s.r.providers.GeronimoGroupPrincipal name=UserGrp/ /role ... /role-mappings But in Geronimo2.2 , after a jira https://issues.apache.org/jira/browse/GERONIMO-4523 It seems that we can do the principal-role mapping without the need for Geronimo-specific deployment plans. Has the feature been implemented? If so, how to do the mapping? -- Best Regards, Rodger.
[jira] Created: (GERONIMO-4696) Directory should be removed when a module's deployment fails.
Directory should be removed when a module's deployment fails. - Key: GERONIMO-4696 URL: https://issues.apache.org/jira/browse/GERONIMO-4696 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 2.2 Reporter: Rodger Zhang I write a war using datasource. Deploy it with a geronimo-web.xml that does not contain the dependence on the datasource. As anticipated , it fails to be deployed. But when I deploy the war again with the right geronimo-web.xml (dependence has been added), there is an error: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: There is no module with the very name in config.xml , but a directory with the very name exists in geronimo_home/repository/ . If I remove the directory in repository manually, then I can depoly the war successfully. So, if a module's deployment fails, the directory created in repository should be removed automatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4696) Directory should be removed when a module's deployment fails.
[ https://issues.apache.org/jira/browse/GERONIMO-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721601#action_12721601 ] Rodger Zhang commented on GERONIMO-4696: En. I think the problem still exists . I'm attaching the war package and the deployment plan. The deployment plan's dependency is commented first, so will be deployed with a problem. Then uncomment the dependency, when deploying it, the problem will emerge. Directory should be removed when a module's deployment fails. - Key: GERONIMO-4696 URL: https://issues.apache.org/jira/browse/GERONIMO-4696 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.2 Reporter: Rodger Zhang I write a war using datasource. Deploy it with a geronimo-web.xml that does not contain the dependence on the datasource. As anticipated , it fails to be deployed. But when I deploy the war again with the right geronimo-web.xml (dependence has been added), there is an error: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: There is no module with the very name in config.xml , but a directory with the very name exists in geronimo_home/repository/ . If I remove the directory in repository manually, then I can depoly the war successfully. So, if a module's deployment fails, the directory created in repository should be removed automatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4696) Directory should be removed when a module's deployment fails.
[ https://issues.apache.org/jira/browse/GERONIMO-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang updated GERONIMO-4696: --- Attachment: geronimo-web.xml general_store.war Deploy a datasource pool named StoreDataSource with the database named generalstore firstly. Directory should be removed when a module's deployment fails. - Key: GERONIMO-4696 URL: https://issues.apache.org/jira/browse/GERONIMO-4696 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.2 Reporter: Rodger Zhang Attachments: general_store.war, geronimo-web.xml I write a war using datasource. Deploy it with a geronimo-web.xml that does not contain the dependence on the datasource. As anticipated , it fails to be deployed. But when I deploy the war again with the right geronimo-web.xml (dependence has been added), there is an error: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: There is no module with the very name in config.xml , but a directory with the very name exists in geronimo_home/repository/ . If I remove the directory in repository manually, then I can depoly the war successfully. So, if a module's deployment fails, the directory created in repository should be removed automatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4696) Directory should be removed when a module's deployment fails.
[ https://issues.apache.org/jira/browse/GERONIMO-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721627#action_12721627 ] Rodger Zhang commented on GERONIMO-4696: see the log, It tried to delete the directory,but it failed to delete the files contained in the directory, because the war contained third-party jars in /lib. Directory should be removed when a module's deployment fails. - Key: GERONIMO-4696 URL: https://issues.apache.org/jira/browse/GERONIMO-4696 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.2 Reporter: Rodger Zhang Attachments: general_store.war, geronimo-web.xml I write a war using datasource. Deploy it with a geronimo-web.xml that does not contain the dependence on the datasource. As anticipated , it fails to be deployed. But when I deploy the war again with the right geronimo-web.xml (dependence has been added), there is an error: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: There is no module with the very name in config.xml , but a directory with the very name exists in geronimo_home/repository/ . If I remove the directory in repository manually, then I can depoly the war successfully. So, if a module's deployment fails, the directory created in repository should be removed automatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4663) Improvement of New Server Instance via plugins-GERONIMO-4382
[ https://issues.apache.org/jira/browse/GERONIMO-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang resolved GERONIMO-4663. Resolution: Fixed Fix Version/s: 2.2 Ok, it has been fixed. Improvement of New Server Instance via plugins-GERONIMO-4382 -- Key: GERONIMO-4663 URL: https://issues.apache.org/jira/browse/GERONIMO-4663 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: commands, Plugins Affects Versions: 2.2 Reporter: Rodger Zhang Fix For: 2.2 When using gshell command deploy/new-instance to new a instance of the server, an error happens in start-server window: ERROR [PluginInstallerGBean] Unable to install plugin java.lang.IllegalArgumentException: Could not find org.apache.geronimo.plugingro ups/framework/2.2-SNAPSHOT/car in any repo: [org.apache.geronimo.system.plugin.GeronimoSourceRepository]. Because in directory GERONIMO_HOME/repository/org/apache/geronimo/plugingroups, no directory /framework (a plugin) exists, we must copy /framework from GERONIMO_HOME/repository/org/apache/geronimo/framework/plugingroups (It is a plugin framework-2.2-SNAPSHOT.car) firstly. I think it is inconvenient for users,so why not put the plugin in the right position? Or maybe it is a bug that in the code there is a path must point to the second directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Migration from Tomcat to Geronimo
I'm summarizing all the modifyings when migrating from tomcat to geronimo. As I know, there are: 1. datasource configuration in context.xml vs in geronimo-web.xml 2. security realm configuration 3. Ports configuration in server.xml vs in config.xml 4. some other configurations which can be configed in geronimo_home/var/catalina/conf/web.xml,such as jsp reloading, persist jsp compilation Any other difference, pls reply. -- Best Regards, Rodger.
Re: Migration from Tomcat to Geronimo
Thank you , Shawn. Yes, I have read this doc. Actually, I want to write a test scenario about this migration. Maybe it's not easy to find a sample with all these diffs. -- Best Regards, Rodger.
