[jira] [Updated] (GERONIMO-5729) Access the wrong web console page should get appropriate error message
[ https://issues.apache.org/jira/browse/GERONIMO-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shenghao Fang updated GERONIMO-5729: Attachment: GERONIMO-5729-updated.patch An updated patch for bug fixes. > Access the wrong web console page should get appropriate error message > -- > > Key: GERONIMO-5729 > URL: https://issues.apache.org/jira/browse/GERONIMO-5729 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2.2, 3.0-M2, 3.0 >Reporter: Shawn Jiang >Assignee: Shenghao Fang > Attachments: GERONIMO-5729-updated.patch, GERONIMO-5729.patch > > > I have also found the reason why I sometimes did not see the menu at the left > hand: > When you log in to "/console/portal/welcome" (which was the default location > in previeous versions) then you do _not_ see the menu. > When you log in to "/console/" the you'll be forwarded to > "/console/portal/0/Welcome, and you see everything correctly. > It seems, that the content I've seen is the default page that will be > displayed for users when they've called illegal page names. It also shows up > for /console/portal/Testpage . Unfortunately the message displayed says > "Welcome to the Apache Geronimo™ Administration Console!" etc. instead of a > error message... > As I think it's not critical enough to delay release, I gave +1. > Thank you all for all the development works! > Johannes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5878) NoClassDefFoundError: org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory while running web service
[ https://issues.apache.org/jira/browse/GERONIMO-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050877#comment-13050877 ] viola.lu commented on GERONIMO-5878: Currently, as workaround, Add import package org.apache.axiom.soap.impl.dom.factory to aixs2-saaj and org.apache.axiom.om.impl.llom.factory to axis2 to make geronimo webservices pass on IBM JDK commit @ 113657 > NoClassDefFoundError: > org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory while running > web service > - > > Key: GERONIMO-5878 > URL: https://issues.apache.org/jira/browse/GERONIMO-5878 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 3.0 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0 > > > The interesting thing is that this exception is only thrown while running on > IBM JDK 6.0, and it works well with Sun's. > ---> > 03-21-2011 19:40:01: ERROR: java.lang.NoClassDefFoundError: > org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory > at java.lang.J9VMInternals.verifyImpl(Native Method) > at java.lang.J9VMInternals.verify(J9VMInternals.java:72) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:134) > at > org.apache.axis2.jaxws.message.impl.XMLPartBase._createSpine(XMLPartBase.java:755) > at > org.apache.axis2.jaxws.message.impl.XMLPartBase.(XMLPartBase.java:129) > at > org.apache.axis2.jaxws.message.impl.XMLPartImpl.(XMLPartImpl.java:53) > at > org.apache.axis2.jaxws.message.impl.XMLPartFactoryImpl.create(XMLPartFactoryImpl.java:64) > at > org.apache.axis2.jaxws.message.impl.MessageImpl.createXMLPart(MessageImpl.java:169) > at > org.apache.axis2.jaxws.message.impl.MessageImpl.(MessageImpl.java:105) > at > org.apache.axis2.jaxws.message.impl.MessageFactoryImpl.create(MessageFactoryImpl.java:85) > at > org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMarshaller.marshalRequest(DocLitWrappedMethodMarshaller.java:530) > at > org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createRequest(JAXWSProxyHandler.java:482) > at > org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:200) > at > org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:171) > at $Proxy40.addNumbers3(Unknown Source) > .. > Caused by: java.lang.ClassNotFoundException: > org.apache.axiom.om.impl.llom.factory.OMLinkedListImplFactory > at > java.lang.ClassNotFoundException.(ClassNotFoundException.java:77) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:430) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410) > at > org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:103) > at java.lang.ClassLoader.loadClass(ClassLoader.java:619) > ... 50 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] branches/2.2: Failed for Revision: 1136737
Geronimo Revision: 1136737 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110616/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110616/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) javax.servlet:jstl:jar:1.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT 2) javax.servlet:jstl:jar:1.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) javax.servlet:jstl:jar:1.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT 2) javax.servlet:jstl:jar:1.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo2.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
Re: Server build failed caused by uddi-ws dependency
that was me :-) there's a problem I don't know how to resolve that they want different profiles to create the same artifact with different classifiers. This doesn't work well with snapshot management. david jencks On Jun 16, 2011, at 2:59 PM, Russell E Glaue wrote: > Kevan, > You are not going to believe this. > > The juddi team just released a uddi-ws 3.1.0 #16 snapshot artifact. > https://repository.apache.org/content/groups/snapshots/org/apache/juddi/uddi-ws/3.1.0-SNAPSHOT/ > > -RG > > > > On 06/16/2011 03:48 PM, Kevan Miller wrote: >> >> A build should find uddi-ws, now. Help me to remember to revert these >> changes, when there's a juddi release... >> >> 1136657 and 1136664 >> >> --kevan >>
Re: Server build failed caused by uddi-ws dependency
Kevan, You are not going to believe this. The juddi team just released a uddi-ws 3.1.0 #16 snapshot artifact. https://repository.apache.org/content/groups/snapshots/org/apache/juddi/uddi-ws/3.1.0-SNAPSHOT/ -RG On 06/16/2011 03:48 PM, Kevan Miller wrote: > > A build should find uddi-ws, now. Help me to remember to revert these > changes, when there's a juddi release... > > 1136657 and 1136664 > > --kevan >
Re: Server build failed caused by uddi-ws dependency
A build should find uddi-ws, now. Help me to remember to revert these changes, when there's a juddi release... 1136657 and 1136664 --kevan
[jira] [Commented] (GERONIMO-5966) Geronimo start failure: Error while starting; GBean is now in the FAILED state: abstractName="org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car
[ https://issues.apache.org/jira/browse/GERONIMO-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050699#comment-13050699 ] Kevan Miller commented on GERONIMO-5966: I don't understand completely. But this problem is caused because 'geronimo start' configures the following parameter setting: -Dkaraf.startLocalConsole=false and geronimo run sets: -Dkaraf.startLocalConsole=true A simple change to geronimo.bat (and always setting -Dkaraf.startLocalConsole=true) will avoid the problem. I assume we'll figure out why startLocalConsole=true is needed. > Geronimo start failure: Error while starting; GBean is now in the FAILED > state: > abstractName="org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car > -- > > Key: GERONIMO-5966 > URL: https://issues.apache.org/jira/browse/GERONIMO-5966 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: JVM-compatibility >Affects Versions: 3.0 > Environment: Windows XP SP3 x86 > IBM jdk IBMJava60 SR9-FP1 > Geronimo build on 20110519 >Reporter: Jacky Liu > > 1. cd %Geronimo Home%\bin > 2. input command: geronimo start or startup > ERROR OCCURS! > 2011-05-19 11:19:13,955 ERROR [GBeanInstanceState] Error while starting; > GBean is now in the FAILED state: > abstractName="org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car,j2eeType=GBean,name=SecurityContextHandler" > java.lang.ExceptionInInitializerError > at java.lang.J9VMInternals.initialize(J9VMInternals.java:222) > at > org.apache.geronimo.connector.wrapper.work.SecurityContextHandler.(SecurityContextHandler.java:71) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:527) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:933) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:560) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:460) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:226) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:702) > at > org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:211) > at > org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:91) > at > org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.java:107) > at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65) > at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32) > Caused by: java.lang.SecurityException: > at javax.security.auth.Policy.getPolicyNoCheck(Policy.java:268) > at javax.security.auth.Policy.getPolicy(Policy.java:219) > at > javax.security.auth.SubjectDomainCombiner$5.run(SubjectDomainCombiner.java:513) > at > java.security.AccessController.doPrivileged(AccessController.java:202) > at > javax.security.auth.SubjectDomainCombiner.compatPolicy(SubjectDomainCombiner.java:509) > at > javax.security.auth.SubjectDomainCombiner.combine(SubjectDomainCombiner.java:223) > at java.security.AccessController.getContext(AccessController.java:141) > at > org.apache.geronimo.security.ContextManager$3.run(ContextManager.java:
[BUILD] branches/2.2: Failed for Revision: 1136549
Geronimo Revision: 1136549 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110616/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110616/unit-test-reports -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) javax.servlet:jstl:jar:1.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT 2) javax.servlet:jstl:jar:1.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:592) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) javax.servlet:jstl:jar:1.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.servlet -DartifactId=jstl -Dversion=1.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT 2) javax.servlet:jstl:jar:1.2 -- 1 required artifact is missing. for artifact: org.apache.geronimo.framework:jee-specs:car:2.2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo2.maven.org/maven2), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
[jira] [Updated] (GERONIMO-5966) Geronimo start failure: Error while starting; GBean is now in the FAILED state: abstractName="org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car
[ https://issues.apache.org/jira/browse/GERONIMO-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5966: -- Priority: Major (was: Minor) This is a blocking issue when using IBM JDK to run geronimo server, pls help fix it asap. thanks! > Geronimo start failure: Error while starting; GBean is now in the FAILED > state: > abstractName="org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car > -- > > Key: GERONIMO-5966 > URL: https://issues.apache.org/jira/browse/GERONIMO-5966 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: JVM-compatibility >Affects Versions: 3.0 > Environment: Windows XP SP3 x86 > IBM jdk IBMJava60 SR9-FP1 > Geronimo build on 20110519 >Reporter: Jacky Liu > > 1. cd %Geronimo Home%\bin > 2. input command: geronimo start or startup > ERROR OCCURS! > 2011-05-19 11:19:13,955 ERROR [GBeanInstanceState] Error while starting; > GBean is now in the FAILED state: > abstractName="org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/transaction-1_6/3.0-SNAPSHOT/car,j2eeType=GBean,name=SecurityContextHandler" > java.lang.ExceptionInInitializerError > at java.lang.J9VMInternals.initialize(J9VMInternals.java:222) > at > org.apache.geronimo.connector.wrapper.work.SecurityContextHandler.(SecurityContextHandler.java:71) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) > at java.lang.reflect.Constructor.newInstance(Constructor.java:527) > at > org.apache.xbean.recipe.ReflectionUtil$ConstructorFactory.create(ReflectionUtil.java:958) > at > org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:276) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) > at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:933) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:271) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:105) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:560) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:386) > at > org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:460) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:226) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:702) > at > org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:211) > at > org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:91) > at > org.apache.geronimo.system.osgi.BootActivator$1.execute(BootActivator.java:107) > at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65) > at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65) > at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32) > Caused by: java.lang.SecurityException: > at javax.security.auth.Policy.getPolicyNoCheck(Policy.java:268) > at javax.security.auth.Policy.getPolicy(Policy.java:219) > at > javax.security.auth.SubjectDomainCombiner$5.run(SubjectDomainCombiner.java:513) > at > java.security.AccessController.doPrivileged(AccessController.java:202) > at > javax.security.auth.SubjectDomainCombiner.compatPolicy(SubjectDomainCombiner.java:509) > at > javax.security.auth.SubjectDomainCombiner.combine(SubjectDomainCombiner.java:223) > at java.security.AccessController.getContext(AccessController.java:141) > at > org.apache.geronimo.security.ContextManager$3.run(ContextManager.java:274) > at > java.security.AccessController.doPrivileged(AccessController.java:224) > at javax.security.auth.Subject.doAsPrivileged(Subject.java:645) > at > org.apache.geronimo.security.ContextManager.registerSubject(ContextManager.java:272) > at > org.apache.geronimo.security.ContextManager
Re: Server build failed caused by uddi-ws dependency
On 06/16/2011 09:58 AM, Kevan Miller wrote: > > On Jun 16, 2011, at 10:12 AM, Russell E Glaue wrote: > >> On 06/13/2011 01:24 PM, Kevan Miller wrote: >>> >>> On Jun 13, 2011, at 2:15 PM, Forrest Xia wrote: >>> Simply waiting for uddi guys to push 3.1.0-snapshot out to apache snapshot repo seems not work, cause juddi guys pushed one 3.1.0-snapshot there already, just they add a classifier "jaxws21" into the artifact jar file name. You can see https://repository.apache.org/content/repositories/snapshots/org/apache/juddi/uddi-ws/3.1.0-SNAPSHOT/ So we may need to find other options to make our server build work: 1. Check out juddi code and build it before server build 2. Publish some juddi artifacts into http://svn.apache.org/repos/asf/geronimo/repo/, and make dependecies point to the self-defined version. 3. Continue asking and waiting for juddi guys to push out a normal uddi-ws artifacts to apache snapshot repo What's your thoughts? >>> >>> 4. Temporarily move back to JUDDI 3.0.5? I'm not sure of all of the >>> implications. But assume we could live with any temporary UDDI >>> regressions... >>> >>> --kevan >> >> Was there a decision made on this? >> Can we build a 3.1.0-SNAPSHOT, put it into a local repository (or your option >> #2), and essentially use a "frozen" snapshot until the juddi team starts >> pushing >> normal uddi-ws artifacts again? >> >> We can rebuild the snapshot if anything significant develops. > > FYI -- > http://mail-archives.apache.org/mod_mbox/juddi-dev/201106.mbox/%3c4df761d0.4040...@gmail.com%3e > > I have no idea why somebody in the JUDDI project didn't push a SNAPSHOT to > help enable other projects, in the meantime. > > I'd do #2, if I could build 3.1.0-SNAPSHOT, which I can't... Is anybody able > to build juddi trunk? > > --kevan > The juddi team is probably not releasing snapshots because they can't build it from the HEAD revision either. I would say to check out the uddi-ws trunk source code at the revision from 20110606.144803 and build that. Otherwise, I have the #13 snapshot (#14 was the last) from the juddi team which I was last able to successfully build G3.0 with - and I can send you that. uddi-ws/3.1.0-SNAPSHOT/uddi-ws-3.1.0-20110606.144803-13.jar uddi-ws/3.1.0-SNAPSHOT/uddi-ws-3.1.0-20110606.144803-13.jar.sha1 uddi-ws/3.1.0-SNAPSHOT/uddi-ws-3.1.0-20110606.144803-13.pom uddi-ws/3.1.0-SNAPSHOT/uddi-ws-3.1.0-20110606.144803-13.pom.lastUpdated uddi-ws/3.1.0-SNAPSHOT/uddi-ws-3.1.0-20110606.144803-13.pom.sha1 -RG
Re: Server build failed caused by uddi-ws dependency
On Jun 16, 2011, at 10:12 AM, Russell E Glaue wrote: > On 06/13/2011 01:24 PM, Kevan Miller wrote: >> >> On Jun 13, 2011, at 2:15 PM, Forrest Xia wrote: >> >>> Simply waiting for uddi guys to push 3.1.0-snapshot out to apache snapshot >>> repo seems not work, cause juddi guys pushed one 3.1.0-snapshot there >>> already, just they add a classifier "jaxws21" into the artifact jar file >>> name. >>> >>> You can see >>> https://repository.apache.org/content/repositories/snapshots/org/apache/juddi/uddi-ws/3.1.0-SNAPSHOT/ >>> >>> So we may need to find other options to make our server build work: >>> 1. Check out juddi code and build it before server build >>> 2. Publish some juddi artifacts into >>> http://svn.apache.org/repos/asf/geronimo/repo/, and make dependecies point >>> to the self-defined version. >>> 3. Continue asking and waiting for juddi guys to push out a normal uddi-ws >>> artifacts to apache snapshot repo >>> >>> What's your thoughts? >> >> 4. Temporarily move back to JUDDI 3.0.5? I'm not sure of all of the >> implications. But assume we could live with any temporary UDDI regressions... >> >> --kevan > > Was there a decision made on this? > Can we build a 3.1.0-SNAPSHOT, put it into a local repository (or your option > #2), and essentially use a "frozen" snapshot until the juddi team starts > pushing > normal uddi-ws artifacts again? > > We can rebuild the snapshot if anything significant develops. FYI -- http://mail-archives.apache.org/mod_mbox/juddi-dev/201106.mbox/%3c4df761d0.4040...@gmail.com%3e I have no idea why somebody in the JUDDI project didn't push a SNAPSHOT to help enable other projects, in the meantime. I'd do #2, if I could build 3.1.0-SNAPSHOT, which I can't... Is anybody able to build juddi trunk? --kevan
Re: Server build failed caused by uddi-ws dependency
On 06/13/2011 01:24 PM, Kevan Miller wrote: > > On Jun 13, 2011, at 2:15 PM, Forrest Xia wrote: > >> Simply waiting for uddi guys to push 3.1.0-snapshot out to apache snapshot >> repo seems not work, cause juddi guys pushed one 3.1.0-snapshot there >> already, just they add a classifier "jaxws21" into the artifact jar file >> name. >> >> You can see >> https://repository.apache.org/content/repositories/snapshots/org/apache/juddi/uddi-ws/3.1.0-SNAPSHOT/ >> >> So we may need to find other options to make our server build work: >> 1. Check out juddi code and build it before server build >> 2. Publish some juddi artifacts into >> http://svn.apache.org/repos/asf/geronimo/repo/, and make dependecies point >> to the self-defined version. >> 3. Continue asking and waiting for juddi guys to push out a normal uddi-ws >> artifacts to apache snapshot repo >> >> What's your thoughts? > > 4. Temporarily move back to JUDDI 3.0.5? I'm not sure of all of the > implications. But assume we could live with any temporary UDDI regressions... > > --kevan Was there a decision made on this? Can we build a 3.1.0-SNAPSHOT, put it into a local repository (or your option #2), and essentially use a "frozen" snapshot until the juddi team starts pushing normal uddi-ws artifacts again? We can rebuild the snapshot if anything significant develops. -RG
[BUILD] trunk: Failed for Revision: 1136424
Geronimo Revision: 1136424 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110616/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20110616/unit-test-reports at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.maven:maven-project:jar': Cannot find parent: org.apache.maven:maven-parent for project: null:maven:pom:2.0.8 for project null:maven:pom:2.0.8 org.apache.maven:maven-project:jar:2.0.8 from the specified remote repositories: geronimo-svn-repo (http://svn.apache.org/repos/asf/geronimo/repo/), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), jetty.oss.sonatype.org (http://oss.sonatype.org/content/groups/jetty-with-staging), java.net2 (http://download.java.net/maven/2/), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), central (http://repo1.maven.org/maven2), local (file:///home/geronimo/.m2/jtidy.repository), openqa-releases (http://nexus.openqa.org/content/repositories/releases) Path to dependency: 1) org.apache.felix:maven-bundle-plugin:maven-plugin:2.0.1 2) org.apache.maven.shared:maven-dependency-tree:jar:1.2 at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:430) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:316) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:835) at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1629) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582) ... 15 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.maven:maven-project:jar': Cannot find parent: org.apache.maven:maven-parent for project: null:maven:pom:2.0.8 for project null:maven:pom:2.0.8 at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:94) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:387) ... 22 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.maven:maven-parent for project: null:maven:pom:2.0.8 for project null:maven:pom:2.0.8 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1407) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:255) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163) ... 24 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.maven:maven-parent' not found in repository: Unable to download the artifact from any repository org.apache.maven:maven-parent:pom:6 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshot
[BUILD] branches/2.2: Failed for Revision: 1136379
Geronimo Revision: 1136379 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110616/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110616/unit-test-reports at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:592) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:592) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure Failure executing javac, but could not parse the error: An exception has occurred in the compiler (1.5.0_22). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. java.lang.InternalError: jzentry == 0, jzfile = 13790, total = 9508, name = /home/geronimo/.m2/repository/org/seleniumhq/selenium/server/selenium-server/1.0.3/selenium-server-1.0.3-standalone.jar, i = 2350, message = invalid LOC header (bad signature) at java.util.zip.ZipFile$3.nextElement(ZipFile.java:429) at java.util.zip.ZipFile$3.nextElement(ZipFile.java:415) at com.sun.tools.javac.jvm.ClassReader.openArchive(ClassReader.java:1447) at com.sun.tools.javac.jvm.ClassReader.list(ClassReader.java:1742) at com.sun.tools.javac.jvm.ClassReader.listAll(ClassReader.java:1882) at com.sun.tools.javac.jvm.ClassReader.fillIn(ClassReader.java:1903) at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1538) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) at com.sun.tools.javac.comp.Enter.visitTopLevel(Enter.java:256) at com.sun.tools.javac.tree.Tree$TopLevel.accept(Tree.java:382) at com.sun.tools.javac.comp.Enter.classEnter(Enter.java:221) at com.sun.tools.javac.comp.Enter.classEnter(Enter.java:235) at com.sun.tools.javac.comp.Enter.complete(Enter.java:444) at com.sun.tools.javac.comp.Enter.main(Enter.java:429) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:404) at com.sun.tools.javac.main.Main.compile(Main.java:592) at com.sun.tools.javac.main.Main.compile(Main.java:544) at com.sun.tools.javac.Main.compile(Main.java
[jira] [Created] (GERONIMO-6014) Got "javax.ejb.EJBException" when running javaee 6 sample jpa20demo-javaee6
Got "javax.ejb.EJBException" when running javaee 6 sample jpa20demo-javaee6 --- Key: GERONIMO-6014 URL: https://issues.apache.org/jira/browse/GERONIMO-6014 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: sample apps Affects Versions: 3.0 Environment: OS:winxp jdk:ibm jdk Reporter: viola.lu Priority: Minor Fix For: 3.0 1.Build javaee6 sample jpa20demo-javaee6 and deploy 2.Access http://localhost:8080/jpa20demo-javaee6/, click add, but got javax.ejb.EJBException: The bean encountered a non-application exception; nested exception is: org.apache.openjpa.persistence.ArgumentException: A connection could not be obtained for driver class "org.apache.derby.jdbc.ClientDriver" and URL "jdbc:derby://localhost:1527/jpa20demodb". You may have specified an invalid URL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6013) Got "javax.el.PropertyNotFoundException" when running javaee6 sample singletonejb-javaee6/
[
https://issues.apache.org/jira/browse/GERONIMO-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
viola.lu updated GERONIMO-6013:
---
Component/s: sample apps
Priority: Minor (was: Major)
Affects Version/s: 3.0
Fix Version/s: 3.0
> Got "javax.el.PropertyNotFoundException" when running javaee6 sample
> singletonejb-javaee6/
> --
>
> Key: GERONIMO-6013
> URL: https://issues.apache.org/jira/browse/GERONIMO-6013
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: sample apps
>Affects Versions: 3.0
> Environment: OS: winxp
> JDK:ibm jdk
>Reporter: viola.lu
>Priority: Minor
> Fix For: 3.0
>
>
> 1.Build javaee6 sample singletonejb-javaee6 and deploy
> 2.Access http://localhost:8080/singletonejb-javaee6/, click add, but got
> javax.el.PropertyNotFoundException: /index.xhtml at line 29 and column 77
> value="#{AddCalculatorBackBean.currentInput}": Target Unreachable, identifier
> 'AddCalculatorBackBean' resolved to null
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6013) Got "javax.el.PropertyNotFoundException" when running javaee6 sample singletonejb-javaee6/
Got "javax.el.PropertyNotFoundException" when running javaee6 sample
singletonejb-javaee6/
--
Key: GERONIMO-6013
URL: https://issues.apache.org/jira/browse/GERONIMO-6013
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Environment: OS: winxp
JDK:ibm jdk
Reporter: viola.lu
1.Build javaee6 sample singletonejb-javaee6 and deploy
2.Access http://localhost:8080/singletonejb-javaee6/, click add, but got
javax.el.PropertyNotFoundException: /index.xhtml at line 29 and column 77
value="#{AddCalculatorBackBean.currentInput}": Target Unreachable, identifier
'AddCalculatorBackBean' resolved to null
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6012) Fail to build restfulorder-javaee6 sample
Fail to build restfulorder-javaee6 sample - Key: GERONIMO-6012 URL: https://issues.apache.org/jira/browse/GERONIMO-6012 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: sample apps Affects Versions: 3.0 Environment: JDK: ibm jdk SR9-Fp1 Reporter: viola.lu Priority: Minor Fix For: 3.0 1.Run mvn clean install under restfulorder-javaee6 2.Get "Can't package plugin" error -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5729) Access the wrong web console page should get appropriate error message
[ https://issues.apache.org/jira/browse/GERONIMO-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050300#comment-13050300 ] Shenghao Fang commented on GERONIMO-5729: - Issues were found for the patch. Please do not commit it. > Access the wrong web console page should get appropriate error message > -- > > Key: GERONIMO-5729 > URL: https://issues.apache.org/jira/browse/GERONIMO-5729 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2.2, 3.0-M2, 3.0 >Reporter: Shawn Jiang >Assignee: Shenghao Fang > Attachments: GERONIMO-5729.patch > > > I have also found the reason why I sometimes did not see the menu at the left > hand: > When you log in to "/console/portal/welcome" (which was the default location > in previeous versions) then you do _not_ see the menu. > When you log in to "/console/" the you'll be forwarded to > "/console/portal/0/Welcome, and you see everything correctly. > It seems, that the content I've seen is the default page that will be > displayed for users when they've called illegal page names. It also shows up > for /console/portal/Testpage . Unfortunately the message displayed says > "Welcome to the Apache Geronimo™ Administration Console!" etc. instead of a > error message... > As I think it's not critical enough to delay release, I gave +1. > Thank you all for all the development works! > Johannes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
