[jira] Assigned: (GERONIMODEVTOOLS-182) Unable to open Deployment plan editor in Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-182: Assignee: Shiva Kumar H R Unable to open Deployment plan editor in Eclipse - Key: GERONIMODEVTOOLS-182 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-182 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Windows Xp Reporter: Ashish Jain Assignee: Shiva Kumar H R Hi!! I am using geronimo-tomcat6-jee5-2.0-M6-rc1-bin, g-eclipse-plugin-2.0.0-v20070812.0209-deployable and wtp-all-in-one-sdk-R-2.0-200706260303-win32 . I am creating a dynamic web project using Eclipse. When I try to open geronimo-web.xml I get an error message unable to open the editor instead default text editor is opened. Thanks Ashish -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-184: Assignee: Shiva Kumar H R An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse Key: GERONIMODEVTOOLS-184 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Windows xp sp2, Eclipse Version: 3.3.0 Reporter: Song Assignee: Shiva Kumar H R After deployed samples (such as cviewer) to the server within Eclipse, Run As--Run on Server,An internal error occurred. In fact, the cviewer sample can be deployed and executed successfully via the command line. Detailed error message see the below: --- java.lang.NoSuchMethodError: org/apache/xmlbeans/XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.deployment.xbeans.EnvironmentDocument.clinit(Unknown Source) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:192) at org.apache.geronimo.st.v20.core.GeronimoV20Utils.getConfigId2(GeronimoV20Utils.java:94) at org.apache.geronimo.st.v20.core.GeronimoV20VersionHandler.getConfigID(GeronimoV20VersionHandler.java:36) at org.apache.geronimo.st.core.DeploymentUtils.getLastKnownConfigurationId(DeploymentUtils.java:202) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getLastKnowConfigurationId(GeronimoServerBehaviourDelegate.java:456) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:402) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:367) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:267) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:234) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521125 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-184: -- Instead of java.lang.NoSuchMethodError: I keep hitting below errors during Publish: javax.enterprise.deploy.spi.exceptions.TargetException: Unknown attribute URLFor in gbean default/HelloWorld/1.0/car?J2EEApplication=null,j2eeType=WebModule,name=default/HelloWorld/1.0/car at org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.getModules(JMXDeploymentManager.java:180) at org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.getAvailableModules(JMXDeploymentManager.java:118) at org.apache.geronimo.st.core.DeploymentUtils.getTargetModuleID(DeploymentUtils.java:171) at org.apache.geronimo.st.core.DeploymentUtils.getLastKnownConfigurationId(DeploymentUtils.java:211) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doNoChange(GeronimoServerBehaviourDelegate.java:477) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:379) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:267) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:234) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.apache.geronimo.kernel.NoSuchAttributeException: Unknown attribute URLFor in gbean default/HelloWorld/1.0/car?J2EEApplication=null,j2eeType=WebModule,name=default/HelloWorld/1.0/car at org.apache.geronimo.gbean.runtime.GBeanInstance.getAttributeByName(GBeanInstance.java:800) at org.apache.geronimo.gbean.runtime.GBeanInstance.getAttribute(GBeanInstance.java:674) at org.apache.geronimo.kernel.basic.BasicKernel.getAttribute(BasicKernel.java:178) at org.apache.geronimo.kernel.KernelGBean.getAttribute(KernelGBean.java:282) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782) at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) An internal error occurred during:
[jira] Commented: (GERONIMODEVTOOLS-184) An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521137 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-184: -- Changing xmlbeans version to 2.3.0 and rebuilding the plug-in doesn't seem to solve the problem. Some of my observations while debugging: 1) Set breakpoint at line 171 of org.apache.geronimo.st.core.DeploymentUtils.class Here dm.getAvailableModules(null, dm.getTargets()) is called. 2) Keep Stepping into until you hit org.apache.geronimo.deployment.plugin.local.CommandSupport.addWebURLs(Kernel, List) line: 295 Here kernel.getAttribute(name, contextPath) is called. 3) Further stepping in, reveals that org.apache.geronimo.system.jmx.KernelDelegate.class's getAttribute(AbstractName abstractName, String attributeName) is called, with the value of second argument changed to URLFor instead of called value contextPath! 4) Also the org.apache.geronimo.system.jmx.KernelDelegate.class that is being used belongs to geronimo-system-1.1.1.jar referenced library of org.apache.geronimo.runtime.v11 plug-in! (A class of org.apache.geronimo.runtime.v20 using a class of org.apache.geronimo.runtime.v11) Looks like a class loading issue due to missing/improper dependencies. An internal error occurred during: Publishing to Apache Geronimo v2.0 Server at localhost... when deploy sample within Eclipse Key: GERONIMODEVTOOLS-184 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Windows xp sp2, Eclipse Version: 3.3.0 Reporter: Song Assignee: Shiva Kumar H R After deployed samples (such as cviewer) to the server within Eclipse, Run As--Run on Server,An internal error occurred. In fact, the cviewer sample can be deployed and executed successfully via the command line. Detailed error message see the below: --- java.lang.NoSuchMethodError: org/apache/xmlbeans/XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.deployment.xbeans.EnvironmentDocument.clinit(Unknown Source) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:192) at org.apache.geronimo.st.v20.core.GeronimoV20Utils.getConfigId2(GeronimoV20Utils.java:94) at org.apache.geronimo.st.v20.core.GeronimoV20VersionHandler.getConfigID(GeronimoV20VersionHandler.java:36) at org.apache.geronimo.st.core.DeploymentUtils.getLastKnownConfigurationId(DeploymentUtils.java:202) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getLastKnowConfigurationId(GeronimoServerBehaviourDelegate.java:456) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:402) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:367) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:267) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:234) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3428) Update user documentation in Create Plan portlet's jsp files
Update user documentation in Create Plan portlet's jsp files -- Key: GERONIMO-3428 URL: https://issues.apache.org/jira/browse/GERONIMO-3428 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Components: console, deployment Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Currently the UI pages of Create Plan portlet only has placeholders for user documentation. Replace these placeholders with useful documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3429) Enhance security page of 'Create Plan' portlet to support addition of run-as-subject, default-subject, credential-store
Enhance security page of 'Create Plan' portlet to support addition of run-as-subject, default-subject, credential-store --- Key: GERONIMO-3429 URL: https://issues.apache.org/jira/browse/GERONIMO-3429 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Currently the 'Create Plan' portlet has no support for specifying run-as-subject, default-subject, credential-store, doas-current-caller use-context-handler. Update the security handling page to support specification of these. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3430) Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app
Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app Key: GERONIMO-3430 URL: https://issues.apache.org/jira/browse/GERONIMO-3430 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Currently 'Create Plan' portlet doesn't handle Web Service references in a web-app. Enhance the wizard to take care of web service references in web-app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3431) Enhance 'Create Plan' portlet to auto handle references to JavaMail resources in a web-app
Enhance 'Create Plan' portlet to auto handle references to JavaMail resources in a web-app -- Key: GERONIMO-3431 URL: https://issues.apache.org/jira/browse/GERONIMO-3431 Project: Geronimo Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3432) Admin Console Wizard to auto generate openejb-jar.xml
Admin Console Wizard to auto generate openejb-jar.xml - Key: GERONIMO-3432 URL: https://issues.apache.org/jira/browse/GERONIMO-3432 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: console, deployment, usability Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 For a background about this work please see GERONIMO-3254. Currently the plan creation wizard only takes a web-app (.war) as an input and helps in auto-creating geronimo-web.xml. Enhance the wizard to take an EJB-JAR input and help in auto-creating openejb-jar.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3433) Admin Console Wizard to auto generate geronimo-application.xml
Admin Console Wizard to auto generate geronimo-application.xml -- Key: GERONIMO-3433 URL: https://issues.apache.org/jira/browse/GERONIMO-3433 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: console, deployment, usability Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 For a background about this work please see GERONIMO-3254 GERONIMO-3432. Enhance Create Plan portlet other Admin Console Wizards to help server-administrators in auto creating the Geronimo Deployment Plan for a J2EE/Java-EE application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-185) Enhance SharedLibEntryCreationOperation to respect entries in classpath containers
Enhance SharedLibEntryCreationOperation to respect entries in classpath containers -- Key: GERONIMODEVTOOLS-185 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-185 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Reporter: Shiva Kumar H R Please see the discussion thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg06976.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-178) Deadlock! while stopping Geronimo server from within Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521536 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-178: -- Bug 200715 in WTP (https://bugs.eclipse.org/bugs/show_bug.cgi?id=200715) has been raised for this. Deadlock! while stopping Geronimo server from within Eclipse Key: GERONIMODEVTOOLS-178 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-178 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.2.0, 1.2.1, 2.0 Reporter: Shiva Kumar H R Assignee: Donald Woods Fix For: 2.0 Attachments: deadlockFix.patch, TestDeadlock.war An interesting deadlock scenario! Here are the steps to reproduce: 1. From within Eclipse start Geronimo server (say 2.0) 2. Deploy attached WAR 3. Access deployed servlet with url http://localhost:8080/TestDeadlock/Test; 4. From within Eclipse invoke Stop server You will see that Stop never returns and Eclipse freezes to respond. 5. Manually kill server process and Eclipse will resume. Here is what is happening: 1. When user invokes Stop on Geronimo server from within Eclipse, Geronimo Eclipse Plug-in invokes stopKernel() in the main Eclipse thread itself. (org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.java::stop()) 2. Server receives the shutdown call, and invokes the deployed WAR's servlet.destroy method, which in turn opens a big text file and starts printing the contents to standard output. 3. All the output buffers overflow because the main thread is the one that should push them to the console view at the end but it is blocked. 4. All the print operations on the server side are blocked waiting for somebody to read the output buffer. The shutdown call will never return. 5. The main Eclipse thread will never print the messages because it waits for the shutdown call to return. Here is one solution thought of: The Geronimo Eclipse plug-in should make the shutdown call in a worker thread not in the main Eclipse thread. In this case the main thread will be able to display all the messages triggered by the shutdown call and everything will work just fine. Attached patch implements this. Please see this also: http://www.eclipse.org/webtools/wst/api/org/eclipse/wst/server/core/model/ServerBehaviourDelegate.html#stop(boolean) It recommends that the plug-in should return from the ServerBehaviourDelegate.stop() method quickly and use the server listener to notify shutdown progress. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-186) Duplicate License Headers in source
Duplicate License Headers in source --- Key: GERONIMODEVTOOLS-186 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-186 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.0 While reviewing the commits of GERONIMODEVTOOLS-184 observed that \modules\eclipse-support\pom.xml has duplicate license header. A look at it's svn log showed that this was a mistake from GERONIMODEVTOOLS-114. Friend 'Anil Kainikara' very quickly wrote an useful script ListFilesWithDuplicateLicenseHeaders.ksh. Upon executing this on devtools-trunk, found that following files have such duplicate license headers: ./modules/eclipse-support/src/main/schema/xmlconfig.xml ./modules/eclipse-support/src/main/schema/eclipse-deployable-1.0.xsd ./modules/eclipse-support/pom.xml ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/IDeploymentCommand.java ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/StartCommand.java ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/SynchronizedDeploymentOp.java Patch attached removes these duplicate license headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-186) Duplicate License Headers in source
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-186: - Attachment: GERONIMODEVTOOLS-186.patch ListFilesWithDuplicateLicenseHeaders.ksh Duplicate License Headers in source --- Key: GERONIMODEVTOOLS-186 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-186 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.0 Attachments: GERONIMODEVTOOLS-186.patch, ListFilesWithDuplicateLicenseHeaders.ksh While reviewing the commits of GERONIMODEVTOOLS-184 observed that \modules\eclipse-support\pom.xml has duplicate license header. A look at it's svn log showed that this was a mistake from GERONIMODEVTOOLS-114. Friend 'Anil Kainikara' very quickly wrote an useful script ListFilesWithDuplicateLicenseHeaders.ksh. Upon executing this on devtools-trunk, found that following files have such duplicate license headers: ./modules/eclipse-support/src/main/schema/xmlconfig.xml ./modules/eclipse-support/src/main/schema/eclipse-deployable-1.0.xsd ./modules/eclipse-support/pom.xml ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/IDeploymentCommand.java ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/StartCommand.java ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/SynchronizedDeploymentOp.java Patch attached removes these duplicate license headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-186) Duplicate License Headers in source
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-186: Assignee: Tim McConnell Duplicate License Headers in source --- Key: GERONIMODEVTOOLS-186 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-186 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Assignee: Tim McConnell Priority: Minor Fix For: 2.0 Attachments: GERONIMODEVTOOLS-186.patch, ListFilesWithDuplicateLicenseHeaders.ksh While reviewing the commits of GERONIMODEVTOOLS-184 observed that \modules\eclipse-support\pom.xml has duplicate license header. A look at it's svn log showed that this was a mistake from GERONIMODEVTOOLS-114. Friend 'Anil Kainikara' very quickly wrote an useful script ListFilesWithDuplicateLicenseHeaders.ksh. Upon executing this on devtools-trunk, found that following files have such duplicate license headers: ./modules/eclipse-support/src/main/schema/xmlconfig.xml ./modules/eclipse-support/src/main/schema/eclipse-deployable-1.0.xsd ./modules/eclipse-support/pom.xml ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/IDeploymentCommand.java ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/StartCommand.java ./plugins/org.apache.geronimo.st.core/src/org/apache/geronimo/st/core/commands/SynchronizedDeploymentOp.java Patch attached removes these duplicate license headers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3439) geronimo-openejb-2.0.xsd not packaged under schema directory!
geronimo-openejb-2.0.xsd not packaged under schema directory! - Key: GERONIMO-3439 URL: https://issues.apache.org/jira/browse/GERONIMO-3439 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: OpenEJB Affects Versions: 2.0.x, 2.1 Reporter: Shiva Kumar H R Fix For: 2.0.x, 2.1 geronimo-openejb-2.0.xsd is currently hidden inside repository\org\apache\geronimo\modules\geronimo-security-builder\2.0.1\geronimo-security-builder-2.0.1.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-187) EMF for new schema version of Geronimo Deployment Plans
EMF for new schema version of Geronimo Deployment Plans --- Key: GERONIMODEVTOOLS-187 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-187 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Priority: Critical Fix For: 2.0 plugins\org.apache.geronimo.st.v20.core is currently using EMF classes from org.apache.geronimo.v11.deployment.model. However Geronimo v2.0.1 has new schema versions for its deployment plans. We need to generate EMF for these new schemas. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-187) EMF for new schema version of Geronimo Deployment Plans
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-187: - Attachment: GERONIMODEVTOOLS-187-reference.patch Looks like there is some more work that needs to be done. With the above patch I am currently getting following errors while building org.apache.geronimo.v20.deployment.model: [INFO] Compiling 230 source files to E:\_src\eclipse-plugin\trunk\plugins\org.ap ache.geronimo.v20.deployment.model\target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure E:\_src\eclipse-plugin\trunk\plugins\org.apache.geronimo.v20.deployment.model\sr c\org\apache\geronimo\xml\ns\j2ee\application\ApplicationPackage.java:[950,2] ca nnot find symbol symbol : class ApplicationFactory location: interface org.apache.geronimo.xml.ns.j2ee.application.ApplicationPacka ge E:\_src\eclipse-plugin\trunk\plugins\org.apache.geronimo.v20.deployment.model\sr c\org\apache\geronimo\xml\ns\j2ee\application\ApplicationPackage.java:[108,81] c annot find symbol symbol : class ApplicationPackageImpl location: package org.apache.geronimo.xml.ns.j2ee.application.impl E:\_src\eclipse-plugin\trunk\plugins\org.apache.geronimo.v20.deployment.model\sr c\org\apache\geronimo\xml\ns\j2ee\ejb\openejb\impl\GeronimoEjbJarTypeImpl.java:[ 288,57] inconvertible types found : org.eclipse.emf.common.util.EListjava.lang.Object required: org.eclipse.emf.ecore.util.FeatureMap E:\_src\eclipse-plugin\trunk\plugins\org.apache.geronimo.v20.deployment.model\sr c\org\apache\geronimo\xml\ns\j2ee\ejb\openejb\impl\GeronimoEjbJarTypeImpl.java:[ 462,38] inconvertible types found : org.eclipse.emf.common.util.EListjava.lang.Object required: org.eclipse.emf.ecore.util.FeatureMap E:\_src\eclipse-plugin\trunk\plugins\org.apache.geronimo.v20.deployment.model\sr c\org\apache\geronimo\xml\ns\j2ee\web\impl\WebAppTypeImpl.java:[622,38] inconver tible types found : org.eclipse.emf.common.util.EListjava.lang.Object required: org.eclipse.emf.ecore.util.FeatureMap [INFO] Wondering why EMF is not generating those missing classes: ApplicationFactory, ApplicationPackageImpl ? EMF for new schema version of Geronimo Deployment Plans --- Key: GERONIMODEVTOOLS-187 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-187 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Priority: Critical Fix For: 2.0 Attachments: GERONIMODEVTOOLS-187-reference.patch plugins\org.apache.geronimo.st.v20.core is currently using EMF classes from org.apache.geronimo.v11.deployment.model. However Geronimo v2.0.1 has new schema versions for its deployment plans. We need to generate EMF for these new schemas. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3254) Admin Console Wizard to auto generate geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMO-3254: - Assignee: Shiva Kumar H R Admin Console Wizard to auto generate geronimo-web.xml -- Key: GERONIMO-3254 URL: https://issues.apache.org/jira/browse/GERONIMO-3254 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console, deployment, usability Affects Versions: 2.0-M7 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Attachments: 1WelcomePage.gif, 2BasicSettings.gif, 3ResolveReferences.gif, 4AddDependencies.gif, 5DisplaysCreatedPlan.gif, 6DeployStatus.gif, 7SecurityHandling_1.gif, 7SecurityHandling_2.gif, 7SecurityHandling_3.gif, buildCreatePlanPortlet.bat, buildCreatePlanPortlet2.bat, consolidated 3254 3394 3395 3396 3397 3398.patch, GERONIMO-3254.patch, PoC.patch, PoC_2(annotations).patch, SampleWebAppsWithAnnotations.zip, TestCreatePlanPortlet.zip, TestSecuritySettings.zip For a background about this work, please see the discussion thread: http://www.mail-archive.com/dev@geronimo.apache.org/msg46831.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-190) Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0, deployment-1.2 etc)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-190: - Attachment: HelloWorld.war Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0, deployment-1.2 etc) --- Key: GERONIMODEVTOOLS-190 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Fix For: 2.0 Attachments: HelloWorld.war Import the attached HelloWorld.war and double click on geronimo-web.xml. An error window will pop up saying .. elements in the plan may not be qualified ... This is caused by trying to parse v2.0 of Geronimo plans with v1.1 of schemas. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-190) Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0, deployment-1.2 etc)
Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0, deployment-1.2 etc) --- Key: GERONIMODEVTOOLS-190 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Fix For: 2.0 Attachments: HelloWorld.war Import the attached HelloWorld.war and double click on geronimo-web.xml. An error window will pop up saying .. elements in the plan may not be qualified ... This is caused by trying to parse v2.0 of Geronimo plans with v1.1 of schemas. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-189) Error opening geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523812 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-189: -- I tried with g-eclipse-plugin-2.0.0-v20070829.1146-deployable.zip available at http://people.apache.org/dist/geronimo/eclipse/unstable/ . Created a new Dynamic Web Project with 'Apache Geronimo v2.0' as Target Runtime and then double-clicked on the generated geronimo-web.xml. It opened successfully without any errors. So Shane Blake, please see if restarting eclipse with a clean workspace solves your problem. I see that the generated plan points to v1.1 of Geronimo plans (web-1.1, naming-1.1, deployment-1.1 etc). If we however try to change the version to 2.0, save, close reopen, it fails by throwing an error as reported in GERONIMODEVTOOLS-190. Error opening geronimo-web.xml -- Key: GERONIMODEVTOOLS-189 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Eclipse SDK Version: 3.3.0 Build id: I20070525-1350 Build id: I20070625-1500 Latest August 23 build from unstable Reporter: Shane Blake Assignee: Tim McConnell Opening geronimo-web.xml getting the following stack trace: java.lang.IllegalArgumentException at org.eclipse.wst.server.core.internal.facets.FacetUtil.getRuntime(FacetUtil.java:61) at org.eclipse.jst.server.core.FacetUtil.getRuntime(FacetUtil.java:47) at org.apache.geronimo.st.ui.editors.SharedDeploymentPlanEditor.getLoader(SharedDeploymentPlanEditor.java:97) at org.apache.geronimo.st.ui.editors.SharedDeploymentPlanEditor.loadDeploymentPlan(SharedDeploymentPlanEditor.java:86) at org.apache.geronimo.st.ui.editors.AbstractGeronimoDeploymentPlanEditor.init(AbstractGeronimoDeploymentPlanEditor.java:181) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:794) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:643) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256) at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209) at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604) at org.eclipse.ui.internal.PartStack.add(PartStack.java:499) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103) at org.eclipse.ui.internal.PartStack.add(PartStack.java:485) at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112) at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217) at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207) at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774) at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673) at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2719) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633) at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2547) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:644) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:603) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:285)
[jira] Commented: (GERONIMODEVTOOLS-183) Eclipse doesnot launch the application with context root instead launches the application with the name of application module
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523817 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-183: -- This looks to have been fixed in trunk by other fixes. Can be closed. Eclipse doesnot launch the application with context root instead launches the application with the name of application module - Key: GERONIMODEVTOOLS-183 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-183 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Microsoft Windows XP Professional version 2002 Service Pack2 Reporter: Ashish Jain Assignee: Tim McConnell Fix For: 2.0 I am using *wtp-all-in-one-sdk-R-2.0-200706260303* and *g-eclipse-plugin-2.0.0-v20070812.0209-deployable*. While I run application hello-1.1.1.war using Eclipse, instead of launching the application with the context root that is *hello* it launches the application with *hello-1.1.1* and I get a 404 error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-202) A geronimo installation was detected, however the version could not be verified warning while adding Geronimo 2.0.1
A geronimo installation was detected, however the version could not be verified warning while adding Geronimo 2.0.1 - Key: GERONIMODEVTOOLS-202 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-202 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.0 Initial debugging shows that this is due to: org.apache.geronimo.st.core.GeronimoRuntimeDelegate.detectVersion() method returning null, which in turn is due to missing geronimo-system-*.jar file in GERONIMO-HOME\lib directory of Geronimo 2.0.1 installation. geronimo-system-2.0.1.jar can however be found GERONIMO-HOME\repository\org\apache\geronimo\modules\geronimo-system\2.0.1 directory of AG 2.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-202) A geronimo installation was detected, however the version could not be verified warning while adding Geronimo 2.0.1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-202: - Attachment: GERONIMODEVTOOLS-202-temp.patch Tim, I am not happy with hard-coding paths as done in this patch. Do you see a better way of solving this? A geronimo installation was detected, however the version could not be verified warning while adding Geronimo 2.0.1 - Key: GERONIMODEVTOOLS-202 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-202 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Priority: Minor Fix For: 2.0 Attachments: GERONIMODEVTOOLS-202-temp.patch Initial debugging shows that this is due to: org.apache.geronimo.st.core.GeronimoRuntimeDelegate.detectVersion() method returning null, which in turn is due to missing geronimo-system-*.jar file in GERONIMO-HOME\lib directory of Geronimo 2.0.1 installation. geronimo-system-2.0.1.jar can however be found GERONIMO-HOME\repository\org\apache\geronimo\modules\geronimo-system\2.0.1 directory of AG 2.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-202) A geronimo installation was detected, however the version could not be verified warning while adding Geronimo 2.0.1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-202: Assignee: Tim McConnell A geronimo installation was detected, however the version could not be verified warning while adding Geronimo 2.0.1 - Key: GERONIMODEVTOOLS-202 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-202 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Assignee: Tim McConnell Priority: Minor Fix For: 2.0 Attachments: GERONIMODEVTOOLS-202-temp.patch Initial debugging shows that this is due to: org.apache.geronimo.st.core.GeronimoRuntimeDelegate.detectVersion() method returning null, which in turn is due to missing geronimo-system-*.jar file in GERONIMO-HOME\lib directory of Geronimo 2.0.1 installation. geronimo-system-2.0.1.jar can however be found GERONIMO-HOME\repository\org\apache\geronimo\modules\geronimo-system\2.0.1 directory of AG 2.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3467) Confusing security exception thrown while authenticating using JMX with a just starting server
Confusing security exception thrown while authenticating using JMX with a just starting server -- Key: GERONIMO-3467 URL: https://issues.apache.org/jira/browse/GERONIMO-3467 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.0.2 Reporter: Shiva Kumar H R Fix For: 2.0.2 Scenario is as below: Let's say server is starting and org.apache.geronimo.configs/rmi-naming/2.0.1/car has started, but org.apache.geronimo.configs/j2ee-security/2.0.1/car hasn't yet started. If an external entity (like Geronimo Eclipse Plug-in) now tries to connect to the kernel remotely through JMX, although rmi connection succeeds, authenticate will fail (because security realm has not yet been started). In this case, org.apache.geronimo.jmxremoting.Authenticator.authenticate() is getting a LoginException with error javax.security.auth.login.LoginException: No LoginModules configured for geronimo-admin. However this exception is not propogated, but rather is thrown back as a 'SecurityException(Invalid login)'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3467) Confusing security exception thrown while authenticating using JMX with a just starting server
[ https://issues.apache.org/jira/browse/GERONIMO-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526785 ] Shiva Kumar H R commented on GERONIMO-3467: --- Forgot to mention that this is causing problem in Geronimo Eclipse Plug-in as reported in GERONIMODEVTOOLS-193. Confusing security exception thrown while authenticating using JMX with a just starting server -- Key: GERONIMO-3467 URL: https://issues.apache.org/jira/browse/GERONIMO-3467 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.0.2 Reporter: Shiva Kumar H R Fix For: 2.0.2 Scenario is as below: Let's say server is starting and org.apache.geronimo.configs/rmi-naming/2.0.1/car has started, but org.apache.geronimo.configs/j2ee-security/2.0.1/car hasn't yet started. If an external entity (like Geronimo Eclipse Plug-in) now tries to connect to the kernel remotely through JMX, although rmi connection succeeds, authenticate will fail (because security realm has not yet been started). In this case, org.apache.geronimo.jmxremoting.Authenticator.authenticate() is getting a LoginException with error javax.security.auth.login.LoginException: No LoginModules configured for geronimo-admin. However this exception is not propogated, but rather is thrown back as a 'SecurityException(Invalid login)'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-193) Runs ping and throws java.lang.SecurityException during Geronimo server startup.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-193: Assignee: Shiva Kumar H R (was: Tim McConnell) Runs ping and throws java.lang.SecurityException during Geronimo server startup. Key: GERONIMODEVTOOLS-193 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Windows XP, Eclipse 3.3, WTP 2.0, Geronimo server 2.0.1, Sun JDK 1.5.0_11 Reporter: Kan Ogawa Assignee: Shiva Kumar H R Hi, While launching Geronimo server on Eclipse, a ping runs in async and the server startup sometimes fails. This server hostname is localhost. Eclipse error log: java.lang.SecurityException: Invalid login at org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java:73) at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:214) at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source) at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getServerConnection(GeronimoServerBehaviourDelegate.java:689) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.getKernel(GeronimoServerBehaviour.java:73) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isKernelAlive(GeronimoServerBehaviour.java:93) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isFullyStarted(GeronimoServerBehaviour.java:113) at org.apache.geronimo.st.core.PingThread.run(PingThread.java:75) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-193) Runs ping and throws java.lang.SecurityException during Geronimo server startup.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526823 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-193: -- Thanks Kan Ogawa for your observations debugging :) Please see the 12-Sep IRC discussions between shivahr and mcconne http://servlet.uwyn.com/drone/log/bevinbot/geronimo/20070912 for further discussions on this. Runs ping and throws java.lang.SecurityException during Geronimo server startup. Key: GERONIMODEVTOOLS-193 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Windows XP, Eclipse 3.3, WTP 2.0, Geronimo server 2.0.1, Sun JDK 1.5.0_11 Reporter: Kan Ogawa Assignee: Shiva Kumar H R Hi, While launching Geronimo server on Eclipse, a ping runs in async and the server startup sometimes fails. This server hostname is localhost. Eclipse error log: java.lang.SecurityException: Invalid login at org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java:73) at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:214) at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source) at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getServerConnection(GeronimoServerBehaviourDelegate.java:689) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.getKernel(GeronimoServerBehaviour.java:73) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isKernelAlive(GeronimoServerBehaviour.java:93) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isFullyStarted(GeronimoServerBehaviour.java:113) at org.apache.geronimo.st.core.PingThread.run(PingThread.java:75) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-193) Runs ping and throws java.lang.SecurityException during Geronimo server startup.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526837 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-193: -- This is fixed in branches\2.0.0. Will however leave the JIRA open for better fixing in trunk. Kan Ogawa, The eclipse plug-in which Tim is going to put up for vote later today will have the fix for this. Can you please give it a try and verify that the problem is fixed? Runs ping and throws java.lang.SecurityException during Geronimo server startup. Key: GERONIMODEVTOOLS-193 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Environment: Windows XP, Eclipse 3.3, WTP 2.0, Geronimo server 2.0.1, Sun JDK 1.5.0_11 Reporter: Kan Ogawa Assignee: Shiva Kumar H R Hi, While launching Geronimo server on Eclipse, a ping runs in async and the server startup sometimes fails. This server hostname is localhost. Eclipse error log: java.lang.SecurityException: Invalid login at org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java:73) at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:214) at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source) at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getServerConnection(GeronimoServerBehaviourDelegate.java:689) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.getKernel(GeronimoServerBehaviour.java:73) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isKernelAlive(GeronimoServerBehaviour.java:93) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isFullyStarted(GeronimoServerBehaviour.java:113) at org.apache.geronimo.st.core.PingThread.run(PingThread.java:75) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-193) Runs ping and throws java.lang.SecurityException during Geronimo server startup.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMODEVTOOLS-193: - Affects Version/s: (was: 2.0) 2.1 Fix Version/s: 2.1 A temp fix has been committed into branches\2.0.0 until GERONIMO-3467 gets fixed. A more elegant fix should be worked out for trunk. Runs ping and throws java.lang.SecurityException during Geronimo server startup. Key: GERONIMODEVTOOLS-193 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-193 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1 Environment: Windows XP, Eclipse 3.3, WTP 2.0, Geronimo server 2.0.1, Sun JDK 1.5.0_11 Reporter: Kan Ogawa Assignee: Shiva Kumar H R Fix For: 2.1 Hi, While launching Geronimo server on Eclipse, a ping runs in async and the server startup sometimes fails. This server hostname is localhost. Eclipse error log: java.lang.SecurityException: Invalid login at org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java:73) at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:214) at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source) at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getServerConnection(GeronimoServerBehaviourDelegate.java:689) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.getKernel(GeronimoServerBehaviour.java:73) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isKernelAlive(GeronimoServerBehaviour.java:93) at org.apache.geronimo.st.v20.core.GeronimoServerBehaviour.isFullyStarted(GeronimoServerBehaviour.java:113) at org.apache.geronimo.st.core.PingThread.run(PingThread.java:75) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-203) No-harm error dialog while switching from Run-to-Debug or Debug-to-Run
No-harm error dialog while switching from Run-to-Debug or Debug-to-Run -- Key: GERONIMODEVTOOLS-203 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-203 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Start server as usual. Once server has started, right click on the server and select Debug. Server will now be stopped and restarted in Debug mode. Although this succeeds, sometimes during the process it throws a confusing error dialog saying Problem Occurred ... Server Apache Geronimo v2.0 Server at localhost failed to start. Similarly scenario while switching back from Debug to Run modes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-204) Change pre-requisite from current wtp-all-in-one-sdk-* (266MB) to Eclipse IDE for Java EE Developers (125MB)
Change pre-requisite from current wtp-all-in-one-sdk-* (266MB) to Eclipse IDE for Java EE Developers (125MB) Key: GERONIMODEVTOOLS-204 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-204 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 2.1 Reporter: Shiva Kumar H R Fix For: 2.1 Geronimo Eclipse Plug-in (GEP) v2.0 currently has following pre-requisites: 1 -- Eclipse Classic 3.3 2 -- Web Tools Platform (WTP) 2.0 3 -- Data Tools Platform (DTP) 1.5 4 -- Eclipse Modeling Framework (EMF) 2.3 5 -- Graphical Editing Framework (GEF) 3.3 A wtp-all-in-one-sdk-* bundle that includes all the above 5 pre-requisites can be downloaded from http://download.eclipse.org/webtools/downloads/drops/R2.0/R-2.0-200706260303/ and it has a size of around 260MB. eclipse.org starting with Europa release (http://www.eclipse.org/europa/) have a new package by name Eclipse IDE for Java EE Developers with a size of just 125MB (no source bundles included) and has all the pre-requistes for GEP. GEP should be updated to utilize this new package of smaller download size. (This was attempted in GERONIMODEVTOOLS-180 and due to some problems faced, this has been deferred to GEP 2.1). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-204) Change pre-requisite from current wtp-all-in-one-sdk-* (266MB) to Eclipse IDE for Java EE Developers (125MB)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527140 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-204: -- An useful link - http://www.eclipse.org/downloads/moreinfo/compare.php Change pre-requisite from current wtp-all-in-one-sdk-* (266MB) to Eclipse IDE for Java EE Developers (125MB) Key: GERONIMODEVTOOLS-204 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-204 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Affects Versions: 2.1 Reporter: Shiva Kumar H R Fix For: 2.1 Geronimo Eclipse Plug-in (GEP) v2.0 currently has following pre-requisites: 1 -- Eclipse Classic 3.3 2 -- Web Tools Platform (WTP) 2.0 3 -- Data Tools Platform (DTP) 1.5 4 -- Eclipse Modeling Framework (EMF) 2.3 5 -- Graphical Editing Framework (GEF) 3.3 A wtp-all-in-one-sdk-* bundle that includes all the above 5 pre-requisites can be downloaded from http://download.eclipse.org/webtools/downloads/drops/R2.0/R-2.0-200706260303/ and it has a size of around 260MB. eclipse.org starting with Europa release (http://www.eclipse.org/europa/) have a new package by name Eclipse IDE for Java EE Developers with a size of just 125MB (no source bundles included) and has all the pre-requistes for GEP. GEP should be updated to utilize this new package of smaller download size. (This was attempted in GERONIMODEVTOOLS-180 and due to some problems faced, this has been deferred to GEP 2.1). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-107) Invalid file name of the deployment plan for a Connector
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527593 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-107: -- This is fixed in 1) \branches\2.0.0 at revision 575767, and 2) \trunk at revision 575769. Thanks Kan Ogawa for re-capturing this. Invalid file name of the deployment plan for a Connector Key: GERONIMODEVTOOLS-107 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-107 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 1.1.0 Environment: Windows XP SP2, Sun J2RE SE 1.5.0._08, Eclipse SDK 3.2.0, Geronimo Eeclipse Plugin 1.1.x (11-Aug-2006) Reporter: Ilya Kanonirov Fix For: 1.2.1 After creating a new connector using the Connector Project wizard, the name of module's deployment plan is geronimo-connector.xml instead of expected geronimo-ra.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-211) Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-211: Assignee: Shiva Kumar H R Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development -- Key: GERONIMODEVTOOLS-211 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.0 After checking-out source code and doing an mvn build, import the source plug-ins into Eclipse for development, as illustrated in http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html After import and a build within Eclipse, some 25 errors similar to the one below get reported: Package 'schemaorg_apache_xmlbeans.element.URI_SHA_1_7468FED616215A569CA8BA192F2C978B6D094868' does not exist in this plug-in. Eliminate these compile time errors. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-211) Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development
Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development -- Key: GERONIMODEVTOOLS-211 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Fix For: 2.0 After checking-out source code and doing an mvn build, import the source plug-ins into Eclipse for development, as illustrated in http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html After import and a build within Eclipse, some 25 errors similar to the one below get reported: Package 'schemaorg_apache_xmlbeans.element.URI_SHA_1_7468FED616215A569CA8BA192F2C978B6D094868' does not exist in this plug-in. Eliminate these compile time errors. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-211) Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMODEVTOOLS-211. Resolution: Fixed Fixed in branches\2.0.0 at revision 575782. Eliminate compile time errors (related to XmlBeans schemas) reported by Eclipse during plug-in development -- Key: GERONIMODEVTOOLS-211 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-211 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.0 After checking-out source code and doing an mvn build, import the source plug-ins into Eclipse for development, as illustrated in http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.html After import and a build within Eclipse, some 25 errors similar to the one below get reported: Package 'schemaorg_apache_xmlbeans.element.URI_SHA_1_7468FED616215A569CA8BA192F2C978B6D094868' does not exist in this plug-in. Eliminate these compile time errors. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3489) Deployment problems caused by file deletion failures
[ https://issues.apache.org/jira/browse/GERONIMO-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530643 ] Shiva Kumar H R commented on GERONIMO-3489: --- Thanks Ted for raising this. I have hit this problem many a times when deploying from within Eclipse Plug-in. I use Windows XP + NTFS + Sun JDK 1.5.0_11. Deployment problems caused by file deletion failures Key: GERONIMO-3489 URL: https://issues.apache.org/jira/browse/GERONIMO-3489 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Reporter: Ted Kirby Fix For: 2.0.2, 2.0.x, 2.1 File.delete() failures in IOUtil.recursiveDelete() are causing various deployment problems. I open this JIRA to discuss them to see how the server might better handle them. In all but one case, delete failures are not even noted with a log record! Deletion problems are seen in many environments and platforms, but they are persistently fatal when using a NFS file system for the repository. In investigating the problem, I have added code to recursiveDelete to retry the delete a few times if it fails. I added code to list directory contents if a directory delete failed, and saw a file named .nfs2bc4350053e in the directory. My first attempt at a bypass was to retry a failed delete 5 times, sleeping a second before each try. This did not work. I added a call to System.gc() before each sleep, and this got me passed the problem. Interestingly, two retries were required to get this to work. In another version, each retry was a second longer, and I printed all file names in a directory before trying the delete. This worked in most cases, but required the full 5 retries, so I suspect System.gc() would have time. System.runFinalization() would be something else to try. RepositoryConfigurationStore.createNewConfigurationDir(Artifact) shows the failing end of the deletion problem, with the dreaded ConfigurationAlreadyExistsException(Configuration already exists: + configId)exception. I think this message is not good. It should really say directory already exists. If the file is not deleted on undeploy, this failure occurs on a subsequent deploy. What is really bad is if the user invokes a redeploy operation, and the file delete fails on the undeploy. It is important that undeploy not complete until the file goes away. From other environments, I am not convinced that all file handles and references, and particularly open streams, are being closed on some artifacts. This will cause the delete to fail. It may be that the gc() calls are cleaning these up, and allowing the deletes to work in my case above. Another option is that RepositoryConfigurationStore.createNewConfigurationDir(Artifact) not throw a ConfigurationAlreadyExistsException if the only problem is an empty directory structure exists. The next line creates the directory structure anyway. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-190) Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0, deployment-1.2 etc)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533613 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-190: -- We are re-looking at some of the basics of Geronimo Eclipse Plug-in's Editors for Geronimo deployment plans: http://www.mail-archive.com/dev@geronimo.apache.org/msg51801.html One promising approach seems to be to use JSR-88 DConfigBeans as the model framework for Geronimo deployment plan editors. However, Geronimo doesn't yet have a complete set of JSR-88 DConfigBeans. The work I am currently doing on Geronimo JIRAs 3254, 3433 3432 (Admin Console Wizards to auto generate Geronimo Deployment Plans) will find/add many of the missing DConfigBeans. Once that is complete I am planning to take up this JIRA. Meanwhile, any and all help is welcome. Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0, deployment-1.2 etc) --- Key: GERONIMODEVTOOLS-190 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Shiva Kumar H R Assignee: Tim McConnell Fix For: 2.0.2 Attachments: HelloWorld.war Import the attached HelloWorld.war and double click on geronimo-web.xml. An error window will pop up saying .. elements in the plan may not be qualified ... This is caused by trying to parse v2.0 of Geronimo plans with v1.1 of schemas. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3428) Update user documentation in Create Plan portlet's jsp files
[ https://issues.apache.org/jira/browse/GERONIMO-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMO-3428. - Resolution: Fixed Completed: At revision: 585559 Update user documentation in Create Plan portlet's jsp files -- Key: GERONIMO-3428 URL: https://issues.apache.org/jira/browse/GERONIMO-3428 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: console, deployment Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Currently the UI pages of Create Plan portlet only has placeholders for user documentation. Replace these placeholders with useful documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3431) Enhance 'Create Plan' portlet to auto handle references to JavaMail resources in a web-app
[ https://issues.apache.org/jira/browse/GERONIMO-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3431: -- Attachment: generated geronimo-web.xml sendmail.war sendmail.war : a test web-app obtained from http://cwiki.apache.org/GMOxDOC20/using-geronimos-default-javamail-session.html generated geronimo-web.xml: Plan generated from Admin Console Wizard. Start a Mail Server (as per the instructions in the above wiki page) before deploying testing the web-app using the generated plan. Enhance 'Create Plan' portlet to auto handle references to JavaMail resources in a web-app -- Key: GERONIMO-3431 URL: https://issues.apache.org/jira/browse/GERONIMO-3431 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Attachments: generated geronimo-web.xml, sendmail.war -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3431) Enhance 'Create Plan' portlet to auto handle references to JavaMail resources in a web-app
[ https://issues.apache.org/jira/browse/GERONIMO-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMO-3431. - Resolution: Fixed Fix Version/s: 2.1 Completed: At revision: 585954 in trunk. Enhance 'Create Plan' portlet to auto handle references to JavaMail resources in a web-app -- Key: GERONIMO-3431 URL: https://issues.apache.org/jira/browse/GERONIMO-3431 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Attachments: generated geronimo-web.xml, sendmail.war -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3429) Enhance security page of 'Create Plan' portlet to support addition of run-as-subject, default-subject, credential-store
[ https://issues.apache.org/jira/browse/GERONIMO-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMO-3429. - Resolution: Fixed Fix Version/s: 2.1 Completed at Revision r593590 Enhance security page of 'Create Plan' portlet to support addition of run-as-subject, default-subject, credential-store --- Key: GERONIMO-3429 URL: https://issues.apache.org/jira/browse/GERONIMO-3429 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Currently the 'Create Plan' portlet has no support for specifying run-as-subject, default-subject, credential-store, doas-current-caller use-context-handler. Update the security handling page to support specification of these. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3254) Admin Console Wizard to auto generate geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMO-3254. - Resolution: Fixed All sub tasks completed. geronimo-web.xml can now be auto generated using Plan Creator wizard for most of the web applications. Admin Console Wizard to auto generate geronimo-web.xml -- Key: GERONIMO-3254 URL: https://issues.apache.org/jira/browse/GERONIMO-3254 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console, deployment, usability Affects Versions: 2.0-M7 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Attachments: 1WelcomePage.gif, 2BasicSettings.gif, 3ResolveReferences.gif, 4AddDependencies.gif, 5DisplaysCreatedPlan.gif, 6DeployStatus.gif, 7SecurityHandling_1.gif, 7SecurityHandling_2.gif, 7SecurityHandling_3.gif, buildCreatePlanPortlet.bat, buildCreatePlanPortlet2.bat, consolidated 3254 3394 3395 3396 3397 3398.patch, GERONIMO-3254.patch, PoC.patch, PoC_2(annotations).patch, SampleWebAppsWithAnnotations.zip, TestCreatePlanPortlet.zip, TestSecuritySettings.zip For a background about this work, please see the discussion thread: http://www.mail-archive.com/dev@geronimo.apache.org/msg46831.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3430) Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app
[ https://issues.apache.org/jira/browse/GERONIMO-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3430: -- Attachment: 1b.gif 1a.gif Snapshots of wizard in action. Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app Key: GERONIMO-3430 URL: https://issues.apache.org/jira/browse/GERONIMO-3430 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Attachments: 1a.gif, 1b.gif, generatedPlan.xml, new-jaxws-calculator-war-2.1-SNAPSHOT.war Currently 'Create Plan' portlet doesn't handle Web Service references in a web-app. Enhance the wizard to take care of web service references in web-app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3430) Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app
[ https://issues.apache.org/jira/browse/GERONIMO-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3430: -- Attachment: generatedPlan.xml new-jaxws-calculator-war-2.1-SNAPSHOT.war A testcase wizard generated plan. Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app Key: GERONIMO-3430 URL: https://issues.apache.org/jira/browse/GERONIMO-3430 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Attachments: 1a.gif, 1b.gif, generatedPlan.xml, new-jaxws-calculator-war-2.1-SNAPSHOT.war Currently 'Create Plan' portlet doesn't handle Web Service references in a web-app. Enhance the wizard to take care of web service references in web-app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3430) Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app
[ https://issues.apache.org/jira/browse/GERONIMO-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMO-3430. - Resolution: Fixed Fix Version/s: 2.1 Completed: At revision: 595692 in trunk. Enhance 'Create Plan' portlet to auto handle Web Service references in a web-app Key: GERONIMO-3430 URL: https://issues.apache.org/jira/browse/GERONIMO-3430 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Attachments: 1a.gif, 1b.gif, generatedPlan.xml, new-jaxws-calculator-war-2.1-SNAPSHOT.war Currently 'Create Plan' portlet doesn't handle Web Service references in a web-app. Enhance the wizard to take care of web service references in web-app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-2503) Webapp classloader prefers WEB-INF/lib over WEB-INF/classes
[ https://issues.apache.org/jira/browse/GERONIMO-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reopened GERONIMO-2503: --- Reopening as requested by Ashish. Webapp classloader prefers WEB-INF/lib over WEB-INF/classes --- Key: GERONIMO-2503 URL: https://issues.apache.org/jira/browse/GERONIMO-2503 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: web Affects Versions: 1.1, 1.1.1 Environment: windows and linux, jetty and tomcat Reporter: Nikla Ratinen Assignee: Rick McGuire Fix For: 1.1.2, 1.2 Attachments: patch.txt, test.war Application classloader looks in WAR's WEB-INF/lib before WEB-INF/classes. This is in violation of servlet 2.4 (and 2.3) specification, 9.5 Directory Structure, which states: TheWeb application class loader must load classes from the WEB-INF/ classes directory first, and then from library JARs in the WEB-INF/lib directory. This behaviour prevents web application from overriding classes and resources from included libraries. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3254) Admin Console Wizard to auto generate geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3254: -- Attachment: Consolidated Test WAR for Plan Creator.zip Please see the Readme.txt inside the zip file. Admin Console Wizard to auto generate geronimo-web.xml -- Key: GERONIMO-3254 URL: https://issues.apache.org/jira/browse/GERONIMO-3254 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console, deployment, usability Affects Versions: 2.0-M7 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Attachments: 1WelcomePage.gif, 2BasicSettings.gif, 3ResolveReferences.gif, 4AddDependencies.gif, 5DisplaysCreatedPlan.gif, 6DeployStatus.gif, 7SecurityHandling_1.gif, 7SecurityHandling_2.gif, 7SecurityHandling_3.gif, buildCreatePlanPortlet.bat, buildCreatePlanPortlet2.bat, consolidated 3254 3394 3395 3396 3397 3398.patch, Consolidated Test WAR for Plan Creator.zip, GERONIMO-3254.patch, PoC.patch, PoC_2(annotations).patch, SampleWebAppsWithAnnotations.zip, TestCreatePlanPortlet.zip, TestSecuritySettings.zip For a background about this work, please see the discussion thread: http://www.mail-archive.com/dev@geronimo.apache.org/msg46831.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3254) Admin Console Wizard to auto generate geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMO-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556858#action_12556858 ] shivahr edited comment on GERONIMO-3254 at 1/8/08 1:51 AM: --- Consolidated Test WAR for Plan Creator.zip : please see the Readme.txt inside the zip file. was (Author: shivahr): Please see the Readme.txt inside the zip file. Admin Console Wizard to auto generate geronimo-web.xml -- Key: GERONIMO-3254 URL: https://issues.apache.org/jira/browse/GERONIMO-3254 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console, deployment, usability Affects Versions: 2.0-M7 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1 Attachments: 1WelcomePage.gif, 2BasicSettings.gif, 3ResolveReferences.gif, 4AddDependencies.gif, 5DisplaysCreatedPlan.gif, 6DeployStatus.gif, 7SecurityHandling_1.gif, 7SecurityHandling_2.gif, 7SecurityHandling_3.gif, buildCreatePlanPortlet.bat, buildCreatePlanPortlet2.bat, consolidated 3254 3394 3395 3396 3397 3398.patch, Consolidated Test WAR for Plan Creator.zip, GERONIMO-3254.patch, PoC.patch, PoC_2(annotations).patch, SampleWebAppsWithAnnotations.zip, TestCreatePlanPortlet.zip, TestSecuritySettings.zip For a background about this work, please see the discussion thread: http://www.mail-archive.com/dev@geronimo.apache.org/msg46831.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3760) Geronimo Tomcat Clustering - Support for disabling multicasting and adding only static members
Geronimo Tomcat Clustering - Support for disabling multicasting and adding only static members -- Key: GERONIMO-3760 URL: https://issues.apache.org/jira/browse/GERONIMO-3760 Project: Geronimo Issue Type: Wish Security Level: public (Regular issues) Components: Clustering Reporter: Shiva Kumar H R Fix For: Wish List This is opened as a feature request on Tomcat bug tracker: http://issues.apache.org/bugzilla/show_bug.cgi?id=44264 Once it is supported in Tomcat, check to see if any configuration elements need to be added in Geronimo's config.xml to expose this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Clustering
Reporter: Shiva Kumar H R
Fix For: 2.1
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to extend
your membership to points beyond multicasting, using configuration as below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have the
required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-279) Figure out how to compile Geronimo schemas using JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568174#action_12568174 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-279: -- Followed instructions as per the following page: Using the JAXB XJC Maven 2 Plugin: https://jaxb.dev.java.net/jaxb-maven2-plugin/ Compilation is failing with below errors: [ERROR] [ERROR] Property Name is already defined. [ERROR] line 682 of file:/E:/IDEworkspaces/testJAXB/shivaTestJAXB/src/main/res ources/geronimo-module-1.2.xsd [ERROR] [ERROR] [ERROR] The following location is relevant to the above error [ERROR] line 661 of file:/E:/IDEworkspaces/testJAXB/shivaTestJAXB/src/main/res ources/geronimo-module-1.2.xsd [ERROR] [INFO] failure in the XJC task. Use the Ant -verbose switch for more details This seems to be a common issue JAXB2.0 users face when compiling a complex schema: https://jaxb.dev.java.net/guide/Dealing_with_errors.html http://weblogs.java.net/blog/kohsuke/archive/2006/03/simple_and_bett.html Now figuring out how to get past that error. Figure out how to compile Geronimo schemas using JAXB - Key: GERONIMODEVTOOLS-279 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-279) Figure out how to compile Geronimo schemas using JAXB
Figure out how to compile Geronimo schemas using JAXB - Key: GERONIMODEVTOOLS-279 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-278) Model framework for G deployment plans - Change from existing EMF to JAXB
Model framework for G deployment plans - Change from existing EMF to JAXB - Key: GERONIMODEVTOOLS-278 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Priority: Critical Fix For: 2.1.0 Please see the discussion on Geronimo dev-list: http://www.mail-archive.com/dev@geronimo.apache.org/msg56777.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMO-3843: - Assignee: Shiva Kumar H R Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3850) Plan Creator suppresses exceptions rather than showing it to user
Plan Creator suppresses exceptions rather than showing it to user
-
Key: GERONIMO-3850
URL: https://issues.apache.org/jira/browse/GERONIMO-3850
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: console
Affects Versions: 2.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.1
Various exceptions could be encountered during plan creation phase. Rather than
showing it to user via Admin Console page, plan creator is currently
suppressing them.
Location to be fixed:
org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
function of plancreator-portlets module.
try {
classFinder =
AbstractWebModuleBuilder.createWebAppClassFinder(webApp, classLoader);
} catch (DeploymentException e2) {
return;
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3851) Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib
Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib --- Key: GERONIMO-3851 URL: https://issues.apache.org/jira/browse/GERONIMO-3851 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.1 If a servlet class is packaged as a compressed JAR and put in WEB-INF/lib directory of a WAR, then plan creator will fail to recognize such class. Due to GERONIMO-3850, you may *not* notice any exceptions on console, rather Plan Creator would have simply failed to detect any references/security configurations required for the web-app. When you input such WARs to Plan Creator, you will see that after WAR - Environment page you will directly move to WAR - Dependencies page. i.e. *no* WAR-References or WAR-Security page will be shown even though the web-app requires certain references to be resolved or security roles to be defined. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3851) Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib
[ https://issues.apache.org/jira/browse/GERONIMO-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3851: -- Attachment: jaxws-calculator-war-2.1-SNAPSHOT.war Test web-app for the failing scenario. Try inputting this WAR to Plan Creator. Although this web-app requires references to be resolved, no WAR-References page will be shown. Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib --- Key: GERONIMO-3851 URL: https://issues.apache.org/jira/browse/GERONIMO-3851 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.1 Attachments: jaxws-calculator-war-2.1-SNAPSHOT.war If a servlet class is packaged as a compressed JAR and put in WEB-INF/lib directory of a WAR, then plan creator will fail to recognize such class. Due to GERONIMO-3850, you may *not* notice any exceptions on console, rather Plan Creator would have simply failed to detect any references/security configurations required for the web-app. When you input such WARs to Plan Creator, you will see that after WAR - Environment page you will directly move to WAR - Dependencies page. i.e. *no* WAR-References or WAR-Security page will be shown even though the web-app requires certain references to be resolved or security roles to be defined. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-283) Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id context root
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.1.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] Commented: (GERONIMODEVTOOLS-278) Model framework for G deployment plans - Change from existing EMF to JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569211#action_12569211 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-278: -- Please see IRC chat between dblevins shivahr http://servlet.uwyn.com/drone/log/bevinbot/geronimo/20080213 for hints from David Blevins on how to accomplish this. Model framework for G deployment plans - Change from existing EMF to JAXB - Key: GERONIMODEVTOOLS-278 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Priority: Critical Fix For: 2.1.0 Please see the discussion on Geronimo dev-list: http://www.mail-archive.com/dev@geronimo.apache.org/msg56777.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-279) Figure out how to compile Geronimo schemas using JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569270#action_12569270 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-279: -- Thanks YunFeng for the testcase. One observation: 1) When I extracted JAXBtest.zip to E:\xjc test (note space in folder name) and ran mvn compile, it failed throwing following errors: [INFO] Compiling file:/E:/xjc%20test/src/main/resources/geronimo-module-1.2.xsd [ERROR] [ERROR] file:/E:/xjc test/src/main/resources/geronimo-module-1.2.xsd i s not a part of this compilation. Is this a mistake for file:/E:/xjc test/src/m ain/resources/geronimo-module-1.2.xjb? [ERROR] line 5 of file:/E:/xjc%20test/src/main/resources/geronimo-module-1.2.x jb [ERROR] [ERROR] [ERROR] Property Name is already defined. [ERROR] line 682 of file:/E:/xjc%20test/src/main/resources/geronimo-module-1.2 .xsd [ERROR] [ERROR] [ERROR] The following location is relevant to the above error [ERROR] line 661 of file:/E:/xjc%20test/src/main/resources/geronimo-module-1.2 .xsd [ERROR] [INFO] failure in the XJC task. Use the Ant -verbose switch for more details 2) When I later renamed folder to xjc-test (note space is removed), and ran mvn compile, it was successful. So make sure there are no spaces in the path. Figure out how to compile Geronimo schemas using JAXB - Key: GERONIMODEVTOOLS-279 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 Attachments: geronimo-module-1.2.xjb, JAXBtest.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-279) Figure out how to compile Geronimo schemas using JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569272#action_12569272 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-279: -- When I copy other Geronimo xsd into src\main\resources directory and run mvn clean compile it fails again with below errors: [ERROR] [ERROR] file:/E:/xjc-test/src/main/resources/geronimo-module-1.2.xsd i s not a part of this compilation. Is this a mistake for file:/E:/xjc-test/src/m ain/resources/geronimo-module-1.2.xjb? [ERROR] line 5 of file:/E:/xjc-test/src/main/resources/geronimo-module-1.2.xjb Figure out how to compile Geronimo schemas using JAXB - Key: GERONIMODEVTOOLS-279 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 Attachments: geronimo-module-1.2.xjb, JAXBtest.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-279) Figure out how to compile Geronimo schemas using JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569787#action_12569787 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-279: -- The culprit throwing those errors turned out to be an older version (v1.0) of maven-jaxb-plugin. Please use maven-jaxb-plugin-1.1.jar from https://maven-repository.dev.java.net/repository/com.sun.tools.xjc.maven2/maven-plugins/ All schema in %Geronimo_HOME%\schema compile successfully now! Figure out how to compile Geronimo schemas using JAXB - Key: GERONIMODEVTOOLS-279 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-279 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 Attachments: geronimo-module-1.2.xjb, JAXBtest.zip, xjctest2.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-278) Model framework for G deployment plans - Change from existing EMF to JAXB
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577529#action_12577529 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-278: -- Committed (at revision: 636035 ) Yun Feng's patch (GEP-JAXB-3.patch) attached in sub-task GERONIMODEVTOOLS-285. Thanks Yun Feng for the patch. Model framework for G deployment plans - Change from existing EMF to JAXB - Key: GERONIMODEVTOOLS-278 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Priority: Critical Fix For: 2.1.0 Please see the discussion on Geronimo dev-list: http://www.mail-archive.com/dev@geronimo.apache.org/msg56777.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-294) Delete existing EMF plug-ins
Delete existing EMF plug-ins Key: GERONIMODEVTOOLS-294 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 After the initial port to JAXB, the following EMF plug-ins/modules are now redundant and need to be deleted. 1) \plugins\org.apache.geronimo.v11.deployment.model 2) \plugins\org.apache.geronimo.v11.deployment.model.edit 3) \emf -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-294) Delete existing EMF plug-ins
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577728#action_12577728 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-294: -- Completed: At revision: 636221 Delete existing EMF plug-ins Key: GERONIMODEVTOOLS-294 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 After the initial port to JAXB, the following EMF plug-ins/modules are now redundant and need to be deleted. 1) \plugins\org.apache.geronimo.v11.deployment.model 2) \plugins\org.apache.geronimo.v11.deployment.model.edit 3) \emf -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-294) Delete existing EMF plug-ins
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMODEVTOOLS-294. Resolution: Fixed Delete existing EMF plug-ins Key: GERONIMODEVTOOLS-294 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 After the initial port to JAXB, the following EMF plug-ins/modules are now redundant and need to be deleted. 1) \plugins\org.apache.geronimo.v11.deployment.model 2) \plugins\org.apache.geronimo.v11.deployment.model.edit 3) \emf -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-295) Delete redundant dependencies from runtime plug-ins - Make GEP thinner!
Delete redundant dependencies from runtime plug-ins - Make GEP thinner! --- Key: GERONIMODEVTOOLS-295 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 GEP is currently 13.3MB! Out of this ~11.6MB (87%) is from following four plug-ins! 1) \plugins\org.apache.geronimo.runtime.common 2) \plugins\org.apache.geronimo.runtime.v11 3) \plugins\org.apache.geronimo.runtime.v20 4) \plugins\org.apache.geronimo.runtime.v21 After GERONIMODEVTOOLS-294, many of the dependencies in above plug-ins might have become redundant. Identify the redundant ones and delete them to make GEP thinner :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-294) Delete existing EMF plug-ins
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578160#action_12578160 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-294: -- Oh! sorry didn't notice. Thanks for fixing. Delete existing EMF plug-ins Key: GERONIMODEVTOOLS-294 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 After the initial port to JAXB, the following EMF plug-ins/modules are now redundant and need to be deleted. 1) \plugins\org.apache.geronimo.v11.deployment.model 2) \plugins\org.apache.geronimo.v11.deployment.model.edit 3) \emf -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-296) Set svn properties on newly added files
Set svn properties on newly added files --- Key: GERONIMODEVTOOLS-296 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-296 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 See the guidelines: http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html Some of the newly added files under directories listed below don't have the required svn properties set. Set them manually to adhere to guidelines: \plugins\org.apache.geronimo.deployment.v11.jaxbmodel \plugins\org.apache.geronimo.deployment.v21.jaxbmodel \plugins\org.apache.geronimo.st.core\src\org\apache\geronimo\st\core\jaxb \plugins\org.apache.geronimo.st.ui\src\org\apache\geronimo\st\ui\providers \plugins\org.apache.geronimo.st.v21.core\src\org\apache\geronimo\st\v21\core\jaxb \plugins\org.apache.geronimo.st.v20.core\src\org\apache\geronimo\st\v20\core\jaxb -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-296) Set svn properties on newly added files
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMODEVTOOLS-296. Resolution: Fixed Completed: At revision: 636723 Set svn properties on newly added files --- Key: GERONIMODEVTOOLS-296 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-296 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 See the guidelines: http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html Some of the newly added files under directories listed below don't have the required svn properties set. Set them manually to adhere to guidelines: \plugins\org.apache.geronimo.deployment.v11.jaxbmodel \plugins\org.apache.geronimo.deployment.v21.jaxbmodel \plugins\org.apache.geronimo.st.core\src\org\apache\geronimo\st\core\jaxb \plugins\org.apache.geronimo.st.ui\src\org\apache\geronimo\st\ui\providers \plugins\org.apache.geronimo.st.v21.core\src\org\apache\geronimo\st\v21\core\jaxb \plugins\org.apache.geronimo.st.v20.core\src\org\apache\geronimo\st\v20\core\jaxb -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-312) Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB
Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using JAXB --- Key: GERONIMODEVTOOLS-312 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Tim McConnell Fix For: 2.1.0 The fixGeronimo*Schema() function inside GeronimRuntime classes is curently implemented using XMLBeans. As part of GERONIMODEVTOOLS-295, xmlbeans-2.3.0.jar has been removed from GEP's dependencies. Hence fixGeronimo*Schema() functionality needs to be reimplemented using JAXB. Classes to be changed: 1) org.apache.geronimo.st.core.IGeronimoRuntime 2) org.apache.geronimo.st.core.operations.ImportDeploymentPlanOperation 3) org.apache.geronimo.st.v11.core.GeronimoRuntime 4) org.apache.geronimo.st.v20.core.GeronimoRuntime 5) org.apache.geronimo.st.v21.core.GeronimoRuntime -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-295) Delete redundant dependencies from runtime plug-ins - Make GEP thinner!
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578584#action_12578584 ] Shiva Kumar H R commented on GERONIMODEVTOOLS-295: -- Some good news!! GEP has Shred Lot of Weight and is Just 5.4MB Now!! Earlier it was 12.6MB, so ~57% reduction in size. I have deleted following redundant JARs from various runtime plug-ins: 1) From \plugins\org.apache.geronimo.runtime.v11 a) geronimo-service-builder, b) geronimo-connector-builder, c) geronimo-web-builder, d) geronimo-naming-builder, e) geronimo-j2ee-builder, f) openejb-builder, g) geronimo-security-builder 2) From \plugins\org.apache.geronimo.runtime.v20 a) geronimo-service-builder, b) geronimo-connector-builder, c) geronimo-web-2.5-builder, d) geronimo-naming-builder, e) geronimo-j2ee-builder, f) geronimo-openejb-builder, g) geronimo-security-builder, h) geronimo-schema-jee_5 3) From \plugins\org.apache.geronimo.runtime.v21 a) geronimo-service-builder, b) geronimo-connector-builder, c) geronimo-web-2.5-builder, d) geronimo-naming-builder, e) geronimo-j2ee-builder, f) geronimo-openejb-builder, g) geronimo-security-builder, h) geronimo-schema-jee_5 Basically all *builder jars from 1), 2) 3), and 4) From \plugins\org.apache.geronimo.runtime.common a) xmlbeans-2.3.0.jar (~2.5MB) They were earlier required by EMF plug-ins (which were coded to pick various XSDs from those builder JARs), and with they getting deleted through GERONIMODEVTOOLS-294, above dependencies have become redundant and hence deleted. (New JAXB model plug-ins have the XSDs directly in source tree). The only other place where those builders JARs xmlbeans.jar were used before, was to implement various fixGeronimo*Schema() functions inside GeronimRuntime classes. These functions will be reimplemented using JAXB as part of GERONIMODEVTOOLS-312. The above listed JARs are deleted at revision: 636971 Delete redundant dependencies from runtime plug-ins - Make GEP thinner! --- Key: GERONIMODEVTOOLS-295 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 GEP is currently 13.3MB! Out of this ~11.6MB (87%) is from following four plug-ins! 1) \plugins\org.apache.geronimo.runtime.common 2) \plugins\org.apache.geronimo.runtime.v11 3) \plugins\org.apache.geronimo.runtime.v20 4) \plugins\org.apache.geronimo.runtime.v21 After GERONIMODEVTOOLS-294, many of the dependencies in above plug-ins might have become redundant. Identify the redundant ones and delete them to make GEP thinner :) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-294) Delete existing EMF plug-ins
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R closed GERONIMODEVTOOLS-294. Delete existing EMF plug-ins Key: GERONIMODEVTOOLS-294 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.1.0 After the initial port to JAXB, the following EMF plug-ins/modules are now redundant and need to be deleted. 1) \plugins\org.apache.geronimo.v11.deployment.model 2) \plugins\org.apache.geronimo.v11.deployment.model.edit 3) \emf -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-306) Plugin: org.apache.geronimo.st.ui
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-306: Assignee: Shiva Kumar H R Plugin: org.apache.geronimo.st.ui - Key: GERONIMODEVTOOLS-306 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-306 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Shiva Kumar H R -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-307) Plugin: org.apache.geronimo.st.v11.ui
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-307: Assignee: Shiva Kumar H R Plugin: org.apache.geronimo.st.v11.ui - Key: GERONIMODEVTOOLS-307 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-307 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Shiva Kumar H R -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-308) Plugin: org.apache.geronimo.st.v20.ui
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-308: Assignee: Shiva Kumar H R Plugin: org.apache.geronimo.st.v20.ui - Key: GERONIMODEVTOOLS-308 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-308 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Shiva Kumar H R -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-310) Plugin: org.apache.geronimo.deployment.v11.jaxbmodel
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-310: Assignee: YunFeng Ma Plugin: org.apache.geronimo.deployment.v11.jaxbmodel Key: GERONIMODEVTOOLS-310 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-310 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: YunFeng Ma -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-309) Plugin: org.apache.geronimo.st.v21.ui
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-309: Assignee: Shiva Kumar H R Plugin: org.apache.geronimo.st.v21.ui - Key: GERONIMODEVTOOLS-309 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-309 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Shiva Kumar H R -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-311) Plugin: org.apache.geronimo.deployment.v21.jaxbmodel
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-311: Assignee: YunFeng Ma Plugin: org.apache.geronimo.deployment.v21.jaxbmodel Key: GERONIMODEVTOOLS-311 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-311 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: YunFeng Ma -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3433) Admin Console Wizard to auto generate geronimo-application.xml
[ https://issues.apache.org/jira/browse/GERONIMO-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3433: -- Affects Version/s: (was: 2.1.1) 2.2 Fix Version/s: (was: 2.1.1) 2.2 Admin Console Wizard to auto generate geronimo-application.xml -- Key: GERONIMO-3433 URL: https://issues.apache.org/jira/browse/GERONIMO-3433 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console, deployment, usability Affects Versions: 2.2 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.2 For a background about this work please see GERONIMO-3254 GERONIMO-3432. Enhance Create Plan portlet other Admin Console Wizards to help server-administrators in auto creating the Geronimo Deployment Plan for a J2EE/Java-EE application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3432) Admin Console Wizard to auto generate openejb-jar.xml
[ https://issues.apache.org/jira/browse/GERONIMO-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3432: -- Affects Version/s: (was: 2.1) 2.2 Fix Version/s: (was: 2.1.1) 2.2 Admin Console Wizard to auto generate openejb-jar.xml - Key: GERONIMO-3432 URL: https://issues.apache.org/jira/browse/GERONIMO-3432 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: console, deployment, usability Affects Versions: 2.2 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.2 For a background about this work please see GERONIMO-3254. Currently the plan creation wizard only takes a web-app (.war) as an input and helps in auto-creating geronimo-web.xml. Enhance the wizard to take an EJB-JAR input and help in auto-creating openejb-jar.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R reassigned GERONIMO-3759:
-
Assignee: Shiva Kumar H R
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.1
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3843: -- Fix Version/s: 2.1.1 Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R Fix For: 2.1.1 The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579826#action_12579826 ] Shiva Kumar H R commented on GERONIMO-3843: --- Plan Creator is calling following piece of code: DeploymentFactory factory = new DeploymentFactoryWithKernel(PortletManager.getKernel()); DeploymentManager deploymentManager = factory.getDeploymentManager(deployer:geronimo:jmx, null, null); DeploymentConfiguration deploymentConfiguration = deploymentManager.createConfiguration(webDeployable); The last one - call to JMXDeploymentManager.createConfiguration() is resulting in following error: ERROR [DisplayPlanHandler] No configurer for module type: war registered javax.enterprise.deploy.spi.exceptions.InvalidModuleException: No configurer for module type: war registered at org.apache.geronimo.deployment.plugin.jmx.JMXDeploymentManager.createConfiguration(JMXDeploymentManager.java:311) at org.apache.geronimo.console.configcreator.JSR88_Util.createDeploymentPlan(JSR88_Util.java:300) This error happens only with Jetty and works correctly with Tomcat. Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R Fix For: 2.1.1 The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R resolved GERONIMO-3843. --- Resolution: Fixed Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R Fix For: 2.1.1 The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579955#action_12579955 ] Shiva Kumar H R commented on GERONIMO-3843: --- As hinted by David Jencks, this turned out to be a missing gbean for org.apache.geronimo.web.deployment.WARConfigurer in jetty6-deployer. Completed: At revision: 638475 Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R Fix For: 2.1.1 The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579987#action_12579987 ] Shiva Kumar H R commented on GERONIMO-3843: --- Oh! thanks for pointing out (I had wrongly assumed that 2.1.1 will be branched out of trunk). Will do this first thing tomorrow. Thanks, Shiva Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R Fix For: 2.1.1 The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3843) Plan creator fails to create plan and to deploy
[ https://issues.apache.org/jira/browse/GERONIMO-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580261#action_12580261 ] Shiva Kumar H R commented on GERONIMO-3843: --- Thanks Donald. Plan creator fails to create plan and to deploy --- Key: GERONIMO-3843 URL: https://issues.apache.org/jira/browse/GERONIMO-3843 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1, 2.1.1, 2.2 Environment: Geronimo 2.1 - Jetty distribution. Reporter: Hernan Cunico Assignee: Shiva Kumar H R Fix For: 2.1.1, 2.2 The plan creator fails to create the deployment plan and consequently to deploy the app in the Jetty distribution. This feature works OK in Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R updated GERONIMO-3759:
--
Attachment: ClusteringStaticMembers_GERONIMO-3759.patch
This is turning out to be a non-trivial task (already spent 4 complete days on
it! and still not complete).
Attached patch has work done so far - allows adding of static members. However
Session failover on static members still doesn't work. Don't know what's going
wrong.
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.1
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R updated GERONIMO-3759:
--
Attachment: config_ag21.xml
Attached config_ag21.xml shows configuration elements required for adding
static members. (Replace !-- hostname/ip of this machine -- and !--
hostname/ip of other machine in the cluster -- accordingly).
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.1
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581537#action_12581537
]
shivahr edited comment on GERONIMO-3759 at 3/24/08 7:01 AM:
Attached config_ag21.xml shows configuration elements required for adding
static members. (Replace hostname/ip of this machine and hostname/ip of
other machine in the cluster accordingly).
was (Author: shivahr):
Attached config_ag21.xml shows configuration elements required for adding
static members. (Replace !-- hostname/ip of this machine -- and !--
hostname/ip of other machine in the cluster -- accordingly).
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.1
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R updated GERONIMO-3759:
--
Attachment: tomcat_server.xml
tomcat_server.xml shows the configurations required in Tomcat for adding static
members into the Cluster.
With tomcat_server.xml it works perfectly in Tomcat, but with config_ag21.xml
it doesn't work in Geronimo! Is StaticMemberGBean the culprit?
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.1
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml, tomcat_server.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3759) Geronimo Tomcat Clustering - No GBeans for adding Static Members
[
https://issues.apache.org/jira/browse/GERONIMO-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R reassigned GERONIMO-3759:
-
Assignee: (was: Shiva Kumar H R)
Geronimo Tomcat Clustering - No GBeans for adding Static Members
Key: GERONIMO-3759
URL: https://issues.apache.org/jira/browse/GERONIMO-3759
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Clustering
Affects Versions: 2.1, 2.1.1
Reporter: Shiva Kumar H R
Fix For: 2.1.1
Attachments: ClusteringStaticMembers_GERONIMO-3759.patch,
config_ag21.xml, tomcat_server.xml
Tomcat uses multicasting for discovering cluster members. It also supports
static memberships using the StaticMembershipInterceptor if you want to
extend your membership to points beyond multicasting, using configuration as
below:
Interceptor
className=org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor
Member className=org.apache.catalina.tribes.membership.StaticMember
port=5678
securePort=-1
host=tomcat01.mydomain.com
domain=staging-cluster
uniqueId={0,1,2,3,4,5,6,7,8,9}/
/Interceptor
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-interceptor.html
However, to add this configuration in Geronimo's config.xml, we don't have
the required GBeans for Member element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3850) Plan Creator suppresses exceptions rather than showing it to user
[
https://issues.apache.org/jira/browse/GERONIMO-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R closed GERONIMO-3850.
-
Resolution: Fixed
Fix Version/s: 2.2
Completed: At revision: 640445 in branches/2.1, and At revision: 640446 in
trunk.
Plan Creator suppresses exceptions rather than showing it to user
-
Key: GERONIMO-3850
URL: https://issues.apache.org/jira/browse/GERONIMO-3850
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: console
Affects Versions: 2.1
Reporter: Shiva Kumar H R
Assignee: Shiva Kumar H R
Fix For: 2.1.1, 2.2
Various exceptions could be encountered during plan creation phase. Rather
than showing it to user via Admin Console page, plan creator is currently
suppressing them.
Location to be fixed:
org.apache.geronimo.console.configcreator.JSR88_Util.parseWarReferences()
function of plancreator-portlets module.
try {
classFinder =
AbstractWebModuleBuilder.createWebAppClassFinder(webApp, classLoader);
} catch (DeploymentException e2) {
return;
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (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 ] Shiva Kumar H R reassigned GERONIMODEVTOOLS-283: Assignee: Shiva Kumar H R 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 Assignee: Shiva Kumar H R Priority: Minor Fix For: 2.1.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: (GERONIMO-3851) Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib
[ https://issues.apache.org/jira/browse/GERONIMO-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R updated GERONIMO-3851: -- Fix Version/s: (was: 2.1.1) 2.2 Plan Creator cannot recognize classes inside compressed JARs of WEB-INF/lib --- Key: GERONIMO-3851 URL: https://issues.apache.org/jira/browse/GERONIMO-3851 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1 Reporter: Shiva Kumar H R Assignee: Shiva Kumar H R Fix For: 2.2 Attachments: jaxws-calculator-war-2.1-SNAPSHOT.war If a servlet class is packaged as a compressed JAR and put in WEB-INF/lib directory of a WAR, then plan creator will fail to recognize such class. Due to GERONIMO-3850, you may *not* notice any exceptions on console, rather Plan Creator would have simply failed to detect any references/security configurations required for the web-app. When you input such WARs to Plan Creator, you will see that after WAR - Environment page you will directly move to WAR - Dependencies page. i.e. *no* WAR-References or WAR-Security page will be shown even though the web-app requires certain references to be resolved or security roles to be defined. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
