You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jürgen Weber (JIRA)" <ji...@apache.org> on 2009/07/22 09:57:15 UTC
[jira] Created: (GERONIMO-4759) Remove repository entries via
Console
Remove repository entries via Console
-------------------------------------
Key: GERONIMO-4759
URL: https://issues.apache.org/jira/browse/GERONIMO-4759
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: console
Reporter: Jürgen Weber
Fix For: 2.2
The Repository Viewer portlet should offer to remove entries that were formerly added by the user (that are not part of the server configuration itself).
If you can add repository entries via the console it would be consistent to remove them via the console, too.
On the details view for an entry there should be e.g.
"remove mysql/mysql-connector-java/3.1.14/jar"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (GERONIMO-4759) Remove repository entries via
Console
Posted by chi runhua <ch...@gmail.com>.
Verified on Revision: 830905 build and the feature works fine now.
Remove feature was recorded in Doc at [1].
[1]
http://cwiki.apache.org/GMOxDOC22/introducing-geronimo-administration-console.html#IntroducingGeronimoAdministrationConsole-Repository
Jeff C
>
> On Thu, Oct 29, 2009 at 6:01 AM, David Jencks (JIRA) <ji...@apache.org>wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>
>> David Jencks closed GERONIMO-4759.
>> ----------------------------------
>>
>> Resolution: Fixed
>>
>> Applied modified version of patch in rev 830774.
>>
>> There are several problems:
>> 1. remove funcationalty should be unavailable unless you enable advanced
>> actions.
>> 2. we should look for uses of the artifact and at least warn if there are
>> any.
>>
>> I think the functionaly is sufficiently useful to add anyway.
>>
>> > Remove repository entries via Console
>> > -------------------------------------
>> >
>> > Key: GERONIMO-4759
>> > URL:
>> https://issues.apache.org/jira/browse/GERONIMO-4759
>> > Project: Geronimo
>> > Issue Type: Improvement
>> > Security Level: public(Regular issues)
>> > Components: console
>> > Reporter: Jürgen Weber
>> > Assignee: David Jencks
>> > Fix For: 2.2
>> >
>> > Attachments: GERONIMO-4759 advanced.patch, GERONIMO-4759
>> advanced.PNG
>> >
>> >
>> > The Repository Viewer portlet should offer to remove entries that were
>> formerly added by the user (that are not part of the server configuration
>> itself).
>> > If you can add repository entries via the console it would be consistent
>> to remove them via the console, too.
>> > On the details view for an entry there should be e.g.
>> > "remove mysql/mysql-connector-java/3.1.14/jar"
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
Re: [jira] Closed: (GERONIMO-4759) Remove repository entries via
Console
Posted by chi runhua <ch...@gmail.com>.
Exception occured when starting a new server with this patch checked-in.
Error log as followed:
2009-10-29 10:07:47,438 ERROR [ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'RequiredContainerServices' defined in ServletContext resource
[/WEB-INF/pluto-portal-driver-services-config.xml]: Cannot resolve reference
to bean 'PortalContext' while setting constructor argument; nested exception
is org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'PortalContext' defined in ServletContext resource
[/WEB-INF/pluto-portal-driver-services-config.xml]: Cannot resolve reference
to bean 'DriverConfiguration' while setting constructor argument; nested
exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'DriverConfiguration' defined in ServletContext
resource [/WEB-INF/pluto-portal-driver-services-config.xml]: Cannot resolve
reference to bean 'PortalURLParser' while setting constructor argument;
nested exception is
org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find
class [org.apache.geronimo.pluto.impl.PortalURLParserImpl] for bean with
name 'PortalURLParser' defined in ServletContext resource
[/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is
java.lang.ClassNotFoundException:
org.apache.geronimo.pluto.impl.PortalURLParserImpl in classloader
org.apache.geronimo.plugins/console-tomcat_portal-driver.war/2.2-SNAPSHOT/car
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
at
org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:495)
at
org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:162)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at
java.security.AccessController.doPrivileged(AccessController.java:224)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3930)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4419)
at
org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:64)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:412)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
at
org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:264)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at
org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:339)
at
org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:525)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:524)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:232)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:493)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d73c640.startConfiguration(<generated>)
at
org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161)
at
org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
at
org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
On Thu, Oct 29, 2009 at 6:01 AM, David Jencks (JIRA) <ji...@apache.org>wrote:
>
> [
> https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> David Jencks closed GERONIMO-4759.
> ----------------------------------
>
> Resolution: Fixed
>
> Applied modified version of patch in rev 830774.
>
> There are several problems:
> 1. remove funcationalty should be unavailable unless you enable advanced
> actions.
> 2. we should look for uses of the artifact and at least warn if there are
> any.
>
> I think the functionaly is sufficiently useful to add anyway.
>
> > Remove repository entries via Console
> > -------------------------------------
> >
> > Key: GERONIMO-4759
> > URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> > Project: Geronimo
> > Issue Type: Improvement
> > Security Level: public(Regular issues)
> > Components: console
> > Reporter: Jürgen Weber
> > Assignee: David Jencks
> > Fix For: 2.2
> >
> > Attachments: GERONIMO-4759 advanced.patch, GERONIMO-4759
> advanced.PNG
> >
> >
> > The Repository Viewer portlet should offer to remove entries that were
> formerly added by the user (that are not part of the server configuration
> itself).
> > If you can add repository entries via the console it would be consistent
> to remove them via the console, too.
> > On the details view for an entry there should be e.g.
> > "remove mysql/mysql-connector-java/3.1.14/jar"
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Closed: (GERONIMO-4759) Remove repository entries via
Console
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-4759.
----------------------------------
Resolution: Fixed
Applied modified version of patch in rev 830774.
There are several problems:
1. remove funcationalty should be unavailable unless you enable advanced actions.
2. we should look for uses of the artifact and at least warn if there are any.
I think the functionaly is sufficiently useful to add anyway.
> Remove repository entries via Console
> -------------------------------------
>
> Key: GERONIMO-4759
> URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Reporter: Jürgen Weber
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: GERONIMO-4759 advanced.patch, GERONIMO-4759 advanced.PNG
>
>
> The Repository Viewer portlet should offer to remove entries that were formerly added by the user (that are not part of the server configuration itself).
> If you can add repository entries via the console it would be consistent to remove them via the console, too.
> On the details view for an entry there should be e.g.
> "remove mysql/mysql-connector-java/3.1.14/jar"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4759) Remove repository entries via
Console
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734187#action_12734187 ]
David Jencks commented on GERONIMO-4759:
----------------------------------------
I think that "remove" functionality is a moderately good idea but
-- there's really no way to distinguish between "server" and "non-server" jars since you can assemble a server out of any plugins you want
-- any such action should show all the dependencies that would be affected so you can see the consequences
> Remove repository entries via Console
> -------------------------------------
>
> Key: GERONIMO-4759
> URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Reporter: Jürgen Weber
> Fix For: 2.2
>
>
> The Repository Viewer portlet should offer to remove entries that were formerly added by the user (that are not part of the server configuration itself).
> If you can add repository entries via the console it would be consistent to remove them via the console, too.
> On the details view for an entry there should be e.g.
> "remove mysql/mysql-connector-java/3.1.14/jar"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4759) Remove repository entries via
Console
Posted by "Jürgen Weber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734320#action_12734320 ]
Jürgen Weber commented on GERONIMO-4759:
----------------------------------------
A "non-server" jar is a jar that was added after the creation/installation of the server.
> Remove repository entries via Console
> -------------------------------------
>
> Key: GERONIMO-4759
> URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Reporter: Jürgen Weber
> Fix For: 2.2
>
>
> The Repository Viewer portlet should offer to remove entries that were formerly added by the user (that are not part of the server configuration itself).
> If you can add repository entries via the console it would be consistent to remove them via the console, too.
> On the details view for an entry there should be e.g.
> "remove mysql/mysql-connector-java/3.1.14/jar"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4759) Remove repository entries via
Console
Posted by "Victor Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Victor Fang updated GERONIMO-4759:
----------------------------------
Attachment: GERONIMO-4759 advanced.PNG
GERONIMO-4759 advanced.patch
> Remove repository entries via Console
> -------------------------------------
>
> Key: GERONIMO-4759
> URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Reporter: Jürgen Weber
> Fix For: 2.2
>
> Attachments: GERONIMO-4759 advanced.patch, GERONIMO-4759 advanced.PNG
>
>
> The Repository Viewer portlet should offer to remove entries that were formerly added by the user (that are not part of the server configuration itself).
> If you can add repository entries via the console it would be consistent to remove them via the console, too.
> On the details view for an entry there should be e.g.
> "remove mysql/mysql-connector-java/3.1.14/jar"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4759) Remove repository entries via
Console
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-4759:
--------------------------------------
Assignee: David Jencks
> Remove repository entries via Console
> -------------------------------------
>
> Key: GERONIMO-4759
> URL: https://issues.apache.org/jira/browse/GERONIMO-4759
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Reporter: Jürgen Weber
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: GERONIMO-4759 advanced.patch, GERONIMO-4759 advanced.PNG
>
>
> The Repository Viewer portlet should offer to remove entries that were formerly added by the user (that are not part of the server configuration itself).
> If you can add repository entries via the console it would be consistent to remove them via the console, too.
> On the details view for an entry there should be e.g.
> "remove mysql/mysql-connector-java/3.1.14/jar"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.