[jira] Resolved: (GERONIMO-4801) it says "JACC manager gbean already present" when i deploy PlantsByWebSphere sample
[ https://issues.apache.org/jira/browse/GERONIMO-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4801. Resolution: Fixed Commit changes to 2.2.1 branch at r947943, currently, it just hold the exception. We should have a better way to avoid this. > it says "JACC manager gbean already present" when i deploy PlantsByWebSphere > sample > > > Key: GERONIMO-4801 > URL: https://issues.apache.org/jira/browse/GERONIMO-4801 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.2 > Environment: windows xp sp2(x86) > jdk6 >Reporter: Bin He >Assignee: Ivan > Fix For: 2.2.1 > > Attachments: PlantsByWebSphere.7z, sample-datasource.7z > > > 1、start server > 2、deploy sample-datasource sample > 3、deploy PlantsByWebSphere sample but it says:(but this sample can run > well) > 2009-08-19 10:28:52,370 ERROR [EjbModuleBuilder] > GeronimoSecurityBuilderImpl.addGBeans() failed: JACC manager gbean already > present > org.apache.geronimo.common.DeploymentException: JACC manager gbean already > present > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:224) > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.addGBeans(GeronimoSecurityBuilderImpl.java:150) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.addGBeans(EjbModuleBuilder.java:825) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:652) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:136) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:599) > at > org.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:850) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) > at > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) > at > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) > at java.lang.Thread.run(Thread.java:735) > Caused by: org.apache.geronimo.kernel.GBeanAlreadyExistsException: > com.ibm.wasce.samples/pbw/2.1.1.2/car?J2EEApplication=com.ibm.wasce.samples/pbw/2.1.1.2/car,j2eeType=JACCManager,name=JACCManager > at > org.apache.geronimo.kernel.config.Configuration.addGBean(Configuration.java:626) > at > org.apache.geronimo.deployment.DeploymentContext.addGBean(DeploymentContext.java:186) > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:222) > ... 16 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-5010) Transport confifential not working, 403 instead of 302 HTTP headers returned
[ https://issues.apache.org/jira/browse/GERONIMO-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu reopened GERONIMO-5010: now it displas a blank page, not redirect to https > Transport confifential not working, 403 instead of 302 HTTP headers returned > > > Key: GERONIMO-5010 > URL: https://issues.apache.org/jira/browse/GERONIMO-5010 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 > Environment: G 2.2 with Tomcat 6, running on Windows XP with Java 6 >Reporter: Łukasz Budnik >Assignee: Delos Dai >Priority: Blocker > Fix For: 2.2.1 > > > I found it out by accident I was migrating Web Service which uses > CONFIDENTIAL transport layer security. > By looking at the tcpmon I found out that POST request weren't forwarded to > HTTPS and was served using plain HTTP. > The quickest way to reproduce this error: > http://localhost:8080/console/secure > Instead of being brought to https schema (followed by HTTP 302), the result > is: HTTP 403 error. > It was all working in G 2.1.x. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5315) concurrent-testsuite/concurrent-basic has failures in the build console output
[ https://issues.apache.org/jira/browse/GERONIMO-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang reassigned GERONIMO-5315: -- Assignee: Rex Wang > concurrent-testsuite/concurrent-basic has failures in the build console output > -- > > Key: GERONIMO-5315 > URL: https://issues.apache.org/jira/browse/GERONIMO-5315 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Rex Wang > Attachments: TestSuite.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5315) concurrent-testsuite/concurrent-basic has failures in the build console output
[ https://issues.apache.org/jira/browse/GERONIMO-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang resolved GERONIMO-5315. Fix Version/s: 2.2.1 Resolution: Fixed fixed in rev947944 of branch2.2 -Rex > concurrent-testsuite/concurrent-basic has failures in the build console output > -- > > Key: GERONIMO-5315 > URL: https://issues.apache.org/jira/browse/GERONIMO-5315 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Rex Wang > Fix For: 2.2.1 > > Attachments: TestSuite.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
upgrade selenium to 1.0.3 and maven-selenium-plugin to 1.0.1
We need to upgrade selenium to 1.0.3 and maven-selenium-plugin to 1.0.1 to enable the support of latest version browsers in testsuite. -- Shawn
[jira] Created: (GERONIMO-5346) infer jndi type from injection target; check type consistency
infer jndi type from injection target; check type consistency - Key: GERONIMO-5346 URL: https://issues.apache.org/jira/browse/GERONIMO-5346 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment, naming Affects Versions: 3.0 Reporter: David Jencks Assignee: David Jencks Fix For: 3.0 Not sure if this was required in ee5, but ee6 requires that if a naming entry type is missing, it be determined from the injection target type, and that all these be consistent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5347) Upgrade selenium to support latest version browsers in testsuite.
Upgrade selenium to support latest version browsers in testsuite. - Key: GERONIMO-5347 URL: https://issues.apache.org/jira/browse/GERONIMO-5347 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: testsuite Affects Versions: 2.2, 2.1.5, 2.1.6, 2.2.1, 2.2.2, 3.0 Reporter: Shawn Jiang Assignee: Shawn Jiang Priority: Minor Upgrade selenium to support latest version browsers in testsuite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5346) infer jndi type from injection target; check type consistency
[ https://issues.apache.org/jira/browse/GERONIMO-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871044#action_12871044 ] David Jencks commented on GERONIMO-5346: env entries rev 947954 > infer jndi type from injection target; check type consistency > - > > Key: GERONIMO-5346 > URL: https://issues.apache.org/jira/browse/GERONIMO-5346 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment, naming >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 3.0 > > > Not sure if this was required in ee5, but ee6 requires that if a naming entry > type is missing, it be determined from the injection target type, and that > all these be consistent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5329) security-testsuite/test-security has 6 test failures
[ https://issues.apache.org/jira/browse/GERONIMO-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5329. Resolution: Fixed Commit changes to 2.2.1 branch at revision: 947957 > security-testsuite/test-security has 6 test failures > > > Key: GERONIMO-5329 > URL: https://issues.apache.org/jira/browse/GERONIMO-5329 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia > Attachments: TestSuite.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 947945
Geronimo Revision: 947945 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 41 minutes 3 seconds [INFO] Finished at: Tue May 25 03:46:01 EDT 2010 [INFO] Final Memory: 557M/979M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/logs-0300-tomcat/ [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure
[jira] Commented: (GERONIMO-5020) "JACC manager gbean already present" deploymentException stop car-maven-plugin to generate valid geronimo plugin car
[ https://issues.apache.org/jira/browse/GERONIMO-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871057#action_12871057 ] Shawn Jiang commented on GERONIMO-5020: --- This should be a duplication of https://issues.apache.org/jira/browse/GERONIMO-4801 Which was just resloved. Can you please verify this jira with the latest build again ? > "JACC manager gbean already present" deploymentException stop > car-maven-plugin to generate valid geronimo plugin car > > > Key: GERONIMO-5020 > URL: https://issues.apache.org/jira/browse/GERONIMO-5020 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: car-maven-plugin >Affects Versions: 2.2 > Environment: ubuntu 8.04 > IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 > jvmxi3260sr7-20091214_49398 (JIT enabled, AOT enabled) >Reporter: Forrest Xia >Assignee: Ivan > Fix For: 2.2.1 > > > If the deployment plan includes security configs, there will be a known issue: > [ERROR] GeronimoSecurityBuilderImpl.addGBeans() failed: JACC manager gbean > already present > org.apache.geronimo.common.DeploymentException: JACC manager gbean already > present > > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:224) > this exception will stop car-maven-plugin to generate configuration data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4130) Unable to preserve comments from plan.xml into config.xml
[ https://issues.apache.org/jira/browse/GERONIMO-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-4130: -- Fix Version/s: (was: 2.2.1) won't fix this in 221 release. > Unable to preserve comments from plan.xml into config.xml > - > > Key: GERONIMO-4130 > URL: https://issues.apache.org/jira/browse/GERONIMO-4130 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: car-maven-plugin >Affects Versions: 2.1.x, 2.2 >Reporter: Lin Sun > Fix For: Wish List > > > I got a user asking me how to turn off tomcat access log. > It was easy in previous releases, as we could provide comment in config.xml > and tell the users to "To disable accesslogging uncomment the following > section...". However, with our new config.xml, we don't preserve any > comments, which makes hard for users to config things. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4872) plugin "Apache Geronimo-Apache Directory Server Plugin 1.0 LDAP " doesn't exist in http://geronimo.apache.org/plugins/geronimo-2.2
[ https://issues.apache.org/jira/browse/GERONIMO-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-4872: -- Fix Version/s: 2.2.2 (was: 2.2.1) won't fix this in 221 release. > plugin "Apache Geronimo-Apache Directory Server Plugin 1.0 LDAP " doesn't > exist in http://geronimo.apache.org/plugins/geronimo-2.2 > - > > Key: GERONIMO-4872 > URL: https://issues.apache.org/jira/browse/GERONIMO-4872 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Plugins >Affects Versions: 2.2 > Environment: jdk6 > windows xp sp2 >Reporter: Bin He >Priority: Minor > Fix For: 2.2.2 > > > http://cwiki.apache.org/GMOxDOC22/ldap-realm.html > Login into the Geronimo Administration Console. > Click on Plugins. > Click on Update Repository List (optional if you are already pointing to > http://geronimo.apache.org/plugins/geronimo-2.2). > Click on Show Plugins in selected repository. > "Apache Geronimo-Apache Directory Server Plugin 1.0 LDAP" doesn't exist . > I think we need update this doc and first make this plugin exist in the > Repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5337) ServerHostName does not control the bind ip address for Tomcat Connectors
[ https://issues.apache.org/jira/browse/GERONIMO-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-5337. Fix Version/s: 2.2.1 Resolution: Fixed Commit changes to trunk At revision: 947969. 3.0 M1 At revision: 947973 and 2.2.1 branch At revision: 947971 > ServerHostName does not control the bind ip address for Tomcat Connectors > - > > Key: GERONIMO-5337 > URL: https://issues.apache.org/jira/browse/GERONIMO-5337 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 3.0 >Reporter: Kevan Miller >Assignee: Ivan > Fix For: 2.2.1, 3.0 > > > ServerHostName in config-substitutions.properties does not control the bind > address for Tomcat Connectors. They are always 0.0.0.0 > Note I didn't test Jetty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Adding OSGi support to Geronimo spec jars.
On 5/24/2010 8:16 PM, David Jencks wrote: On May 24, 2010, at 5:06 PM, David Blevins wrote: On May 24, 2010, at 3:49 PM, David Jencks wrote: On May 24, 2010, at 2:18 PM, David Blevins wrote: 1. Using EJB as an example, how does one say "I am a provider". There is no "i am the EJB container" interface to implement so what exactly are we looking for? EJB is not an example. the provider stuff works for 2 situations: The activator and locator were added to the EJB spec jar. Was that a mistake? I was wrong... thinking of ejb 3. You need a META-INF/services file for EJBContainerProvider and the SPI-Provider header in the manifest. EJB 3.1 is an example. BTW the only way I've talked the maven-bundle-plugin into adding this header is to supply a value such astrue Anyone know a value-free way? I encountered the same problem and arrived at the same solution point you did. I never found any means of getting the header included without a value specified. Rick thanks david jencks -David
[jira] Resolved: (GERONIMO-5347) Upgrade selenium to support latest version browsers in testsuite.
[ https://issues.apache.org/jira/browse/GERONIMO-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-5347. --- Fix Version/s: 2.1.6 2.2.1 2.2.2 3.0 Resolution: Fixed > Upgrade selenium to support latest version browsers in testsuite. > - > > Key: GERONIMO-5347 > URL: https://issues.apache.org/jira/browse/GERONIMO-5347 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: testsuite >Affects Versions: 2.1.5, 2.1.6, 2.2, 2.2.1, 2.2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Shawn Jiang >Priority: Minor > Fix For: 2.1.6, 2.2.1, 2.2.2, 3.0 > > > Upgrade selenium to support latest version browsers in testsuite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Adding OSGi support to Geronimo spec jars.
On 5/24/2010 8:06 PM, David Blevins wrote: On May 24, 2010, at 3:49 PM, David Jencks wrote: On May 24, 2010, at 2:18 PM, David Blevins wrote: 1. Using EJB as an example, how does one say "I am a provider". There is no "i am the EJB container" interface to implement so what exactly are we looking for? EJB is not an example. the provider stuff works for 2 situations: The activator and locator were added to the EJB spec jar. Was that a mistake? I don't believe it was. There are two sides to this generally. The first side is the role played by the specs, which generally need to locate a provider. Typically, the specification defines a search path that generally searches for 1) a META-INF/services definition, 2) a class defined in a properties file, and 3) a system property. Depending on the age of the specification, the order in which these 3 are searched will vary, and the newest java ee components only define step 1. Generally, this search order will resolve to the name of a provider class that the API code will then instantiate to create the provider instance. The second role is that of the provider class itself. Typically, a provider jar would use the META-INF/services mechanism to advertise its availability. The java EE defined mechanism for locating the provider is to search the classpath for an appropriate META-INF/services file and load the first definition it locates. In an OSGi environment, there are a number of problems associated with the "search the classpath" step, so the ProviderLocator was created. There are two pieces to this: 1) A provider registry. This is an extender that watches new bundles being activated, and if the bundle contains the appropriate metadata, then then the services it exports are made part of a framework-wide registry. 2) The ProviderLocator. This is how APIs that need to resolve providers access the registry information. The provider registry is an OSGi service, so the ProviderLocator needs a bundle context instance to resolve the service instance. The Activator manages obtaining the bundle context at activation and setting up a service tracker to give access to the registry service. The ProviderLocator code manages the details of locating a loading a service instance and will revert to classic classpath behavior if used outside of an OSGi environment. There are two different models in play here for locating a provider instance. In the first model, the API has been handed the name of the desired provider directly as a class name. The API could would then attempt to instantiate that class directly (typically by using the thread context classloader). In the second model, an appropriate META-INF/services definition is located using the interface that the provider is expected to implement as the search key. The services definition file provides a mapping to the provider class name, which is then loaded and instantiated. In terms of my search paths defined in the first paragraph above, 1) is the META-INF/services mode, and 2) and 3) are the first mode of direct loading. The provider registry can handle either of these locator modes. If your provider is already using a META-INF/services model, then the registry then generally all you need to do is add an SPI-Provider header to your jar file. Openejb should have this already, but the EJB3 spec code is not strictly following the EJB specification for locating the provider, so it is possible it is not. If your provider needs to be located via a direct load mechanism where the class name is provided, then you can use an Export-Service-Provider header to advertise your provider class so the ProviderLocator code can locate it by name. So, what should the openejb code be doing? The best solution would be to create the META-INF/services file that maps EJBContainerProvider to your implementation class and add the SPI-Provider header. Unfortunately, there is a gotcha here, in the form of this Jira: https://issues.apache.org/jira/browse/GERONIMO-5186 The EJB specification says the EJBContainerProvider lookup mechanism should use only the META-INF/services mechanism, and for each definition if finds, it should instantiate the service instance and call createEJBContainer() passing the property bundle that was passed to EJBContainer.createEJBContainer(). The provider instance is then responsible for determining if it is the appropriate provider by examining the provider name in the properties bundle. Here's the wording from the spec: The EJBContainer bootstrap class will locate all of the container providers by their provider configuration files and call EJBContainerProvider.createEJBContainer(Map) on them in turn until an appropriate backing provider returns an EJBContainer. A provider may deem itself as appropriate for the embeddable application if any of the following are true : •The javax.ejb.embeddable.provider property
[BUILD] trunk: Failed for Revision: 948031
Geronimo Revision: 948031 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 40 minutes 21 seconds
[INFO] Finished at: Tue May 25 10:02:20 EDT 2010
[INFO] Final Memory: 534M/986M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/logs-0900-tomcat/
Running TestSuite
Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 89.432 sec <<<
FAILURE!
--
Running TestSuite
Tests run: 22, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 62.055 sec <<<
FAILURE!
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/logs-0900-jetty/
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 40.663 sec <<<
FAILURE!
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/security-testsuite/3.0-SNAPSHOT/security-testsuite-3.0-SNAPSHOT.pom
[INFO] [failsafe:verify {execution: verify}]
[INFO] No tests to run.
[INFO]
[INFO] Building Geronimo TestSuite :: Security Testsuite :: Test Security
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [selenium:xvfb {execution: xvfb}]
[INFO] Starting Xvfb...
[INFO] Using display: :21
[INFO] Using Xauthority file: /tmp/Xvfb868930546425768.Xauthority
Deleting: /tmp/Xvfb868930546425768.Xauthority
xauth: creating new authority file /tmp/Xvfb868930546425768.Xauthority
Created dir:
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/selenium
Launching Xvfb
Waiting for Xvfb...
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/selenium/xvfb.log
Xvfb started
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 5 source files to
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[test-security] in
[/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/test-security-3.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp
webResources[/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/src/main/webapp]
to[/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/test-security-3.0-SNAPSHOT]
[INFO] Copying webapp
webResources[/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/classes]
to[/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/test-security-3.0-SNAPSHOT]
[INFO] Copying webapp
resources[/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/src/main/webapp]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/security-testsuite/test-security/target/test-security-3.0-SNAPSHOT/WEB-INF/lib/test-security-3.0-SNAPSHOT.jar
[INFO] Webapp assembled in[
[jira] Resolved: (GERONIMO-5203) JTA OSGi services & blueprint extensions
[ https://issues.apache.org/jira/browse/GERONIMO-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5203. --- Resolution: Fixed Resolving as work for this item is done. > JTA OSGi services & blueprint extensions > > > Key: GERONIMO-5203 > URL: https://issues.apache.org/jira/browse/GERONIMO-5203 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Aries, osgi, transaction manager >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > > There are two things that need to be done: 1) Register JTA transaction > services into service registry and 2) Integrate Aries blueprint transaction > extensions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5247) IllegalStateException during Geronimo build.
[ https://issues.apache.org/jira/browse/GERONIMO-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5247. --- Resolution: Fixed I fixed the problem in Aries and updated trunk to use the latest Aries JNDI module (committed in revision 948077). > IllegalStateException during Geronimo build. > - > > Key: GERONIMO-5247 > URL: https://issues.apache.org/jira/browse/GERONIMO-5247 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: osgi >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Jarek Gawor > Fix For: 3.0 > > > The following IllegalStateException occurs over and over during the Geronimo > build process: > java.lang.IllegalStateException: ObjectFactoryBuilder already set > at > javax.naming.spi.NamingManager.setObjectFactoryBuilder(NamingManager. > java:94) > at org.apache.aries.jndi.startup.Activator.start(Activator.java:52) > at > org.apache.felix.framework.util.SecureAction.startActivator(SecureAct > ion.java:661) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:1801) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1723) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) > at > org.apache.geronimo.system.configuration.DependencyManager.starting(D > ependencyManager.java:191) > at > org.apache.geronimo.system.configuration.DependencyManager.bundleChan > ged(DependencyManager.java:89) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerC > allback(EventDispatcher.java:800) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately( > EventDispatcher.java:728) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(Event > Dispatcher.java:610) > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3670) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:1791) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1723) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) > at > org.apache.geronimo.system.configuration.DependencyManager.starting(D > ependencyManager.java:191) > at > org.apache.geronimo.system.configuration.DependencyManager.bundleChan > ged(DependencyManager.java:89) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerC > allback(EventDispatcher.java:800) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately( > EventDispatcher.java:728) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(Event > Dispatcher.java:610) > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3670) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:1791) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1723) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) > at > org.apache.geronimo.system.configuration.DependencyManager.starting(D > ependencyManager.java:191) > at > org.apache.geronimo.system.configuration.DependencyManager.bundleChan > ged(DependencyManager.java:89) > at > org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerC > allback(EventDispatcher.java:800) > at > org.apache.felix.framework.util.EventDispatcher.fireEventImmediately( > EventDispatcher.java:728) > at > org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(Event > Dispatcher.java:610) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5034) Integrate JMX (RFC 142) implementation from Apache Aries
[ https://issues.apache.org/jira/browse/GERONIMO-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5034. --- Assignee: Jarek Gawor Resolution: Fixed The Aries JMX bundles (including the one for Blueprint MBeans) are installed by the rmi-naming configuration. Changes committed in revision 935808. > Integrate JMX (RFC 142) implementation from Apache Aries > > > Key: GERONIMO-5034 > URL: https://issues.apache.org/jira/browse/GERONIMO-5034 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Aries, osgi >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > > Integrate JMX (RFC 142) implementation from Apache Aries into Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 947723
Geronimo Revision: 947723 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100524/build-1400.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100524
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 40 minutes 51 seconds
[INFO] Finished at: Mon May 24 14:50:22 EDT 2010
[INFO] Final Memory: 304M/1014M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100524/logs-1400-tomcat/
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 22.872
sec <<< FAILURE!
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100524/logs-1400-jetty/
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 21.414
sec <<< FAILURE!
[INFO] [INFO] Building Geronimo TestSuite :: Commands Testsuite :: GShell
[INFO] [INFO]task-segment: [install]
[INFO] [INFO]
[INFO] [INFO] [genesis:validate-configuration {execution: default}]
[INFO] [INFO] [enforcer:enforce {execution: default}]
[INFO] [INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] [INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] [INFO] Setting property: resource.loader => 'classpath'.
[INFO] [INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [INFO] [remote-resources:process {execution: default}]
[INFO] [INFO] [resources:resources]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/main/resources
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/main/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:compile]
[INFO] [INFO] No sources to compile
[INFO] [INFO] [resources:testResources]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/test/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:testCompile]
[INFO] [INFO] Nothing to compile - all classes are up to date
[INFO] [INFO] [surefire:test]
[INFO] [INFO] Tests are skipped.
[INFO] [INFO] [jar:jar]
[INFO] [INFO] Building jar:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/gshell-2.2.1-SNAPSHOT.jar
[INFO] [INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] [INFO] Failsafe report directory:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/failsafe-reports
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.235
sec
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [WARNING] File encoding has not been set, using platform encoding
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] [INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [WARNING] Skipping verification of legal files in artifacts:
[INFO] [WARNING] org.apache.geronimo.testsuite:gshell:jar:2.2.1-SNAPSHOT
[INFO] [INFO] [failsafe:verify {execution: verify}]
[INFO] [INFO] Failsafe report directory:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/failsafe-reports
[INFO] [WARNING] File encoding has not been set, using platform encoding
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] [INFO] [install:install]
[INFO] [INFO] Installing
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/gshell-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/gshell/2.2.1-SNAPSHOT/gshell-2.2.1-SNAPSHOT.jar
[INFO] [INFO]
[INFO] [INFO] BUILD SUCCESSFUL
[INFO] [INFO]
[INFO] [INFO] Total time: 37 seconds
[INFO] [INFO] Finished at: Tue May 25 12:13:35 EDT 2010
[INFO] [INFO] Final Memory: 38M/565M
[INFO] [INFO]
[INFO] [ianal:verify-legal
[BUILD] branches/2.2: Failed for Revision: 948120
Geronimo Revision: 948120 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100525/build-1400.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100525
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 37 minutes 22 seconds
[INFO] Finished at: Tue May 25 14:52:43 EDT 2010
[INFO] Final Memory: 302M/1014M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100525/logs-1400-tomcat/
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 21.615
sec <<< FAILURE!
[INFO] [INFO] Building Geronimo TestSuite :: Commands Testsuite :: GShell
[INFO] [INFO]task-segment: [install]
[INFO] [INFO]
[INFO] [INFO] [genesis:validate-configuration {execution: default}]
[INFO] [INFO] [enforcer:enforce {execution: default}]
[INFO] [INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] [INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] [INFO] Setting property: resource.loader => 'classpath'.
[INFO] [INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [INFO] [remote-resources:process {execution: default}]
[INFO] [INFO] [resources:resources]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/main/resources
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/main/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:compile]
[INFO] [INFO] No sources to compile
[INFO] [INFO] [resources:testResources]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/test/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:testCompile]
[INFO] [INFO] Compiling 1 source file to
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/test-classes
[INFO] [INFO] [surefire:test]
[INFO] [INFO] Tests are skipped.
[INFO] [INFO] [jar:jar]
[INFO] [INFO] Building jar:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/gshell-2.2.1-SNAPSHOT.jar
[INFO] [INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] [INFO] Failsafe report directory:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/failsafe-reports
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.492
sec
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [WARNING] File encoding has not been set, using platform encoding
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] [INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [WARNING] Skipping verification of legal files in artifacts:
[INFO] [WARNING] org.apache.geronimo.testsuite:gshell:jar:2.2.1-SNAPSHOT
[INFO] [INFO] [failsafe:verify {execution: verify}]
[INFO] [INFO] Failsafe report directory:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/failsafe-reports
[INFO] [WARNING] File encoding has not been set, using platform encoding
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] [INFO] [install:install]
[INFO] [INFO] Installing
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/gshell-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/gshell/2.2.1-SNAPSHOT/gshell-2.2.1-SNAPSHOT.jar
[INFO] [INFO]
[INFO] [INFO] BUILD SUCCESSFUL
[INFO] [INFO]
[INFO] [INFO] Total time: 38 seconds
[INFO] [INFO] Finished at: Tue May 25 15:16:03 EDT 2010
[INFO] [INFO] Final Memory: 38M/566M
[INFO] [INFO]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/pom.xml to
/ho
[BUILD] trunk: Failed for Revision: 948174
Geronimo Revision: 948174 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 36 minutes 10 seconds
[INFO] Finished at: Tue May 25 15:40:16 EDT 2010
[INFO] Final Memory: 596M/997M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/logs-1500-tomcat/
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO] Generating application.xml
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/resources
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [ear:ear {execution: default-ear}]
[INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:3.0-SNAPSHOT]
to[corba-marshal-ejb-3.0-SNAPSHOT.jar]
[INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:3.0-SNAPSHOT]
to[corba-marshal-client-3.0-SNAPSHOT.jar]
[INFO] Copy ear resources to
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT
[INFO] Could not find manifest file:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT.ear
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
into
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@158c7fa}
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.ConnectException: Connection refused]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refus
Re: Adding OSGi support to Geronimo spec jars.
Hey I got an idea. Since we're already modding spec jars, some of which will have to be installed into the endorsed dir directory anyway, Why don't we just mod the java.util.ServiceLoader class to do this optional OSGi search? You know, the whole one to rule them all approach. Then we don't have to mod each spec jar and it would work even for SAXParserFactory and other Java SE searches. And people could opt-in. "If you want this functionality, install this jar to your endorsed dir" -David On May 25, 2010, at 3:17 AM, Rick McGuire wrote: > On 5/24/2010 8:06 PM, David Blevins wrote: >> On May 24, 2010, at 3:49 PM, David Jencks wrote: >> >> >>> On May 24, 2010, at 2:18 PM, David Blevins wrote: >>> >>> 1. Using EJB as an example, how does one say "I am a provider". There is no "i am the EJB container" interface to implement so what exactly are we looking for? >>> >>> EJB is not an example. the provider stuff works for 2 situations: >>> >> The activator and locator were added to the EJB spec jar. Was that a >> mistake? >> > I don't believe it was. There are two sides to this generally. The first side > is the role played by the specs, which generally need to locate a provider. > Typically, the specification defines a search path that generally searches > for 1) a META-INF/services definition, 2) a class defined in a properties > file, and 3) a system property. Depending on the age of the specification, > the order in which these 3 are searched will vary, and the newest java ee > components only define step 1. Generally, this search order will resolve to > the name of a provider class that the API code will then instantiate to > create the provider instance. > > The second role is that of the provider class itself. Typically, a provider > jar would use the META-INF/services mechanism to advertise its availability. > The java EE defined mechanism for locating the provider is to search the > classpath for an appropriate META-INF/services file and load the first > definition it locates. > > In an OSGi environment, there are a number of problems associated with the > "search the classpath" step, so the ProviderLocator was created. There are > two pieces to this: > > 1) A provider registry. This is an extender that watches new bundles being > activated, and if the bundle contains the appropriate metadata, then then the > services it exports are made part of a framework-wide registry. > > 2) The ProviderLocator. This is how APIs that need to resolve providers > access the registry information. The provider registry is an OSGi service, so > the ProviderLocator needs a bundle context instance to resolve the service > instance. The Activator manages obtaining the bundle context at activation > and setting up a service tracker to give access to the registry service. The > ProviderLocator code manages the details of locating a loading a service > instance and will revert to classic classpath behavior if used outside of an > OSGi environment. > > There are two different models in play here for locating a provider instance. > In the first model, the API has been handed the name of the desired provider > directly as a class name. The API could would then attempt to instantiate > that class directly (typically by using the thread context classloader). In > the second model, an appropriate META-INF/services definition is located > using the interface that the provider is expected to implement as the search > key. The services definition file provides a mapping to the provider class > name, which is then loaded and instantiated. In terms of my search paths > defined in the first paragraph above, 1) is the META-INF/services mode, and > 2) and 3) are the first mode of direct loading. > > The provider registry can handle either of these locator modes. If your > provider is already using a META-INF/services model, then the registry then > generally all you need to do is add an SPI-Provider header to your jar file. > Openejb should have this already, but the EJB3 spec code is not strictly > following the EJB specification for locating the provider, so it is possible > it is not. > > If your provider needs to be located via a direct load mechanism where the > class name is provided, then you can use an Export-Service-Provider header to > advertise your provider class so the ProviderLocator code can locate it by > name. > > So, what should the openejb code be doing? The best solution would be to > create the META-INF/services file that maps EJBContainerProvider to your > implementation class and add the SPI-Provider header. Unfortunately, there is > a gotcha here, in the form of this Jira: > > https://issues.apache.org/jira/browse/GERONIMO-5186 > > The EJB specification says the EJBContainerProvider lookup mechanism should > use only the META-INF/services mechanism, and for each definition if finds, > it should
[jira] Assigned: (GERONIMO-5065) EJBs in WAR files enhancement
[ https://issues.apache.org/jira/browse/GERONIMO-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-5065: -- Assignee: David Jencks > EJBs in WAR files enhancement > - > > Key: GERONIMO-5065 > URL: https://issues.apache.org/jira/browse/GERONIMO-5065 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: javaee6, Jetty, OpenEJB, Tomcat, web >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: David Jencks > Fix For: 3.0 > > > JSR 316 includes new support to allow EJBs to be package inside of WAR files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5117) Implement builder support for war embedded EJBs.
[ https://issues.apache.org/jira/browse/GERONIMO-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-5117: -- Assignee: David Jencks > Implement builder support for war embedded EJBs. > - > > Key: GERONIMO-5117 > URL: https://issues.apache.org/jira/browse/GERONIMO-5117 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: David Jencks > Fix For: 3.0 > > > Once the OpenEJB support is complete, there will be some builder support > necessary to enable the new support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5346) infer jndi type from injection target; check type consistency
[ https://issues.apache.org/jira/browse/GERONIMO-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871452#action_12871452 ] David Jencks commented on GERONIMO-5346: resources rev 948266 > infer jndi type from injection target; check type consistency > - > > Key: GERONIMO-5346 > URL: https://issues.apache.org/jira/browse/GERONIMO-5346 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment, naming >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 3.0 > > > Not sure if this was required in ee5, but ee6 requires that if a naming entry > type is missing, it be determined from the injection target type, and that > all these be consistent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5117) Implement builder support for war embedded EJBs.
[ https://issues.apache.org/jira/browse/GERONIMO-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871457#action_12871457 ] David Jencks commented on GERONIMO-5117: rev 948268 introduces the idea of Module having sub modules and modifies the EjbModuleBuilder to be both a ModuleBuilder and ModuleBuilderExtension. This should let us support not only ejbs in wars but also rars in wars, ejbs, and clients, and ejbs in clients. This does not yet support the ridiculous requirement that java:comp be shared across all the ejbs in the war... what's java:module for anyway? > Implement builder support for war embedded EJBs. > - > > Key: GERONIMO-5117 > URL: https://issues.apache.org/jira/browse/GERONIMO-5117 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: David Jencks > Fix For: 3.0 > > > Once the OpenEJB support is complete, there will be some builder support > necessary to enable the new support. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 948253
Geronimo Revision: 948253 built with tests included
See the full build-2000.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100525/build-2000.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100525
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 33 minutes 53 seconds
[INFO] Finished at: Tue May 25 20:48:31 EDT 2010
[INFO] Final Memory: 327M/893M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100525/logs-2000-tomcat/
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 22.681
sec <<< FAILURE!
[INFO] [INFO] Building Geronimo TestSuite :: Commands Testsuite :: GShell
[INFO] [INFO]task-segment: [install]
[INFO] [INFO]
[INFO] [INFO] [genesis:validate-configuration {execution: default}]
[INFO] [INFO] [enforcer:enforce {execution: default}]
[INFO] [INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] [INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] [INFO] Setting property: resource.loader => 'classpath'.
[INFO] [INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [INFO] [remote-resources:process {execution: default}]
[INFO] [INFO] [resources:resources]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/main/resources
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/main/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:compile]
[INFO] [INFO] No sources to compile
[INFO] [INFO] [resources:testResources]
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 1 resource
[INFO] [INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/src/test/filtered-resources
[INFO] [INFO] Copying 3 resources
[INFO] [INFO] [compiler:testCompile]
[INFO] [INFO] Compiling 1 source file to
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/test-classes
[INFO] [INFO] [surefire:test]
[INFO] [INFO] Tests are skipped.
[INFO] [INFO] [jar:jar]
[INFO] [INFO] Building jar:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/gshell-2.2.1-SNAPSHOT.jar
[INFO] [INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] [INFO] Failsafe report directory:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/failsafe-reports
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running TestSuite
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.199
sec
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] [WARNING] File encoding has not been set, using platform encoding
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] [INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [WARNING] Skipping verification of legal files in artifacts:
[INFO] [WARNING] org.apache.geronimo.testsuite:gshell:jar:2.2.1-SNAPSHOT
[INFO] [INFO] [failsafe:verify {execution: verify}]
[INFO] [INFO] Failsafe report directory:
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/failsafe-reports
[INFO] [WARNING] File encoding has not been set, using platform encoding
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] [INFO] [install:install]
[INFO] [INFO] Installing
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/gshell/target/gshell-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/gshell/2.2.1-SNAPSHOT/gshell-2.2.1-SNAPSHOT.jar
[INFO] [INFO]
[INFO] [INFO] BUILD SUCCESSFUL
[INFO] [INFO]
[INFO] [INFO] Total time: 38 seconds
[INFO] [INFO] Finished at: Tue May 25 21:00:33 EDT 2010
[INFO] [INFO] Final Memory: 37M/566M
[INFO] [INFO]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/testsuite/commands-testsuite/pom.xml to
/ho
Recursive or nested modules
David Blevins said something to me that made me think that we could easily nest ejbs in wars, rars in just about anything, ejbs in app clients etc etc by making the Module have submodules and by having our ModuleBuilder also implement ModuleBuilderExtension. I got started on this in rev 948268 it looks pretty promising so far. I'm thinking of having an AbstractRecursiveModuleBuilder that implements the common methods of ModuleBuilder and ModuleBuilderExtension to work on the main module or the appropriate nested modules as appropriate, to abstract the code I put in EjbModuleBuilder. thanks david jencks
[BUILD] trunk: Failed for Revision: 948282
Geronimo Revision: 948282 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/build-2100.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100525/unit-test-reports
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car,j2eeType=ModuleBuilder,name=GBeanBuilder
State changed from stopping to stopped
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car,j2eeType=XmlAttributeBuilder,name=JavaBeanXmlAttributeBuilder
State changed from running to stopping
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car,j2eeType=XmlAttributeBuilder,name=JavaBeanXmlAttributeBuilder
State changed from stopping to stopped
[org.apache.geronimo.kernel.config.Configuration] : Stopping configuration
org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car?configurationName=org.apache.geronimo.framework/geronimo-gbean-deployer/3.0-SNAPSHOT/car
State changed from stopping to stopped
[org.apache.geronimo.kernel.config.Configuration] : Stopping configuration
org.apache.geronimo.framework/plugin/3.0-SNAPSHOT/car
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/plugin/3.0-SNAPSHOT/car?configurationName=org.apache.geronimo.framework/plugin/3.0-SNAPSHOT/car
State changed from stopping to stopped
[org.apache.geronimo.kernel.config.Configuration] : Stopping configuration
org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car?configurationName=org.apache.geronimo.framework/rmi-naming/3.0-SNAPSHOT/car
State changed from stopping to stopped
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car?configurationName=org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car
State changed from running to stopping
[org.apache.geronimo.kernel.config.Configuration] : Stopping configuration
org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car
[org.apache.geronimo.gbean.runtime.GBeanInstanceState] : GBeanInstanceState
for:
org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car?configurationName=org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car
State changed from stopping to stopped
[org.apache.geronimo.kernel.basic.BasicKernel] : Kernel shutdown complete
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling SLF4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling Jakarta Commons Logging API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling Log4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling Avalon Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Disabling JULI Logger API support.
[INFO] [car:archive-car {execution: default-archive-car}]
[INFO] Expanding:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/client-transaction-1_6/target/repository/org/apache/geronimo/configs/client-transaction-1_6/3.0-SNAPSHOT/client-transaction-1_6-3.0-SNAPSHOT.car
into /tmp/archived-file-set.364533125.tmp
[INFO] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/client-transaction-1_6/target/client-transaction-1_6-3.0-SNAPSHOT.car
[INFO] Building jar:
/home/geronimo/geronimo/trunk/plugins/connector-1_6/client-transaction-1_6/target/client-transaction-1_6-3.0-SNAPSHOT.car
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: client-transaction-1_6-3.0-SNAPSHOT.car
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/connector-1_6/client-transaction-1_6/target/client-transaction-1_6-3.0-SNAPSHOT.car
to
/home/geronimo/.m2/repository/org/apache/geronimo/configs/client-transaction-1_6/3.0-SNAPSHOT/client-transaction-1_6-3.0-SNAPSHOT.car
[INFO] Installing
/home/geronimo
Re: svn commit: r946857 - in /geronimo/devtools/eclipse-plugin/trunk: eclipse/ plugins/org.apache.geronimo.st.v30.core/META-INF/ plugins/org.apache.geronimo.st.v30.core/src/main/java/org/apache/geroni
Hi Delos, I've revert the change to the build script since we cannot
automatically download the free Aries tools due to licensing. Later this
week I'll remove both the runtime and build dependencies we have on the
free Aries tooling. If you have trouble building the GEP until then you
can manually download the free Aries tools, unzip them into the eclipse
subdirectory of your m2 repo, and then invoke the no-eclipse-downloads
maven profile (i.e., mvn install -Pno-eclipse-downloads). Thanks
On 5/20/2010 11:25 PM, de...@apache.org wrote:
Author: delos
Date: Fri May 21 03:25:16 2010
New Revision: 946857
URL: http://svn.apache.org/viewvc?rev=946857&view=rev
Log:
GERONIMODEVTOOLS-614 update build script to download free Aries tool
Modified:
geronimo/devtools/eclipse-plugin/trunk/eclipse/build.xml
geronimo/devtools/eclipse-plugin/trunk/eclipse/pom.xml
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/META-INF/MANIFEST.MF
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/src/main/java/org/apache/geronimo/st/v30/core/DeploymentUtils.java
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/src/main/java/org/apache/geronimo/st/v30/core/GeronimoServerDelegate.java
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/src/main/java/org/apache/geronimo/st/v30/core/GeronimoUtils.java
Modified: geronimo/devtools/eclipse-plugin/trunk/eclipse/build.xml
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/trunk/eclipse/build.xml?rev=946857&r1=946856&r2=946857&view=diff
==
--- geronimo/devtools/eclipse-plugin/trunk/eclipse/build.xml (original)
+++ geronimo/devtools/eclipse-plugin/trunk/eclipse/build.xml Fri May 21
03:25:16 2010
@@ -44,6 +44,11 @@
http://www.eclipse.org/downloads/download.php?file=/tptp/4.7.0/TPTP-4.7.0M7-201005041505"/>
+
+
+
+
+https://www6.software.ibm.com/sdfdl/v2/regs2/OSGI_Tools/Xa.2/Xb.Bhtd1U2AGuQI_IMsx-2bmOlvfZa89CHrFb1bAYveFA/Xc.OSGi_Tools_1.0.0.0.zip/Xd./Xf.LPr.U1ay/Xg.5462396/Xi.swg-osgitools/XY.regsrvs/XZ.RNxpGEd_bq2XMRbT9BTu6wl2SoM/OSGi_Tools_1.0.0.0.zip"/>
@@ -72,6 +77,30 @@
overwrite="true"/>
+
+#
+##
+## Downloading: ${ariestools}
+##
+## From: ${free_aries_tool_url}
+##
+#
+
+
+#
+##
+## Unzipping: ${ariestools}
+##
+#
+
+
+
Modified: geronimo/devtools/eclipse-plugin/trunk/eclipse/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/trunk/eclipse/pom.xml?rev=946857&r1=946856&r2=946857&view=diff
==
--- geronimo/devtools/eclipse-plugin/trunk/eclipse/pom.xml (original)
+++ geronimo/devtools/eclipse-plugin/trunk/eclipse/pom.xml Fri May 21 03:25:16
2010
@@ -47,6 +47,7 @@
+
Modified:
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/META-INF/MANIFEST.MF
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/META-INF/MANIFEST.MF?rev=946857&r1=946856&r2=946857&view=diff
==
---
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/META-INF/MANIFEST.MF
(original)
+++
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/META-INF/MANIFEST.MF
Fri May 21 03:25:16 2010
@@ -7,7 +7,7 @@ Bundle-Activator: org.apache.geronimo.st
Bundle-Vendor: %providerName
Bundle-Localization: plugin
Require-Bundle:
- com.ibm.etools.aries.core,
+ com.ibm.etools.aries.core;resolution:=optional,
org.apache.geronimo.jee.v21.jaxbmodel,
org.apache.geronimo.runtime.v30,
org.eclipse.core.commands,
Modified:
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/src/main/java/org/apache/geronimo/st/v30/core/DeploymentUtils.java
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core/src/main/java/org/apache/geronimo/st/v30/core/DeploymentUtils.java?rev=946857&r1=946856&r2=946857&view=diff
==
---
geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v30.core
[jira] Commented: (GERONIMO-5314) commands-testsuite/jaxws test failures
[ https://issues.apache.org/jira/browse/GERONIMO-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871492#action_12871492 ] Forrest Xia commented on GERONIMO-5314: --- The root cause is found that the com.sun.xml.bind/jaxb-xjc and com.sun.xml.bind/jaxb-impl is not consistent in version number. In the root pom.xml of Geronimo 2.2.1-SNAPSHOT, jaxb-xjc is 2.1.7, while jaxb-impl is 2.1.12. After updating xjc to 2.1.12, all jaxws cases pass. Committed revision 948303. > commands-testsuite/jaxws test failures > -- > > Key: GERONIMO-5314 > URL: https://issues.apache.org/jira/browse/GERONIMO-5314 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: testsuite >Affects Versions: 2.2.1 >Reporter: Forrest Xia > Attachments: testng-results.xml, TestSuite-output.txt, TestSuite.txt > > > See the console output for failure cases: > [INFO] [INFO] Failsafe report directory: > /home/forrestxm/src/g22branch/testsuite/commands-testsuite/jaxws/target/failsafe-reports > [INFO] > [INFO] --- > [INFO] T E S T S > [INFO] --- > [INFO] Running TestSuite > [INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 17.804 > sec <<< FAILURE! > [INFO] > [INFO] Results : > [INFO] > [INFO] Failed tests: > [INFO] testWSDL2Java(org.apache.geronimo.testsuite.jaxws.CXFToolsTest) > [INFO] testWsImport(org.apache.geronimo.testsuite.jaxws.JAXWSToolsTest) > [INFO] > [INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0 > Check error log in attachments for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5314) commands-testsuite/jaxws test failures
[ https://issues.apache.org/jira/browse/GERONIMO-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5314. - Fix Version/s: 2.2.1 Resolution: Fixed > commands-testsuite/jaxws test failures > -- > > Key: GERONIMO-5314 > URL: https://issues.apache.org/jira/browse/GERONIMO-5314 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: testsuite >Affects Versions: 2.2.1 >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 2.2.1 > > Attachments: testng-results.xml, TestSuite-output.txt, TestSuite.txt > > > See the console output for failure cases: > [INFO] [INFO] Failsafe report directory: > /home/forrestxm/src/g22branch/testsuite/commands-testsuite/jaxws/target/failsafe-reports > [INFO] > [INFO] --- > [INFO] T E S T S > [INFO] --- > [INFO] Running TestSuite > [INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 17.804 > sec <<< FAILURE! > [INFO] > [INFO] Results : > [INFO] > [INFO] Failed tests: > [INFO] testWSDL2Java(org.apache.geronimo.testsuite.jaxws.CXFToolsTest) > [INFO] testWsImport(org.apache.geronimo.testsuite.jaxws.JAXWSToolsTest) > [INFO] > [INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0 > Check error log in attachments for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5314) commands-testsuite/jaxws test failures
[ https://issues.apache.org/jira/browse/GERONIMO-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reassigned GERONIMO-5314: - Assignee: Forrest Xia > commands-testsuite/jaxws test failures > -- > > Key: GERONIMO-5314 > URL: https://issues.apache.org/jira/browse/GERONIMO-5314 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: testsuite >Affects Versions: 2.2.1 >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 2.2.1 > > Attachments: testng-results.xml, TestSuite-output.txt, TestSuite.txt > > > See the console output for failure cases: > [INFO] [INFO] Failsafe report directory: > /home/forrestxm/src/g22branch/testsuite/commands-testsuite/jaxws/target/failsafe-reports > [INFO] > [INFO] --- > [INFO] T E S T S > [INFO] --- > [INFO] Running TestSuite > [INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 17.804 > sec <<< FAILURE! > [INFO] > [INFO] Results : > [INFO] > [INFO] Failed tests: > [INFO] testWSDL2Java(org.apache.geronimo.testsuite.jaxws.CXFToolsTest) > [INFO] testWsImport(org.apache.geronimo.testsuite.jaxws.JAXWSToolsTest) > [INFO] > [INFO] Tests run: 4, Failures: 2, Errors: 0, Skipped: 0 > Check error log in attachments for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
jaxb-xjc and jaxb-impl should have the same version number in G trunk and 3.0 M1 branch
Hi, Recently, when I work on a JIRA( https://issues.apache.org/jira/browse/GERONIMO-5314) for G 2.2 branch, I see a cxf wsdl2java command failure caused by mismatch version of jaxb-xjc and jaxb-impl. After check the trunk and 3.0 M1 branch, I see the difference too. jaxb-xjc is still 2.1.7, while jaxb-impl is a bundlized version which uses jaxb-impl 2.2. I think we need to make the aligned in the same version level to avoid potential issues. Any thoughts? If that is OK, I will create a patch for trunk and M1. Forrest
[jira] Closed: (GERONIMO-5020) "JACC manager gbean already present" deploymentException stop car-maven-plugin to generate valid geronimo plugin car
[ https://issues.apache.org/jira/browse/GERONIMO-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-5020. -- Resolution: Fixed https://issues.apache.org/jira/browse/GERONIMO-4801 this jira is fixed and verified. This exception is removed already from latest build 2010.05.25-15:32:06.587-0400, so close it. > "JACC manager gbean already present" deploymentException stop > car-maven-plugin to generate valid geronimo plugin car > > > Key: GERONIMO-5020 > URL: https://issues.apache.org/jira/browse/GERONIMO-5020 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: car-maven-plugin >Affects Versions: 2.2 > Environment: ubuntu 8.04 > IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 > jvmxi3260sr7-20091214_49398 (JIT enabled, AOT enabled) >Reporter: Forrest Xia >Assignee: Ivan > Fix For: 2.2.1 > > > If the deployment plan includes security configs, there will be a known issue: > [ERROR] GeronimoSecurityBuilderImpl.addGBeans() failed: JACC manager gbean > already present > org.apache.geronimo.common.DeploymentException: JACC manager gbean already > present > > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:224) > this exception will stop car-maven-plugin to generate configuration data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4801) it says "JACC manager gbean already present" when i deploy PlantsByWebSphere sample
[ https://issues.apache.org/jira/browse/GERONIMO-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-4801. -- This exception is removed already from latest build 2010.05.25-15:32:06.587-0400, so close it. > it says "JACC manager gbean already present" when i deploy PlantsByWebSphere > sample > > > Key: GERONIMO-4801 > URL: https://issues.apache.org/jira/browse/GERONIMO-4801 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.2 > Environment: windows xp sp2(x86) > jdk6 >Reporter: Bin He >Assignee: Ivan > Fix For: 2.2.1 > > Attachments: PlantsByWebSphere.7z, sample-datasource.7z > > > 1、start server > 2、deploy sample-datasource sample > 3、deploy PlantsByWebSphere sample but it says:(but this sample can run > well) > 2009-08-19 10:28:52,370 ERROR [EjbModuleBuilder] > GeronimoSecurityBuilderImpl.addGBeans() failed: JACC manager gbean already > present > org.apache.geronimo.common.DeploymentException: JACC manager gbean already > present > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:224) > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.addGBeans(GeronimoSecurityBuilderImpl.java:150) > at > org.apache.geronimo.openejb.deployment.EjbModuleBuilder.addGBeans(EjbModuleBuilder.java:825) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:652) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:257) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:136) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:599) > at > org.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:850) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) > at > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:116) > at > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:61) > at java.lang.Thread.run(Thread.java:735) > Caused by: org.apache.geronimo.kernel.GBeanAlreadyExistsException: > com.ibm.wasce.samples/pbw/2.1.1.2/car?J2EEApplication=com.ibm.wasce.samples/pbw/2.1.1.2/car,j2eeType=JACCManager,name=JACCManager > at > org.apache.geronimo.kernel.config.Configuration.addGBean(Configuration.java:626) > at > org.apache.geronimo.deployment.DeploymentContext.addGBean(DeploymentContext.java:186) > at > org.apache.geronimo.security.deployment.GeronimoSecurityBuilderImpl.buildJaccManager(GeronimoSecurityBuilderImpl.java:222) > ... 16 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5347) Upgrade selenium to support latest version browsers in testsuite.
[ https://issues.apache.org/jira/browse/GERONIMO-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-5347. -- Now firefox 3 can be launched to run tests, so close it. > Upgrade selenium to support latest version browsers in testsuite. > - > > Key: GERONIMO-5347 > URL: https://issues.apache.org/jira/browse/GERONIMO-5347 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: testsuite >Affects Versions: 2.1.5, 2.1.6, 2.2, 2.2.1, 2.2.2, 3.0 >Reporter: Shawn Jiang >Assignee: Shawn Jiang >Priority: Minor > Fix For: 2.1.6, 2.2.1, 2.2.2, 3.0 > > > Upgrade selenium to support latest version browsers in testsuite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5265) Modify the redeploy behavior to start all the running childs along with the parent
[ https://issues.apache.org/jira/browse/GERONIMO-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-5265: -- Fix Version/s: 2.2.2 (was: 2.2.1) won't fix this in 221 release. > Modify the redeploy behavior to start all the running childs along with the > parent > -- > > Key: GERONIMO-5265 > URL: https://issues.apache.org/jira/browse/GERONIMO-5265 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.1.5, 2.2.1, 3.0 > Environment: geronimo tomcat assembly >Reporter: Ashish Jain >Assignee: Ashish Jain > Fix For: 2.2.2, 3.0 > > Attachments: 5265_21.patch > > > Kindly refer the discussion thread > http://n3.nabble.com/Modify-the-redeploy-behaviour-td739706.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5331) Connection refused excpetion in ActiveMQ Pure Master/Slave
[ https://issues.apache.org/jira/browse/GERONIMO-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871516#action_12871516 ] Shawn Jiang commented on GERONIMO-5331: --- Have you ever tried activemq itself ? I just want to make sure it's not a environment problem. > Connection refused excpetion in ActiveMQ Pure Master/Slave > --- > > Key: GERONIMO-5331 > URL: https://issues.apache.org/jira/browse/GERONIMO-5331 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2.1 > Environment: Windows 2003 Sp2 > JDk: sun jdk 1.5.22 >Reporter: viola.lu > Fix For: 2.2.1 > > Attachments: PureMasterSlave.zip > > > 1. Refer to http://activemq.apache.org/pure-master-slave.html setup pure > master/slave, and sample master/slave configuration file from activemq source > : > http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/broker/ft/slave.xml, > master.xml > 2. Setup master activemq, change var/activemq/conf/activemq.xml as > attachement master.xml under geronimo install directory > 3.Setup slave activemq in the same box as master. change > var/activemq/conf/activemq.xml as attachement slave.xml under anohter > geronimo install directory.change var/config/config-substitutions.properties > portoffset attribute to 1 as attached config-substitutions_slave.properties > 4. Startup master/slave geronimo, but connection refused when starting > activemq module as below: > 2010-05-21 15:39:45,593 ERROR [RecoveryController] Recovery error > javax.transaction.SystemException: Could not obtain recovery XAResource for > managedConnectionFactory > org.apache.activemq.ra.activemqmanagedconnectionfact...@450c8891 > at > org.apache.geronimo.connector.outbound.AbstractConnectionManager.doRecovery(AbstractConnectionManager.java:74) > at > org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapper.doStart(ManagedConnectionFactoryWrapper.java:164) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:953) > 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:525) > 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:295) > 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:539) > 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.KernelConfigurationManager.start(KernelConfigurationManager.java:190) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) > at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:592) > 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:816) > 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.ker
[jira] Updated: (GERONIMO-5198) MultiParentClassLoader caching not found resources
[ https://issues.apache.org/jira/browse/GERONIMO-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-5198: -- Fix Version/s: 2.2.2 (was: 2.2.1) won't fix this in 221 release. > MultiParentClassLoader caching not found resources > -- > > Key: GERONIMO-5198 > URL: https://issues.apache.org/jira/browse/GERONIMO-5198 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 > Environment: Linux 64 bit >Reporter: Marco Laponder > Fix For: 2.2.2 > > > We have extended the default classpath with a directory by specifying in the > deployment plan an org.apache.geronimo.system.sharedlib.SharedLib gbean. So > we are able to read application specific files from this directory. > It is possbile for out application the resource can not be found at a given > time, but the resource exists at a later time because it has been added to > the directory. However when geronimo doesn't find the resource its add its > name to the 'resourcesNotFound' map in the MultiParentClassLoader.java:571 in > the 2.2 branch. > The result of this caching is that we cannot find the resource after it has > been placed in the direcotry. Would it be possible to configure this > behaviour, clear the not found cache or is there an other solution to this > problem ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4898) can't install app-per-port sample using deploy/install-plugin command
[ https://issues.apache.org/jira/browse/GERONIMO-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-4898. -- Resolution: Invalid Now i install app-per-port sample and then export it as plugin , uninstall sample from console, then run gshell command: deploy/install-plugin /download/app-port*.car, then it can be installed. But if i used http://geronimo.apache.org/plugins/samples-2.2.1/ sample plugin to isntall this plugin, there will be errors, so i will open another jira to track this sample plugin url problem. So close this one. > can't install app-per-port sample using deploy/install-plugin command > - > > Key: GERONIMO-4898 > URL: https://issues.apache.org/jira/browse/GERONIMO-4898 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: sample apps >Affects Versions: 2.2 > Environment: windows xp sp2 > jdk 6 >Reporter: Bin He >Priority: Minor > Fix For: 2.2.1 > > > 2009-09-28 16:44:53,000 WARN [PluginInstallerGBean] Invalid repository: > ~/.m2/repository/ > java.lang.IllegalStateException: Maven2Repository must have a root that's a > valid readable directory (not C:\Documents and > Settings\Administrator\.m2\repository) > at > org.apache.geronimo.kernel.repository.AbstractRepository.(AbstractRepository.java:66) > at > org.apache.geronimo.kernel.repository.Maven2Repository.(Maven2Repository.java:32) > at > org.apache.geronimo.system.plugin.LocalSourceRepository.(LocalSourceRepository.java:46) > at > org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:218) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.addRepos(PluginInstallerGBean.java:857) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.getRepos(PluginInstallerGBean.java:845) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:772) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:1017) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean$4.run(PluginInstallerGBean.java:923) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > 2009-09-28 16:44:53,000 WARN [PluginInstallerGBean] Invalid repository: > ~/.m2/repository/ > java.lang.IllegalStateException: Maven2Repository must have a root that's a > valid readable directory (not C:\Documents and > Settings\Administrator\.m2\repository) > at > org.apache.geronimo.kernel.repository.AbstractRepository.(AbstractRepository.java:66) > at > org.apache.geronimo.kernel.repository.Maven2Repository.(Maven2Repository.java:32) > at > org.apache.geronimo.system.plugin.LocalSourceRepository.(LocalSourceRepository.java:46) > at > org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getSourceRepository(PluginRepositoryDownloader.java:218) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.addRepos(PluginInstallerGBean.java:857) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.getRepos(PluginInstallerGBean.java:849) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:772) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean.install(PluginInstallerGBean.java:1017) > at > org.apache.geronimo.system.plugin.PluginInstallerGBean$4.run(PluginInstallerGBean.java:923) > at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214) > at > org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > 2009-09-28 16:44:53,093 INFO [StandardService] This service has already been > initialized > 2009-09-28 16:44:53,093 INFO [StandardService] Starting service null > 2009-09-28 16:44:53,109 INFO [StandardService] Starting service null > 2009-09-28 16:44:53,109 INFO [StandardService] This service has already been > initialized > 2009-09-28 16:44:53,109 INFO [StandardService] Starting service null > 2009-09-28 16:44:53,125 INFO [StandardService] Starting service null > 2009-09
[jira] Created: (GERONIMO-5348) Fail to install plugin from Geronimo2.2.1 Sample Plugin URL
Fail to install plugin from Geronimo2.2.1 Sample Plugin URL --- Key: GERONIMO-5348 URL: https://issues.apache.org/jira/browse/GERONIMO-5348 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Plugins Affects Versions: 2.2.1 Environment: Suse 1- Sp2 Reporter: viola.lu 1. Go to admin console "Plugin" porlet ->Add Geronimo2.2.1 Sample Plugin URL http://geronimo.apache.org/plugins/samples-2.2.1/ to repository url list 2.List all plugins from this repository, choose any one sample plugin you would like to install 3. But ther will errors: A problem has occured: java.lang.IllegalArgumentException: Could not find org.apache.geronimo.samples/calculator-tomcat/2.2.1-SNAPSHOT/car in any repo: [org.apache.geronimo.system.plugin.RemoteSourceRepository:http://geronimo.apache.org/plugins/samples-2.2.1/, org.apache.geronimo.system.plugin.RemoteSourceRepository:http://repo1.maven.org/maven2/, org.apache.geronimo.system.plugin.RemoteSourceRepository:http://people.apache.org/repo/m2-snapshot-repository/, org.apache.geronimo.system.plugin.RemoteSourceRepository:http://people.apache.org/repo/m2-incubating-repository/] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5010) Transport confifential not working, 403 instead of 302 HTTP headers returned
[ https://issues.apache.org/jira/browse/GERONIMO-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMO-5010. - Resolution: Fixed Redirect it to secure port in revision #948344. > Transport confifential not working, 403 instead of 302 HTTP headers returned > > > Key: GERONIMO-5010 > URL: https://issues.apache.org/jira/browse/GERONIMO-5010 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2 > Environment: G 2.2 with Tomcat 6, running on Windows XP with Java 6 >Reporter: Łukasz Budnik >Assignee: Delos Dai >Priority: Blocker > Fix For: 2.2.1 > > > I found it out by accident I was migrating Web Service which uses > CONFIDENTIAL transport layer security. > By looking at the tcpmon I found out that POST request weren't forwarded to > HTTPS and was served using plain HTTP. > The quickest way to reproduce this error: > http://localhost:8080/console/secure > Instead of being brought to https schema (followed by HTTP 302), the result > is: HTTP 403 error. > It was all working in G 2.1.x. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
